competitor-recon-weapon

The arsenal for competitor-recon-guardian. It turns a competitor or reference product into auditable evidence: authenticated UI captures, public-artifact facts, and client-bundle constants, synthesized into a per-surface gap table and a phased build-order recommendation that feeds PRDs and strategy verdicts owned by other Guardians.

This weapon is generalized from a real hand-run teardown: Assistable versus the cuantico-sms portal, 2026-07-02. Throughout the guides, "Assistable" is the worked instance, never a template to copy. The schemas, checklists, and directives are domain-agnostic.

First action when this weapon is loaded

Read these in order:

1. guides/00-principles.md -- the eight hard rules (never mutate live data, read facts not prose, owner-assisted fallback, verify across states, PII discipline, license-scope-per-artifact, route-don't-render, no em dashes) with their justifications.
2. guides/01-teardown-methodology.md -- the overall method and the four UX-analysis techniques the walkthrough is built on.
3. guides/07-gap-analysis-synthesis.md -- the output you are building toward (the gap-table schema + phased build order), so every capture step is aimed at it.

Then walk the capture and archaeology guides (02 through 06) as the specific task requires, and use the templates in templates/.

The eight hard rules (full text in guides/00-principles.md)