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, implementing API handlers and services, frontend bootstrap, integration tests, or design documents…
Instructions for clubpay/ronykit: All agent and contributor instructions for this repository are maintained in AGENTS.md. Read that file first — it covers project layout, architecture, build commands, testing, intent/agent conventions, and git practices.
Structure software around the Dependency Rule — dependencies point inward from frameworks to use cases to entities. Use when deciding where code belongs in a RonyKit feature module (handler vs app vs repo), reviewing layer boundaries, or keeping business rules independent of Postgres/Rony/HTTP. For refactoring with…
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.
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, 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.
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…
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…
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.
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.
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.
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.
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.
Apply named refactoring transformations to improve structure without changing behavior. Use when refactoring Go or TypeScript in this workspace, identifying code smells, or preparing code for a new feature. Requires tests first — pair with working-with-legacy-code when coverage is missing.
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, and config. Use when creating or editing .stories. files, configuring .storybook/, or ensuring every UI component ships with stories.