'specification' 검색 결과

Tested output format specifications for Claude prompts. Use when the user wants a specific deliverable structure — retrieving, reviewing, customizing, or building output formatting. Trigger on: "give me the Executive Brief format," "show me the output template for," "I need the Decision Matrix structure," "show me available output formats," "build a custom output format for." Provides 10 ready-to-use structures (executive briefs, technical designs, research summaries, implementation plans, decision matrices, competitive analyses, post-mortems, stakeholder updates, strategic memos, process documentation) plus a custom template, with per-section length guidance and format constraints tested against Claude formatting defaults. If unsure which format fits, use rootnode-block-selection first if available. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or choosing reasoning/identity approaches (use rootnode-block-selection if available).

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

Builds, validates, packages, tests, and optimizes deployment-ready Skill files (SKILL.md + references/ + scripts/ + agents/) from design specifications. Three pre-build gates + 9-dimension quality gate (with D9a/b/c empirical evidence tiers) + behavioral iteration loop + automated description optimizer + blind version comparator. Use for building, reviewing, revising, testing, or optimizing Skills. Trigger on: "build this Skill," "review this Skill," "test my Skill," "optimize the description," "compare these Skill versions," "should this be a hook instead," "build a template first." Also: "my Skill doesn't activate," "my description truncates," "my SKILL.md is too long," "my Skill is overtriggering." Do NOT use when designing Skill methodology — that's design work, not packaging. Do NOT use for prompt compilation, project auditing, or prompt scoring (use rootnode-prompt-compilation, rootnode-project-audit, or rootnode-prompt-validation if available).

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

Create polished, code-driven Remotion motion explainers from scripts, narration, subtitles, product specifications, reference videos, UI recordings, diagrams, or abstract concepts. Use for product launches, AI demonstrations, UI interactions, algorithms, scientific principles, electrical systems, data flows, architecture, charts, equations, and concepts best expressed with React, SVG, Canvas, WebGL, or Three.js. Prioritize continuous spatial logic, visible cause and effect, precise interaction states, editable parameters, deterministic rendering, and evidence-backed visual QA.

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

Generate professional Agent Skills for AI agents. Creates complete skill packages with SKILL.md, references, scripts, and templates. Use when creating new skills, generating custom slash commands, or building reusable AI capabilities. Validates against Agent Skills specification.

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

Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".

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

Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".

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

Generate professional Agent Skills for AI agents. Creates complete skill packages with SKILL.md, references, scripts, and templates. Use when creating new skills, generating custom slash commands, or building reusable AI capabilities. Validates against Agent Skills specification.

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

Write well-structured RFCs with normative clauses. Use when: (1) Creating a new RFC, (2) Adding or editing RFC clauses, (3) User mentions RFC, specification, or normative requirements

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

Trigger when: (1) User wants to create an educational/explainer video, (2) User has a vague concept they want visualized, (3) User mentions "3b1b style" or "explain like 3Blue1Brown", (4) User wants to plan a Manim video or animation sequence, (5) User asks to "compose" or "plan" a math/science visualization. Transforms vague video ideas into detailed scene-by-scene plans (scenes.md). Conducts research, asks clarifying questions about audience/scope/focus, and outputs comprehensive scene specifications ready for implementation with ManimCE or ManimGL. Use this BEFORE writing any Manim code. This skill plans the video; use manimce-best-practices or manimgl-best-practices for implementation.

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

Prompt engineering and task-specification skill for improving prompts, agent instructions, system messages, evaluation prompts, coding-agent tasks, multi-step workflows, and LLM output reliability. Use when rewriting vague prompts, adding constraints, reducing ambiguity, improving safety, creating reusable prompt templates, or converting goals into actionable agent instructions.

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

Execute git commits using the Conventional Commits specification. Use this skill whenever the user says "commit", "git commit", "/commit", "stage and commit", "make a commit", "save my changes", or asks to commit specific files or all changes. Also triggers on phrases like "push my changes" (commit first), "commit everything", "commit with message X", or whenever git diff/status suggests uncommitted work the user wants to save. Handles auto-staging, diff analysis, message generation, breaking change detection, batch splitting of unrelated changes, safe pushes, and pre-commit hook failures gracefully. Always use this skill rather than ad-hoc git commit commands.

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

Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.

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

Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: "create a company", "make me a company", "build a company from this repo", "set up an agent company", "create a team of agents", "hire some agents", or when given a repo URL and asked to turn it into a company. Do NOT use for importing an existing company package (use the CLI import command instead) or for modifying a company that is already running in Galyarder Framework.

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

Run Phase 1a (behavioral specification) and Phase 1b (verification architecture) for the active VCSDD feature. Invokes vcsdd-builder to write EARS-format requirements and purity boundary analysis.

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

Use this skill when writing Phase 1a behavioral specifications in VCSDD. Provides EARS format requirements writing, purity boundary analysis, edge case enumeration, and spec quality validation patterns.

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

Preserve an approved specification through a complete implementation plan and execution. Use for major refactors, migrations, or multi-session work when a confirmed spec is authoritative; keep scope and order changes explicit.

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

"Calculate Cpk process capability index to assess whether a process meets specification requirements. Use this skill when the user needs to evaluate process capability, compare processes, or determine if quality targets are achievable — even if they say 'can our process meet spec', 'process capability', or 'Cpk calculation'.".

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

Design REST APIs or function contracts with clear request/response specifications, error handling patterns, authentication strategies, and comprehensive documentation.

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

Frontend specification planning frameworks. Use when a spec touches UI components, forms, client state, or user-facing flows. Covers UI-state completeness (loading, error, empty, success), component boundaries, form validation contracts, state ownership, and measurable UI success criteria.

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

CLI specification frameworks — flag contracts, prompt flows, config precedence, exit codes, output per context (TTY, piped, JSON), error and help text, signals and cross-platform behaviour. Use when a spec adds or changes a command surface, an interactive flow, a config key, an exit path or what a command prints.

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

Backend specification frameworks — endpoint contracts, error catalogs, auth per endpoint, schema with constraints and indexes, migration strategy, middleware order. Load when a spec adds or changes an API endpoint, a database table, or a request pipeline.

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

Specification frameworks for features that call a model — approach tier, model pinning, output contracts, budgets, failure modes and eval design. Load when a spec touches model calls, prompts, retrieval, tool calling, agent loops or evals.

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

OpenAPI 3.1 specification, schema design, code generation

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

Top-level orchestrator for Flutter feature specification. Runs the full uninterrupted pipeline: prd → techspec → tasks in one shot. Use when the user says "spec a feature", "write a spec for", "start feature spec", "plan a feature", or wants to go from idea to implementation-ready tasks without typing three separate commands.

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