Loading...
Loading...
Found 8,537 Skills
Use when making a small, quick change — a bug fix, typo, minor feature, tweak, or anything the user calls "vibe coding" — that looks like 1-3 files in the same module
Do direct-send's unattended work, but stop with commits ready to push to the default branch. Use when the user says direct stop or wants work committed locally without pushing.
Debug Rails issues systematically. Use when encountering ActiveRecord errors like RecordNotFound, routing issues, N+1 query problems detected by Bullet, asset pipeline issues, migration failures, gem conflicts, ActionController errors, CSRF token problems, or any Ruby on Rails application errors requiring diagnosis.
Prevent N+1 queries by eager loading; enable lazy-loading protection in non-production; choose selective fields
Wrap multi-write operations in transactions; use dispatchAfterCommit and idempotency patterns to ensure consistency
Process large datasets efficiently using chunk(), chunkById(), lazy(), and cursor() to reduce memory consumption and improve performance
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.
Technical Design - picks one variant per problem area from the research catalogue, then produces architecture diagrams, interfaces, and data flow. Decisions live here, not in research.
Mock interview coach for AI engineering roles, built on the interview bank of AI Engineering from Scratch. Asks one question or one incident scenario, stops, and waits for the learner's own answer. Then it grades the answer against the bank, asks follow-ups one at a time, sends each gap to the lessons and manual sections that teach it, and keeps an append-only record in INTERVIEW-LEARNING.md. Trigger phrases: "interview prep", "mock interview", "ask me an interview question", "practise for my AI engineering interview", "run an incident scenario", "debugging round", "system design round", "inference engineer loop", "review my interview gaps", "how ready am I for the interview"
Use when a client can't connect or gets a connection error (timeout, 53/10060/10061, SQLSTATE 08001, TLS, firewall 'IP not allowed', 4060). For login or permission issues, use `authentication-diagnostics`.
Use when the user asks what caused blocking that already ended (yesterday's incident, intermittent lock waits) or who is behind a supplied blocking chain. For blocking happening now, use `check-live-blocking`.
Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.