Plugin Claude Code
Marketplace for the doc-everything plugin — per-feature documentation kept in sync with code via a Stop hook and templating skills.
Plugin Claude Code
Marketplace for the doc-everything plugin — per-feature documentation kept in sync with code via a Stop hook and templating skills.
Plugin Claude Code
Keep per-feature documentation in sync with code. A Stop hook nudges you to document whatever you just changed, and two skills give you canonical templates for the engineering view (technical.md) and the user-facing view (product.md), plus a maintained index. Language- and framework-agnostic; tune the watched…
Cursor rule Cursor
Set up doc-everything in a Cursor project — install the docs-sync stop hook, scaffold the docs/features/ directory with an index, and (only if the defaults don't fit) write a doc-everything.json config so the hook watches the right paths. Apply once per repo when adopting doc-everything in Cursor, or when the stop…
Cursor rule Cursor
How to write/update the PRODUCT documentation for a feature — the user-facing view (what it is + who it's for, why it exists, the user journey, states/edge cases, copy). Apply when you finish or change a feature, or when the docs-sync stop hook asks you to document what changed. Produces docs/features/ /product.md AND…
Cursor rule Cursor
How to write/update the TECHNICAL documentation for a feature — the engineering view (architecture & data flow, the files involved, data model, auth/validation, key decisions, tests). Apply when you finish or change a feature implementation, or when the docs-sync stop hook asks you to document what changed. Produces…
Hook
Runs when the agent finishes a response, executing docs-sync.sh. From rafaelszago/doc-everything.
Skill Claude CodeCodex
Set up the doc-everything plugin for the current project — detect the source layout, scaffold the docs/features/ directory with an index, and (only if the defaults don't fit) write a .claude/doc-everything.json config so the docs-sync Stop hook watches the right paths. Use once per repo when adopting the plugin, or…
Skill Claude CodeCodex
How to write/update the PRODUCT documentation for a feature — the user-facing view. Use whenever you finish or change a feature and need to record what it does for the user, or when the docs-sync Stop hook reminds you that source changed but docs didn't. Produces docs/features/ /product.md (what it is + who it's for…
Skill Claude CodeCodex
How to write/update the TECHNICAL documentation for a feature — the engineering view. Use whenever you finish or change a feature implementation and need to record how it works under the hood, or when the docs-sync Stop hook reminds you that source changed but docs didn't. Produces docs/features/ /technical.md…