kurenn

Switch the current session into Rails background-jobs specialist mode. Use for focused ActiveJob / async / queue / retry / idempotency work.

Switch the current session into Rails Tailwind CSS specialist mode. Use for focused utility-class / responsive / component-styling work in ERB.

Build a Rails feature with the specialist team. Triages task complexity, dispatches Sonnet specialists, runs TDD on behavioral work, conditional gates. Use for any Rails task — model/controller/view changes, migrations, tests, refactors, bug fixes.

Diagnose and fix a Rails bug with root-cause discipline. No patches before root cause is identified. Use when given a failing test, stacktrace, log error, or behavioral bug report.

Switch the current session into Rails controllers specialist mode. Use for focused controller / routes / request-handling work.

Switch the current session into Rails models specialist mode. Use for focused ActiveRecord / migration / association work without team coordination overhead.

Switch the current session into Rails services specialist mode. Use for service object extraction, business logic, design patterns.

Switch the current session into Rails tests specialist mode. Use for writing/improving RSpec specs, factories, test coverage.

Generates and compares implementation alternatives for Ruby on Rails decisions. Use when choosing between architectural approaches, query patterns, service boundaries, framework features, or rollout strategies. Triggers on alternatives, tradeoffs, option A/B, design choice, compare approaches, or should we use X vs Y.

Performs root-cause diagnosis for Ruby on Rails issues across performance, correctness, architecture, security, and reliability. Use when requests involve bugs, regressions, N+1 queries, slow endpoints, flaky tests, unexpected behavior, or unclear failures. Triggers on words like diagnose, debug, investigate, root cause, slowdown, flaky, regression, N+1, timeout.

Optimizes developer experience in Ruby on Rails workflows without compromising safety or quality. Use when teams face slow feedback loops, repetitive tasks, unclear errors, onboarding friction, or low development flow. Triggers on DX, developer productivity, faster feedback, workflow friction, onboarding, and ergonomics.

Defines the operating framework for AI-assisted Ruby on Rails development. Use when planning architecture, framing implementation strategy, creating multi-step workflows, coordinating specialized Rails skills, or aligning a team on a consistent delivery model. Triggers on requests like framework definition, implementation workflow, Rails standards, feature planning, or system-level guidance.

Runs and interprets quality gates for Ruby on Rails delivery. Use when validating PR readiness, release safety, or implementation quality across tests, linting, security, and performance checks. Triggers on quality gate, readiness, release check, CI parity, lint, test suite, security scan, or pre-merge validation.

Applies implementation safety checklists for Ruby on Rails code changes. Use when writing or reviewing code that touches user input, authorization, database migrations, background jobs, external APIs, or production-critical paths. Triggers on secure, safe migration, pre-merge checklist, rollout risk, data integrity, and production hardening.

Deep security workflow for Ruby on Rails applications. Use when auditing or implementing controls for XSS, SQL injection, CSRF, file uploads, command injection, session/cookie hardening, and security monitoring. Triggers on appsec audit, security review, OWASP, CSP, CSRF, upload hardening, or secure coding requests.

Maintain the Rails bootstrapping blueprint and install pipeline for newly generated apps. Use when changing default gems, Rails generator flags, post-bundle install commands, or feature defaults (Tailwind, PG, RSpec, Devise, ActiveStorage, ActionText, Untitled UI, Claude on Rails).

Build, refactor, or debug Thor-based Ruby CLI tools with interactive terminal UX, command orchestration, and test coverage. Use when tasks involve command options, prompts, colorful output, executable entrypoints, or CLI architecture in this repository.

Scaffold a Rails project to use /dev-loop. Verifies @kurenn/roundhouse and @openai-codex/codex are installed, adds a '## Dev-loop config' block to CLAUDE.md (gate, critical paths, extra rating axes, learnings path, PR conventions), and creates the learnings file. Run once per repo before the first /dev-loop.

Run the virtuous development loop for a Rails feature or bug — Opus plans, a parallel Sonnet specialist army implements (via roundhouse /rails-feature), Codex adversarially reviews, a fresh Opus reviewer rates the work against the plan, Sonnet agents fix until the quality gate passes, learnings are captured, and a PR is opened. Use for any non-trivial feature or bug. Prefers @kurenn/roundhouse and @openai-codex/codex; degrades gracefully without them. Run /dev-loop-setup once per repo first.

Translates casual, non-technical application requests into detailed, step-by-step technical specifications that AI coding assistants can execute faithfully. Use this skill whenever a user describes an app, feature, or tool they want built using everyday language — especially when the request is vague, missing technical details, or would benefit from structured decomposition. Trigger on phrases like "I want an app that...", "build me a...", "can you make...", "I need a tool for...", "create a website that...", or any request to build software where the user clearly isn't providing a full technical specification. Also trigger when a user says "refine this prompt", "make this more technical", "help me describe this better for AI", or "turn this into a spec". Even if the user provides some detail, if they're describing WHAT they want rather than HOW to build it, this skill should activate.

Build production-feel HTML prototypes for sales demos, stakeholder reviews, and design exploration. Runs a discovery Q&A, scaffolds a zero-dep static site (HTML + Tailwind CDN + CSS variables + theme switcher + layout switcher + URL-state + feedback overlay + always-visible control bar), and runs a design-quality assessment loop. Use when the user says "prototype", "mockup", "demo", "pitch page", "sales demo", "click-through", or describes a UI they want to show someone without building the real thing. Also handles /prototype variant "<vibe>" (fork a variant) and /prototype apply-feedback <file> (apply pinned feedback JSON).

Comprehensive Rails project stability audit across 18 dimensions — foundation, domain shape, specs, coverage, deploy/CI, security, authorization, money paths, code health, code smells, performance, reliability, observability, jobs, data integrity, governance, DX, and cost. Use when user asks to "audit this Rails project", "stability assessment", "code health check", "pre-launch review", "Rails security audit", or "is this ready to ship". Produces a severity-ranked markdown report with a recommended fix sequence. Read-only — never edits code.

Generate beautiful single-page client proposals as a document-format replacement for PDFs and Google Docs. Persists answers, fetches brand colors from the client's site (with WCAG contrast warnings), generates a Tailwind-built single-page HTML, and runs the `/critique` design skill via the Skill tool to grade and fix the output. Includes dynamic OG images for unfurls and version-history snapshots on revise. Use when the user says "create a proposal", "client proposal", "scope of work", "SOW", or "pitch document". Use `/proposal --revise <slug>` to update an existing proposal, `/proposal --clone <slug>` to start a new one from an existing discovery, or `/proposal --meetings <url|path>,...` to draft answers from Circleback transcripts and/or local meeting notes.