test-designTest design and strategy skill for comprehensive testing. Use when: designing test cases, planning testing strategy, writing unit/integration/e2e tests, or i...
Install via ClawdBot CLI:
clawdbot install sydpz/test-designGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Oct 8, 2026
A fintech startup with a legacy Node.js codebase has zero automated tests and frequent production regressions in its withdrawal and balance logic. The team wants to adopt the testing pyramid by first writing unit tests for core money-handling functions using the AAA pattern, then gradually introducing integration tests around the payment ledger. This reduces hotfix frequency and builds engineer confidence in refactoring.
An e-commerce platform experiences revenue loss when checkout flows break after each deploy. The team uses this skill to define E2E tests only for critical paths (add to cart, payment, order confirmation) while relying on faster unit and integration tests for cart calculations and coupon logic. This balances release speed with high-confidence coverage of money-critical journeys.
A healthcare SaaS integrates with multiple EHR systems via a gateway service with strict compliance requirements. The team applies mocking strategies carefully—using fakes and stubs instead of heavy mocks—to test integration points between services while keeping unit tests focused on business rules. Coverage targets are documented per layer to satisfy audit and QA requirements.
A B2B analytics company wants to shift to test-driven development to reduce bug backlog and improve onboarding for new engineers. The skill provides naming conventions, test case categories (happy path, edge cases, error cases), and execution cadences so the team runs unit tests on every save and integration tests before each PR. This standardizes practice across squads.
A logistics company manages a fleet tracking platform with complex scheduling and routing logic prone to edge-case failures (empty routes, extreme distances, concurrent driver assignments). The team uses the skill's edge-case and extreme-case categories plus test data strategies like factories and seeded data to systematically cover boundary conditions. This cuts incident response time and improves reliability of dispatch operations.
A vendor offers a test-design assistant or CI-integrated testing platform that guides engineering teams through pyramid-based test planning and coverage targets. Teams subscribe per seat or per repository to access templates, conventions, and automated test scaffolding.
A consultancy uses the skill's frameworks to run workshops and audits for client engineering teams, helping them establish testing strategy, naming conventions, and execution cadences. Engagements often include hands-on pairing with engineers to retrofit test suites into legacy codebases.
An enterprise platform embeds testing strategy guidance, coverage dashboards, and test case management directly into CI/CD pipelines. Large organizations license it to standardize testing practice across many teams while meeting compliance and audit requirements.
💬 Integration Tip
Pair this skill with your existing test runner and CI configuration so generated test plans map directly to executable suites, and start by applying it to one high-risk module before rolling conventions out broadly.
Scored Oct 8, 2026
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Tailwind reference tool. Use when working with tailwind in frontend contexts.
A product creation skill based on the "Bee Website Builder" Open API. It is used to create a new product under a specified site language and product group, w...
A product update skill based on the "Bee Website Builder" Open API. It is used to update an existing product under a specified site language and supports upd...
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.