Loading...
Loading...
Found 914 Skills
Architectural refactoring guide for Rust applications covering type safety, ownership patterns, error handling strategies, API design, project organization, module structure, naming conventions, conversion traits, and idiomatic patterns. Use when refactoring Rust codebases, reviewing PRs for architectural issues, improving type safety, designing error handling strategies, or organizing project structure. Complements the rust-optimise skill (performance patterns). Does NOT cover performance optimization, memory allocation, or async concurrency tuning (see rust-optimise skill).
React DevTools CLI for AI agents. Use when the user asks you to debug a React or React Native app at runtime, inspect component props/state/hooks, diagnose render performance, profile re-renders, find slow components, or understand why something re-renders. Triggers include "why does this re-render", "inspect the component", "what props does X have", "profile the app", "find slow components", "debug the UI", "check component state", "the app feels slow", or any React runtime debugging task.
A clear description of what this skill does and when Claude should use it. Include trigger phrases like "when asked to...", "use when...", or specific keywords that should activate this skill.
Verify that a pull request fully implements the requirements described in its linked GitHub issue. Use when asked to "verify PR implementation", "check PR coverage", "does PR implement the issue", "verify PR against issue", "is PR complete", or "PR completeness check". Extracts the linked issue from the PR body or GitHub linked issues, analyzes the diff against issue requirements, and reports either missing items or confirms 100% coverage.
Complete PostHog lifecycle management. Audits current state, fixes all issues, and verifies event tracking works end-to-end. Every run does all of this. Auto-invoke when: files contain posthog/analytics/tracking, imports posthog-js package, references POSTHOG_* env vars, event tracking code modified, user mentions "analytics not working" or "events not sending".
Explain and document MTHDS bundles. Use when user says "what does this pipeline do?", "explain this workflow", "explain this method", "walk me through this .mthds file", "describe the flow", "document this pipeline", "how does this work?", or wants to understand an existing MTHDS method bundle.
Application-level React performance optimization covering React Compiler mastery, bundle optimization, rendering performance, data fetching, Core Web Vitals, state subscriptions, profiling, and memory management. Use when optimizing React app performance, analyzing bundle size, improving Core Web Vitals, or profiling render bottlenecks. Complements the react skill (API-level patterns) with holistic performance strategies. Does NOT cover React 19 API usage (see react skill) or Next.js-specific features (see nextjs-16-app-router skill).
Strategic discovery of a project's capabilities from a solutions architect perspective. Deploys parallel discovery agents to map architecture, inventory features, and assess infrastructure, then synthesizes findings into a capabilities report with strategic improvement recommendations. Use when user says "explore", "what does this do", "project overview", "capabilities", "feature inventory", or asks about strategic direction.
When the user wants to edit, review, or improve existing marketing copy. Use when the user says anything like "edit this copy," "review my copy," "copy feedback," "proofread," "polish this," "make this better," "tighten this up," "this reads awkwardly," "clean up this text," "too wordy," "sharpen the messaging," "this doesn't sound like me," "something's off with this," "make this punchier," "this is boring," or "can you fix this copy." Handles everything from quick polish on a sentence to deep restructuring of a full page. World Code integrated — edits against your voice rules and World Code consistency. For writing new copy from scratch, see boring-copywriting.
Search and analyze research papers, find related work, summarize key ideas. Use when user says "find papers", "related work", "literature review", "what does this paper say", or needs to understand academic papers.
Virtual try-on — see how clothes look on a person. Use when the user requests "Try on clothes", "Virtual try-on", "How does this look on me", "Fashion try-on", "Garment transfer".
Search the web and scrape pages using the local tool stack: SearXNG (meta-search), Lightpanda (fast headless fetch), and Agent-Browser (full browser automation). This is your DEFAULT web skill — use it whenever you need to look something up, research a topic, fetch a webpage, extract content from a URL, check current information, find documentation, do competitive research, or answer any question that benefits from live web data. Triggers on any form of: search for, look up, google, find out, research, what's the latest on, fetch this page, scrape this site, check this URL, pull info from, web search, or any task where current web information would improve your answer. Even if the user doesn't explicitly ask you to search — if answering well requires current info you don't have, use this skill. NOT for interactive browser automation like form filling or clicking (use [[agent-browser]] or [[browser-use]]).