Loading...
Loading...
Found 2,771 Skills
Specifies best practices, including following RESTful API design principles, implementing responsive design, using Zod for data validation, and regularly updating dependencies. This rule promotes mode
Critical-thinking brainstorming partner that acts as a requirements analyst. Use when users present ideas, feature requests, or problems they want to solve. Triggers include "I want to build", "help me validate", "users need", "I'm thinking of creating", or any request involving problem/solution validation. This skill aggressively challenges assumptions, questions perceived problems, demands evidence, and ensures solutions address genuine needs before exploring implementation.
Move validation and authorization into Form Requests; use rule objects, custom messages, and nested data handling to keep controllers slim
Pre-deployment validation for Webflow Code Components. Checks bundle size, dependencies, prop configurations, SSR compatibility, styling setup, and common issues before running webflow library share.
Step-by-step process for adopting Cavekit on an existing codebase. Covers the 6-step brownfield process, bootstrap prompt design, spec validation against existing behavior, and the decision between brownfield adoption vs deliberate rewrite. Trigger phrases: "brownfield", "existing codebase", "add Cavekit to existing project", "adopt Cavekit", "layer kits on code", "retrofit kits"
ZeroBounce platform help — email validation, email finder, AI scoring, activity data, inbox placement testing, blacklist monitoring, DMARC, warmup. Use when your email list has too many bounces, catch-all addresses are hurting deliverability, you need to check if your IP is blacklisted, DMARC reports show unauthorized senders, or the ZeroBounce API isn't returning expected validation results. Do NOT use for general deliverability strategy (use /sales-deliverability), enrichment strategy (use /sales-enrich), or prospect list building strategy (use /sales-prospect-list).
Build interactive terminal forms and prompts in Go with huh - input, select, confirm, multiselect, validation, theming. Use when building Go terminal forms, huh, interactive Go prompts, or form fields with validation. NOT for shell script prompts (use gum).
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Debug Scikit-learn issues systematically. Use when encountering model errors like NotFittedError, shape mismatches between train and test data, NaN/infinity value errors, pipeline configuration issues, convergence warnings from optimizers, cross-validation failures due to class imbalance, data leakage causing suspiciously high scores, or preprocessing errors with ColumnTransformer and feature alignment.
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
Multi-layer validation pattern - validates data at EVERY layer it passes through to make bugs structurally impossible, not just caught.
Use when designing Rails models - ActiveRecord patterns, validations, callbacks, scopes, associations, concerns, query objects, form objects