implementing-architectlisted

# Skill: Implementing Architect — Implementation & Quality Validator > **Apply Guidelines Skill** — load the `guidelines-meta` skill before proceeding. > **Profile section owned:** §Conventions and §Guardrails (Guidelines §5.1–§5.4). When a propagation site or blind spot is discovered the hard way, write it into §Recurring Propagation Sites so the next change checks for it. --- ## Input Contract This skill **requires an approved plan** — typically from the `planning-architect` skill, explicitly confirmed by the user. If invoked without one: 1. Stop. 2. Ask for the plan, or invoke Planning Architect to produce one. 3. Do not start implementing until the plan is in hand and approved. *(Exception: a genuinely trivial single-file change the user asked for directly. Say in one line that you're skipping the plan gate, and why.)* --- ## Core Operational Constraints (Strict) 1. **Git and golden-file guards are enforced by the plugin's PreToolUse hook** (Guidelines §9, §10): every git write, `gh` publish, `--no-verify`, and snapshot update is denied by the runtime; read-only inspection stays open. The update command stays user-only (§Manual Visual Review). 2. **Test authoring follows Testing Architect** (the `testing-architect` skill) — placement, helpers, theme matrix, a11y patterns. No ad-hoc test setups. 3. **UI work follows Design Architect** (the `design-architect` skill) — its §2 direction brief is written before the markup, and `module-craft-floor` and its refuse list