핵심 개념
| 항목 |
설명 |
| SDLC 태그 |
코드 탐색 → 설계 → 구현 → 배포 → 운영 흐름으로 필터 |
| cat |
작업 유형 (Understand, Implement, Review 등) |
| slots |
프롬프트 안의 치환 자리 (예: path, behavior) |
| 사용법 |
터미널/Desktop/웹 세션 입력창에 프롬프트를 붙여넣고 실행 |
SDLC 분포
| 단계 |
개수 |
| 탐색(discover) |
7 |
| 설계(design) |
6 |
| 구현(build) |
22 |
| 배포(ship) |
5 |
| 운영(operate) |
12 |
카테고리 분포
| 카테고리 |
개수 |
| Onboard |
1 |
| Understand |
6 |
| Plan |
4 |
| Prototype |
2 |
| Implement |
7 |
| Refactor |
4 |
| Test |
3 |
| Debug |
3 |
| Review |
5 |
| Git |
3 |
| Release |
2 |
| Incident |
3 |
| Data |
2 |
| Steer |
3 |
| Automate |
4 |
상세 — 카테고리별 프롬프트
Onboard
get-oriented-in-a
give me an overview of this codebase: architecture, key directories, and how the pieces connect
Understand
explain-unfamiliar-code
explain what {path} does and how data flows through it. write it up as {format}
find-where-something-happens
where do we {behavior}?
see-what-depends-on
what would break if I deleted {target}?
trace-how-code-evolved
look through the commit history of {path} and summarize how it evolved and why
scope-a-change-before
which files would I need to touch to {change}?
ask-the-codebase-a
I am a {role}. walk me through what happens when a user {action}, from the UI down to the result
Plan
plan-a-multi-file
plan how to refactor the {target} to {goal}. list the files you would change, but don't edit anything yet
draft-a-spec-by
I want to build {feature}. interview me about implementation, UX, edge cases, and tradeoffs until we have covered everything, then write the spec to SPEC.md
turn-a-meeting-into
read {input} and write up the action items, then create a {tracker} ticket for each with acceptance criteria
map-edge-cases-before
list the error states, empty states, and edge cases for {feature} that the design needs to cover
Prototype
turn-a-mockup-into
here is a mockup. build a working prototype I can click through, matching the layout and states shown
implement-from-a-screenshot
implement this design, then take a screenshot of the result, compare it to the original, and fix any differences
Implement
follow-an-existing-pattern
look at how {example} is implemented to understand the pattern, then build {new} the same way
generate-docs-for-code
find {scope} without {format} comments and add them, matching the style already used in the file
add-a-small-well
add a {endpoint} endpoint that returns {payload}
build-a-small-internal
create a {tool} using HTML, CSS, and vanilla JavaScript, then open it in my browser
work-an-issue-end
read issue #{issue}, implement the fix, and run the tests
find-and-update-copy
find every place we say "{copy}" or a close variant, show me each one in context, then update them all to "{new}". leave tests and the changelog alone
draft-from-past-examples
read the {examples} in {folder} to learn the structure and voice, then draft a new one for {topic}
Refactor
migrate-a-pattern-across
migrate everything from {from} to {to}: identify every place that needs to change, then make the changes
port-code-between-languages
port {source} to {target}, keeping the same {keep}
optimize-against-a-measurable
optimize {target} to bring {metric} from {current} down to under {goal}
fix-a-precise-visual
the {element} extends {amount} beyond the {container} on {viewport}. fix it.
Test
write-tests-run-them
write tests for {path}, run them, and fix any failures
drive-implementation-from-tests
write tests for {feature} first, then implement it until they pass
fill-gaps-from-a
read {report} and add tests for the lowest-covered files until each is above {target}%
Debug
find-and-fix-a
the {test} test is failing, find out why and fix it
investigate-a-reported-error
users are seeing {symptom} on {where}. investigate and tell me what is going on
fix-a-build-error
here is a build error. fix the root cause and verify the build succeeds
Review
review-your-changes-before
review my uncommitted changes and flag anything that looks risky before I commit
review-a-pull-request
review PR #{pr} and summarize what changed, then list any concerns
review-infrastructure-changes-before
here is my Terraform plan output. what is this going to do, and is anything here going to cause problems?
run-a-security-review
use a subagent to review {path} for security issues and report what it finds
review-content-before-sending
review {file} for {concerns} and list anything I should fix before it goes to {reviewer}
Git
resolve-merge-conflicts
resolve the merge conflicts in this branch and explain what you kept from each side
commit-with-a-generated
commit these changes with a message that summarizes what I did
open-a-pull-request
find the {tracker} ticket about {topic} and open a PR that implements it
Release
draft-release-notes-from
compare {from} to {to} and draft release notes grouped by feature, fix, and breaking change
write-a-ci-workflow
write a GitHub Actions workflow that {steps} on every push to {branch}
Incident
investigate-a-production-incident
{symptom}. check the logs, recent deploys, and config changes, then tell me the most likely cause
diagnose-from-a-console
here is a screenshot of {console}. walk me through why {resource} is failing and give me the exact commands to fix it
query-logs-in-plain
show me all {events} for {scope} over {timeframe}. write the query, run it, and tell me what stands out
Data
analyze-a-data-file
read {file}, summarize the key patterns, and write the results to {output}
generate-variations-from-performance
read {file}, find the underperforming {items}, and generate {n} new variations that stay under {limit} characters
Steer
course-correct-a-wrong
that is not right: {feedback}. try a different approach
narrow-the-scope-of
that is too much. keep only the changes to {scope} and undo your other edits
turn-a-correction-into
you keep {mistake}. add a rule to CLAUDE.md so this stops happening
Automate
turn-a-recurring-task
create a /{name} skill for this project that {steps}
add-a-hook-for
write a hook that {action} after every {event}
connect-a-tool-with
set up the {server} MCP server so you can read my {data} directly
capture-what-to-remember
summarize what we did this session and suggest what to add to CLAUDE.md
체크리스트
다음 단계
- 공통 워크플로에서 시나리오별 흐름 확인
- 반복 패턴은 스킬 또는 slash command로 고정
- 팀 공유는 저장소
CLAUDE.md에 팀 전용 프롬프트 추가
공식 원문: https://code.claude.com/docs/en/prompt-library
