module-generator

Generates feature module shells and validates registry entries in Next.js apps.

Updated Apr 12, 2025

Search Tags:#workflow #development #schema #scaffold #registry #generator #module

Ready to run

npx skills add https://github.com/DavidKk/vercel-openapi --skill module-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: module-generator
Source: https://github.com/DavidKk/vercel-openapi/tree/main/.ai/skills/module-generator
Command: npx skills add https://github.com/DavidKk/vercel-openapi --skill module-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds and governs the creation of feature modules in a Next.js app, generating a consistent module shell and ensuring registry alignment to reduce manual setup time and drift.

Core Features & Use Cases

Generator-based module shell creation for new features, including layout, pages, API routes, and MCP scaffolds.
Registry-first workflow that updates .ai/specs/modules-registry.yaml and related module docs, ensuring CI alignment.
End-to-end module development workflow support: requirements audit, schema usage, generator execution, and validation.

Quick Start

Run the generator to scaffold a new module using your schema file at .ai/schemas/<module>.yaml.

Frequently Asked Questions about module-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I scaffold a new feature module in a Next.js app?▼

To scaffold a new feature module in a Next.js app, run the generator using your module schema file located at .ai/schemas/<module>.yaml to automatically produce the complete module shell. This generates layouts, pages, API routes, and MCP scaffolds.

What is a registry-first workflow for module development?▼

A registry-first workflow for module development governs module creation by updating the .ai/specs/modules-registry.yaml file and related docs before generating code. This ensures CI alignment and reduces configuration drift across feature modules.

Do I need a schema file to generate a Next.js module shell?▼

Yes, you need a module schema file at .ai/schemas and a registry entry in .ai/specs/modules-registry.yaml to generate a Next.js module shell. These inputs allow the generator and validation scripts to produce code and enforce consistency.

Can I extend an existing module instead of creating a new one?▼

Yes, you can extend an existing module by applying the generator and validation scripts to update the module shell. The workflow supports both adding new modules and extending existing ones while enforcing registry rules and schema validation.

What is the best way to ensure consistency across generated Next.js feature modules?▼

The best way to ensure consistency across generated Next.js feature modules is to use schema validation and enforce registry rules via the .ai/specs/modules-registry.yaml file. This governance reduces manual setup time and prevents configuration drift.