メニュー
Use when setting up a new project's repository conventions and house style, the _private vs docs vs code layout, .gitignore, CLAUDE.md, the conventions/pattern registry, and the recommended MCP setup. Run early (Phase 0) and consult when introducing new patterns.
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-conventions |
| description | Use when setting up a new project's repository conventions and house style, the _private vs docs vs code layout, .gitignore, CLAUDE.md, the conventions/pattern registry, and the recommended MCP setup. Run early (Phase 0) and consult when introducing new patterns. |
Announce at start: "I'm using claude-engineer:project-conventions to set up the repo's house style."
_private/ - UNCOMMITTED working area: drafts, screenshots, scratch notes, research. Add to .gitignore.docs/ - COMMITTED non-code: docs/plan/* (the plan), docs/decisions.md, architecture, runbooks, API docs..claude-engineer/ - durable state (see claude-engineer:project-memory). Commit memory.md/progress.md; ignore quality-gate-status.json.apps/, packages/, services/, libs/; see claude-engineer:monorepo-and-tooling).git init (if not a repo). Create .gitignore covering _private/, .claude-engineer/quality-gate-status.json, node_modules, .venv, build dirs, .env*._private/ and docs/ (with docs/plan/).CLAUDE.md capturing: the stack, the iron laws (plan-gated, CX-first, services-in-docker/app-native, the four quality gates), how to run things, and where state lives. This is the project's standing instruction file.docs/conventions.md - the house style the agent must reuse instead of reinventing: naming, error handling, API response shape, folder patterns, and a UI pattern registry (component + token usage; generalize the design system's DESIGN.md into reusable patterns). Append to it whenever a new pattern is established.docs/recommended-mcps.md from templates/recommended-mcps.md and tell the user which MCPs to install with their own keys.Claude-Engineer references MCP servers; it never bundles secrets. Users install with their own keys via each provider's command. See templates/recommended-mcps.md for Playwright, Chrome DevTools, 21st.dev Magic, and designmd (getdesign.md).
_private/.docs/conventions.md → reuse the house style or update the registry deliberately..env* (git-ignored) and document required vars.