vitest-bdd-3layer
Implement structured BDD testing with Vitest. Separates business-readable scenarios from technical mock/adapter implementations.
Install
mkdir -p .claude/skills/vitest-bdd-3layer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4571" && unzip -o skill.zip -d .claude/skills/vitest-bdd-3layer && rm skill.zipInstalls to .claude/skills/vitest-bdd-3layer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
DashPlayer 三层 Vitest-BDD 技能。Use when developers want business-readable BDD scenarios without coupling scenario writing to code implementation details. Triggers on: "BDD 三层", "行为测试分层", "给定当那么", "Vitest BDD", "不想在场景里写实现".Key capabilities
- →Write BDD tests using Vitest and a three-layer model
- →Decouple scenario writing from implementation details
- →Organize business actions into a step dictionary
- →Manage mock, fixture, and dependency injection in an implementation layer
- →Ensure business-readable BDD scenarios
How it works
The skill enforces a three-layer structure for Vitest BDD tests, separating business sentences (scenario layer) from business actions (step dictionary layer) and underlying mock/fixture management (implementation layer). This ensures scenarios are business-readable and maintainable.
Inputs & outputs
When to use vitest-bdd-3layer
- →Write business-readable tests
- →Decouple tests from service logic
- →Standardize BDD test structure
- →Verify complex service contracts
About vitest-bdd-3layer
Enforces a three-layer model (Scenario, Step Dictionary, Implementation) for Vitest tests. It keeps business requirements readable while isolating mock and fixture complexity.
DashPlayer 三层 Vitest-BDD 技能。Use when developers want business-readable BDD scenarios without coupling scenario writing to code implementation details. Triggers on: "BDD 三层", "行为测试分层", "给定当那么", "Vitest BDD", "不想在场景里写实现".
When not to use it
- →For pure algorithm utility functions
- →For highly volatile, flaky, or strongly sequential use cases
Limitations
- →Scenario layer cannot contain technical details like mock or new service instances
- →Step methods must follow 'given/when/then' naming conventions
- →A single scenario should not cover multiple business promises
How it compares
This skill standardizes BDD testing by strictly separating concerns into three layers, preventing the coupling of business scenarios with technical implementation details often found in less structured testing approaches.
Compared to similar skills
vitest-bdd-3layer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| vitest-bdd-3layer (this skill) | 1 | 6mo | Review | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| angular-best-practices | 21 | 3mo | No flags | Advanced |
| validate-typescript | 5 | 9mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by solidSpoon
View all by solidSpoon →You might also like
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
angular-best-practices
sickn33
Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
validate-typescript
BerryKuipers
Run TypeScript compiler type-checking (tsc --noEmit) to validate type safety and catch type errors. Works with any TypeScript project. Returns structured output with error counts, categories (type/syntax/import errors), and affected files. Used for quality gates and pre-commit validation.
ts-testing
johnlindquist
Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that should be covered by tests.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.