메뉴
Use when drafting a recipe seed JSON for CMS import. Output at the target repo's resolved recipe seed path. Include structured-data fields (times, servings, difficulty). Match brand-voice.md before finishing. Do NOT merge or publish — seed PR only.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Web development practice setup interview — detects or creates .agency/target.json binding, reads instance profile from `/agency-hub:setup`, interviews tech stack, deployment platform, connectors, and persona preference (six engineering personas vs merged), writes practice profile. Use on first install after `/agency-hub:setup`, when the user says "set up web development" or "bind target repo", or to redo engineering defaults only.
Use when the user wants to run a Ralph loop: an autonomous, self-referential delivery loop that drives a whole epic through implement, code review, fix, UX review, validate, commit, and merge request, one task per iteration, until a completion promise is emitted (ralph setup, ralph start), or to inspect or stop a running loop (ralph status, ralph cancel). Also supports simple ad-hoc loops that repeat a single prompt until done. Do NOT use to implement a single task once (implement), review a diff (code-review), or sign off an epic (validate) — the loop orchestrates those skills.
Use when the user wants a UX/design review of implemented UI — frontend components, pages, or flows — against the design source of truth (Figma via MCP, mockups, tokens, or style guide, whatever the repo provides), covering design fidelity, accessibility (WCAG 2.2 AA), interaction states, responsiveness, and design-system conformity; or to address UX review findings (ux-design-review fix, optionally scoped to an action tier). Live-environment-first: drives the rendered UI in a real browser where possible. Works with any framework or design tooling. Do NOT use for code correctness/security review (code-review), to review a design.md document (design), or to implement features (implement).
Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author pushes. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Do NOT use to review your own working diff before opening an MR (code-review), to open or babysit an MR (merge-request), or to implement changes (implement).
Use when the user wants to open a merge request or pull request for the current branch (merge-request create — the default — with a generated title, description, labels, and reviewer suggestions), or to babysit an open MR/PR to a merge-ready state (merge-request babysit) by watching CI, review comments, and merge conflicts. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise, and plain git as a last resort. Do NOT use to review code or an MR as its reviewer (code-review, merge-request-review) or to implement changes (implement).
Use when the user wants a code review of a branch, PR, or diff against its acceptance criteria and declared scope (whatever form they take in this repo), or to address review feedback without changing behaviour (code-review fix, optionally scoped to a blocking or warning action tier). Works with any language, delivery process, or issue tracker. Do NOT use to implement code, sign off completion of a larger body of work, or review rendered UI/UX (design fidelity, accessibility — use ux-design-review).
| name | draft-recipe |
| description | Use when drafting a recipe seed JSON for CMS import. Output at the target repo's resolved recipe seed path. Include structured-data fields (times, servings, difficulty). Match brand-voice.md before finishing. Do NOT merge or publish — seed PR only. |
| license | MIT |
| allowed-tools | ["Read","Write","Glob","Grep"] |
| argument-hint | <slug> [--brief from calendar] |
| metadata | {"version":"0.1.0","owner":"content-marketing","review_cadence":"quarterly","work_shape":"generate-draft","output_class":"draft-for-review"} |
Draft a recipe seed JSON when a calendar brief or user request specifies a recipe slug and topic.
content-calendar)import-content-seed.tstechnical-seo-audit)<resolved-brand-path>/brand-voice.md and match tone on excerpt and instruction steps| Failure mode | Mitigation |
|---|---|
| Direct apply vs draft | Seed JSON in PR only; human merges then imports as CMS draft |
| Brand safety | Reads brand-voice.md from resolved brand path; inline tone ask if missing |
| Blast radius | Writes only under resolved recipe seed directory |
| DoD bypass | Does not mark recipe live |
Follow prompts/run.prompt.md.
{recipe-seed-dir}/{slug}.json on the target repo (resolve per content-conventions).
Schema derived from the target CMS recipe collection config:
| Field | Type | Required |
|---|---|---|
slug | string | yes |
title | string | yes |
date | ISO date | yes |
author | author slug | yes |
difficulty | easy | medium | hard | no |
servings | number | no |
prepTime | ISO 8601 duration | no, e.g. PT20M |
cookTime | ISO 8601 duration | no |
totalTime | ISO 8601 duration | no |
excerpt | string, max 500 | yes |
description | string, max 300 | no |
image | public path | no |
tags | tag slug array | no |
ingredients | [{ "item": "..." }] | yes, min 1 |
instructions | [{ "step": "..." }] | yes, min 1 |
Structured data: valid ISO 8601 durations; totalTime equals prep + cook when both set;
ingredients as full lines in item.
content-seo-review — SEO review on seed PRkeyword-research — target keywords for recipe SEO