Keep code consistently formatted and lint-clean before completing work. Use when finishing an edit, fixing linter/formatter failures, or setting up format/lint commands for Go, TypeScript/JavaScript, and Markdown.
Review code (your own or others') for correctness, design, and risk before it merges. Use when reviewing a diff or pull request, doing a self-review before opening a PR, or giving structured, prioritized feedback. For layer violations, smell fixes, and untested changes in Go, see go-design; for shallow or leaky…
Design reusable React component APIs that scale — compound components, lifted state, generic context, explicit variants. Use when a component is growing boolean props (isThread, isEditing…), when building a component library, or when reviewing component architecture. Includes React 19 API changes.
Write clear, atomic commits using Conventional Commits. Use when committing changes, writing or rewriting a commit message, or splitting work into reviewable commits.
Design and build data-dense dashboards, admin panels, analytics views, and operational SaaS interfaces (Operate mode) — information hierarchy, KPI cards, tables, filter bars, charts, empty/loading states, and density controls. Use when building back-office tools, observability UIs, financial/ops consoles, CRM views…
Architect CSS custom-property design token systems (3-tier primitive → semantic → component tokens) using OKLCH color ramps, 4-tier text hierarchy, dedicated control tokens, spacing/radius/elevation scales, and first-class light/dark theming in Tailwind CSS v3/v4 and shadcn/ui. Use when setting up globals.css…
Create distinctive, production-grade frontend interfaces with high design quality and zero "AI slop". Use when the user asks to build or restyle web components, pages, landing pages, or applications (React, Next.js, Vue, Svelte, or plain HTML/CSS) where visual identity, typography, color, motion, and composition…
Test web frontends (React/Next.js) effectively. Use when writing or fixing unit/component tests with Vitest + Testing Library, end-to-end, a11y, and responsive layout tests with Playwright, or testing shared WebMCP/RonyKit stub handlers.
Write idiomatic, modern Go (1.25+/1.26) using current language and stdlib features and the RonyKIT package map. Use when authoring or reviewing Go code, choosing between stdlib, x/, and third-party helpers, or working with errors (rony/errs), generics, iterators, contexts, goroutines, or doc comments in this…
Write clear, fast, deterministic Go tests including mandatory repo integration tests (x/testkit) and app unit tests. Use when adding or fixing Go tests, implementing internal/repo or internal/app, designing table-driven tests, writing benchmarks, using testify, or improving coverage in this workspace. For…
Build and review Next.js App Router applications (Next.js 15/16+) — Server vs Client Component boundaries, async request APIs, data fetching and caching, Server Actions, streaming Suspense, URL state, LCP/image optimization, and deterministic metadata/SEO. Use when creating or modifying app/ routes, layouts…
Optimize React/Next.js runtime performance — eliminate waterfalls, shrink bundles, cut unnecessary re-renders, and speed up rendering. Use when writing, reviewing, or refactoring components for speed, or chasing slow renders, large bundles, janky interactions, or high TTFB/LCP/INP.
Build production-ready services: timeouts, circuit breakers, bulkheads, retry budgets, health checks, and observability. Use when hardening RonyKit services for production, reviewing outbound calls, capacity planning, or preventing cascading failures. Pair with MCP characteristics/telemetry and package x/ratelimit…
Build UI with shadcn/ui — find, install, compose, and customize components using the correct CLI and patterns. Use when adding or styling frontend components, building forms/dashboards, theming, or working with components.json and the shadcn registry/MCP.
Author and maintain Storybook stories with CSF 3.0 best practices — args, decorators, parameters, token/theme wiring, 8-state coverage, and a11y verification. Use when creating or editing .stories. files, configuring .storybook/, or ensuring every UI component ships with stories.
Find the root cause before changing code. Use when encountering any bug, test failure, crash, flaky test, performance regression, or unexpected behavior, before proposing or applying a fix. After the fix, use verification-before-completion to prove it; for production failure modes (timeouts, cascades), see release-it.
Apply professional web typography: font pairing by surface mode, modular/fluid vs. fixed type scales, unitless line-height by role, weight floors, line length, vertical rhythm, OpenType CSS properties, dark-mode optical adjustments, and typographic hygiene. Use when setting up CSS/Tailwind typography, designing…
Review and build web UIs against WCAG 2.2 AA accessibility, keyboard/focus discipline, 8-state interactive completeness, form ergonomics, layout resilience, and clear UX copy. Use when building or auditing forms, dialogs, navigation, interactive controls, responsive/RTL layouts, or running a UX and accessibility…
Require fresh verification evidence before claiming work is done, fixed, or passing. Use before reporting completion, expressing success, committing, or opening a PR — run the command, read the output, then make the claim.
Build agent-friendly web apps with the W3C Web Model Context API (WebMCP). Use when exposing frontend features as structured tools for in-browser AI agents, adding document.modelContext tools to React/Next.js apps, designing tool schemas for dashboards or admin UIs, or making existing UI automatable without DOM…
Write a concrete implementation plan before touching code on a multi-step task. Use when you have a spec or requirements and the work spans several files or steps — decompose into small, independently testable tasks first.
Language-agnostic discipline for writing valuable tests and practicing TDD. Use when deciding what to test, structuring a test suite, doing red-green- refactor, or judging whether coverage is meaningful rather than vanity. For Go specifics and the mandatory repo/app tests, see go-testing; for Vitest/Playwright, see…
Design data systems with storage engines, indexes, replication, partitioning, transactions, isolation levels, and consistency models (Kleppmann). Use when writing the SDD data design, choosing between Postgres, Redis, and S3, designing schemas, indexes, or table partitioning, reasoning about races, lost updates…
Model software around the business domain — bounded contexts, aggregates, entities vs value objects, domain events, and ubiquitous language. Use when writing an SRS/SDD, deciding how to split features into RonyKit service modules, designing internal/domain types, placing invariants, integrating with another service or…
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: