Enterprise-grade systems with microservices, Kubernetes, Terraform, and AI Native methodology. Triggers: microservices, k8s, terraform, monorepo, AI native, ๋ง์ดํฌ๋ก์๋น์ค, init enterprise.
Define project terminology, data structures, entities, and relationships. Triggers: schema, data model, entity, terminology, ์คํค๋ง, ๋ฐ์ดํฐ ๋ชจ๋ธ, ์ฉ์ด.
Build platform-independent design systems and consistent component libraries. Triggers: design system, component library, design tokens, ๋์์ธ ์์คํ , ์ปดํฌ๋ํธ.
bkend.ai authentication โ email/social login, JWT tokens, RBAC, session management. Triggers: bkend auth, login, signup, JWT, RBAC, ์ธ์ฆ, ๋ก๊ทธ์ธ, ํ์๊ฐ์ .
Design and implement backend APIs with Zero Script QA validation. Triggers: API design, REST API, backend, endpoint, ๋ฐฑ์๋ API, API ์ค๊ณ.
Desktop app development guide โ Electron and Tauri for cross-platform apps. Triggers: desktop app, Electron, Tauri, mac app, windows app, ๋ฐ์คํฌํฑ ์ฑ.
Mobile app development guide โ React Native, Flutter, Expo for cross-platform. Triggers: mobile app, React Native, Flutter, Expo, iOS, Android, ๋ชจ๋ฐ์ผ ์ฑ.
Implement frontend UI and integrate with backend APIs โ state management and API clients. Triggers: UI integration, frontend-backend, API client, ํ๋ก ํธ์๋ ํตํฉ, UI ๊ตฌํ.
Use Parchi Relay to control a real browser via the Parchi extension agent (WebSocket) or directly via JSON-RPC from a CLI/tooling workflow.
Standard scopy plugin patterns including ToolTemplate, refresh buttons, sections, plugin lifecycle, and architecture. Auto-loads when creating plugin scaffolds, tool classes, or section layouts.
Scopy styling system patterns including Style::setStyle, theme colors, section backgrounds, and widget styling. Auto-loads when applying styling to scopy widgets or sections.
How to create IIOWidgets for device attributes using IIOWidgetBuilder. Covers spinbox, combo, checkbox, and read-only patterns. Auto-loads when creating IIOWidgets, mapping attributes, or building plugin UI.
Generate perfectly aligned ASCII diagrams โ architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.
Unified router that auto-routes user intent to the right orchestrator or skill. Classifies input by scope, complexity, persistence needs, and parallelism, then dispatches to the cheapest path that can handle it: direct command, skill, marshal, archon, or fleet. Single entry point for all work.
Creates and refactors model and controller concerns for shared behavior. Use when extracting shared code, organizing models with horizontal concerns, DRYing up controllers, or when user mentions concerns, mixins, or modules. WHEN NOT: Logic used by only one model (keep in place), service object extraction (use model-patterns), or job organization (use job-patterns).
Implements shallow background jobs with _later/_now conventions using Solid Queue. Use when adding background processing, async operations, scheduled tasks, or when user mentions jobs, queues, workers, or background processing. WHEN NOT: Business logic implementation (use model-patterns), controller work (use crud-patterns), or mailer delivery (use mailer-patterns).
Creates minimal Action Mailer classes with bundled notification patterns following 37signals conventions. Use when sending emails, creating notification systems, digest emails, or when user mentions mailers, emails, notifications, or transactional messages. WHEN NOT: For background job scheduling (use job-patterns), for event-driven triggers (use event-tracking).
Implements URL-based multi-tenancy with account scoping, membership patterns, and data isolation following 37signals patterns. Use when setting up multi-tenant architecture, account isolation, membership management, or when user mentions multi-tenancy, accounts, or tenant separation. WHEN NOT: For basic model setup without tenancy (use model-patterns), for auth/session setup (use auth-setup).
Guides decisions about when and how to extract code into services, queries, concerns, form objects, or other patterns. Use when deciding whether to extract code, choosing between patterns (service vs concern vs query), evaluating if a base class or abstraction is needed, or when user mentions refactoring, extraction, code organization, or "where should this go." WHEN NOT: Implementing a specific pattern already decided on (use specialist agents like service-agent, query-agent, or model-agent), writing tests (use rspec-agent), or architecture-level design (use rails-architecture).
Guides modern Rails 8 code architecture decisions and patterns. Use when deciding where to put code, choosing between patterns (service objects vs concerns vs query objects), designing feature architecture, refactoring for better organization, or when user mentions architecture, code organization, design patterns, or layered design. WHEN NOT: Implementing specific patterns (use specialist agents like service-agent or query-agent), writing tests, or debugging runtime errors.
Creates Rails concerns for shared behavior across models or controllers with TDD. Use when extracting shared code, creating reusable modules, DRYing up models/controllers, or when user mentions concerns, modules, mixins, or shared behavior. WHEN NOT: Logic used by only one model or controller (keep it in place), complex business logic (use service objects), or query encapsulation (use query objects).
