941건 · 관련도순
Declare an agentic application's interaction disclosure, state, context, capabilities, and effect-control boundaries. Use for a reviewable design specification and static consistency audit before implementation. NOT for proving that controls are deployed or enforced, exposing private chain-of-thought, selecting a model/router, or designing a multi-agent protocol.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for writing high-quality acceptance criteria and acceptance tests using industry-standard BDD (Behavior-Driven Development) and ATDD (Acceptance Test-Driven Development) practices. Use this skill when creating acceptance criteria for user stories, writing Gherkin scenarios, or implementing acceptance test specifications following Given-When-Then format.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parse and validate project specifications. Use when loading YAML/JSON specs, validating spec structure, extracting requirements, or converting between spec formats.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates a structured skill template based on provided specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
使用 A2UI v0.8（以 renderers/lit/src/0.8 与 specification/0.8 为准）生成服务端 JSONL UI 消息，并实现客户端事件与 A2A 扩展回传。适用于把用户需求转成 A2UI 组件树+数据模型+渲染序列，以及处理 action/userAction 与后端接口调用的场景。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive Product Owner skill for requirements gathering, analysis, and PRD generation. Triggers when users request product requirements, feature specification, PRD creation, or need help understanding and documenting project requirements. Uses quality scoring and iterative dialogue to ensure comprehensive requirements before generating professional PRD documents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a complete, production-ready application from an OpenAPI specification
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides expert guidance on Development Containers (devcontainers) — creating, configuring, and optimising containerised development environments using the Dev Container Specification. This skill should be used when users ask about devcontainer.json, .devcontainer setup, Dev Container Features or Templates, pre-building images, multi-container workflows, Docker-in-Docker, cloud development environments (Codespaces, DevPod), or troubleshooting container performance and permission issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Formats commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a new track with specification and phased implementation plan
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discover and inventory shadow API endpoints that operate outside documented specifications using traffic analysis, code scanning, and API discovery platforms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy a Software-Defined Perimeter using the CSA v2.0 specification with Single Packet Authorization, mutual TLS, and SDP controller/gateway configuration to enforce zero trust network access.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or materially revise a durable specification when the user explicitly requests a spec/new feature contract or a named ambiguity requires formal DEFINE; do not trigger for ordinary bounded edits, implementation, task breakdown alone, review, or documentation of already-settled behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break a clear scope or accepted specification into ordered tasks/packages when the user explicitly asks for a plan, estimate, dependency order, or task breakdown; do not trigger for ordinary implementation, every multi-step task, speculative parallelism, review, or completion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Converts Figma/design specifications into production-ready UI components with accurate spacing, typography, color tokens, responsive rules, and interaction states (hover, focus, disabled, active). Generates Tailwind/shadcn code with design system tokens mapping. Use when translating "Figma to code", "design specs to components", or "implement design system".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates API documentation using OpenAPI/Swagger specifications with interactive documentation, code examples, and SDK generation. Use when users request "API documentation", "OpenAPI spec", "Swagger docs", "document API endpoints", or "generate API reference".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements API contract testing to ensure provider-consumer compatibility using Pact or similar tools. Prevents breaking changes with contract specifications and bi-directional verification. Use for "contract testing", "API contracts", "Pact", or "consumer-driven contracts".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.