Build typed, content-driven Nuxt applications with @nuxt/content. Use when working with content.config.ts, collections, queryCollection, Markdown or MDC rendering, content databases, hooks, custom sources, search, or Content v2 migrations.
Use when building NuxtHub v0.10.6 applications - provides database (Drizzle ORM with sqlite/postgresql/mysql), KV storage, blob storage, and cache APIs. Covers configuration, schema definition, migrations, multi-cloud deployment (Cloudflare, Vercel), and the new hub:db, hub:kv, hub:blob virtual module imports.
A development workflow that divides an implementation plan into independent tasks, assigns fresh coding agents to them, and reviews each result before a final review.
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, build tooling (tsdown/unbuild), API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, configuring dual CJS/ESM output, or setting up release workflows.
A workflow tool for creating isolated Git worktrees, which are separate working directories connected to the same repository. It coordinates parallel tasks without mixing their changes.
An API contract maintenance workflow that keeps the system's shared description of endpoints, data shapes, responses, errors, and state changes up to date. It supports adding, changing, deleting, or leaving API operations unchanged.
A behavior-driven development workflow that turns existing feature files into tests and product-code changes. BDD describes expected behavior in examples, while TDD means writing a failing test, making it pass, and then improving the code.
A requirements-review skill that examines an existing specification after it has been written. It finds important missing decisions or contradictions and folds confirmed answers back into the specification and its checklist.
A requirements-clarification skill that asks focused questions when a request is incomplete, contradictory, or open to several reasonable interpretations. It presents context and answer choices, then returns the confirmed decisions to the calling workflow.
A project-governance skill for creating or changing a repository's written rules. It keeps those rules modular by placing them in the smallest appropriate constitution file.
A data-model planning skill that maintains the project's authoritative description of stored data, including tables, fields, links, and indexes. It records whether each data element is added, changed, removed, or unchanged.
A testing-specification skill that turns business journeys into executable interface feature files and shared test vocabulary. It keeps the current frontend and backend behavior descriptions in the project's truth files.
Evaluate and refactor Gherkin feature files and DSL vocabularies so they can be implemented as test code with minimal inference. Use when converting test plans into Gherkin, reviewing or tightening Given/When/Then sentences, deciding Rule/Background/Scenario Outline/DataTable structure, or checking whether Gherkin and…
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.
Use when user asks to start or continue product work after clade-onboard confirms an onboard repo. Do not use for onboard status/readiness or registry drift.
★not rated 45
changed todayA36 tokens
originalMIT
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: