decision-doc-sync
Trigger: architecture change, new convention, UI/UX standard, quality gate change, ADR. Keep existing project docs in sync with structural decisions.
- Installs
- 3.2K
- Last 24h
- +170
- Trending rank
- #1408
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/c3sc0-v4113/scaffold --skill decision-doc-sync- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads decision-doc-sync automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Decision Documentation Sync
Activation Contract
Load this skill when a change introduces or changes a structural decision: architecture, UI/UX standards, scripts or quality gates, or a cross-cutting convention.
Hard Rules
- Check which documents exist before editing; update only documents that exist, and create one only when a rule below requires it.
- Keep each fact in one document and link to it from others instead of duplicating it.
- Record the decision itself, not the change history.
- Never leave a document contradicting the code after the change.
Decision Gates
| Change type | Document |
|---|---|
| Architecture, folder structure, scripts | README.md |
| Visual or UX standard, tokens, component usage | DESIGN.md |
| Agent workflow, commands, operational guidance | AGENTS.md |
| Durable decision with alternatives and consequences | new record in docs/adr/ |
Execution Steps
- Check which of
README.md,DESIGN.md,AGENTS.md, anddocs/adr/exist. - Classify the change with the table above; one change may hit several rows.
- Update each affected document that exists.
- For an ADR, follow the existing numbering and format in
docs/adr/; see references/doc-map.md. - Reread the edited sections against the code.
Output Contract
List every document updated, created, or deliberately skipped, with a one-line reason each.
References
- references/doc-map.md — ADR format and edge cases.
FAQ
What does the decision-doc-sync skill do?
Trigger: architecture change, new convention, UI/UX standard, quality gate change, ADR. Keep existing project docs in sync with structural decisions.
How do I install decision-doc-sync?
Run npx skills add https://github.com/c3sc0-v4113/scaffold --skill decision-doc-sync in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/decision-doc-sync/ (personal) or .claude/skills/decision-doc-sync/ (project).
Which AI agents can use decision-doc-sync?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is decision-doc-sync safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains decision-doc-sync?
It is published by c3sc0-v4113 in c3sc0-v4113/scaffold. It has 3,214 recorded installs.
More from c3sc0-v4113/scaffold
project-min-evaluation
c3sc0-v4113/scaffold
Trigger: done, complete, finish, before commit, quality check, verify. Run the project's own minimum quality scripts before claiming work is complete.
project-architecture
c3sc0-v4113/scaffold
Trigger: UI change, layout, component architecture, state flow, theming, server/client boundary, Astro island. Keep Next.js or Astro apps server-first.
shadcn-component-boundaries
c3sc0-v4113/scaffold
Trigger: components/ui, shadcn, component placement, common components, feature components, atomic design. Enforce registry and product component boundaries.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.