Loading...
Loading...
Found 6,446 Skills
Use when symfony doctrine transactions
Reconcile the project's FPF state with recent repository changes
Create Requirements Document - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
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.
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.
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
Plan Requirements - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Continuously question users about their plan or design. Suitable for scenarios where users want to stress-test their plan before building, or when using any "grill" trigger phrases.
Compile durable knowledge into interlinked-markdown stores the "karpathy method" way — atomic files, [[wiki-links]], a maintained index. Use after producing research, intel, a digest, a learned non-obvious fact, or finishing any knowledge-shaped task, BEFORE you close it. Also when asked to "save this", "write this to the wiki", "update the wiki/memory", "log this finding", "structure this knowledge", or "follow the karpathy method".