Plan Tacbench architecture and execution work. Use when deciding repo structure, module boundaries, desktop versus web layering, ADRs, implementation phases, or how new features should fit the Tacbench workbench-first architecture.
Specify Tacbench's IDE-style GUI. Use when designing or refining the workbench layout, panel responsibilities, inspector behavior, diagnostics flows, layout presets, or reusable UI conventions for Tacbench.
Validate Tacbench gunpacks before export or publishing. Use when checking missing references, orphan files, hidden entry mismatches, language keys, texture coverage, dependencies, publish metadata, or release readiness for Tacbench packs.
Design or update Tacbench schemas and validators. Use when defining beginner-mode fields, advanced-mode source editing, required or deprecated fields, validation rules, or compatibility handling for guns, attachments, ammo, blocks, and melee plugins.
Prepare Tacbench project and release content for future community features. Use when drafting pack summaries, changelogs, dependency notes, author metadata, tags, release blurbs, or other publish-facing text for Tacbench projects.
Analyze TACZ gunpack folders or zip packs for Tacbench. Use when work involves scanning gunpack structure, building a resource graph, tracing references, finding hidden entries, alias relationships, orphan files, missing language keys, or compatibility anomalies in Tacbench sample packs.