plus-uno

Scaffolds a NEW prototypes prototype from a Figma design frame (a page, screen, or flow) — React + Vite + PLUS design system, mirroring the prototypes/home-redesign reference structure. Use when a designer pastes a Figma URL (optionally with a Notion PRD link) in Slack and asks the bot to build a prototype, or when figma-implement-design.yml fires via repository_dispatch. Distinct from uno-implement, which updates an existing DS-library component.

Implements a design-system change end-to-end: both the component source (.jsx, .scss) and its Storybook docs (.stories.jsx, .mdx) update together in one Claude pass. Use when a designer types `implement <component>` in Slack after the polling flow created a Notion PRD, or when figma-implement.yml fires via repository_dispatch.

Diagnose-only design review with three scenarios: (1) stage-lens review of any artifact exiting prototyping — DS, product-intent (UNO), and accessibility lenses in parallel at stage-appropriate depth; (2) the handoff gate (DS / UNO / a11y) before a package publishes; (3) Design QA — Figma spec vs the QA build when a Roadmap card hits Ready for QA. Use when the user says "review this", "critique", "check against the design system", "poke holes", "run design QA", when an artifact exits uno-prototype, before uno-publish hands off, or when Dev Status flips to Ready for QA (RTT). Mandatory input: a one-line artifact manifest (fidelity / tools / PRD link). It never fixes what it finds — fixes route to uno-prototype (artifact) or uno-maintain (harness/docs).

Monthly conventions-integrity sweep: executes the uno-maintain integrity checklist headlessly and files intakes per the shared headless-intake contract. This prompt is an ADAPTER — the checklist and the intake pipeline live in the skill; this file only adds the headless execution contract. Registry row (and lifecycle status): docs/conventions/automations.md.

Weekly post-ship reconciliation check: finds Roadmap cards that shipped recently and verifies the DS + harness reflect built reality, filing intakes per the shared headless-intake contract. Adapter only — the reconciliation duty AND its check set are owned by skills/uno-maintain/references/method.md §6 (post-ship reconciliation). Registry row (and lifecycle status): docs/conventions/automations.md.

Weekly digest of auto-applied Tier-1 fixes: reads docs/evals/runs/digest.jsonl, composes the week's digest per Slack conventions, and posts it to #plus-design. Adapter only — what counts as Tier 1, why the digest exists, and the digest.jsonl row shape are owned by skills/uno-maintain/references/method.md §4. Registry row (and lifecycle status): docs/conventions/automations.md.

Keeps the harness itself current. Captures a flagged issue — improvement, inaccuracy, inconsistency, or bug — routes it across the three estates (codebase, Figma, Notion) to one of eleven targets, drafts the fix, and runs the tiered pipeline: Tier-1 trivial fixes (typos, links, dates only) apply directly with a weekly-digest line; Tier-2 changes ship as a PR + PRD pair through Slack review to a verdict. Also runs the standing sweeps (staleness, hygiene, shipped watchdog) and captures lessons into docs/knowledge/. Use when the user says "file an intake", "this doc is stale", "the spec and Storybook disagree", "the skill/persona is off", "fix this typo", "run the staleness sweep", "document this", "capture this lesson", or after a feature ships and the DS/harness need reconciling.

Puts finished-enough design work in front of people, on one of two rails that never re-merge: share for feedback (async bundle — Loom + live preview + Decisions DB + Figma replica — or a sync user study) or hand off to development (componentize, Handoff Spec, rails propagation, DS/UNO/a11y review, dev + PM + stakeholder sign-off, marketplace entry). Use when the user says "share this for feedback", "post a share-out", "set up a feedback session", "hand this off to dev", "publish", "submit to market", or "register this prototype".

Gathers context that does not exist yet: preliminary data analysis, user-study guides, SME and participant sourcing, Slack/analytics evidence sweeps, and codebase/design-system discovery. Instrument-first — the study guide is written before any conversation — and it hands cited findings to uno-synthesize rather than concluding. Use for fuzzy hunches ("tutors seem to churn — can we look into it?"), discovery questions ("do we already have a component for X", "where is", "how does"), sourcing knowledge-holders ("who actually knows how Y works?"), or evidence toward a go/no-go. Not for summarizing prior studies, ingesting pasted context, or drafting PRDs — that is uno-synthesize.

Distills gathered context — Slack thread exports, interview transcripts, meeting notes, analytics pulls, docs — into a documented Findings & Takeaways doc and, on the designer's explicit go, a PRD with its paired uno-blueprint write. Use when the user says "synthesize this", "summarize the findings", "what are the takeaways", "what did people say", "what would we build", "draft the PRD", "write the update summary", or has collected raw context that needs distilling toward a build/no-build decision. Ingests existing context only — running new queries against raw data is uno-research.