understand
Use the Socratic method to understand something.
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-20 00:12
41,964 results
Use the Socratic method to understand something.
Use when implementing features, fixing bugs, refactoring code, or making any multi-step code changes. Guides agents to commit early and often in atomic…
Use when encountering bugs, test failures, or unexpected behavior. Provides a systematic debugging process based on surfacing assumptions, building decision…
Use when refactoring code or when asked to refactor. Provides a 6-gate decision framework to determine whether refactoring is appropriate and when to stop.
Persistent Obsidian-based memory for coding agents. Use at session start to orient from a knowledge vault, during work to look up…
Enforce the no-useEffect rule when writing or reviewing React code. ACTIVATE when writing React components, refactoring existing useEffect calls, reviewing PRs…
Modern Rust backend with Axum, SQLx, tokio + CI/CD automation. Use when: building Rust APIs, high-performance services, or needing build/test/lint/audit…
Build Discord bots with modern frameworks. Use when: creating Discord bot, slash commands, moderation bot. Triggers: "discord", "discord bot", "serenity",…
Build Telegram bots with modern frameworks. Use when creating a Telegram bot, chatbot, or notification bot. Triggers: telegram, tg bot, or телеграм бот (Russian for Telegram bot),…
Set up the local tooling needed to contribute changes to the marketing-skills repo from Claude Code. Checks for the gh CLI, gh authentication, and git…
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design…
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of…
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix,…
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which…
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust…
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that…
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving…
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of…
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states…
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy,…
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one…
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a…
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand…