671 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
日本語の概要は準備中です。原文の説明を表示しています。
A brand product-launch email — masthead with wordmark, hero image block, headline lockup with skewed-italic accent, body copy, primary CTA, and a specifications grid. Pure HTML email layout (centered single column, table fallback). Use when the brief asks for an "email", "newsletter blast", "MJML", "product launch email", or "email template".
日本語の概要は準備中です。原文の説明を表示しています。
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification.
日本語の概要は準備中です。原文の説明を表示しています。
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user wants to visualize data. It intelligently selects the most suitable chart type from 26 available options, extracts parameters based on detailed specifications, and generates a chart image using a JavaScript script.
日本語の概要は準備中です。原文の説明を表示しています。
SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion). Use when: new features, complex implementations, architectural changes. Skip when: simple fixes, documentation, configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
日本語の概要は準備中です。原文の説明を表示しています。
Run the SPARC Refinement and Completion phases — review code, improve test coverage, validate against specification, and generate documentation
日本語の概要は準備中です。原文の説明を表示しています。
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
日本語の概要は準備中です。原文の説明を表示しています。
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification.
日本語の概要は準備中です。原文の説明を表示しています。
Load the body before the first implementation edit for a bug fix or behavior change, or when the user or governing specification makes reusable tests a deliverable. It keeps the smallest focused test with the delivered project and updates coverage when behavior changes. Do not load for greenfield work unless reusable tests are explicitly required, behavior-preserving refactors, verification-only work, plan/review/explanation/documentation/formatting/generated-output-only work, explicit no-change or no-tool work, or when the user declines tests.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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"
日本語の概要は準備中です。原文の説明を表示しています。
Generates complete, production-ready REST API endpoint specifications for any system or domain the user describes.
日本語の概要は準備中です。原文の説明を表示しています。
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
日本語の概要は準備中です。原文の説明を表示しています。
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
日本語の概要は準備中です。原文の説明を表示しています。
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/
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Use when creating a new branch, naming a branch, or checking whether a branch name complies with the spec.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。