What problem does it solve? Defining consistent bootstrap metadata for OpenCode skills is error-prone: scaffold commands, verification commands, runtime smoke checks, and dependency fields often drift across framework, UI kit, API client, and testing skills. This Skill provides a single specification for producing clean, executable, boundary-scoped opencode-bootstrap-json fenced blocks. ## Core Features & Use Cases - Metadata Field Specification: Defines role, category, frameworks, requiresPrimarySkills, order, packageManager, scaffoldCommand, verificationCommands, runtimeSmokeCommand, and runtimeSmokeHealthUrl with clear boundary rules per skill type. - Script Launcher Pattern: Standardizes short launcher commands that delegate multi-step file generation to bundled .cjs scripts with preseeded-directory fallbacks. - Boundary Enforcement: Separates framework scaffold, UI kit, API client, testing, Docker, and docs-only README add-ons so each skill only expresses its own business scope. - Use Case: When authoring a new Nuxt UI kit add-on skill, use this Skill to emit a compliant metadata block with empty-mutation verification launchers and correct requiresPrimarySkills wiring. ## Quick Start Ask the assistant to generate an opencode-bootstrap-json metadata block for a new testing add-on skill following the boundary rules.
