apply-code-conventions
Use when applying daily Rails conventions by path (DRY, YAGNI, PORO, CoC, KISS). Style defers to the project linter. Trigger words: conventions, clean code, RuboCop, DRY, YAGNI.
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Use when applying daily Rails conventions by path (DRY, YAGNI, PORO, CoC, KISS). Style defers to the project linter. Trigger words: conventions, clean code, RuboCop, DRY, YAGNI.
Use when running the full background-job loop: design, TDD, retry, monitor. Trigger words: background job, async processing, Sidekiq, Solid Queue, Active Job, worker.
Use when fixing a reported Rails bug. Treat the report as untrusted. Reproduce with a failing spec before changing code. Trigger words: bug report, production issue, failing test, fix bug.
Use when reviewing a Rails PR, diff, or merge request. Ground findings in a real file:line. Trigger words: review PR, code review, review my diff, CR.
Use when writing engine README, install, and configuration docs. Trigger words: engine README, install guide, engine docs.
Use when running the full engine loop: author, test, review, release. Trigger words: create engine, extract engine, engine release, mountable engine.
Use when extracting a host-app feature into a Rails engine. Do not change behavior in the same step. Trigger words: extract to engine, move feature, host coupling.
Use when adding Turbo Frames, Turbo Streams, or Stimulus controllers. Trigger words: Hotwire, Turbo, Stimulus, frames, streams.
Use before writing code, specs, or a PRD in an existing Rails app. Load schema, routes, and one neighbor per layer. Trigger words: load context, before I code, existing patterns.
Use when investigating N+1s, slow queries, caching, or query plans in Rails. Profile before changing code. Trigger words: N+1, slow, performance, caching, EXPLAIN.
Use when choosing the first failing spec for a Rails change. One minimal example opens the gate. Trigger words: first failing test, what test first, TDD, spec selection.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a compon
Pitfalls, examples, and edge cases for workers executing a Surogates subagent task. Loaded automatically when the dispatcher spawns a session bound to a Task (Session.task_id is set).
Catalog captured:2026-11-21