Loading...
Loading...
Found 726 Skills
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
Create new capabilities and skills systematically. Architects, documents, and implements reusable skills with proper specifications.
Use when writing effective BDD scenarios including acceptance criteria, edge cases, and scenario organization. Use when defining behavior specifications.
Prepare detailed, professional prompts for Google Imagen 3/4 image generation. Supports character, environment, and object prompts using natural language with technical photography specifications. Extensible support for multiple art styles via reference files.
Generates test code from specifications, components, and API endpoints. Creates unit tests, integration tests, and E2E tests following project testing patterns and conventions.
Task Closure Specification, including log generation and optimization analysis. Applicable to the closure phase after major deliverables are completed.
This skill should be used when implementing DDD tactical design patterns in Go, including Entities, Value Objects, Aggregates, Repositories, Domain Services, Domain Events, Factories, and Specifications.
Guidance for writing git commit messages that follow the Conventional Commits 1.0.0 specification. Use when preparing commit messages, summarizing code changes for a commit, or validating commit text for compliance.
Apply SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) for systematic development. Use for feature development, TDD workflows, and structured problem-solving.
Apply OpenEd's visual brand identity to presentations, websites, and digital materials. Specifies colors, typography, spacing, and design specifications for consistent visual branding across all OpenEd materials.
Generate or sync a "Living Specification" (docs/spec.md) from source code to eliminate doc-code drift. Use when creating, updating, or reviewing architecture documentation for a directory or module. Triggers on requests like "generate spec", "create spec.md", "sync documentation", "update architecture docs", "/spec.doc", or when asked to document a codebase directory.
Systematically gather comprehensive travel itinerary requirements through structured discovery questions, MCP-powered research (Perplexity, Exa), and expert detail gathering. Use when users request travel planning, itinerary creation, or trip assistance requiring deep research and personalized requirements gathering. Outputs detailed requirements specification with day-by-day itineraries.