Audit and establish current agent context for the technologies that define a project's stack. Use when setting up a project for agent work, after selecting or adding a framework, library, developer tool, or hosted service, or when entering an existing project whose agent context has not been audited.
日本語の概要は準備中です。原文の説明を表示しています。
toy-crane/claude-code-playbook-template☆ 772026年10月21日 更新
Revise active `docs/specs/SLUG/` specs so they match what has shipped since they were written. Use when earlier work has landed and queued specs may now rest on stale assumptions, acceptance criteria, constraints, terms, or prototypes, or when implementation reports a spec as stale before changing source. Takes one or more spec folders, or every folder under `docs/specs/` when none is named. Do not use to shape a new spec from a problem and direction, which belongs to `shape-idea`, or to reconcile durable project context and retire shipped folders, which belongs to `maintain-project-context`.
日本語の概要は準備中です。原文の説明を表示しています。
toy-crane/claude-code-playbook-template☆ 772026年10月21日 更新
Build a complete dummy-data HTML prototype or a temporary comparison of up to three alternatives for a specific user situation. Use to settle a screen-based product before implementation or resolve a visual or interaction decision during shaping or prototype review. Do not use for production implementation or CLI, terminal, or voice interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
toy-crane/claude-code-playbook-template☆ 772026年10月21日 更新
Create Git commits for the current request's in-scope changes as logical Conventional Commits. Always use this skill for an actual Git commit operation, including requests to commit or amend changes, save work in repository history, stage and record selected files, or group staged or unstaged changes into commits. Use it even when the request describes recording changes without saying "commit"; it performs the commit rather than only suggesting a message, and it does not push.
日本語の概要は準備中です。原文の説明を表示しています。
toy-crane/claude-code-playbook-template☆ 772026年10月21日 更新
Interview the user to define or revise the app's overall product direction, then preserve the confirmed meaning in root PRODUCT.md. Always use for a new app direction or any app-wide change to users, usage situations, problem, promised change, core loop, durable boundaries, experience principles, success signals, assumptions, or unknowns, even when PRODUCT.md is not named. Start from an existing definition or a rough app direction. Do not use for blank-page idea discovery, architecture, or shaping or specifying one feature or work unit.
日本語の概要は準備中です。原文の説明を表示しています。
toy-crane/claude-code-playbook-template☆ 772026年10月21日 更新
Render an explanation as a diagram, comparison, trace with real values, or annotated code. Use when the user asks to have a concept, decision, flow, or code explained, or says they do not follow.
日本語の概要は準備中です。原文の説明を表示しています。
toy-crane/claude-code-playbook-template☆ 772026年10月21日 更新