Bandersnatch0x

Bandersnatch0x/design-playbook

Skill Claude CodeCodex

UI craft and feedback quality. Use when polishing product UI (motion, loading/error feedback) or when a page reads as AI slop.

Bandersnatch0x/design-playbook

Skill Claude CodeCodex

Discover, validate, or draft a project-owned DESIGN.md before adding or revising UI in an existing frontend. Use during design-playbook initialization when a repository already has pages, components, themes, tokens, or styles; when new UI looks inconsistent with existing surfaces; when DESIGN.md may be missing…

Bandersnatch0x/design-playbook

Skill Claude CodeCodex

Route and orchestrate outcome-first product UI work. Use for answer, review, diagnosis, plan, prototype, build, or fix asks involving a page, dashboard, list, or settings surface, and for recirculating failed design review through declarations and evidence.

Bandersnatch0x/design-playbook

Skill Claude CodeCodex

Native-feel declaration for desktop apps. Use when a cross-platform desktop app (macOS+Windows) must feel indistinguishable from native. Invoked before ui-picker for native-desktop targets, not web pages.

Bandersnatch0x/design-playbook

Skill Claude CodeCodex

Reference intake contract from screenshot, URL, design file, or product analogy. Use when the user supplies visual/product reference before build, or when Keep/Change/Do not copy boundaries are missing for a design ask.

Bandersnatch0x/design-playbook

Skill Claude CodeCodex

Run evidence-backed UI acceptance. Use after generating a page, or when the user wants a design review or recirculatable critique against declared goals and success criteria.

Bandersnatch0x/design-playbook

Skill Claude CodeCodex

UI shell and component semantics. Use when scaffolding a product page (list, dashboard, settings, detail, agent-admin), or when the wrong template/Badge-Tag pairing is about to be coded.

Bandersnatch0x/design-playbook

Skill Claude CodeCodex

Declaration-first UI spec (six-layer spec.md) shaped through an S0-S6 interactive session. Use when turning a short product/UI ask into six-layer spec.md, or when goal, edge-state, acceptance, or evidence requirements are missing before build.