Assess and install the kromatic-dev-stack personas against this user's actual setup. Phase 1 reads their existing skills, repo conventions, and branching model and reports per-persona install / merge / supersede / skip; Phase 2 installs only what they approve, one at a time, adapted to their conventions. Use when adopting, installing, renaming, or re-evaluating the bundle.
Aristotle the Analyst persona — Answer GA4 to BigQuery conversion and prioritization questions for your web properties, with visitor-based definitions, Bayesian impact-first ranking, route ownership attribution, and strict JSON-first outputs.
Lean default development workflow for branch choice, incremental commits, merge/promotion boundaries, and concise reporting.
UX director for all experience design — human and agent. Defines JTBD, identifies user types, and runs the human-facing and agent-facing design-intent passes for detailed specification and verification.
Top-level orchestrator for multi-repo planning and execution with complexity gating, issue-graph enforcement, fanout orchestration, repo-local lane safety, and retrospective governance.
Occam sub-skill — comprehensive single-repo audit producing (a) a decision sheet for a human and (b) an issue graph for implementers with no session memory. Diagnosis only, never fixes. Use when asked to audit, review, or assess the health of a repository.
Product strategy and scope review before implementation. Challenges assumptions, sharpens MVP slices, and sequences incremental delivery. Use before planning or coding begins.
Perlman sub-skill — retrieve and cite the constraints that already bound this request, never invent them. Runs before scope-lock (Step 5) in the single process. Reads company-level strategy (your durable strategy record) and product-level positioning docs for the two-tier constraint model; anything that cannot be traced to a source artifact surfaces as an open question, not a boundary.