Loading...
Loading...
Found 5,470 Skills
Orchestrates parallel KB generation using spatial analysis and a map-reduce architecture with incremental update support.
3-Phase Knowledge Search strategy for the RLM Factory ecosystem. Auto-invoked when tasks involve finding code, documentation, or architecture context in the repository. Enforces the optimal search order: RLM Summary Scan (O(1)) -> Vector DB Semantic Search -> Grep/Exact Match. Never skip phases.
Collaborative planning using abstract roles (designer + inspiration + reviewer).
Single table design patterns for DynamoDB with SST - modeling complex data relationships in a single table for optimal performance and cost
Эксперт по политикам бэкапов. Используй для стратегий резервного копирования, retention rules и disaster recovery.
Эксперт по troubleshooting гайдам. Используй для создания диагностических процедур, FAQ и решения проблем.
MongoDB transaction correctness, consistency, and retry safety. Use when implementing multi-document writes, debugging transaction failures, choosing readConcern/writeConcern, handling TransientTransactionError or UnknownTransactionCommitResult, or deciding when transactions are required. Triggers on "transaction", "withTransaction", "session", "read concern", "write concern", "causal consistency", "snapshot", "retry commit", "ACID", "TransientTransactionError", and "UnknownTransactionCommitResult".
Use this before touching code when you have a requirement for a specification or multi-step task
Command: sync-testing-skill
Analyze and optimize slow SQL queries. Use when the user says a query is slow, asks to optimize or speed up SQL, wants to find anti-patterns, needs index recommendations, or asks for a query rewrite. Also use when EXPLAIN output shows full table scans or poor join strategies.
Write, rewrite, or review content in the evidence-led reframe voice style. Use when the user explicitly asks to write in "reframe voice", "reframe style", or asks to apply the content style spec. Do NOT use for general writing tasks.
Configure transaction isolation levels to prevent race conditions and handle concurrent access. Use when dealing with concurrent updates, financial operations, inventory management, or when users mention race conditions, dirty reads, phantom reads, or concurrent modifications.