| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[codex] Add DESIGN.md skill support (#21) * Add DESIGN.md skill support * fix(design-md): narrow triggers, add precondition, align activation, register decision Follow-up to PR #21 (the original adds the design-md skill). Cross-model review (Claude + Codex) flagged 9 issues; addressing all of them in one commit so the PR can land. P1 — Triggers were too broad. Original list included "UI", "frontend", "components", "styling" — substring-matched against every UI task in any project, even ones with no DESIGN.md. Existing skills (git-proxy, deploy-checklist) use 4–7 specific phrases. Trimmed to 7 narrow triggers focused on DESIGN.md / Google Stitch / design tokens / design system / visual design. P2 — Missing precondition. Skill is only useful when DESIGN.md exists at the project root. git-proxy uses ["..git exists"]; design-md now uses ["DESIGN.md exists at project root"] following the same pattern. Skill loader short-circuits when the file isn't there. P2 — Activation rules drifted between AGENTS.md and the manifest. AGENTS.md said to load the skill "during UI, frontend, component, styling, or prototype work" while the manifest used a different (overly broad) trigger set. Same task, different harness, different behavior. AGENTS.md now mirrors the manifest's narrower trigger list and notes the preconditions-gated load. P2 — Skill body had no "don't modify DESIGN.md by default" guard. For a contract file, read-only-by-default is the right posture. Added an explicit "Default: read-only" section + a constraint that says "do not modify DESIGN.md unless the user explicitly asks". Implementation work consumes the contract; it doesn't edit it. P3 — Skill was not logged in .agent/memory/semantic/DECISIONS.md. docs/writing-skills.md:50 says new skills must be logged there. Added a 2026-04-26 entry covering the decision, rationale, and rejected alternatives. P3 — Self-rewrite hook didn't follow the repo's own format. Replaced the vague "if UI work repeatedly drifts" prose with the standard "after every 5 uses OR on any failure" template from docs/writing-skills.md:36-44 with concrete steps and a commit message format. P3 — Stale "five seed skills" copy. README.md:124 said "five" and docs/demo/src/scenes/Outro.tsx:6 hardcoded `value: "5"` for seed skills, but the same PR adds a sixth. Both bumped to 6. P3 — Validation guidance overstated the manual fallback. The CLI checks contrast ratios and orphaned tokens; the manual checklist doesn't. Note that the manual fallback is best-effort and re-run the CLI when network is available. Codex confirmed `@google/design.md` exists on npm and the CLI commands in the skill body are correct (https://github.com/google-labs-code/design.md). --------- Co-authored-by: codejunkie99 <email@email.com> | 4 个月前 | |
feat: add Remotion demo video and embed GIF in README | 5 个月前 | |
feat: add Remotion demo video and embed GIF in README | 5 个月前 | |
feat: add Remotion demo video and embed GIF in README | 5 个月前 | |
feat: add Remotion demo video and embed GIF in README | 5 个月前 | |
feat: add Remotion demo video and embed GIF in README | 5 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 4 个月前 | ||
| 5 个月前 | ||
| 5 个月前 | ||
| 5 个月前 | ||
| 5 个月前 | ||
| 5 个月前 |