What problem does it solve?
Forge pack development helps you turn reusable integrations into a consistent, installable unit that cleanly ships templates, config defaults, dependencies, and optional migrations—without forcing users to manually stitch everything together.
Core Features & Use Cases
- Define the pack contract in pack.yaml: specify name, version, subpath, config defaults, rendered files, dependencies, generation behavior, and migrations.
- Control install vs generate output: use overwrite policies to ensure generated wrappers can be clobbered safely while user-editable code stays intact.
- Provide safe, composable conventions: ensure rendered code lands under pkg/<subpath>/ and avoids scaffold symbol collisions via per-pack package naming and careful wiring.
Use case: you are creating a new JWT authentication integration that installs validators/interceptors, adds the required Go modules, merges auth config into forge.yaml, and optionally renders DB migrations at install time.
Quick Start
Ask your AI to generate a complete pack.yaml plus template and migration scaffolding that matches the required schema, overwrite rules, and install lifecycle for a new Forge integration.
