Coding standards
Layered rules the agent reads before it edits a file.
Chapter 1
Three layers, read top down
Universal rules first, then the file's role, then the framework.
What each layer holds
Layer 1 is the global law for a discipline and applies to every file of that type, for example RULE 14 in the CSS standard: no !important, anywhere. Fix the selector instead.
Layer 2 is the file-type rules, one partial per role, for example RULE T-05 for token files: semantic colours reference the palette and are never hardcoded.
Layer 3 is the framework layer. It extends a universal rule or overrides it with an explicit note, for example RULE SC-05 in the Strata CSS file: no !-prefixed variants.
Chapter 2
A rule you can check
Rules are declarative and testable, with a wrong and a right example wherever one could be misread.
Overrides and conflicts
A framework file that overrides a universal rule must say so: OVERRIDES [filename] RULE [number], then the reason. A rule that only adds detail needs no note.
No rule may conflict with another at the same layer. Conflicts between layers use the override note.
A project uses exactly one script standard: JavaScript only, TypeScript only, or both together. Each is standalone.
Shelf 1 of 7
The files you write
CSS, HTML and scripts, each with partials per file role.
CSS · 23 rules
Global CSS laws, with partials for token, layout, component, overlay and utility files.
HTML · 10 rules
Global markup laws, with partials for layout templates, page files and component markup.
TypeScript · 16 rules
For projects that use TypeScript only. Partials cover entry scripts, classes, controllers, presets, utilities and type files.
JavaScript · 11 rules
For projects that use JavaScript only. A third standard of 16 rules covers JS and TS used together.
Shelf 2 of 7
How the work is tracked
Commits, branches and versions.
Git · 12 rules
Commit, branch and pull request conventions.
Versioning · 9 rules
Package and changelog versioning.
Shelf 3 of 7
Who can find and use it
Search, speed and access.
SEO · 12 rules
Titles, meta, structure and schema.
Performance · 15 rules
Assets, scripts, CSS and Core Web Vitals.
Accessibility · 24 rules
WCAG 2.2 AA, keyboard use, ARIA, contrast, focus not obscured, drag alternatives and 24 px targets.
Shelf 4 of 7
What to make and how to behave
Design taste and the AI's own conduct.
Design · 15 rules
What to make: Floor, Reflex and Finish rules against generated-looking UI.
AI · 19 rules
AI behaviour: hallucination detection and token efficiency.
Shelf 5 of 7
Quality assurance
An umbrella of six concerns rather than one file.
Definition of done
What done means for any task, and the self-QA pass.
Branch gates
What must be true before work moves from dev to test to beta to main.
Logic and error checks
Code-path tracing, async errors, null checks and state coverage.
Security checks
XSS, secrets, eval, CSP, dependency risk and the rest of the OWASP-adjacent checks.
End-to-end testing
Playwright fixture and page-object discipline, when specs are written and how they stay current.
Bug reporting
The standard format and severity levels for anything the AI finds.
Shelf 6 of 7
Frameworks and tooling
Layer 3, plus the lint configs that enforce what can be checked.
Astro · 6 rules
Astro-specific additions and overrides.
Bootstrap
Bootstrap conflicts, violations and workarounds.
Strata CSS · 11 rules
Mandatory utility-first framework, with coverage discipline.
Tooling
Machine enforcement: lint configs for the rules that can be checked by a tool.
Shelf 7 of 7
UI elements and company rules
What the file-type rules do not cover, and rules a company brings itself.
UI standards
A routing table plus 30 compact partials (button, fields, modal, table, header, sidebar, charts, theming, landing, mobile and more). They cover empty and error states, validation, pagination, upload and export security and sign-in. A UI edit reads at most two.
Company standards
A separate coding-standards/company/ folder for a company's own rules. install-kit.cli.js company sync scans it, writes a routing INDEX.md and a company-standards skill, and where a company rule and a kit default disagree, the company rule wins.
Project signature
One alias you choose at install, used in exactly three places: abc- classes and ids, data-abc- attributes and Abc shared components. Never applied to package or framework names.
Finale
Not sure which one?
Start from the situation.
You are writing or editing CSS
css-standardsYou are about to write a commit message
git-standardsYou are writing a page title and meta description
seo-standardsYou are checking keyboard use and contrast
accessibility-standardsYou are building a new UI from scratch
design-standards
Keep reading
On to the next page
The docs are a short run of pages. Use the buttons, or jump to any page.