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

content-spark

This skill should be used when a story has been captured but content direction is unresolved - the spark describes WHAT to build structurally but not WHAT goes in it. Reads the story spark, splits it into Resolved (structurally clear) vs. Assumed (would have to guess) content dimensions, and surfaces each assumption for the human to confirm, correct, or expand. Also classifies implementation risk tags (has-variants, has-data-pipeline, has-animation, has-touch-targets, diverges-from-existing) so plan-chunks translates them into acceptance criteria that name the implementation mechanism. Captures answers into

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

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.4 KB

SKILL.md(원문)

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

Content Spark Skill

You are the content checkpoint of the Craft harness. Your job is to ensure the human has authorship over WHAT goes into what's being built, before the system decides HOW it looks or HOW to build it.

Orchestrator Context

The orchestrator may pass enriched args. Parse labeled fields if present:

  • STORY: story name - locate the story file
  • STORY_FILE: full path to the story file - skip file discovery
  • CYCLE: cycle directory name - locate story within a cycle
  • PROJECT_TYPE: web/cli/library - tailor dimension analysis

Fallback: Args are primarily a story file path. All phases work without labeled fields.

Execution

Read and execute the logic in ${CLAUDE_PLUGIN_ROOT}/commands/references/content-spark-inline.md.

Risk Tag Authoring Rule

When writing ## Risk Tags, each tag's # comment must name the implementation mechanism or cite a project locked rule. A numeric threshold may appear ONLY as a verification criterion attached to a mechanism - never as the implementation instruction. (A threshold as a CHECK is legitimate; a threshold as the INSTRUCTION is the antipattern - it gets implemented literally, e.g. min-height: 44px instead of an extended hit area.)

  • Wrong: # must stay >=44px
  • Right: # hit area extended via padding/pseudo-element, not min-height; verify computed target >=44px

Canonical statement and per-tag translation detail: ${CLAUDE_PLUGIN_ROOT}/skills/plan-chunks/references/chunk-format-guide.md, section Risk Tag Authoring Rule.

Your goal: Make the user say "Oh good, I'm glad you asked about that."

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

adhoc

무료

Adhoc workflow for small targeted changes to existing behavior or appearance, without the full story ceremony. Use when the orchestrator encounters a bug with a clear root cause and surgical solution, OR a small enhancement to something already built (a different icon, wording, spacing, color). Triggers on: 'fix this', 'this is broken', 'the alignment is off', 'that button doesn't work', 'quick fix', 'patch this', 'tweak this', 'change the icon', 'adjust the wording', post-story corrections, or any situation where the write gate blocks a small targeted change. Acts NOW - a defect to file and fix later belongs in /craft:bugs, other deferred work in the notebook. Do NOT use for new features, design exploration, or changes requiring creative spark.

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

drobins25/craft682026년 10월 18일 업데이트

approve

무료

Request write permission from the user before making file changes. MUST be invoked before any write attempt when the write gate is closed. Creates scoped approval via AskUserQuestion + TaskCreate, opens the write gate, and closes it when work is done. Triggers: write hook blocks an edit, agent is about to write files outside .craft/, agent needs to modify project source files. This skill requires user approval 100% of the time - never bypass AskUserQuestion.

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

drobins25/craft682026년 10월 18일 업데이트

browser

무료

Interactive browser automation via playwright-cli. Use when you need to navigate a site, click elements, fill forms, take snapshots, or triage a live app.

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

drobins25/craft682026년 10월 18일 업데이트

This skill should be used when the user asks to "brainstorm", "explore options", "get creative", "what if we...", or selects "Let's get creative" during story or cycle creation. NOT for a bare vague feature idea where generating options would mean inventing the premise first - that routes to /craft:riff (riff first, options after). Generates 3-4 creative options with trade-offs, visual direction for UI stories, and wireframes.

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

drobins25/craft682026년 10월 18일 업데이트

Use this skill when the user wants to discover, define, or refine their product's aesthetic identity. Triggers on "what should this feel like?", "help me figure out the vibe", "something feels off visually", "I want it to feel like [X]", "define the visual language", or when a project has no established design direction. This is the art director skill - it helps users articulate something they can feel but can't name. Also handles quick cohesion checks when the orchestrator needs one during cycle planning.

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

drobins25/craft682026년 10월 18일 업데이트

This skill should be used when the user says "lock it", "go with that", "approved", "that's the standard", or explicitly establishes a project-wide pattern like "from now on all forms should use this approach". Formalizes approved decisions into locked standards that the system enforces going forward. Not needed for story-scoped decisions — only for project-wide patterns.

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

drobins25/craft682026년 10월 18일 업데이트

drobins25의 스킬 모두 보기

이 스킬의 문제 신고