Claude Code Skills · page 4

LobeHub code review checklist. Use when reviewing a PR, diff, or branch for console leftovers, return await, secrets, i18n, desktop router drift, UI imports, migrations, or cloud impact.

Audit .agents/skills SKILL.md files. Use for recurring checks of duplicate, overlapping, stale, inconsistent, or broken skills and merge/delete candidates.

LobeHub SPA route architecture. Use when editing src/routes, src/features delegation, desktop/mobile/popup router configs, .desktop variants, route segments, redirects, or new pages.

LobeHub Zustand store data-shape patterns. Use when designing store state, list/detail splits, normalized maps, reducers, messagesMap, topicsMap, or choosing shared type sources.

Vitest testing guide. Use when writing or updating tests, fixing failing tests, improving coverage, debugging test issues, or setting up mocks.

TRPC router development guide. Use when creating or modifying apps/server/src/routers, adding procedures, or implementing server-side API endpoints.

LobeHub TypeScript style and type-safety guide. Use when editing TS/TSX/MTS, fixing types, choosing interface vs type, avoiding any/object, import type, async flow, or ts-expect-error.

LobeHub Upstash Workflow and QStash guide. Use for async workflows, process/paginate/execute fan-out, serve handlers, context.run/call/sleep, or workflow triggers.

Version release workflow — release process and GitHub Release notes (not docs/changelog pages).

LobeHub Zustand store conventions. Use when editing src/store, store slices, public/internal actions, dispatch actions, flattenActions, optimistic updates, selectors, maps, or class action migration.

Backfill and maintain model-bank metadata (knowledgeCutoff, family, generation). Use when adding models, fixing cutoff/family data, running a metadata sweep across aiModels providers, or researching official knowledge cutoffs.

>

LobeHub product design values / principles / checklists. Load this skill whenever the work touches user-interface features or implementation — designing or building any user-facing flow — to get better UX results.

>

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

Use when you need to ask questions about a codebase or understand code using a knowledge graph

Launch the interactive web dashboard to visualize a codebase's knowledge graph

Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks

Extract business domain knowledge from a codebase and generate an interactive domain flow graph. Works standalone (lightweight scan) or derives from an existing /understand knowledge graph.

Use when you need a deep-dive explanation of a specific file, function, or module in the codebase

Analyze a Karpathy-pattern LLM wiki knowledge base and generate an interactive knowledge graph with entity extraction, implicit relationships, and topic clustering.

Use when you need to generate an onboarding guide for new team members joining a project

Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships

|

Perform thorough code reviews with security, performance, and maintainability analysis. Use when user asks to review code, check for bugs, or audit a codebase.

Build MCP (Model Context Protocol) servers that give Claude new capabilities. Use when user wants to create an MCP server, add tools to Claude, or integrate external services.

Process PDF files - extract text, create PDFs, merge documents. Use when user asks to read PDF, create PDF, or work with PDF files.

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.

Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Abstract tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Abyssale tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Accredible Certificates tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Acculynx tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate ActiveCampaign tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Addresszen tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Adobe tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Adrapid tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Adyntel tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Aero Workflow tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Aeroleads tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Affinda tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Affinity tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Agencyzoom tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Agent Mail tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Agentql tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Agenty tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Agiled tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Agility CMS tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate SEO research with Ahrefs -- analyze backlink profiles, research keywords, track domain metrics history, audit organic rankings, and perform batch URL analysis through the Composio Ahrefs integration.

Automate AI ML API tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Aivoov tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Alchemy tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Algodocs tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Algolia tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate All Images AI tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Alpha Vantage tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Altoviz tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Alttext AI tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Amara tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Amazon tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Ambee tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Ambient Weather tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Amcards tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Anchor Browser tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Anonyflow tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Anthropic Admin tasks via Rube MCP (Composio): API keys, usage, workspaces, and organization management. Always search tools first for current schemas.

Automate Apaleo tasks via Rube MCP (Composio). Always search tools first for current schemas.

Automate Apex27 tasks via Rube MCP (Composio). Always search tools first for current schemas.