embed-code-go

Encodes the embed-code-go Go implementation policy and recurring pitfalls. Use whenever writing, modifying, refactoring, debugging, or reviewing Go code in this repository, especially CLI/config parsing, parser state transitions, embedding behavior, fragmentation, filesystem handling, error reporting, package APIs, formatting, vetting, and build verification.

The embed-code-go authority on writing and reviewing Go tests. Use when adding, restructuring, or reviewing tests for Go production code, parser behavior, embedding flows, fragmentation, CLI/config validation, fixtures, malformed inputs, regression coverage, focused go test commands, or full suite verification. go-engineer remains the baseline for Go inside test helper code.

Writes, edits, and restructures embed-code-go documentation. Use when asked to create or update README.md, showcase guides, PROJECT.md, AGENTS.md, skills, Markdown fixtures, contributor notes, examples, command snippets, Go doc comments, or inline explanatory comments. Verifies claims against current Go code, tests, fixtures, and project flows.

Reviews documentation changes in embed-code-go: Go doc comments, inline comments, README.md, showcase guides, PROJECT.md, AGENTS.md, skills, Markdown fixtures, and user-facing examples. Use when a diff touches prose, documentation comments, embedding syntax docs, command examples, architecture/package maps, or agent instructions. Read-only; does not run builds unless explicitly asked.