Cline rules
.clinerules/writing-style.mdCline rules
Quality
88/100
Scores the file, not the repository.Length
581 words
26 headings · 4 code blocksRepository
0
— · pushed 5 days agoLast changed
2 days ago
First indexed 2 days ago.1# Writing Style Rules23## Voice and Tone4- Professional but accessible, narrative-driven with technical depth5- Use conversational elements and real-world examples to make technical concepts relatable6- Maintain authoritative voice while being approachable78## Content Structure Pattern91. **Introduction**: Compelling hook/scenario with context and preview of what reader will learn102. **Historical Context**: Evolution and background of the topic113. **Technical Deep Dive**: Detailed analysis with code/architecture examples124. **Practical Applications**: Real-world implications and use cases135. **Future Outlook**: Forward-looking analysis and predictions1415## British English Standards (CRITICAL)16**ALL content MUST use British English spellings exclusively.**1718### Common -ise/-isation endings (NOT -ize/-ization)19- organise, organisation, recognise, realise, specialise20- optimise, optimisation, customise, customisation21- analyse, utilise, summarise, categorise, materialise, digitise2223### -our endings (NOT -or)24- behaviour, colour, honour, favour, labour, humour, rigour, vigour25- harbour, flavour, endeavour2627### -re endings (NOT -er)28- centre, theatre, metre, litre, fibre, calibre2930### -ce endings for nouns (NOT -se)31- licence (noun), defence, offence, practice (noun)32- **Note**: license/practise are verbs; licence/practice are nouns3334### Other Important British Spellings35- analogue (NOT analog), catalogue, dialogue, grey (NOT gray)36- tyre (NOT tire), focussed (NOT focused), travelled (NOT traveled)3738### Pre-Publication Verification39Before publishing, search for and correct these American spellings:40- Words ending in -ize, -ization41- Words ending in -or when should be -our42- Words ending in -er when should be -re43- Common words: center, defense, license (noun), realize, organize, analyze, optimise4445## File Structure Reference46```47_posts/48 └── YYYY/49 ├── YYYY-MM-DD-post-slug.md # Blog posts by year50 └── YYYY-MM-DD-another-post.md51_pages/52 ├── about.md53 ├── categories.md54 ├── disclaimer.md55 ├── posts.md56 └── tags.md57_data/58 └── navigation.yml59_includes/60 └── head/61 └── custom.html62assets/63 ├── css/64 │ └── main.scss65 └── images/66_config.yml # Main site configuration67Gemfile # Ruby dependencies68```6970## Local Development Commands71```bash72# Install dependencies73bundle install7475# Serve locally with live reload76bundle exec jekyll serve7778# Serve with drafts (for preview)79bundle exec jekyll serve --drafts8081# Build site for production82bundle exec jekyll build8384# Clean generated files85bundle exec jekyll clean86```8788## Development Workflow891. Make changes to posts or configuration902. Test locally with `bundle exec jekyll serve`913. Review changes at `http://localhost:4000`924. Commit and push to trigger automatic deployment9394## Deployment Process951. **Local Development**: Test changes locally962. **Git Push**: Push to main branch973. **GitHub Actions**: Automatic build and deployment984. **GitHub Pages**: Site updated at jonbeckett.github.io99100## Common Technical Issues101102### Build Failures103- Check for YAML syntax errors in front matter104- Ensure all required front matter fields are present105- Verify Markdown syntax is correct106- Check for broken image URLs107108### Archive Configuration109- Never change archive type from `liquid` to `jekyll-archives`110- This will break all category and tag links site-wide111- GitHub Pages has limited plugin support112113## QUICK REFERENCE114115### Essential File Patterns116```117_posts/YYYY/YYYY-MM-DD-slug-title.md # Blog posts118_pages/*.md # Static pages119_config.yml # Site configuration120_data/navigation.yml # Navigation menu121```122123### Core Front Matter (Minimal)124```yaml125---126title: "Main Title: Subtitle"127layout: single128date: YYYY-MM-DD129categories: [primary-category]130tags: [tag1, tag2, tag3]131excerpt: "Compelling one-sentence description"132---133```134135### Critical Reminders136- **British English spellings exclusively** (organise, colour, centre, optimise)137- **Target length**: 2,000-5,000+ words138- **Content structure**: Hook → History → Technical → Applications → Future139- **Archive type**: Must use `liquid` NOT `jekyll-archives` (GitHub Pages limitation)140- **Layout**: Always `single` for blog posts141- **Unsplash images**: Always include photographer attribution
Also in jonbeckett/jonbeckett.github.io
Diff this repo’s formatsOne repository carrying more than one format is the comparison this product exists for: does anyone actually write different content in each file, or is one a copy of the other?
| Repository | Format | Stack | Covers | Score | Changed |
|---|---|---|---|---|---|
| jonbeckett/jonbeckett.github.io.clinerules/README.md · 0 | Cline rules | archdo-not | 36/100 | 2 days ago | |
| jonbeckett/jonbeckett.github.io.clinerules/content-creation.md · 0 | Cline rules | styledo-not | 73/100 | 2 days ago | |
| jonbeckett/jonbeckett.github.io.clinerules/project-overview.md · 0 | Cline rules | archtypessecuritydo-not | 55/100 | 2 days ago |
Similar configs
Same format, overlapping stack, ranked by quality.
| Repository | Format | Stack | Covers | Score | Changed |
|---|---|---|---|---|---|
| jonbeckett/jonbeckett.github.io.clinerules/content-creation.md · 0 | Cline rules | styledo-not | 73/100 | 2 days ago | |
| dev-ai-kar/vaibhavdeokar-portfolio.clinerules/project-context.md · 0 | Cline rules | stylegitdocs | 61/100 | 3 days ago | |
| jonbeckett/jonbeckett.github.io.clinerules/project-overview.md · 0 | Cline rules | archtypessecuritydo-not | 55/100 | 2 days ago | |
| jonbeckett/jonbeckett.github.io.clinerules/README.md · 0 | Cline rules | archdo-not | 36/100 | 2 days ago |
