Loading...
Loading...
Found 3,364 Skills
Use when building features with TCA (The Composable Architecture), structuring reducers, managing state, handling effects, navigation, or testing TCA features. Covers @Reducer, Store, Effect, TestStore, reducer composition, and TCA patterns.
Implement pre-commit hooks and GitHub Actions for quality assurance. Use when asked to "setup CI/CD", "add pre-commit hooks", "create GitHub Actions", "setup quality gates", "automate testing", "add linting to CI", or any DevOps automation for code quality. Detects project type and configures appropriate tools.
The project's all-seeing guide. Sentinel MUST activate before Claude takes any action that modifies, creates, or deletes anything in the project. It understands the codebase, architecture, brand, design system, business model, deployment pipeline, testing strategy, and every convention. Trigger on: action requests (build, fix, add, change, update, refactor, implement, create, remove, delete, migrate, deploy, integrate, improve, configure, install, bump, upgrade, debug, troubleshoot, move, rename); casual requests (can you, I need to, let's, go ahead and, help me, we need to); status reports (X is broken/failing, there's a bug); project questions (how does X work here, where would I add, walk me through); planning (scope this, break this down, write a spec). Do NOT trigger on general knowledge, blog posts, interview prep, or tech comparisons for other projects. Key test: does this need THIS project's context? If yes, trigger. Sentinel guides Claude, it does not execute. No task is too small.
Devil's Advocate stress-testing for code, architecture, PRs, and decisions. Surfaces hidden flaws through structured adversarial analysis with metacognitive depth. Use for high-stakes review, stress-testing choices, or when the user wants problems found deliberately. NOT for routine code review (use engineering:code-review). Triggers on "스트레스 테스트", "stress test", "devil's advocate", "반론", "이거 괜찮아", "문제 없을까", "깊은 리뷰", "critical review", "adversarial".
Smartlead platform help — campaigns, SmartSenders, SmartInfra, SmartAgents, SmartDialer, SmartProspect, SmartDelivery, warmup, API, integrations, agency/white-label. Use when asking 'how do I do X in Smartlead', configuring Smartlead settings, setting up SmartSenders, managing campaigns/leads, provisioning mailboxes, configuring SmartInfra, building SmartAgents, using SmartDialer, testing with SmartDelivery, setting up agency workspaces, white-labeling, or using the Smartlead API. Do NOT use for building prospect lists (use /sales-prospect-list), designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), or multi-client agency architecture (use /sales-agency-outbound).
Financial time series analysis method toolkit. Covers stocks / commodity futures / cryptocurrencies / ETFs / foreign exchange / indices, full process from data acquisition to high-level analysis. Built-in 70+ analysis methods, covering 8 major method domains: time series testing, predictive modeling, cross-asset relationships, volatility risk, portfolio optimization, state recognition, commodity-specific analysis and network analysis. Tushare MCP tool (A shares/Hong Kong stocks/US stocks/futures/funds/macro) is preferred for data acquisition, and yfinance scripts are used to supplement assets not covered by tushare such as commodity futures (CL=F) and crypto (BTC-USD).
SendGrid platform help — transactional email via Email API (REST + SMTP), Marketing Campaigns (drag-and-drop editor, automations, A/B testing, signup forms, segmentation), Email Validation API, Dynamic Templates (Handlebars), Event Webhooks, Inbound Parse, domain authentication (SPF/DKIM/DMARC), dedicated IPs, suppressions, Design Library, email testing, statistics. Use when asking 'how do I do X in SendGrid', sending transactional email with SendGrid, setting up Marketing Campaigns, configuring Event Webhooks, managing SendGrid domain authentication, using Dynamic Templates, or troubleshooting SendGrid deliverability. Do NOT use for general email marketing strategy (use /sales-email-marketing), cross-platform email deliverability (use /sales-deliverability), or email open/click tracking strategy (use /sales-email-tracking).
Customer.io platform help — customer engagement & marketing automation for behavior-based multi-channel messaging. Journeys (visual workflow builder with branching, delays, wait-untils), Campaigns (segment/event/date-triggered), Transactional Messages (API-triggered email, push, SMS), Segmentation (data-driven auto-updating and manual/static), Multi-channel (email, SMS via Twilio, push iOS/Android/web, in-app, WhatsApp), Data Pipelines (primary ingestion API, reverse ETL), Custom Objects, Ad Audience Sync (Google, Facebook, Instagram, YouTube), Design Studio (drag-and-drop email editor), A/B & cohort testing, Broadcasts (one-time/scheduled/API-triggered), Webhooks in workflows, and Analytics with AI-powered insights. Use when asking 'how do I do X in Customer.io', building behavior-triggered automation, setting up transactional messaging via Customer.io, configuring segments or journeys, integrating Customer.io Data Pipelines, or working with the Track/App/Transactional APIs. Do NOT use for general email marketing strategy (use /sales-email-marketing), cross-platform email deliverability (use /sales-deliverability), or email open/click tracking strategy (use /sales-email-tracking).
Run and debug C# MCP servers locally. Covers IDE configuration, MCP Inspector testing, GitHub Copilot Agent Mode integration, logging setup, and troubleshooting. USE FOR: running MCP servers locally with dotnet run, configuring VS Code or Visual Studio for MCP debugging, testing tools with MCP Inspector, testing with GitHub Copilot Agent Mode, diagnosing tool registration issues, setting up mcp.json configuration, debugging MCP protocol messages, configuring logging for stdio and HTTP servers. DO NOT USE FOR: creating new MCP servers (use mcp-csharp-create), writing automated tests (use mcp-csharp-test), publishing or deploying to production (use mcp-csharp-publish).
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.
A complete guide to developing MusicFree desktop theme packs from scratch. It is triggered when users request to write, create, design MusicFree desktop theme packs, or ask to generate themes based on reference images, color schemes, or style keywords. It covers the full process including CSS variable system, color design paradigms, static themes, dynamic iframe themes, resource optimization, packaging testing, and submission to the theme market. This Skill is designed for AI execution, guiding AI to collaborate with community contributors (who may have no front-end experience) to complete theme pack development.
Comprehensive Drupal patterns from "Drupal at Your Fingertips" by Selwyn Polit. Covers 50+ topics including services, hooks, forms, entities, caching, testing, and more.