Sworm

Sworm's authoritative design system. Tokens, surfaces, type scale, shadows, motion, iconography, voice, and component recipes. Use this skill whenever you touch UI in Sworm — building new components, refactoring styling, updating primitives, reviewing design choices, or designing a new surface (dialog, panel, row, menu). Trigger on any edit to src/app.css, src/lib/components/ui/**, or Svelte files under src/lib. Also use when questions arise about Sworm's palette, typography, surface hierarchy, focus states, shadows, radii, or iconography. Supersedes extensions/handoff/ and extensions/Sworm Design System/.

Evidence-first debugging loop for bugs that resist a first fix. Use when a bug has already survived one attempted patch, when the user says "still broken", "you keep guessing", "stop making assumptions", "shotgun", or explicitly asks to debug/root-cause an issue. Also trigger on UI/focus/rendering/lifecycle bugs, Svelte `$effect` misbehavior, Tauri command wiring failures, and anything where the failure mode is not directly visible in the diff. Do NOT use for trivial typos, compile errors, or bugs where the cause is already stated in the stack trace.

Review Sworm changes with strict, skeptical, codebase-aware scrutiny. Use when the user wants a critical review of code, a PR, or staged changes and wants realistic issues surfaced around Svelte 5, Tauri, Rust boundaries, UI primitive reuse, architecture, design consistency, and comment style.

Lightweight i18n workflow guidance. Use only if Sworm adopts an i18n system and you are adding or changing user-facing strings across locales.

Scaffold a new Svelte component for Sworm. Use when creating reusable UI or terminal/project-specific frontend components.