Loading...
Loading...
Found 3,730 Skills
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.
Design color palettes that are accessible to all users including those with color blindness. Ensure sufficient contrast, meaningful use of color, and inclusive design.
Track user metrics and provide data-driven insights for product decisions. Use when measuring product health, analyzing user behavior, conducting cohort analysis, or optimizing key metrics. Covers acquisition, engagement, retention, revenue metrics, and data-driven decision making.
Implement features using tracer bullet approach - build minimal end-to-end vertical slice first, then expand.
Conversion-focused landing page optimization playbook. Use when auditing or improving landing pages, hero/CTA sections, forms, social proof, or experimentation plans for marketing sites, SaaS, or e-commerce.
REQUIRED when modifying any file in packages/playground-ui or packages/playground. Triggers on: React component creation/modification/refactoring, UI changes, new playground features, bug fixes affecting studio UI. Generates Playwright E2E tests that validate PRODUCT BEHAVIOR, not just UI states.
Design Sprint methodology based on Jake Knapp's "Sprint" (Google Ventures). Use when you need to: (1) validate product ideas in 5 days instead of months, (2) rapidly prototype and test solutions, (3) answer critical business questions quickly, (4) align teams on product direction, (5) de-risk product development before building, (6) test multiple concepts with real users, (7) make fast strategic decisions through structured process.
Expert guidance for R package development following best practices for devtools, testthat, roxygen2, and R ecosystem tools
Execute and manage Rust tests including unit tests, integration tests, and doc tests. Use when running tests to ensure code quality and correctness.
Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.
HTTP Parameter Pollution (HPP): duplicate query/body keys parsed differently by servers, proxies, WAFs, and app frameworks. Use when filters and application layers disagree on which value wins, enabling bypass, SSRF second URL, logic abuse, or CSRF token confusion.