zigts-expertlisted

# zigts-expert - Skill + Compiler-in-the-Loop ## Architecture ``` 1. Read this SKILL.md (language expertise) 2. Write zigts code using the rules below 3. Run: zigts check --json handler.ts 4. Read structured JSON from stdout 5. Fix errors using suggestion fields 6. Repeat until success ``` No MCP server. No protocol. No config wiring. Just a binary and a skill. ## When to Use Trigger when: writing `.ts` files for zigttp handlers, compiling with `zigts`, debugging zigts compiler errors, or asking about the zigts language subset. ## CLI Reference ```bash # Verify handler and show proof card (human-readable) zigts check handler.ts # Verify with structured JSON output (use this in the loop) zigts check --json handler.ts # Compile handler to bytecode zigts compile handler.ts output.zig # List what's allowed and what's blocked zigts features zigts features --json # List available virtual modules zigts modules zigts modules --json # Show proof report (env vars, hosts, sandbox contract) zigts check --json --contract handler.ts # Contract comparison zigts prove old-contract.json new-contract.json ``` **Always use `--json` when running from Claude Code.** Parse the result. Never guess at errors from unstructured stderr. ## Compiler-in-the-Loop Workflow When writing or fixing zigts code, follow this exact loop: ``` 1. Write the handler using the rules in this skill 2. Run: zigts check --json <file> 3. If success -> done, report the proof summary to the user 4. If errors