529건 · 관련도순
Authoring standalone and cross-team specifications: PRD/SRS/HLD/LLD, staged L0-L4 unified packages, BDD acceptance criteria, and traceability. Use for technical or multi-audience documentation; not implementation or architecture decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture the user's UX vision in two documents: DESIGN.md for how the product looks and EXPERIENCE.md for how it behaves. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform ideas into detailed visual specifications through scenario-driven design
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate visual and text assets from specifications through AI-powered creative production
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build Model Context Protocol servers from specifications. Use when creating an MCP server for a tool, resource, or service that AI agents should access. Generates tool definitions, resource handlers, and test suites in TypeScript or Python (FastMCP).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications. Triggers on reference docs, API reference, function reference, parameters table, symbol documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
BDD-Driven Mathematical Content Verification Skill Combines Behavior-Driven Development with mathematical formula extraction, verification, and transformation using: - Cucumber/Gherkin for specification - RSpec for implementation verification - mathpix-gem for LaTeX/mathematical content extraction - Pattern matching on syntax trees for formula validation Enables iterative discovery and verification of mathematical properties through executable specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate creative direction for ad campaigns — visual concepts, copy variants, video scripts, image specifications, and A/B test matrices. Platform-aware with format specs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parses AsyncAPI 2.x/3.x specifications to generate event-driven architecture catalogs using the AsyncAPI Generator. Produces channel documentation, message schema validators, and EventBridge rule templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates event-driven architecture documentation from AsyncAPI 3.0 specifications. Uses the AsyncAPI parser-js library to extract channels, message schemas, and server bindings for Kafka and RabbitMQ.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates translation of motion designer video specifications into working Remotion code by coordinating specialized agents. Acts as pipeline coordinator that delegates to remotion-scaffold, remotion-animation, remotion-composition, and remotion-component-gen. Use when you have a complete VIDEO_SPEC.md and need full Remotion implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map testable surfaces, audit existing tests for quality, and write test specifications that prevent AI shortcuts. Use when asked to "audit tests", "specify tests", "test architect", "map test coverage", or invoke /test-architect. Two modes — audit (evaluate existing tests against Beck's principles) and specify (write test specs for new code). Powered by Carmack × Beck quality-testing.md reference doc. Stack: Next.js App Router / TypeScript / Vitest / Cypress / tRPC / Prisma / Neon.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture the user's UX vision in two documents: DESIGN.md for how the product looks and EXPERIENCE.md for how it behaves. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Process external specifications through transformation, classification, gap analysis, component discovery, and decomposition. Creates workflow items with classified context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided requirements gathering through structured questions to create comprehensive specifications. Produces a complete requirements document via non-blocking conversational interaction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Templates and validation for writing product specifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze specifications and decompose into independent changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform Markdown or text specifications into human-readable HTML documents with summaries, reordered structure, visual explanations, diagrams, charts, and traceability to the source. Use when asked to convert a spec, requirements document, API spec, product spec, design doc, or technical document into readable HTML, especially when the user wants summarization, restructuring, diagrams, graphs, images, or visual aids rather than a literal Markdown-to-HTML conversion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce publication-ready 2D graphics with proper DPI, color profiles, typography, and export formats for print and digital media. Use when preparing figures for academic journal submission, creating graphics for print publications, ensuring graphics meet publisher technical specifications, exporting visualizations for web with proper optimization, or creating multi-format exports from a single source.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify that implementation code faithfully implements its specification — checks function contracts, API contracts, and protocol compliance against source specifications
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates comprehensive documentation from code, APIs, and specifications. Creates API documentation, developer guides, architecture docs, and user manuals with examples and tutorials.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.