メニュー
Reads the latest timestamped context files from .context/ to understand the current project state, tech stack, recent changes, and blockers before continuing development. Use at the start of any session when you need to catch up on where the project stands.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Deeply analyze a codebase for architectural improvements, refactoring opportunities, and testability issues. Walks through exploration, candidate presentation, and a collaborative implementation loop with the user. Use when the codebase feels messy, untested, hard to navigate, or when preparing for feature work that touches core structures.
Run systematic technical quality checks on frontend code across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with prioritized fix recommendations. Use for pre-ship checks, codebase health assessments, or before significant redesigns.
UX and visual planning for a frontend feature before any code is written. Produces a structured design brief that guides implementation. Use for any new UI surface, component, page, or significant visual redesign. Does not write code — only plans. Complements plan-then-build (which handles architecture and data flow).
One-time design context setup for a project. Interviews the user to capture strategic design intent, then writes .context/PRODUCT.md and optionally .context/DESIGN.md. Use before any design work (new project, or first time using design skills in an existing project). Not for backend-only projects.
Final shipping readiness pass on a UI surface, component, or page. Checks for completeness, consistency, edge cases, micro-interactions, and copy polish. Use after implementation is functionally complete but before declaring it done. Not for finding bugs — for finding gaps between "it works" and "it ships."
Reads staged git changes, recent commit history, and project context to generate a well-structured conventional commit message. Present it to the user for approval before committing.
| name | resume-session |
| description | Reads the latest timestamped context files from .context/ to understand the current project state, tech stack, recent changes, and blockers before continuing development. Use at the start of any session when you need to catch up on where the project stands. |
Load the most recent context files and summarize the project state so we can continue development without losing continuity.
List context files
ls -1 .context/ | sort
Read the most recent .context/ files, up to 6, prioritizing the latest timestamps. Use the read tool on each.
Synthesize a summary covering:
Ask clarifying questions if anything is ambiguous, contradictory, or missing critical detail (e.g., "The spec says X but the code shows Y — should I implement X?").
Confirm readiness — state clearly that you are caught up and ready to continue, referencing specific files or decisions from the context.
.context/; do not rely on memory from previous turns..context/ does not exist, create it.