菜单
Understand and apply Claude Code project structure patterns. Use when user asks about project organization, wants to add new modules, or needs guidance on where to place files in a Claude Code project.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Collaborate with other AI agents (Kiro CLI, the peer host CLI, and Agy) for a second opinion. Multi-AI review of code/architecture, decision support when you're unsure, and ADR co-authoring, plus autonomous consensus/harness pipelines. The current host chairs and synthesizes the final answer. 멀티 AI 협업: 리뷰, 의사결정 보조, ADR 협업.
Claude plans and verifies, Kiro CLI implements on its own flat-rate subscription credits — a cost-savings implementation-delegation workflow, not a second opinion (see co-agent for that). Kiro implements inside an isolated git worktree; only the captured, scope-guarded diff ever reaches the main tree. Triggers on 'kiro한테 시켜서 구현', 'kiro로 구현', 'kiro한테 구현 위임', 'delegate implementation to kiro', 'kiro implement this'. For read-only review of a diff, use the /kiro:review command instead — this skill is write-capable (it commits) and deliberately does NOT own review triggers.
AWS Workshop Studio 프로젝트 구조 생성 및 콘텐츠 작성 스킬. "워크샵 만들어", "workshop init", "랩 작성" 요청 시 활성화
After creating a PR, poll for AI and human review feedback, auto-fix issues, and push (max 3 iterations)
Create a single-page, responsive online brochure (landing page) for an AWS solution, product, or platform as one self-contained HTML file — editorial design, hero + value + features + embedded architecture diagram + CTA, deployed publicly via GitHub Pages. Use whenever the user wants a brochure, landing page, marketing one-pager, product overview page, solution showcase, '온라인 브로셔', '브로셔 만들어', '랜딩 페이지', '소개 페이지', or wants to present a cloud product's value and architecture on the web — even if they don't say the word 'brochure'. Not for slide decks (use reactive-presentation) or multi-page docs sites (use gitbook).
Create dynamic animated SVG diagrams with SMIL animations for AWS architecture traffic flow, service interactions, and deployment pipelines. Use when creating animated or dynamic diagrams.
| name | project-scaffolder |
| description | Understand and apply Claude Code project structure patterns. Use when user asks about project organization, wants to add new modules, or needs guidance on where to place files in a Claude Code project. |
| tools | Read, Glob |
| user-invocable | false |
Knowledge skill for Claude Code project structure patterns and conventions.
A well-organized Claude Code project follows this structure:
project-root/
├── CLAUDE.md # Project memory and instructions for Claude
├── README.md # Project documentation
├── .gitignore
├── .env.example # Environment variable template (no real secrets)
├── .editorconfig # Editor formatting rules
├── .mcp.json # MCP server configuration
├── docs/
│ ├── architecture.md # System architecture document
│ ├── onboarding.md # New developer onboarding guide
│ ├── api-reference.md # API documentation (if applicable)
│ ├── decisions/ # Architecture Decision Records (ADRs)
│ │ └── .template.md
│ └── runbooks/ # Operational runbooks
│ └── .template.md
├── .claude/
│ ├── settings.json # Permissions and hooks configuration
│ ├── hooks/
│ │ ├── check-doc-sync.sh # PostToolUse: Documentation sync detection
│ │ ├── secret-scan.sh # PreToolUse: Secret detection gate
│ │ ├── session-context.sh # SessionStart: Load project context
│ │ └── notify.sh # Notification: Webhook alerts
│ ├── commands/
│ │ ├── review.md # /review: Code review on diff
│ │ ├── test-all.md # /test-all: Execute full test suite
│ │ └── deploy.md # /deploy: Build and deploy
│ ├── skills/
│ │ ├── code-review/SKILL.md # Confidence-based code review
│ │ ├── refactor/SKILL.md # Safe refactoring with verification
│ │ ├── release/SKILL.md # Semver release automation
│ │ └── sync-docs/SKILL.md # Documentation sync with quality scoring
│ └── agents/
│ ├── code-reviewer.yml # Parallel code review agent
│ └── security-auditor.yml # Security audit agent
├── scripts/
│ ├── setup.sh # Project setup for new developers
│ └── install-hooks.sh # Git hooks installer
└── src/
├── api/
│ └── CLAUDE.md # API module context
└── persistence/
└── CLAUDE.md # Persistence module context
docs/ with a link; 500+ lines is a hard smell (anti-pattern table below)| Type | Location | Purpose |
|---|---|---|
| Skills | .claude/skills/ | Auto-activate on task match (AI-driven) |
| Commands | .claude/commands/ | User-invocable slash commands |
| Hooks | .claude/hooks/ | Deterministic lifecycle event scripts |
| Agents | .claude/agents/ | Isolated parallel work (subagents) |
| MCP | .mcp.json | External tool connections |
/add-module <path> to create directory + CLAUDE.md + update architecture docs in one step/add-adr <title> for auto-numbered creation/add-runbook <name> for template-based creationWhen evaluating or creating CLAUDE.md files, target these scores (total 100):
| Criterion | Max | What to check |
|---|---|---|
| Commands/workflows | 20 | Build/test/deploy commands present and copy-paste ready? |
| Architecture clarity | 20 | Codebase structure understandable from this file alone? |
| Non-obvious patterns | 15 | Gotchas, quirks, and conventions documented? |
| Conciseness | 15 | No verbose explanations or obvious info? |
| Currency | 15 | Reflects current codebase state? |
| Actionability | 15 | Instructions are executable, not vague? |
Grades: A (90-100), B (70-89), C (50-69), D (30-49), F (0-29)
| Anti-Pattern | Impact | Detection |
|---|---|---|
| Over 500 lines | Context bloat | wc -l |
| Vague instructions ("write good code") | Useless guidance | Grep for vague phrases |
| Duplicated docs (copy of README) | Wasted context | Compare with README |
| No test guidance | Skipped tests | Missing test commands/patterns |
| No error patterns | Inconsistent handling | Missing error handling section |
| Contains secrets | Security risk | Grep for key patterns |
.env.example: Use for environment variable templates (no real values)settings.local.json: Add to .gitignore for local overridesWhen applying this structure to existing projects:
For detailed templates, see: