Loading...
Loading...
Found 3,725 Skills
QA cycling workflow - test, verify, fix, repeat until goal met
Guidelines for Blazor development including component lifecycle, state management, and performance optimization
Use when developing or documenting trading strategies - guides edge hypothesis formation, validates statistical significance, documents strategy rules systematically (entry, exit, risk management). Activates when user says "research this strategy", "document my approach", "test this idea", mentions "trading strategy", "edge", or uses /trading:research command.
Extract raw price dataframe for a test case
Use when backing up, restoring, or validating golden datasets. Prevents data loss and ensures test data integrity for AI/ML evaluation systems.
Validate WCAG 2.1 compliance, screen reader compatibility, and Universal Design for Learning (UDL) principles implementation throughout curriculum materials. Use when checking accessibility, validating UDL, or ensuring compliance. Activates on "accessibility check", "WCAG validation", "UDL review", or "screen reader test".
When the user wants to design, prioritize, or analyze growth experiments -- including A/B tests, hypothesis frameworks, ICE/RICE scoring, or growth sprints. Also use when the user says "A/B test," "experiment design," "growth sprint," "experiment prioritization," or "statistical significance." For analytics setup, see product-analytics. For growth modeling, see growth-modeling.
Run Rust tests after making changes to verify correctness
Debug regex patterns with visual breakdowns, plain English explanations, test case generation, and flavor conversion. Use when user needs help with regular expressions or pattern matching.
Use when conducting user research (interviews, usability tests, surveys, A/B tests) or designing research studies. Covers discovery, validation, evaluative methods, research ops, governance, and measurement for software experiences.
Use when working with tdd workflows tdd refactor
Expert implementation guide for custom Clean Architecture pattern in Golang projects. Use when implementing features with domain-driven design, creating API endpoints, or working with this specific 4-layer architecture (Domain, Application, Integration, Infrastructure). NOT Uncle Bob's standard Clean Architecture - this is a specialized adaptation with strict dependency rules and specific conventions.