Implement and verify Svelte 5 (SvelteKit) UI changes with rendered evidence. Use when building pages, forms, components, or shadcn-svelte/Bits UI primitives; fixing responsive, dark-mode, or accessibility issues; writing Storybook stories; or collecting screenshots for a visible change.
State what a change means for users and the business in plain words, as "When does , . Before, ." Use when writing the impact part of a PR description, change note, changeset, release note, incident summary, or status update, or when someone asks what a change does for users.
Model an entity's lifecycle (status, state, phase) as an explicit state machine with a pure decide function, one guarded write path, and events from a durable record. Use when adding or changing a status field, a transition, or a reaction to one, when several writers set the same status, or when moving ad hoc status…
Add, write, customize, or review shadcn-svelte components built on Svelte 5, Bits UI, tailwind-variants, and Tailwind v4 tokens. Use when adding a primitive with the shadcn-svelte CLI, changing a variant, adding a theme token, wrapping a Bits UI part, publishing primitives from a component package, or re-syncing a…
Manage macOS system defaults, Homebrew casks, Lix or Nix daemon settings, and Home Manager packages and dotfiles with a nix-darwin flake. Use when adding packages or casks, changing macOS defaults or launchd agents, debugging flake evaluation or brew bundle failures, or activating changes from an agent shell.
Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.
★not rated 23 3d agoA64 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: