name: style-standards
type: standard
depth: extended
description: Enforces style consistency for documentation and code with support for taxonomy, voice, and formatting domains. Use when creating or modifying files requiring: (1) markdown structure (headers, lists, tables, Dictums, separators), (2) code organization (comments, section dividers, naming conventions), (3) voice compliance (tone, grammar, imperative phrasing), or (4) formatting validation against project standards.
[H1][STYLE-STANDARDS]
Dictum: Style consistency maximizes agent comprehension.
Govern file creation and modification in monorepo.
Tasks:
- Read index.md — Reference file listing for navigation
- Read keywords.md — Canonical keyword list; all Markers use official terms
- (taxonomy) Read taxonomy.md — Lexicon, references, stati definitions
- (voice) Read voice.md — Grammar, ordering, comments, constraints, naming, density
- (formatting) Read formatting.md — Structure, typeset, spacing, examples
- Apply standards — Implement per domain Guidance and Best-Practices
- Validate — Quality gate; see §VALIDATION
Scope:
- Documentation: Markdown structure, headers, lists, tables, Dictums, separators.
- Code: Comments, headers, section dividers, naming conventions, file organization.
Domain Navigation:
- [TAXONOMY] — Terms, markers, cross-references. Load for: sigils, stati, lexicon definitions.
- [VOICE] — Tone, grammar, comments, naming. Load for: imperative phrasing, headers, code naming.
- [FORMATTING] — Layout, separators, spacing. Load for: header structure, dividers, whitespace rules.
[REFERENCE]: index.md — Reference file listing
[1][TAXONOMY]
Dictum: Vocabulary anchors structure; Markers encode state.
Signals intent for agent execution. Leverage terms for document traversal.
Guidance:
Dictum - Read Dictum + headers first—rapid file mapping.Qualifier - [ALWAYS] respect inline directives when encountered.Preamble - Signals section-wide imperative.Terminus - Signals task-specific imperative; isolated effect.Corpus - Read after Preamble/Terminus orientation.Gate - [CRITICAL] Finalize checklist items prior to proceeding; use [VERIFY] for Gate checklists.Directive - Lists require strict adherence; polarity set by Modifier.Stati - Replace emoji.
Best-Practices:
- Markers: Hard limit: 10 per file. Strategic placement maximizes compliance.
- Preamble/Terminus - 0–4 markers per file maximum.
[REFERENCE]: →taxonomy.md — Lexicon, references, stati
[2][VOICE]
Dictum: Universal standards for LLM-optimized context, documentation, and agentic instructions.
Applies to documentation and comments. Scope: tone, list semantics, ordering primacy, grammar, syntax, modals, visuals, comment standards, keywords.
Guidance:
Voice - Active voice: 56% token reduction.Tone - Mechanical, domain-specific. No hedging, no self-reference.Syntax - Simple sentences: 93.7% accuracy vs 46.8% nested.Punctuation - Attention sinks—absorb 20-40% weight despite minimal semantic content.Ordering - [CRITICAL] Primacy effects peak at 150-200 instructions; 5.79× attention for early items.
- Critical-First - Highest-priority constraints at sequence start.
- Middle Burial - Middle positions suffer U-shaped attention loss.
Comments - Front-load architectural decisions where attention peaks.Density - Tables: >2 entities, >2 dimensions. Diagrams: >3 steps or >2 hierarchy levels.
Best-Practices:
- Comments - Incorrect: 78% accuracy loss—omit if uncertain. Why > What: intent = signal, logic = noise.
- Constraints - 6+ simultaneous: <25% satisfaction. Max 3-5 per level.
- Delimiters - Consistency over choice. 18-29% variance per change.
- Stopwords - Remove
the, a, an, please, kindly.
- Tone - Actions: imperative. Context/facts: declarative.
- Naming - Prohibited:
utils, helpers, misc, config, cfg, opts, params, Data, Info, Manager, Service.
[REFERENCE]: →voice.md — Grammar, ordering, comments, constraints, naming, density
[3][FORMATTING]
Dictum: Whitespace and separator rules for document structure.
Separators encode hierarchy. Whitespace: semantic, not cosmetic. Patterns enable rapid reference.
Guidance:
Dictum - Place first after H1/H2. State WHY, not WHAT. Format: >**Dictum:** *statement*Depth - H1: File Truth. H2: Smallest agent read unit. H3: Nesting limit. [CRITICAL] H4+ requires new file.Lists - Use numbered 1. for sequence/priority. Use bullet - for equivalence/sets.Labels - Format parent: **Bold:** with colon. Format child: *Italic:* for contrast.Separators - Use --- for hard boundaries (H2 → H2, H3 → H3). Use <br> for soft transitions (H2 → H3).Spacing - Place 1 blank after header. Place none after ---. Place none between list items.Dividers - Pad code separators // --- [LABEL] --- to column 80.Tables - Include [INDEX] first column. Format headers as [HEADER] sigil. Align: center index, right numeric, left prose.
Best-Practices:
- Separator Prohibitions -
--- between H2 and first H3 prohibited. <br> between sibling H3s prohibited.
- List Prohibitions - Single-item lists prohibited—use prose. Bullet
- only; */+ prohibited. Parallel grammar required.
- Header Integrity - Level skipping prohibited. H1 → H2 → H3 strictly sequential.
- Thresholds - Lists: 2-7 items. Items: <100 chars. Nesting: 2 levels max.
- Sigils - UPPERCASE, max 3 words, underscores for compound. Exception:
.claude/ infrastructure (skills, commands, agents) use hyphens matching file/folder name.
- Soft Breaks -
<br> required after Dictum and Preamble. Groups 2-3 related definitions inline.
- Case Taxonomy - UPPERCASE: sigils, rubrics, keywords, section labels. Title Case: table cells. kebab-case: files.
- Directive Ordering -
[IMPORTANT]: precedes [CRITICAL]:. Within list: [ALWAYS] precedes [NEVER].
- Table Styling - First column bold for category anchoring.
[REFERENCE]: →formatting.md — Structure, typeset, spacing, example
[4][VALIDATION]
Dictum: Gates prevent non-compliant output.
[VERIFY] Completion:
[REFERENCE] Operational checklist: →validation.md
1---2name: style-standards3description: Enforces style consistency for documentation and code with support for taxonomy, voice, and formatting domains. Use when creating or modifying files requiring: (1) markdown structure (headers, lists,4---5
6---
7name: style-standards
8type: standard
9depth: extended
10description: Enforces style consistency for documentation and code with support for taxonomy, voice, and formatting domains. Use when creating or modifying files requiring: (1) markdown structure (headers, lists, tables, Dictums, separators), (2) code organization (comments, section dividers, naming conventions), (3) voice compliance (tone, grammar, imperative phrasing), or (4) formatting validation against project standards.
11---
12
13# [H1][STYLE-STANDARDS]
14>**Dictum:** *Style consistency maximizes agent comprehension.*
15
16<br>
17
18Govern file creation and modification in monorepo.
19
20**Tasks:**
211. Read [index.md](./index.md) — Reference file listing for navigation
222. Read [keywords.md](./references/keywords.md) — Canonical keyword list; all Markers use official terms
233. (taxonomy) Read [taxonomy.md](./references/taxonomy.md) — Lexicon, references, stati definitions
244. (voice) Read [voice.md](./references/voice.md) — Grammar, ordering, comments, constraints, naming, density
255. (formatting) Read [formatting.md](./references/formatting.md) — Structure, typeset, spacing, examples
266. Apply standards — Implement per domain Guidance and Best-Practices
277. Validate — Quality gate; see §VALIDATION
28
29**Scope:**
30- *Documentation:* Markdown structure, headers, lists, tables, Dictums, separators.
31- *Code:* Comments, headers, section dividers, naming conventions, file organization.
32
33**Domain Navigation:**
34- *[TAXONOMY]* — Terms, markers, cross-references. Load for: sigils, stati, lexicon definitions.
35- *[VOICE]* — Tone, grammar, comments, naming. Load for: imperative phrasing, headers, code naming.
36- *[FORMATTING]* — Layout, separators, spacing. Load for: header structure, dividers, whitespace rules.
37
38[REFERENCE]: [index.md](./index.md) — Reference file listing
39
40---
41## [1][TAXONOMY]
42>**Dictum:** *Vocabulary anchors structure; Markers encode state.*
43
44<br>
45
46Signals intent for agent execution. Leverage terms for document traversal.
47
48**Guidance:**<br>
49- `Dictum` - Read `Dictum` + headers first—rapid file mapping.
50- `Qualifier` - [ALWAYS] respect inline directives when encountered.
51- `Preamble` - Signals **section-wide** imperative.
52- `Terminus` - Signals **task-specific** imperative; **isolated** effect.
53- `Corpus` - Read after `Preamble`/`Terminus` orientation.
54- `Gate` - [CRITICAL] Finalize checklist items prior to proceeding; use `[VERIFY]` for `Gate` checklists.
55- `Directive` - Lists require strict adherence; polarity set by `Modifier`.
56- `Stati` - Replace emoji.
57
58**Best-Practices:**<br>
59- **Markers:** Hard limit: **10 per file**. Strategic placement maximizes compliance.
60 - *Preamble/Terminus* - 0–4 markers per file maximum.
61
62[REFERENCE]: [→taxonomy.md](./references/taxonomy.md) — Lexicon, references, stati
63
64---
65## [2][VOICE]
66>**Dictum:** *Universal standards for LLM-optimized context, documentation, and agentic instructions.*
67
68<br>
69
70Applies to documentation and comments. Scope: tone, list semantics, ordering primacy, grammar, syntax, modals, visuals, comment standards, keywords.
71
72**Guidance:**<br>
73- `Voice` - Active voice: 56% token reduction.
74- `Tone` - Mechanical, domain-specific. No hedging, no self-reference.
75- `Syntax` - Simple sentences: 93.7% accuracy vs 46.8% nested.
76- `Punctuation` - Attention sinks—absorb 20-40% weight despite minimal semantic content.
77- `Ordering` - [CRITICAL] Primacy effects peak at 150-200 instructions; 5.79× attention for early items.
78 - **Critical-First** - Highest-priority constraints at sequence start.
79 - **Middle Burial** - Middle positions suffer U-shaped attention loss.
80- `Comments` - Front-load architectural decisions where attention peaks.
81- `Density` - Tables: >2 entities, >2 dimensions. Diagrams: >3 steps or >2 hierarchy levels.
82
83**Best-Practices:**<br>
84- **Comments** - Incorrect: 78% accuracy loss—omit if uncertain. *Why > What*: intent = signal, logic = noise.
85- **Constraints** - 6+ simultaneous: <25% satisfaction. Max 3-5 per level.
86- **Delimiters** - Consistency over choice. 18-29% variance per change.
87- **Stopwords** - Remove `the`, `a`, `an`, `please`, `kindly`.
88- **Tone** - Actions: imperative. Context/facts: declarative.
89- **Naming** - Prohibited: `utils`, `helpers`, `misc`, `config`, `cfg`, `opts`, `params`, `Data`, `Info`, `Manager`, `Service`.
90
91[REFERENCE]: [→voice.md](./references/voice.md) — Grammar, ordering, comments, constraints, naming, density
92
93---
94## [3][FORMATTING]
95>**Dictum:** *Whitespace and separator rules for document structure.*
96
97<br>
98
99Separators encode hierarchy. Whitespace: semantic, not cosmetic. Patterns enable rapid reference.
100
101**Guidance:**<br>
102- `Dictum` - Place first after H1/H2. State WHY, not WHAT. Format: `>**Dictum:** *statement*`
103- `Depth` - H1: File Truth. H2: Smallest agent read unit. H3: Nesting limit. [CRITICAL] H4+ requires new file.
104- `Lists` - Use numbered `1.` for sequence/priority. Use bullet `-` for equivalence/sets.
105- `Labels` - Format parent: `**Bold:**` with colon. Format child: `*Italic:*` for contrast.
106- `Separators` - Use `---` for hard boundaries (H2 → H2, H3 → H3). Use `<br>` for soft transitions (H2 → H3).
107- `Spacing` - Place 1 blank after header. Place none after `---`. Place none between list items.
108- `Dividers` - Pad code separators `// --- [LABEL] ---` to column 80.
109- `Tables` - Include `[INDEX]` first column. Format headers as `[HEADER]` sigil. Align: center index, right numeric, left prose.
110
111**Best-Practices:**<br>
112- **Separator Prohibitions** - `---` between H2 and first H3 prohibited. `<br>` between sibling H3s prohibited.
113- **List Prohibitions** - Single-item lists prohibited—use prose. Bullet `-` only; `*`/`+` prohibited. Parallel grammar required.
114- **Header Integrity** - Level skipping prohibited. H1 → H2 → H3 strictly sequential.
115- **Thresholds** - Lists: 2-7 items. Items: <100 chars. Nesting: 2 levels max.
116- **Sigils** - UPPERCASE, max 3 words, underscores for compound. Exception: `.claude/` infrastructure (skills, commands, agents) use hyphens matching file/folder name.
117- **Soft Breaks** - `<br>` required after Dictum and Preamble. Groups 2-3 related definitions inline.
118- **Case Taxonomy** - UPPERCASE: sigils, rubrics, keywords, section labels. Title Case: table cells. kebab-case: files.
119- **Directive Ordering** - `[IMPORTANT]:` precedes `[CRITICAL]:`. Within list: `[ALWAYS]` precedes `[NEVER]`.
120- **Table Styling** - First column bold for category anchoring.
121
122[REFERENCE]: [→formatting.md](./references/formatting.md) — Structure, typeset, spacing, example
123
124---
125## [4][VALIDATION]
126>**Dictum:** *Gates prevent non-compliant output.*
127
128<br>
129
130[VERIFY] Completion:
131- [ ] Structure: Nesting ≤H3, critical constraints at sequence start.
132- [ ] Voice: Active voice, no stopwords, no hedging, no self-reference.
133- [ ] Formatting: Separators correct, spacing rules applied.
134- [ ] Consistency: All markers use canonical keywords.
135
136[REFERENCE] Operational checklist: [→validation.md](./references/validation.md)
majiayu000