본문으로 건너뛰기
cccskills
무료GitHub에 공개

recipe-template

Create a reusable command with explicit preconditions, numbered actions, checks after each step, and error handling. This template provides a structure to customize so Claude verifies the required context before starting a defined workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Template for commands that implement a structured recipe: validate preconditions, then execute numbered steps. Fork this and replace the placeholder content. The 'Context Validation Checkpoints' section is the key pattern, forcing Claude to verify preconditions before starting.

설치 방법 보기

이럴 때 유용합니다

  • Turning a recurring task into a reusable command
  • Defining checks for files, permissions, and configuration before work
  • Adding validation after each workflow step
  • Documenting error responses and completion summaries

포함된 파일(1)

  • SKILL.md2.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Recipe command template

This is a template. Replace all [placeholder] content with your specifics.

When to use

  • [Describe the exact situation where this command applies]
  • [Describe when NOT to use it, with a common misuse case]

Context validation checkpoints

Before executing any step, verify all of these are true. If any checkpoint fails, stop and explain why to the user.

  • [Precondition 1: e.g., "The target branch exists and is up to date with main"]
  • [Precondition 2: e.g., "No uncommitted changes in the affected files"]
  • [Precondition 3: e.g., "Required config file exists at path X"]
  • [Precondition 4: e.g., "Necessary permissions or credentials are available"]

Recipe steps

Step 1: [Action name]

[Clear instructions for this step. Be specific about what to read, what to check, what to write.]

Validation: [How Claude verifies this step completed correctly before moving to Step 2]


Step 2: [Action name]

[Instructions]

Validation: [How to verify]


Step 3: [Action name]

[Instructions]

Validation: [How to verify]


Step 4: Confirm completion

Summarize what was done:

  • [Item 1 completed]
  • [Item 2 completed]
  • Files modified: [list]
  • Next action for the user (if any): [instruction]

Error handling

SituationResponse
[Error condition 1][What to do: retry / stop / ask user]
[Error condition 2][What to do]
Precondition checkpoint failsStop. Explain which checkpoint failed and what the user needs to fix before re-running

Arguments

If $ARGUMENTS[0] was provided: [how to use it] If no argument was provided: [default behavior]


The "Context Validation Checkpoints" section is the key pattern from this template. It forces Claude to verify preconditions explicitly rather than discovering failures mid-execution. Inspired by recurring patterns in Packmind commands (Apache 2.0).

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Evaluate Claude Code agents, skills, and commands with weighted quality criteria. Get scores, readiness grades, template comparisons, and practical improvement suggestions in Markdown or JSON reports to guide reviews before release.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Review skills before release
  • Compare agent definitions with reference templates
  • Quickly check critical quality criteria
FlorianBruniaux/claude-code-ultimate-guide6.2천2026년 10월 20일 업데이트

Assess a codebase across seven areas, including exposed credentials, security, dependencies, structure, and tests. Receive category scores, findings tied to file locations, and a prioritized improvement plan with smaller tasks that can be completed quickly.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Assessing the overall health of an inherited project
  • Reviewing exposed credentials and security risks
  • Identifying dependency and test coverage gaps
FlorianBruniaux/claude-code-ultimate-guide6.2천2026년 10월 20일 업데이트

Measure code patterns such as casts to any or disabled lint rules, then run repeated, targeted edits. Keep changes that improve the chosen metric, revert unsuccessful changes, and track results for each improvement loop.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Finding code patterns to prioritize for cleanup
  • Preparing measurement files for an improvement loop
  • Repeating targeted edits to reduce casts to any
FlorianBruniaux/claude-code-ultimate-guide6.2천2026년 10월 20일 업데이트

best-of-n

무료

Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing implementation options before choosing one
  • Verifying a solution when a wrong choice would be costly
  • Keeping evaluation evidence for delivery or audit
FlorianBruniaux/claude-code-ultimate-guide6.2천2026년 10월 20일 업데이트

canary

무료

Monitor a live application after deployment and compare it with a saved baseline, a record of its earlier state. Check page responses, loading times, and new errors, flag persistent changes, and produce a per-page health report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Recording a healthy baseline before deployment
  • Monitoring production immediately after deployment
  • Checking key pages for slower responses or failures
FlorianBruniaux/claude-code-ultimate-guide6.2천2026년 10월 20일 업데이트

catchup

무료

Rebuild project context after clearing a conversation or returning to work. Review recent Git history, uncommitted changes, and TODO markers to get a structured summary of project status and suggested next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Restoring project context after /clear
  • Reviewing recent changes after a long break
  • Checking unfinished work before choosing the next task
FlorianBruniaux/claude-code-ultimate-guide6.2천2026년 10월 20일 업데이트

FlorianBruniaux의 스킬 모두 보기

이 스킬의 문제 신고