956 skills · sorted by relevance
Turn specifications and designs into working code using test-driven development: write failing tests, implement enough code to pass, then refactor. The workflow also covers error handling, performance improvements, documentation, and coordinated changes across components.
Turn an approved specification into pseudocode, a plain outline of program logic, and an architecture defining module responsibilities and API inputs and outputs. After user confirmation, proceed with implementation and unit tests based on those designs.
Review implemented features against their requirements, add missing tests, and check performance constraints. Produce documentation, a table linking requirements to code and tests, and evidence showing whether the feature is ready for deployment.
Carry out Docupost tasks through Rube MCP, an agent connection to external tools. Discover supported actions, check their required inputs and the service connection, then execute operations according to the specifications returned by tool search.
Turn a feature idea or fix request into an OpenSpec implementation plan. The skill examines the project and prepares the required proposal, specification changes, design, and tasks for review, without changing project code.
Archive several OpenSpec changes together after reviewing their documents and task progress. The skill checks code to resolve overlapping specification updates, syncs the selected updates, and reports which changes were archived, skipped, or failed.
Implement pending tasks from an OpenSpec change using its specifications and design documents. The skill updates task checkboxes, confirms progress, supports resuming unfinished work, and pauses when requirements or implementation issues need clarification.
Compare an implementation with its OpenSpec specifications, tasks, and design decisions before archiving the change. Get a report on completion, requirement coverage, and consistency, with prioritized issues, actionable recommendations, and explicit limits where evidence is missing.
Plan the visual and narrative direction of HyperFrames videos, including colors, fonts, composition, narration, and scene rhythm. The skill helps apply existing design specifications, choose a style, and check whether the finished work follows that direction.
Create HeyGen avatar videos with a chosen presenter, voice, exact script, and backgrounds for each scene. Use photos as presenters, generate transparent WebM files for compositing, or produce batches of videos with consistent specifications.
Turn a math or science video idea into a detailed scene plan. Research the topic, clarify the audience, and outline visuals, narration, transitions, and implementation notes for Manim, an animation tool.
Add or update a focused, reusable test when fixing bugs or changing behavior. Keep it in the project's existing test structure, verify the relevant change, and maintain coverage as the expected behavior evolves.
Consult Sally, a UX and UI specialist, to translate user needs into interaction designs and UX specifications. The role considers unusual situations as well as everyday use, helping communicate clear design intent to architecture and implementation work.
Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.
Turn API code into documentation covering available operations, inputs, outputs, authentication, and errors. Add practical request examples and usage guides, with OpenAPI specifications or Postman collections where possible to help developers explore and use the API.
Organize API documentation work from endpoint discovery to OpenAPI specifications, developer guides, and tested code examples. The workflow also covers interactive documentation, documentation sites, and maintenance, helping select the phases and supporting skills needed for a task.
Create or update API documentation from source code. Produce OpenAPI or Swagger specifications, endpoint descriptions, parameter tables, response examples, authentication guides, error references, and usage examples that explain how to call the API.
Create or update API documentation from source code. The skill produces OpenAPI/Swagger specifications, descriptions of API operations, parameter and response references, authentication guidance, and practical examples for developers integrating an API.
Generate API documentation from source code, including OpenAPI/Swagger specifications. Describe endpoints, the addresses used to access API operations, with parameters, responses, errors, authentication guidance, and examples in cURL, JavaScript, and Python.
Organize features, bug fixes, and refactors as Conductor tracks, units of related work. Create specifications and task plans, maintain status and dependency records, and preserve completed work with verification details and commit references.
Design and review REST and GraphQL APIs with consistent naming, data structures, error responses, pagination for large result sets, and versioning strategies. Helps teams define shared standards and plan changes that existing clients can adopt gradually.
Research products against a budget and required features, then compare prices, specifications, and review findings in a table. Get one recommendation with its tradeoff, plus a price history check for deals when available.
Clarifies missing product or implementation decisions through one focused question at a time. It records answers and produces a short brief or specification once enough is known, while investigating facts that can be found directly.
Compare project documentation with existing code to identify missing core features. Rank the gaps and create GitHub issues with practical specifications, implementation plans, acceptance criteria, effort estimates, and dependencies.