GitHub

Discover, install, and author Spec Kit bundles via `specify bundle`. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and installing a bundle, managing bundle catalog sources. DO NOT USE FOR: individual extensions/presets/integrations/workflows (use their respective skills).

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

Manage Spec Kit extensions via `specify extension`. USE FOR: listing installed extensions as text or JSON, installing/removing/updating extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting resolution priority, or managing extension catalogs. DO NOT USE FOR: artifact composition stacks (use speckit-artifact), presets (use speckit-preset), bundles (use speckit-bundle), or workflows (use speckit-workflow).

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

Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running `specify init --integration copilot --integration-options="--skills"`. USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO NOT USE FOR: managing extensions/presets/bundles of an already-initialized project (use the speckit-extension / speckit-preset / speckit-bundle skills instead).

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

Manage Spec Kit presets via `specify preset`. USE FOR: listing installed presets as text or JSON, installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting resolution priority, or managing preset catalogs. DO NOT USE FOR: full artifact composition stacks (use speckit-artifact), extensions (use speckit-extension), bundles (use speckit-bundle), or workflows (use speckit-workflow).

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

Check for and apply Spec Kit CLI updates via `specify self`. USE FOR: checking whether a newer specify-cli release is available, previewing an upgrade with --dry-run, upgrading the CLI in place (optionally to a pinned tag). DO NOT USE FOR: checking project tools/integrations (use speckit-check) or managing extensions/presets/integrations/workflows.

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

Check the local environment for Spec Kit by running `specify check` (and `specify version`). USE FOR: verifying required tools are installed, diagnosing a broken spec-kit setup, reporting CLI version/feature capabilities. DO NOT USE FOR: installing or upgrading the CLI itself (use the speckit-self skill).

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

Manage Spec Kit workflow step types via `specify workflow step`. USE FOR: listing built-in and custom workflow step types, installing/removing a custom step type from a catalog, searching/showing step-type info, managing step-type catalog sources. DO NOT USE FOR: running or installing whole workflows (use speckit-workflow), or bundles (use speckit-bundle).

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

Manage and run Spec Kit automation workflows via `specify workflow`. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use speckit-extension), presets (use speckit-preset), or bundles (use speckit-bundle).

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

Scan files, content, or recent changes for secrets such as API keys, passwords, tokens, and credentials using the GitHub MCP Server's run_secret_scanning tool.

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

Scan repository dependencies for known vulnerabilities using the GitHub MCP Server's Dependabot toolset and the GitHub Advisory Database. Use when asked to check dependency security, audit lockfiles, or verify packages before merging.

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

Publishes a Replica prototype through its existing workflow and Hub Build. Use for prototype canvas publishing requests that include verified target JSON and a publishing mode.

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

Write meaningful Replica tests. Use when adding regression coverage, testing new behavior, or changing existing automated tests.

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

Reviews page hierarchy, grouping, density, actions and state design using consumer-owned product and design-system guidance. Use when asked for a visual design review, page critique or whether a new page communicates its task clearly.

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

Audits actual components and routes against applicable WCAG 2.2 A/AA criteria using consumer-owned design-system evidence and repository tools. Use when asked for an accessibility audit, a11y check, keyboard or focus review, contrast check, or screen-reader verification.

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

Shared context template library for setup-skills. Read when discovering context documents or their ownership. This library supplies research inputs, not active product context or a separate authoring workflow.

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

Configures shared sources and drafts context with independent writers. Plain/fresh setup offers installation of user-named packages and reuses built-in browser capabilities, adding browser tooling only for an evidenced required-check gap. Use for setup, source repair, writing context or refreshing drafts. Configure-only skips tooling and authoring; installations and activation require separate approval.

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

Reviews existing UI components for design-system consistency, states, responsiveness and accessibility using consumer-owned context. Use when asked to review component quality, check design-system adherence or audit component consistency.

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

Review Replica pull requests using the same shared conventions and project guides as implementation agents. Use when reviewing changes to code, tests, workflows, or documentation in this repository.

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

Writes a lightweight Markdown concept handoff from existing decisions and evidence. Use when explicitly asked for a developer handoff, to transfer a prototype or concept to another team, or to prepare a brief for implementation. Not for ordinary prototype completion, building, reviewing or publishing.

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

Review Hub feedback for reusable design themes through discovery, independent judging and synthesis. No diagnosis or optimization.

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

Use for explicit agent-browser CLI checks or a named browser capability neither the Copilot canvas nor configured Playwright MCP can supply. Ordinary rendered checks and browser selection belong to browser-canvas-validation.

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

Audits UI layout, overflow and navigation across product-defined viewports using consumer context and browser tools. Use when asked to check responsiveness, test mobile layout or audit breakpoint behavior.

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

Use the Copilot browser canvas first for rendered route checks, interaction tests, screenshots and visual, responsive or accessibility evidence. Use configured isolated Playwright MCP only when the canvas is unavailable for a required check.

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

Guides product-design decisions using the consuming repository's design-system, product, and repository context. Use when designing UI, choosing layout or navigation, handling states and forms, messaging, disclosure, onboarding, visualization, copy, delete, filter, or search interactions. Triggers on 'design guidance', 'how to design', 'UI pattern', 'product design', 'scenario pattern', 'confirmation dialog', 'delete flow', 'copy to clipboard', 'filter', and 'search'.

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