ronykit

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 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 scraping.

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.

Design distinctive, production-grade frontend interfaces that don't read as templated AI defaults. Use when bootstrapping a frontend app, building or restyling a landing page, marketing site, hero, brand-forward product surface, or any UI where visual identity matters — choosing palette, typography, layout, motion, and copy. Required before running create-next-app or writing UI.

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.

Architect a scalable, themeable design-token system — primitive → semantic → component layers, CSS variables, a 4px spacing/type scale, and dark mode. Use when setting up or refactoring a project's tokens, naming color/spacing/radius values, wiring tokens into Tailwind/shadcn, enabling theme switching, or killing hard-coded hex/px scattered through components.

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.

Get screen typography correct — the details models reliably get wrong: curly quotes, en/em dashes, real ellipses, line length, line-height, hierarchy, and the JSX entity trap. Use whenever generating or reviewing HTML/CSS/React with visible text (landing pages, components, docs, dashboards) — apply the rules automatically, even if typography wasn't mentioned.

Make web UI actually usable and accessible — keyboard/focus, interaction and loading states, forms, navigation, and motion. Use when building or reviewing any interactive surface (forms, modals, menus, tables, flows) for usability, accessibility (WCAG), interaction states, or the "it looks fine but feels janky / fails a keyboard or screen-reader" class of problems.

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.

Design and build data-dense dashboards, back-office, and admin apps that surface the few metrics a decision needs. Use when laying out an admin/console screen, KPI strip, chart grid, data table, sidebar nav, or reviewing the visual design and information hierarchy of an internal/operational UI.

Build modern Next.js (16, App Router) apps with React Server Components. Use when creating or reviewing Next.js routes, layouts, server/client components, data fetching, Server Actions, caching, or metadata in the frontend app.

Author and maintain Storybook stories with CSF 3.0 best practices — args, decorators, parameters, and config. Use when creating or editing *.stories.* files, configuring .storybook/, or ensuring every UI component ships with stories.

Test web frontends (React/Next.js) effectively. Use when writing or fixing unit/component tests with Vitest + Testing Library, end-to-end tests with Playwright, or deciding what to test in a frontend app.

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.

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.

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.

Write clear, atomic commits using Conventional Commits. Use when committing changes, writing or rewriting a commit message, or splitting work into reviewable commits.

Write idiomatic, modern Go (1.25+/1.26) using current language and stdlib features. Use when authoring or reviewing Go code, choosing between stdlib and third-party helpers, working with generics, iterators, contexts, or error wrapping in this workspace.

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.

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.

Orchestrates RonyKit service development using the ronyup MCP server (knowledge resources, prompts, scaffold tools). Use when the user mentions RonyKit, ronyup, EdgeServer, contracts, scaffolding a workspace or feature, or implementing API handlers and services in RonyKit style.

Orchestrates RonyKit service development using the ronyup MCP server (knowledge resources, prompts, scaffold tools). Use when the user mentions RonyKit, ronyup, EdgeServer, contracts, scaffolding a workspace or feature, or implementing API handlers and services in RonyKit style.