BuildModule

Scaffold and validate forge modules for Claude Code, Gemini CLI, Codex, and OpenCode.

5|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/N4M3Z/forge-core --skill buildmodule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: BuildModule
Source: https://github.com/N4M3Z/forge-core/tree/main/skills/BuildModule
Command: npx skills add https://github.com/N4M3Z/forge-core --skill buildmodule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing, building, and validating forge modules is complex and error-prone without a standardized blueprint.

Core Features & Use Cases

  • Structured module layout and lifecycle: module.yaml, defaults.yaml, config.yaml, agents/, skills/, hooks/, bin/, src/, and tooling to enforce conventions.
  • Core mandates: config conventions, separation of concerns, lazy compilation, and verification to ensure portable, reliable modules.
  • Use Case: Quickly scaffold a new module with consistent structure and validated packaging for Claude Code, Gemini CLI, Codex, and OpenCode.

Quick Start

Run the module scaffold tooling to generate a compliant Forge module structure and begin validation.

Frequently Asked Questions about BuildModule

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

FAQPage Schema
How do I scaffold a new forge module with a standardized directory structure?

To scaffold a forge module, run the module scaffold tooling to generate a compliant structure including module.yaml, defaults.yaml, config.yaml, and directories like agents/, skills/, hooks/, bin/, and src/ for consistent design and validation.

What is the best way to package modules for Claude Code, Gemini CLI, Codex, and OpenCode?

Packaging modules across Claude Code, Gemini CLI, Codex, and OpenCode requires enforcing config conventions, separation of concerns, lazy compilation, and verification to ensure portable, reliable cross-provider module structures.

Does forge module validation enforce separation of concerns and lazy compilation?

Yes, forge module validation enforces core mandates including separation of concerns, lazy compilation, config conventions, and verification to ensure modules are portable and reliable across different providers.

Can I audit an existing forge module layout against standard conventions?

Yes, you can audit existing forge modules by validating their layout against standardized artifacts like module.yaml, defaults.yaml, config.yaml, Makefile, and plugin.json to ensure compliance with enforced structural conventions.

Why does cross-provider module creation fail without standardized artifacts like module.yaml?

Cross-provider module creation fails without standardized artifacts because it lacks a unified blueprint to enforce config conventions, separation of concerns, and lazy compilation, resulting in non-portable, error-prone module structures.