AGENTS.md

1# StyleSeed repository guide
2 
3StyleSeed is an AI design-method engine for coding agents. It combines fixed judgment,
4job-specific output grammars, surface adapters, and project-local reference grammars. Keep the
5rules, skills, components, skins, and generated demo artifacts in sync.
6 
7## Before changing the engine
8 
9- Read `engine/AGENTS.md` for the cross-agent design rules.
10- Read the relevant nested guide before editing its subtree. In particular,
11  `demo-pricing/AGENTS.md` applies to the Next.js demo.
12- Read `engine/PRODUCT-PRINCIPLES.md`, `engine/RULESETS.md`, `engine/ADAPTERS.md`,
13  `engine/BRAND-RECIPES.md`, and
14  `engine/ARCHITECTURE.md` before changing product behavior.
15- Treat `engine/.claude/skills/` as the canonical source for all 21 StyleSeed
16  skills. `.agents/skills` is a repository-scoped Codex symlink to that same
17  directory; never create a second copy of a skill there.
18- Claude Code invokes a skill as `/ss-setup`, `/ss-build`, and so on. Codex
19  invokes it as `$ss-setup`, `$ss-build`, or from its Skills picker.
20 
21## Generated files
22 
23`demo-pricing/scripts/build-llms.mjs` regenerates the public agent index,
24registry, context catalog, skin bundle, engine mirrors, and `llms.txt`/`llms-full.txt`. Edit the source in
25`engine/` or `skins/`, then run the generator; do not hand-edit generated
26copies as the source of truth.
27 
28## Verification
29 
30- Every engine change: run `node scripts/validate-engine.mjs` and `git diff --check`.
31- Engine, skin, component, registry, or demo changes: run `npm run build` from
32  `demo-pricing/`, then run `git diff --check` from the repository root.
33- The demo build fetches Google Fonts and may require network access.
34- Do not claim a visual pass without rendering and inspecting the affected UI.
35 
36## Pull requests and releases
37 
38- Keep unrelated design-canon changes, tooling changes, and compatibility work
39  in separate commits or pull requests.
40- Do not change `engine/VERSION`, the changelog, or publish a release unless the
41  maintainer explicitly includes release work in the task.
42