What problem does it solve?
Developers working on the moai-adk-go codebase need to know where each subsystem lives, how templates are embedded and built, and which workflows to follow when adding templates, hooks, agents, or SPECs. This Skill gives the four harness specialists a single domain-patterns reference so they stop guessing at source paths and build steps.
Core Features & Use Cases
- Architecture Quick Reference: Maps the four subsystems (CLI, template system, config, hook/CI) plus the SPEC lifecycle to concrete source paths like internal/cli, internal/template/templates, and internal/config/defaults.go.
- Template-First Build Cycle: Enforces the edit-templates-then-make-build-then-moai-update sequence so changes ship correctly through go:embed into user projects.
- Namespace Separation Contract: Clarifies which .claude and .moai paths are template-managed versus user-owned, and how moai update treats each.
- Use Case: A specialist asked to add a new hook consults this Skill, writes the bash wrapper in .claude/hooks/moai, wires it in settings.json, and adds the template source before running the neutrality audit test.
Quick Start
Ask the harness specialist to add a new template file to moai-adk-go and have it follow the template-first build cycle from this reference.