Loading...
Loading...
Found 505 Skills
iLEAP technical specs for exchanging logistics emissions data (ISO 14083 / GLEC Framework) via the PACT protocol. Use when implementing iLEAP APIs, data models (ShipmentFootprint, TCE, TOC, HOC, TAD), PACT DataModelExtensions, or conformance testing. Language-agnostic.
Use the Docyrus CLI (`docyrus`) to interact with the Docyrus platform from the terminal. Use when the user asks to authenticate, list apps, query/manage data records (`ds`), manage dev app data source schema objects (`studio`), send API requests, switch environments/tenants/accounts, or discover OpenAPI specs via the `docyrus` command-line tool. Triggers on tasks involving docyrus CLI commands, terminal-based Docyrus operations, `docyrus ds list`, `docyrus studio`, `docyrus discover`, `docyrus auth`, `docyrus env`, or shell-based Docyrus workflows.
Reviews REST API designs for quality, consistency, and breaking changes. Lints OpenAPI specs, generates API scorecards, and detects breaking changes between versions. Use when designing APIs, reviewing API contracts, or managing API versioning.
Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.
Use this skill when > Convert plans, specs, or requirements into independently-grabbable vertical slice issues. Each slice is a thin but complete end-to-end cut through all layers (schema, API, UI, tests). Classifies issues as HITL (human-in-the-loop) or AFK (automated, no human interaction needed).
Drives interactive requirement discovery to produce spec files. Use when the user says "spec this", "write specs", "create specs", or "run the spec skill".
Collect products from Sephora — title, price, specs, images, availability. Use when the user wants to research products or collect catalog data.
Extract a behavioral specification from a source-code bundle — a handful of files up to a whole 500+ file application. Produces reproducible, stack-neutral specs another engineer or LLM could use to rebuild the same observable behavior without reading the original source.
Structured TDD workflow that decomposes features into small specs and implements them one at a time through the strict red/green/refactor cycle. Use this skill whenever the user wants to build, implement, or fix something using TDD, test-driven development, or a test-first approach. Also trigger when the user says "red green refactor", "write tests first", "one test at a time", "failing test first", or asks to develop something incrementally with tests driving the design. Even if the user just says "use TDD" or "do it test-driven" alongside a feature request, this skill applies. Do NOT trigger for: running existing tests, adding tests after the fact to untested code, fixing a single failing test, or test infrastructure setup.
Use when an app has to move onto a design system that already exists, such as "migrate the app to our design system", "move every screen onto the new components", a rollout, or an adoption audit. When design-system-boss is installed and nobody has checked the system's specs, the boss triages first, since a migration copies a weak system's gaps everywhere. Not for making the system.
Generate comprehensive Product Requirements Documents (PRD) from idea validation files. Use when users ask to "create a PRD", "generate product requirements", "write a PRD", or want to turn validated ideas into actionable product specs. Works with idea.md and validate.md files from the idea-validator skill.
Archives completed changes and merges specification deltas into living documentation. Use when changes are deployed, ready to archive, or specs need updating after implementation. Triggers include "openspec archive", "archive change", "merge specs", "complete proposal", "update documentation", "finalize spec", "mark as done".