Loading...
Loading...
Found 527 Skills
SolidJS and SolidStart performance and correctness guidelines for AI agents. This skill should be used when writing, reviewing, or refactoring SolidJS/SolidStart code to ensure correct reactivity patterns and optimal performance. Triggers on tasks involving SolidJS components, signals, stores, Solid Query, SolidStart server functions, routing, or fine-grained reactivity.
Create media playback experiences using AVKit. Use when adding video players with AVPlayerViewController, enabling Picture-in-Picture, routing media with AirPlay, using SwiftUI VideoPlayer views, configuring transport controls, displaying subtitles and closed captions, or integrating AVFoundation playback with system UI.
Design and implement lead routing and assignment rules — round-robin, territory-based, score-based, and account-based models. Use when designing how leads get assigned to reps, building routing rules in your CRM, optimizing speed-to-lead, setting up territory assignments, configuring lead queues, or scaling assignment as your team grows. Do NOT use for lead scoring model design (use /sales-lead-score), CRM platform configuration (use /sales-apollo or /sales-salesloft), or marketing-to-sales handoff process (use /revops).
Use Tabbit with agent-browser by reading Tabbit's live DevToolsActivePort file, deriving the browser wsEndpoint, and routing browser actions through agent-browser --cdp.
Reference skill for Zoom Probe SDK. Use after routing to a preflight workflow when testing browser compatibility, media permissions, audio or video diagnostics, and network readiness before users join.
Reviews Rails pull requests, focusing on controller/model conventions, migration safety, query performance, and Rails Way compliance. Covers routing, ActiveRecord, security, caching, and background jobs. Use when reviewing existing Rails code for quality, conducting a PR review, or doing a code review on Ruby on Rails (RoR) code.
Implement and configure Syncfusion React Breadcrumb component for navigation paths, routing, and site hierarchy. Use this skill whenever users need breadcrumb navigation, want to create hierarchical navigation paths, display location breadcrumbs, handle navigation between pages, customize overflow behaviors, or integrate breadcrumbs with routing libraries.
Reference skill for Zoom Rivet SDK. Use after routing to a Rivet-based server workflow when implementing auth handling, webhook consumers, API wrappers, multi-module composition, or Lambda receiver patterns.
A comprehensive guide to building React apps with a modern 2026 stack, covering frameworks, build tools, routing, state management, and AI integration.
C-suite orchestration layer that routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, tracks decisions, and manages cross-functional alignment. Every C-suite interaction starts here. Use when coordinating executive decisions, routing strategic questions, managing board meetings, synthesizing multi-perspective advice, tracking decision history, resolving inter-department conflicts, or when user mentions chief of staff, orchestrator, c-suite coordinator, executive routing, board coordination, decision synthesis, advisor routing, multi-agent coordination, or strategic orchestration.
When the user wants to optimize delivery routes, solve vehicle routing problems, or minimize transportation costs. Also use when the user mentions "route planning," "delivery optimization," "VRP," "TSP," "multi-stop routing," "route sequencing," or "dispatch optimization." For fleet sizing and management, see fleet-management. For last-mile specific challenges, see last-mile-delivery.
The root entry of the CodeStable workflow family — introduces the overall system to users and routes users' specific requests to the correct cs-* sub-skills. Trigger scenarios: users only input `cs` / `/cs`, say "introduce codestable", "do something with codestable", "I want to do X, which skill should I use", "don't know which one to use", or users' described requests are open-ended (e.g., "start working") and haven't converged to a specific sub-skill. This skill itself **does not perform actual tasks** — it doesn't write specs, write code, or read/write content products in the codestable/ directory — it only performs scanning, routing, prompting, and then transfers control to the target sub-skill.