A coding-work execution skill that follows a task list one unlocked task at a time, or one explicitly parallel group. It verifies each task, marks it complete, and continues until the plan is delivered.
A requirements-to-examples skill that turns a new plan's specification into business-readable acceptance scenarios. These scenarios use Gherkin, a Given/When/Then format, to describe the journeys the planned change should support.
A writing guide for API specifications in OpenAPI 3.0, a standard format for describing web APIs. It defines naming and file-location rules and links API operations to readable test steps.
A configuration guide for SpecFormula, a testing framework that uses API specifications and database definitions to support declarative tests. It explains how to set paths, data sources, database types, and instruction mappings in isa.yml.
A guide for defining business entities and their database tables in SpecFormula. It covers the mapping file and SQL table definitions, including database-specific SQL such as PostgreSQL or MySQL syntax.
A guide for writing SpecFormula feature files using Gherkin, a plain-language format for describing behaviour with Given, When, and Then steps. It explains how those steps map to configured actions such as setting up data or calling an API.
A requirements-planning skill that turns a natural-language feature request into a new, numbered plan package. The package contains a specification, a requirements checklist, and an initial record of specification changes.
A skill that turns a software plan, research, interface drafts, and specification changes into an ordered tasks.md checklist for implementation. It also runs the project's canonical doctor check, meaning its standard health or validation command.
A research and technology-planning skill for a software change. It produces a research document for the current plan and updates the project's shared record of its technology choices.
A handoff format for recording what changed in the project's authoritative specifications. It lists additions, modifications, deletions, or confirmed no-change areas for each specification owner.
A planning skill for designing a software interface and making static HTML mock-ups from a feature plan and the project's current requirements. It keeps these drafts separate from the project's authoritative specifications.
A workflow for upgrading versions across project dependencies, automation actions, installed tools, and agent skills. It first identifies what kind of upgrade is being requested and whether the change belongs in the repository or only on a machine.
Code quality, error handling, shell safety, language, and maintainability rules. Use when implementing or refactoring code, scripts, or language-specific components.
Database, schema, storage, logging, and data-path rules. Use when changing persistence, migrations, queries, RLS, database environments, or application logging; also before running integration tests, needing a test or dev database, running any supabase CLI command, or deciding where the dev DB lives. Also use when…
Frontend, interaction, accessibility, localization, and UX integrity rules. Use when changing UI, forms, display values, interactions, translations, or visual completeness.
Runtime, deployment, local service, and infrastructure rules. Use when changing Cloudflare, Nitro, APIs, tunnels, ports, service URLs, or operational configuration.
Authentication, secrets, production access, and security boundary rules. Use when changing identity, authorization, credentials, production MCP access, or user lifecycle behavior.
Session, delegation, handoff, work tracking, and follow-up rules. Use when planning work, delegating, opening worktrees, coordinating agents, or ending a session.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: