3.1천건 · 관련도순
Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
小红书 (XHS) 3:4 vertical cover template — two voices: spring/lifestyle soft watercolor cover with Songti + ink-green accents, and bold editorial typography cover with cobalt-blue bands + folded-paper interior. Despite the "ppt" prefix in the path, these are fixed-image XHS covers, not slide decks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deliver a small bounded change inside an initialized SDD Composy workspace through the quick path: at most five implementation files, a registered TASK, TDD, evidence, trace, and a verified verdict, escalating otherwise. Use for a precise objective with no existing task — 'ajuste rápido via SDD', 'quick fix under SDD', 'small change to X in the SDD flow'. Do NOT use for an already registered task (sdd-execute), for architecture, migrations, or destructive work, or in repositories without SDD Composy (other plugins' quick).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement exactly one SDD Composy task in the ready state with dependency preflight, TDD RED evidence, allowed paths, real verification commands, and the guarded transition to qa_required. Use when a ready task should be executed — 'executar a TASK-003', 'implementar a próxima tarefa', 'run task 4'. Do NOT use for changes without an approved task (sdd-quick), for autonomous multi-stage correction (sdd-loop), or for QA, review, or verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize or resume the SDD Composy workspace of a repository: preview missing governance and OKF bundle files, apply only approved absent paths, persist the artifact language, and verify. Use when a project needs SDD set up or resumed — 'inicializar o SDD', 'configurar o workspace SDD', 'run init first', or when any SDD skill returned not_initialized. Do NOT use for generic CLAUDE.md or repository setup outside SDD Composy, or for other plugins' init.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an approved PRD must become an executable roadmap — 'gerar roadmap do PRD', 'quebrar o PRD em épicos e features', 'cadeia de dependências', 'roadmap with dependencies' — Phase/Epic/Feature/Task with explicit dependencies, waves and critical path, validated by a deterministic checker, with an approval gate. Do NOT use for a PRD that is not approved (prd- create/prd-refine first).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to evolve the features of a PRD roadmap with user stories — 'refinar as histórias da feature', 'escrever histórias de usuário', 'critérios de aceite', 'regras de negócio da feature', 'deixar a feature pronta', 'user stories for FT01' — one feature at a time, interviewing the human until each story meets the Definition of Ready: persona, value, INVEST, CA (Gherkin, happy and error paths) and RN from the PRD. Do NOT use to create the roadmap (prd-roadmap) or to change requirements without stories (prd-refine).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Segundo cérebro persistente em Markdown — LLM Wiki no padrão Karpathy mantida como bundle Open Knowledge Format v0.2, com fontes imutáveis em raw/ e conceitos citados em wiki/. Use quando o usuário disser "segundo cérebro", "second brain", "adiciona isso ao meu brain", "salva na minha wiki", "ingere esse artigo/PDF/link", "o que minha wiki diz sobre", "o que meu brain sabe sobre", "consulta meu conhecimento", "lint da wiki", ou pedir para acumular conhecimento de fontes de forma durável. NÃO use para notas do Obsidian (pwdev-obsidian), planejamento de features (pwdev-feat) nem PRDs (pwdev-prd).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trace bugs backward through call stacks and execution flows to identify the original source of errors, invalid data, or incorrect behavior. Use when debugging complex issues, tracing error origins, investigating data corruption, following execution paths, identifying where invalid data enters the system, or finding root causes of cascading failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits". (gstack)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Publish, deactivate, and delete AEM content programmatically via the Cloud Service Replication API (com.day.cq.replication). Covers single-path and bulk activation, preview-tier targeting with AgentFilter, synchronous/async options, ReplicationStatus checks, permission validation, workflow process steps, and replication event handling. Use when the user needs to publish pages, activate or deactivate content, check replication status, build workflow steps that replicate content, listen to replication events, query batch publication state, or work with Replicator, ReplicationOptions, or ReplicationStatusProvider in AEM Cloud Service.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scrape webpage content, extract metadata, download images, and prepare for import/migration to AEM Edge Delivery Services. Returns analysis JSON with paths, metadata, cleaned HTML, and local images.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a personalized learning roadmap with milestones and practice checkpoints
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
DALL-E 3 image generation workflow for this repo MCP server. Use for dalle3, DALL-E 3, OpenAI image generation, concept art, UCUF reference exploration, UI icon, badge, card art, prompt drafting, and saving generated images to local files under artifacts/ui-source or other workspace paths.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GPT Image 2 image generation workflow for this repo MCP server. Use for gpt-image-2, OpenAI image generation, concept art, UCUF reference exploration, UI icon, badge, card art, prompt drafting, transparent-background asset drafts, and saving generated images to local files under artifacts/ui-source or other workspace paths.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strict routing mode for prompts prefixed with `(best)`. USE FOR: any turn where the user explicitly wants the safest, smallest-context, highest-discipline execution path. This skill must route into context-budget-guard first, then continue into the task-specific workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a stuck or complex problem into the smallest sub-question that, if answered, unlocks the next step — then answer it and repeat until the path forward is clear. Load when a problem feels genuinely stuck, when reasoning keeps circling, or when deep-thinking diagnoses a Socratic frame. Also triggers on "I keep going in circles", "what is the real question here", "help me reason through this step by step", "unstick my thinking", "recursive questioning", "what is the root question". Based on the recursive Socratic questioning method (EMNLP 2023) which outperforms CoT and Tree-of-Thought on complex reasoning tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply Boyd's OODA loop to navigate fast-moving, uncertain, or competitive situations — Observe what is actually happening, Orient through mental models and context, Decide on the clearest path, Act quickly, then loop again. Load when the situation is changing faster than the current plan, when a competitive response is needed, when the user is stuck in analysis paralysis in a dynamic environment, when shipping under uncertainty, or when deep-thinking diagnoses a fast-moving / competitive frame. Triggers on "what should we do right now", "the situation is changing", "how do we respond to this", "competitive response", "we need to move fast", or "we're stuck deciding". Based on John Boyd's OODA loop — Observe, Orient, Decide, Act — adapted for product and business contexts (OODA Canvas 2026).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan which model tier handles which work BEFORE execution begins — a high-cognition model deeply understands the problem, lays the foundations, then emits a modular plan assigning each module the cheapest tier that can safely execute it, with escalation tripwires and one-way-door protection. Advisory only: it announces "next module → tier X / model Y" at each boundary and the HUMAN switches models — harnesses like Cursor cannot switch mid-run. Load when the user asks which model to use, wants a model plan, model tiers, model-tier routing, assign models to tasks or modules, says "cheap model got stuck", "which model for this task", "cost-efficient model choice", or when implementation-plan / problem-to-plan need a model: tier column. NOT dynamic-routing (plan-path selection after failure) — this skill assigns cognition tiers to work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Tactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or when process-decomposer routes here after determining the user needs lightweight planning deliverables. Also triggers on "create tasks from this problem", "make this actionable", or "turn this into a plan agents can execute". For feature-sized work that needs an executable spec + constitution + cross-check gate, route to `spec-driven-development` (or `feature-spec`) instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.