164건 · 관련도순
Convert long-form Markdown (plan, spec, system design, RFC, runbook, postmortem, brainstorm, notes) into a single self-contained HTML page with Mermaid diagrams, step timelines, callouts, sidebar TOC. Claude-orange light+dark theme. Multi-language. Portable across Claude Code / Codex / Antigravity / any AI agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interview the user about a product idea and write PRD.md. Use at the start of a new project, before features, rules or RFCs exist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Technical specification and design document expert. Use when writing design docs, RFCs, ADRs, or evaluating technology choices. Covers C4 model, system design, and architecture documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OAuth 2.1 + JWT authentication security best practices. Use when implementing auth, API authorization, token management. Follows RFC 9700 (2025).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract and summarize core features, constraints, and priorities from requirement documents. Use when analyzing PRDs, RFCs, business requirements, user stories, epics, or any requirement documentation to identify must-have features, technical constraints, priority levels (P0/P1/P2/MoSCoW), and key decision points. Triggers when users ask to summarize, analyze, extract, or understand requirements from documents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Think and work like an expert Cryptography Engineer. Use when a task calls for Cryptography Engineer judgment. Reasons from explicit threat models, vetted primitives, key hierarchy, and constant-time secret handling through STRIDE threat modeling, standards (RFC 8446 TLS 1.3, FIPS 203/204, Ed25519), test vectors (Wycheproof, NIST CAVP), and protocol verifiers (Tamarin, ProVerif) while treating nonce reuse in AEAD, padding/Bleichenbacher oracles, timing side channels, and weak-RNG keys as first-class failure modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate, validate, and explain `auth.md` files — the open protocol for AI agent registration. Use when making apps agent-ready, generating Protected Resource Metadata (RFC 9728), validating auth.md files, or implementing agent registration endpoints. Triggers on "auth.md", "agent registration", "agent auth", "make my app agent-ready", "ID-JAG", "identity_assertion", "service_auth", "protected resource metadata", "agentic registration".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review design specification documents for Go programs before implementation begins. Use this skill when a user has a Go spec, design doc, RFC, or PRD to review, wants feedback on a planned feature in a Go codebase, is about to start implementing from a spec, or asks "is this spec ready?" or "review this before I build it". Applies Go philosophy — simplicity, composition, explicit errors, context propagation — plus Cobra/Viper CLI conventions where applicable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzing dependencies, circular references, and God Classes; authoring ADRs/RFCs. Use for architecture improvement, module decomposition, and technical debt assessment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
E-Mail-Entwürfe auf die Merkmale prüfen, mit denen Spamfilter Werbepost erkennen, und empfangene Nachrichten auswerten, die im Junk gelandet sind. Nutze diesen Skill, wenn eine Mail vor dem Versand geprüft werden soll, wenn jemand wissen will, warum eine Nachricht im Spam- oder Junk-Ordner gelandet ist, oder wenn Betreff, Text, HTML und Kopfzeilen einer Mail auf Aufbau- und Inhaltsfehler durchgesehen werden. Prüft unter anderem Linktext gegen Linkziel, defekte Abmeldewege nach RFC 8058, erfundene Thread-Bezüge, sichtbare Seriendruckreste, versteckte Zählpixel, Domainstreuung sowie unbelegte Zahlen und Superlative. Sagt keine Zustellung voraus und ist kein Werkzeug, um Filter zu umgehen. Für die Frage, ob eine Kaltakquise-Mail überhaupt versendet werden darf, ist cold-email zuständig.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author and manage Architecture Decision Records (ADRs) in docs/specs/. Use when a significant architectural decision needs to be documented.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Works backward from the stated goal through its prerequisite chain — what must exist to reach the goal, then what each of those requires, back to the current state — classifying each prerequisite as AVAILABLE, DERIVABLE, or MISSING, and blocking planning until nothing is MISSING. Use before creating plans, delegating to agents, or defining acceptance criteria. Activates on specs, PRDs, tickets, RFCs, architecture designs, and multi-step engineering tasks. Always pass `#N` or an inline goal — invoking with no argument and no inline context returns BLOCKED. Integrates with CoVe-style planning pipelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform a thorough, Incan-project-aware code review. Use when the user asks for a review, code critique, PR review, or says /review. Checks Rust anti-patterns, compiler pipeline completeness, error handling, test coverage, style conventions, and RFC compliance specific to the Incan compiler codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review user-facing docs, CLI reference text, examples, and scaffolds for truthfulness, prose quality, and RFC leakage. Use when a broad review needs a dedicated docs/claims pass or when the user asks for docs-truth review specifically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a high-thoroughness end-to-end implementation loop using clean worker worktrees, per-slice planning, implementation, explicit review/fix iteration, orchestrator integration, and final commit/PR drafting. Use when the user explicitly wants a Ralph/Wiggum-style loop, autonomous multi-agent execution, a delegated feature/bugfix carried from confirmed scope through review-ready completion, or RFC-driven implementation that should be reviewed, bumped to In Progress, decomposed into phases, and executed through nested sub-loops. Supports Codex subagents by default and external CLI workers such as OpenCode when explicitly requested and available.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts a GitHub issue title and body using the target repository's issue templates under .github/ISSUE_TEMPLATE. Use when the user asks to create, draft, or file a GitHub issue, bug report, feature request, chore, documentation issue, or RFC proposal, or wants issue text that matches the repo's template.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely close out completed Incan work after a PR is merged by verifying merge status, syncing the base branch, removing task-owned local worktrees/assets, deleting merged local/remote branches, pruning refs, and reporting dirty or ambiguous leftovers. Use when the user says /closeout, asks to clean up after a merged PR, or wants local RFC/issue branch/worktree cleanup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a change against issue, RFC, branch, and user-request scope. Use when a broad review needs a dedicated scope/completeness pass or when the user asks whether the implementation actually matches the intended surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
设计具体 API 端点时使用。适用于资源建模后的下一步、列端点清单、HTTP 方法和状态码选择。优先使用 RFC 7231 HTTP 语义 + GitHub REST 命名规范。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.