Loading...
Loading...
Found 3,730 Skills
Guide for using MassGen to develop and improve itself. This skill should be used when agents need to run MassGen experiments programmatically (using automation mode) OR analyze terminal UI/UX quality (using visual evaluation tools). These are mutually exclusive workflows for different improvement goals.
Test skill for argument substitution
When the user wants to optimize a signup or registration flow -- including field selection, social auth, single-step vs multi-step forms, or mobile signup. Also use when the user says "signup conversion," "registration form," "reduce signup friction," "signup A/B test," or "signup drop-off." For post-signup onboarding, see product-onboarding. For activation measurement, see activation-metrics.
Validate and test Doppler secrets. TRIGGERS - add to Doppler, store secret, validate token, test credentials.
Generates wiring verification YAML for loom plans. Helps agents prove that features are properly integrated — commands registered, endpoints mounted, modules exported, components rendered. Use when writing truths/artifacts/wiring fields for loom plan stages.
Update Storybook visual regression snapshots after intentional UI changes. Use when visual tests fail due to expected changes, or when asked to update snapshots.
Run UX walkthroughs and QA sweeps on live web apps using browser automation. Walks through apps as a real user, flags friction points and usability issues, tests CRUD operations, and produces ranked audit reports. Trigger with 'ux audit', 'ux walkthrough', 'qa test', 'test the app', or 'check all pages'.
Test quality inspection framework for reviewing test coverage, identifying gaps, and ensuring comprehensive validation
ALWAYS use when writing code importing "@vue/test-utils". Consult for debugging, best practices, or modifying @vue/test-utils, vue/test-utils, vue test-utils, vue test utils, test-utils, test utils.
Use when implementing well-scoped Python tasks with clear requirements, writing unit tests, and producing documented code for senior-developer review.
TypeScript, React, and Node.js coding standards: naming, types, hooks, components, error handling, refactoring, code review. Use when creating/editing TS/JS/React files, naming variables or components, designing API endpoints, handling async, structuring components, or when the user asks "how should I name...", "what's the best way to...", "is this good practice...", "can you review this code". Keywords: TypeScript, React, hooks, React Query, Jest, RTL, naming, immutability. Do not load for: CSS-only changes, documentation writing, JSON config edits, shell scripts.
Gauntlet for absolute claims (always/never/guaranteed/optimal); pressure-test, then refine with explicit boundaries. Use when users ask to prove or disprove strong certainty claims, request devil's-advocate challenge rounds, or want the $prove-it gauntlet to run in default autoloop/full-auto style.