Loading...
Loading...
Found 13,548 Skills
Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.
UI/UX design patterns and best practices. Pattern library + heuristic checks for shipping clean, usable interfaces.
Unified learning-and-memory system: confidence-scored instincts (observe-hypothesize-confirm, stored in .claude/instincts.md), user corrections captured as permanent rules in MEMORY.md, and organic discoveries logged to .claude/learning-log.md. Includes status, export, and import modes. Load this skill when you notice a recurring pattern, a user corrects your output, or you discover something non-obvious. Triggers: "show instincts", "what have you learned", "list instincts", "export instincts", "share instincts", "import instincts", "load instincts from", "learn this", "I think they always", "notice a pattern", "instinct", "hypothesis", "confidence", "learn from mistakes", "remember this", "don't do that again", "log this", "document this finding", "gotcha", "what did we learn", "learnings", "discoveries", or at session start (to load existing knowledge).
Turn the current conversation into a spec (Problem, Solution, User Stories, Decisions) and publish it as a GitHub issue. Validates a feature before any code is written.
Apply the canonical GitHub issue and pull-request label set to a repository.
In chat-only mode, reply like a chat assistant without changing the current code base.
Проводит независимое ревью изменений кода без их исправления. Используй, когда пользователь явно просит проверить код, коммит, ветку, pull request или diff на соответствие задаче, корректность, безопасность, производительность и качество тестов. Не используй, когда пользователь просит изменить код, реализовать задачу или сначала найти причину проблемы.
Автономно реализует задачу из диалога, строгого плана или спецификации через повторяемые итерации разработки, независимое ревью и проверку тестами. Используй только при явном вызове /bro-do-it для выполнения согласованной задачи.
Use when answering, explaining, comparing, or guiding conversationally, or when generating and choosing among possible directions, before creating artifacts or mutating state.
Case Radar. Given a new thing (new tool/new concept/new ecosystem), scan the ecosystem to find interesting real-world cases, focusing on capturing "authentic assets" (screenshots/source code/demos) instead of GitHub homepage, and output a browsable HTML case collection. Triggered when users say "See what people are doing with X", "Scan the X ecosystem", "What new ways are there to use X in the market", "Show me authentic cases of X", or "/case-radar". Not suitable for: ① In-depth research with clear objectives (use long-research) ② Writing articles/creating PRDs (use writing-assistant / prd-doc-writer) ③ Pure knowledge-seeking without needing HTML (just ask directly).
Autonomous execution workflow for complex long-running tasks. This applies to scenarios where users have a complex or vague task (e.g., "Help me figure out X / Help me evaluate Y / Help me organize this pile of stuff / Help me compare N solutions / Help me run a research"), and expect the AI to decompose, execute, and verify the task on its own, only reaching out to the user at critical moments. It enables unattended autonomous execution for 1-2 hours through the process of "Task Confirmation → Task Queue → Batch Execution → Periodic Queue Verification → Triggered Reporting". It is triggered when users say phrases like "Help me figure out / Evaluate / Organize / Compare / Run a research / Run it on your own don't bother me / Long-running task / Run autonomously". **Not applicable to**: UI design (use design-exploration), to-do priority judgment (use priority-judge), article writing (use writing-assistant), backlog management (use backlog-manager), vision exploration (use vision-exploration), naming (use product-naming), implementation coding tasks with clear specs (code directly).
Know a company completely. Opens by asking your goal and where your context lives (CRM? call recorder? team chat? email?), then routes to 4 modes - account deep-dive & plan (external + your internal history with them), org chart (who runs it), tech stack & wedge, competitive battlecard. Use for "tell me about <company>", "account plan for <company>", "org chart for <company>", "what's their tech stack", "battlecard for <competitor>", "how do we beat <X>", "research this account".