From composure
Refreshes Composure config, hooks, reference docs, or stack in initialized projects without full re-initialization. Targets only changes or specified components via [config] [docs] [hooks] [stack] [all].
How this skill is triggered — by the user, by Claude, or both
Slash command
/composure:update-projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Lightweight refresh for an already-initialized project. Unlike `/initialize`, this skips first-time setup (Context7 install, task queue creation, graph bootstrap) and only updates what's stale or explicitly requested.
Lightweight refresh for an already-initialized project. Unlike /initialize, this skips first-time setup (Context7 install, task queue creation, graph bootstrap) and only updates what's stale or explicitly requested.
Load each step through the fetch command (handles caching, decryption, and auth):
"~/.composure/bin/composure-fetch.mjs" skill composure update-project {step-filename}
Do NOT read cache files directly — they are encrypted at rest. Always use the fetch command above.
npx claudepluginhub hrconsultnj/claude-plugins --plugin composureDetects project tech stack and generates Composure config (.composure/no-bandaids.json), task queue, and framework reference docs. Run once per project to bootstrap.
Updates CLAUDE.md and project.json by comparing against current just-ship framework templates, adding missing sections and framework content while preserving project-specific details.
Detects tech stack changes, plugin updates, and local modifications to selectively update Memory Bank files with 3-way merge preserving user edits.