メニュー
Use to create and maintain durable cross-session project memory and the progress ledger, so long autonomous builds resume cleanly after compaction, restarts, or new sessions. Read it when starting work and update it as decisions and tasks land.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when building or structuring a Python backend on FastAPI + SQLAlchemy 2.0 (async) + Alembic + Pydantic v2. Provides the opinionated project layout, the standard kit (auth, async jobs, caching, storage, observability), and best practices.
Use near the end of a project to generate CI and make the app deploy-ready. Produces a polyglot GitHub Actions workflow (lint, typecheck, test, build) and multi-stage Dockerfiles. The finish line is CI-green and container-ready, not an actual deploy.
Use when starting a frontend or working on its look and feel, to establish and enforce a DESIGN.md-driven custom design system as the single source of truth for tokens, components, and icons. Make any generated UI (including 21st.dev Magic output) conform to DESIGN.md.
Use when setting up local development services or running the project locally. Establishes the "stateful services in Docker, app runs native" pattern with Postgres, Redis, MinIO, and Mailpit.
Use after the plan is signed off, to drive the autonomous, plan-gated build to completion. Orchestrates per-task implementation, review, and verification in customer-experience-first order, stopping only on genuine blockers.
Use when building or structuring a React/Next.js + TypeScript + Tailwind frontend, choosing libraries, or wiring design tokens. Provides the opinionated blessed-library stack and the React-vs-Next decision, all on-token to DESIGN.md and accessible to WCAG AA.
| name | project-memory |
| description | Use to create and maintain durable cross-session project memory and the progress ledger, so long autonomous builds resume cleanly after compaction, restarts, or new sessions. Read it when starting work and update it as decisions and tasks land. |
Announce at start: "I'm using claude-engineer:project-memory to keep durable project state."
Long autonomous builds outlive a single context window. Memory lives in files, not your head. The claude-engineer SessionStart hook auto-loads these at the start of every session.
.claude-engineer/)memory.md - durable project memory: key decisions (+ why), established conventions, the data model, open threads/risks, and "next action". The single source of truth for why things are the way they are.progress.md - the task ledger: each task with status (todo / doing / done), the commit/branch, and a one-line result. Append-only-ish; never delete history.current-phase.txt - one line naming the active phase (e.g. Phase 2 - Frontend).quality-gate-status.json - written by the project quality-gate runner; read by the commit gate. Do not hand-edit.Trust the ledger and git log over your own recollection. After compaction, re-read these files before acting. Never re-run a task progress.md marks done.
progress.md.memory.md (mirror big ones into docs/plan/decisions.md).current-phase.txt.Create .claude-engineer/ with seed memory.md (problem, stack, data model, decisions-so-far, next action), an empty progress.md ledger, and current-phase.txt. Add .claude-engineer/quality-gate-status.json to .gitignore (machine-generated); commit memory.md/progress.md so teammates and future sessions share them.
memory.md + progress.md first.memory.md.