-
- docs-04 template: remove § 2.5 样式与主题 (tokens live in src/styles/tokens.css) + § 3.5 配置与安全 (config in config-vars.yaml, rules in docs/07→now config-vars header) - styles-tokens-template.css: fix 3 stale docs/06 refs missed in the earlier docs/06 removal (greps had excluded *.css) → self-contained '色值单一来源 / SSoT' - coding.mjs: frontend ref §一 前端架构 → §二 前端规范 (§一 is 后端); backend drop frontend §2.1 → §1.2 分层; 样式/色值 → tokens.css; remove docs/07 from value-lookup order
-
docs-06-static-template.md actually defines § 二 Design Tokens with subsections 2.1 / 2.2 / 2.3. The CSS template comments still cited the pre-renumber § 四 / § 4.1 / § 4.2, so downstream-generated tokens.css files pointed readers to non-existent sections of docs/06.
-
Visual clarity: the file tree now matches the README's phase model. - skills/plan/ — 8 skills (plan-start entry + A0~A6) - skills/coding/ — 1 skill (coding-start thin entry) Slugs unchanged. /erp-workflow:<name> still resolves identically because each SKILL.md declares its own `name:` frontmatter (verified for all 9). Plugin loader treats the default `./skills/` scan as flat, so the nested layout is opted into via an explicit path array in plugin.json — the only mechanism Claude Code provides for nested skill discovery. Changes: - mv skills/{plan-start,project-init,scope-lock,skeleton-gen, db-design-gen,db-init,downstream-gen,frontend-scope-lock} → skills/plan/<same>/ - mv skills/coding-start → skills/coding/coding-start/ - .claude-plugin/plugin.json: skills[] now lists all 9 explicit paths - README.md: directory tree + Skill 清单 heading updated to reflect grouping No code touches any skill path (only README did, and only in the tree diagram). lib tests still pass (62/62).
-
- docs-04 模板新增 § 2.5 样式与主题（命名规范 + tokens.css 位置 + 引用约定） - docs-06 模板 § 四改为 Design Tokens 三段式（4.1 全局调色板 / 4.2 组件级状态色 / 4.3 引用约定） - 新增 styles-tokens-template.css：8 个全局调色板 + 10 个组件状态色默认值 - SKILL.md 同步：C.1 加 mkdir src/styles + cp tokens.css；C.3 加勾选项；参考列表加新模板