Skip to content

Commit 8accc29

Browse files
committed
init
1 parent a72bc0c commit 8accc29

File tree

1 file changed

+59
-0
lines changed

1 file changed

+59
-0
lines changed

.cursor/rules/style-guide.mdc

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
description: style guide
3+
globs: docs/source/en/**/*.md
4+
alwaysApply: false
5+
---
6+
7+
## Sentence structure
8+
- Write short, declarative sentences most of the time.
9+
- Vary sentence length to avoid sounding robotic. Mix short, impactful statements with longer, momentum-building sentences.
10+
- Every time you use a comma, ask whether you can use a period instead.
11+
- Avoid repeating the same words in a paragraph. Use synonyms or rephrase.
12+
13+
## Voice and tone
14+
- Write like humans speak. Avoid corporate jargon and marketing fluff.
15+
- Be confident and direct. Avoid softening phrases like "I think", "maybe", or "could".
16+
- Use active voice instead of passive voice.
17+
- Use positive phrasing - say what something *is* rather than what is *isn't*.
18+
- Say "you" more than "we" when addressing external audiences.
19+
- Use contractions like "I'll", "won't", and "can't" for a warmer tone.
20+
21+
## Specificity and evidence
22+
- Be specific with facts and data instead of vague superlatives.
23+
- Back up claims with concrete examples or metrics.
24+
- Highlight customers and community members over company achievements.
25+
- Use realistic, product-based examples instead of `foo/bar/baz` in code.
26+
- Make content concrete, visual, and falsifiable.
27+
28+
## Title creation
29+
- Make a promise in the title so readers know exactly what they'll get if they click.
30+
- Tap into controversial points your audience holds and back them up with data (use wisely, avoid clickbait).
31+
- Share something uniquely helpful that makes readers better at meaningful aspects of their lives.
32+
- Avoid vague titles like "My Thoughts on XYZ". Titles should be opinions or shareable facts.
33+
- Write placeholder titles first, complete the content, then spend time iterating on titles at the end.
34+
35+
## Ban phrases
36+
- Avoid using "You can"
37+
38+
## Avoid LLM patterns
39+
- Replace em dashes (-) with semicolons, commas, or sentence breaks.
40+
- Avoid starting responses with "Great question!", "You're right!", or "Let me help you."
41+
- Don't use phrases like "Let's dive into..."
42+
- Skip cliché intros like "In today's fast-paced digital world" or "In the ever-evolving landscape of"
43+
- Avoid phrases like "it's not just [x], it's [y]"
44+
- Don't use high-school essay closers: "In conclusion,", "Overall,", or "To summarize"
45+
- Avoid numbered lists in cases where bullets work better.
46+
- Replace "In conclusion" with direct statements.
47+
- Avoid hedge words: "might", "perhaps", "potentially" unless uncertainty is real.
48+
- Don't stack hedging phrases: "may potentially", "it's important to note that".
49+
- Don't create perfectly symmetrical paragraphs or lists that start with "Firstly... Secondly..."
50+
- Avoid title-case headings: prefer sentence casing.
51+
- Remove Unicode artifacts when copy-pasting: smart quotes ("), em-dashes, non-breaking spaces.
52+
- Use '
53+
- Delete empty citation placeholders like "[1]" with no actual source
54+
55+
## Punctuation and formatting
56+
- Use Oxford commas consistently
57+
- Use exclamation points sparingly
58+
- Sentences can start with "But" and "And" but don't overuse
59+
- Use periods instead of commas when possible for clarity

0 commit comments

Comments
 (0)