メニュー
Deployment / procedure document skeleton — the binding structure for client-facing .md procedure docs (top summary + prerequisites checklist + numbered steps + number-match + link-don't-redefine). Loaded by the docs-forge deploy-doc workflow.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate or edit bitmap images from Claude Code by delegating to Codex CLI image generation, without managing OpenAI API keys. Use when the user asks to generate or edit a raster image, or when an active task's spec explicitly designates codex-image as the image path (e.g. deck builds); never research raw codex invocation instead of loading this skill. When the grounding or scope is ambiguous, confirm before generating — image generation has cost and side effects.
Use when the user asks an in-depth question about a GitHub repository's internals, architecture, or implementation details — anything that benefits from AI-summarized repo documentation rather than raw code reading. Triggers on phrases like "how does <repo> handle X", "explain the architecture of <repo>", "what's inside <owner/repo>", or "compare <repoA> and <repoB>". Wraps the DeepWiki MCP (`mcp__deepwiki__read_wiki_structure` / `read_wiki_contents` / `ask_question`).
Onboard a full Playwright E2E test harness in the current project — verify/install Playwright, generate the official planner/generator/healer agents via npx playwright init-agents --loop=claude, scaffold auth separation (storageState + setup project), network route mocking, an E2E operating SSOT doc, and a gated GitHub Actions CI workflow with trace artifacts and PR-failure comments. Use when the user asks to set up E2E, add Playwright AI agents, bootstrap end-to-end testing, or wire E2E into CI. Never overwrites an existing playwright.config (merge proposal + backup). Degrades gracefully when Playwright is absent. Run from the user's project root, not this marketplace repo.
Use to scaffold the LLM-Wiki knowledge system (`.llmwiki/` insight + wiki + raw, plus spec) in a new repo that doesn't have it yet. Copies templates from the plugin's bundled assets, prompts for project pitch and 1-3 first domains, writes a slim CLAUDE.md.
Use after producing a new audit md, after merging a PR with non-obvious findings, or when a debugging session uncovers lore worth saving. Pulls the finding into the wiki with reversible diff-log + multi-page cross-update. Universal — works in any repo with a `.llmwiki/wiki/` or legacy `.claude/wiki/`.
Use when the user asks to audit wiki health, or periodically (manual trigger) to catch the 4 wiki-rot failure modes — identity duplication, level flattening, monotonic relationships, and staleness. Universal — works in any repo with a `.llmwiki/wiki/` or legacy `.claude/wiki/`.
| name | deploy-doc-guide |
| description | Deployment / procedure document skeleton — the binding structure for client-facing .md procedure docs (top summary + prerequisites checklist + numbered steps + number-match + link-don't-redefine). Loaded by the docs-forge deploy-doc workflow. |
The cross-runtime SSOT for client-facing deployment / procedure documents. The ## Quick Reference skeleton below is binding — the deploy-doc command and any agent must self-verify against it before writing.
The skeleton (Korean default; English labels in parentheses for --lang en). Each item is a self-verify checklist entry — confirm all before output:
# H1 document title (from --title) on the first line, then a 2-3 line summary paragraph directly below it and above the first ##. The summary is untitled in the sense that it carries no section heading of its own (no ## 요약) — it is bare prose between the # H1 and the first ##. If no title is given, the summary paragraph is the very top of the file. The summary states what is deployed and the step count at a high level.## 전제조건 (## Prerequisites) section where every line is a - [ ] checklist item. No bare prose bullets.## 절차 (## Procedure) section where every step is a ### N. heading, numbered contiguously from ### 1. with no gaps and no ### N.-less prose steps.### N. headings. Mismatch = FAIL.--links documents), never inlined. The procedure references the authority; it does not restate it.Compliance check before writing: summary 2-3 lines? prerequisites all - [ ]? procedure all contiguous ### N.? summary count == ### N. count? contracts linked not inlined?
../../references/DEPLOY_DOC_PATTERNS.md — empty skeleton, a filled example, and anti-patterns.