Claude Skills by AlexCiortan

Survey, sanity-check, spec-scoped commit, branch lifecycle, and the close gate (Part 6)

The design surface for UI projects (Part 5c): the design-heavy routing test, locked redlines as spec contracts, the bundle rule, design QA on the branch, /insights at gates

Diagrams as close-gated source: the routing test that picks a type, the drawing and truthfulness rules, altitude and layout, node evidence, the Design sketch at creation and the sync at close

Run a stage-gate transition session per Part 7b (verify the gate leg by leg, reconcile the next stage's backlog, spec its first entry)

Write the numbered journal entry for a substantive session per Part 4 (raw notes, what surprised you, no narrative smoothing)

The capability-tier escalation rules for Planner and Builder sessions (Part 2)

Bootstrap a new project with the Spec-Driven Development Framework (Part 8)

The Planner role's operating loop, read budget, and park-do-not-improvise rule (Parts 7 and 2)

Retrofit the Spec-Driven Development Framework onto an existing codebase (Part 8b)

The spec template and the Closing report contract (Appendix C and Part 5)

Upgrade a framework instance to the edition bundled in this plugin (Part 8c)

Idempotent framework health check of the instance (Part 6). Reports findings, fixes nothing without approval.

QA Pass 1 binding for web UIs (framework Part 5). Playwright driving Chromium against the production build; emits the machine-readable qa-pass-1 verdict block plus the evidence report for the Closing report.