Loading...
Loading...
Found 2,664 Skills
Use this skill when designing ticket triage systems, managing SLAs, creating macros, or building escalation workflows. Triggers on ticket triage, SLA management, support macros, escalation workflows, support queue, first response time, and any task requiring customer support process design or optimization.
Expert in cross-platform mobile development (React Native/Flutter), bridging native performance with shared business logic.
Conducts comprehensive backend design reviews covering API design quality, database architecture validation, microservices patterns assessment, integration strategies evaluation, security design review, and scalability analysis. Evaluates API specifications (REST, GraphQL, gRPC), database schemas, service boundaries, authentication/authorization flows, caching strategies, message queues, and deployment architectures. Identifies design flaws, security vulnerabilities, performance bottlenecks, and scalability issues. Produces detailed design review reports with severity-rated findings, architecture diagrams, and implementation recommendations. Use when reviewing backend system designs, validating API specifications, assessing database schemas, evaluating microservices architectures, reviewing integration patterns, or when users mention backend design review, API design validation, database design review, microservices assessment, or backend architecture evaluation.
Build Chrome extensions using WXT framework with TypeScript, React, Vue, or Svelte. Use when creating browser extensions, developing cross-browser add-ons, or working with Chrome Web Store projects. Triggers on phrases like "chrome extension", "browser extension", "WXT framework", "manifest v3", or file patterns like wxt.config.ts.
Use when a frontend needs motion choreography, interaction polish, and scroll behavior that improves hierarchy without hurting performance. Works alongside layout and style skills instead of replacing them.
Pre-commit quality checklist covering lint, typecheck, tests, code-spec sync, API changes, database migrations, cross-layer verification, and manual testing. Blocks commit if infra or cross-layer specs lack executable depth. Use when code is written and tested but not yet committed, before submitting changes, or as a final review before git commit.
Pay-per-call access to premium APIs via x402 micropayments (USDC on Base or Solana). Run `npx agentcash@latest discover <origin>` to get endpoints, pricing, and usage instructions for any service below. AVAILABLE SERVICES: - stableenrich.dev — people/company search, LinkedIn scraping, Google Maps, Exa web search, Firecrawl web scraping, GTM & sales prospecting (name → contact info) - stablesocial.dev — social media data (Instagram, TikTok, YouTube, Facebook, Reddit) - stablestudio.dev — AI image & video generation - stableupload.dev — file hosting & sharing - stableemail.dev — send emails - stablephone.dev — AI phone calls - stablejobs.dev — job search - stabletravel.dev — travel search TRIGGERS: research, enrich, scrape, generate image, generate video, social data, send email, travel, look up, prospect, "find info about", "who is", "find contact"
Collaborative coding with enforced micro-steps: announce, show diff, wait for confirmation, apply, verify. User controls pace with commands. Works with any domain agent as the executor. Use when: "pair program", "pair with me", "let's code together", "step by step coding", "walk me through implementing", "code with me"
Plan multi-part content series with structure, cross-linking, and publishing cadence. Use when user needs to plan a blog post series, structure a multi-part tutorial, or design content with cross-linked navigation. Use for "plan series", "series on [topic]", "multi-part blog", or "content series". Do NOT use for writing individual posts, single-article outlines, or content calendar planning without series structure.
Verify cross-component wiring: exports are imported AND used, real data flows through connections, output shapes match input expectations. Use after /feature-implement, before /feature-validate, or standalone on any codebase. Use for "check integration", "verify wiring", "are components connected", "integration check", or "/integration-checker". Do NOT use for unit test failures, linting, or single-file correctness issues.
A professional guide for handling dynamic deployment parameter configuration (lzc-deploy-params.yml), Go template rendering of manifest files, and front-end page script injection via application.injects for Lazycat MicroServer applications.
Chain patterns for CC 2.1.71 pipelines — MCP detection, handoff files, checkpoint-resume, worktree agents, CronCreate monitoring. Use when building multi-phase pipeline skills. Loaded via skills: field by pipeline skills (fix-issue, implement, brainstorm, verify). Not user-invocable.