Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From Captain's Cabinet
Use when creating, updating, or completing Claude Code native Tasks for Captain's Cabinet work.
npx claudepluginhub nate-step/captains-cabinet --plugin captains-cabinetHow this skill is triggered — by the user, by Claude, or both
Slash command
/captains-cabinet:cabinet-taskThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Claude Code native Tasks are the execution surface. Cabinet org events are the durable record underneath.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Claude Code native Tasks are the execution surface. Cabinet org events are the durable record underneath.
When creating or updating a Task, include a Cabinet metadata block in the task description:
mission_id: <mission id or unassigned>
node_id: <work graph node id or unassigned>
owner_role: <cos|cto|cpo|cro|coo>
acceptance_criteria: <observable finish condition>
evidence_required: <artifact, test, metric, or review needed>
verifier_role: <role that verifies completion>
risk_level: <low|medium|high>
If no mission or node exists yet, use mission-compile first when the work is material. For a small exploratory task, mark mission_id: unassigned and node_id: unassigned, then link it once the mission is compiled.
Completion requires evidence. Before marking a Task complete, make sure the evidence requirement is satisfied or explicitly state what remains unverified.