skills.rest
masakinihirota
masakinihirotaCOMMUNITY
Explore all skills by this author →
𝕏@masakinihirotaGitHub

test-case-outline-generation

Generates Vitest test case outlines using describe and it.todo before TDD implementation.

Updated Jul 21, 2026
Search Tags:#vitest#tdd#unit testing#test design#test cases#react hooks#it.todo
One-click install
npx skills add https://github.com/masakinihirota/2026src-ni --skill test-case-outline-generation-masakinihirota
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-case-outline-generation
Source: https://github.com/masakinihirota/2026src-ni/tree/main/.agents/skills/test-case-outline-generation
Command: npx skills add https://github.com/masakinihirota/2026src-ni --skill test-case-outline-generation-masakinihirota

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting TDD without a fixed test design leads to missed edge cases and inconsistent coverage. This Skill produces a complete, implementation-free test case outline so test perspectives are locked in before any code is written. ## Core Features & Use Cases - Outline-only generation: Outputs only Vitest describe and it.todo blocks with intent comments, never Arrange/Act/Assert logic or mock implementations. - Structured coverage categories: Enforces normal cases, error cases, boundary values, spec constraints, parameter changes, and date/time boundaries. - React Hook support: Adds dedicated perspectives for initial state, state transitions, async completion, error recovery, unmount cleanup, and Strict Mode re-execution. - Use Case: Before implementing a template usage ranking feature (top 20, default past 7 days, /dashboard display), generate the full test outline to confirm spec ambiguities like tie-breaking rules and empty-data behavior with stakeholders. ## Quick Start Ask the AI to apply the test-case-outline-generation skill and output test cases for your target function or React Hook using only describe and it.todo.

Frequently Asked Questions about test-case-outline-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design test cases before writing implementation code?▼

Write test outlines using only describe and it.todo blocks in Vitest, with a one-line intent comment above each case. This fixes test perspectives during the TDD RED phase without writing any Arrange/Act/Assert logic.

What test categories should a Vitest outline cover?▼

Cover normal cases, error cases, boundary values, spec constraints, parameter changes, and date/time boundaries. For React Hooks, add initial state, state transitions, async completion, error recovery, unmount cleanup, and Strict Mode re-execution.

Can I use it.todo for React Hook test design?▼

Yes, it.todo works well for outlining React Hook tests before implementation. Structure cases around initial render state, dependency changes, async state updates, error transitions, and unmount behavior without writing hook invocation code.

When should I not write test logic in an outline?▼

Avoid writing executable logic when specifications are still ambiguous, such as timezone handling, tie-breaking rules, or empty-data display behavior. Confirm these details with stakeholders first, then generate the outline cases.

Why use it.todo instead of skipped tests in Vitest?▼

it.todo explicitly marks tests as planned but unimplemented, appearing as todo items in test reports. This keeps the outline as living documentation for spec review while making unimplemented cases visible in CI output.

Related Skills

Explore More Software Engineering Skills→
dmayerdesigndmayerdesign

spex-specify

Define software behavior specifications using given/when/then scenarios.

Community
Advanced
ThePhoenixAgencyThePhoenixAgency

tdd-mastery

Enforce the TDD Red-Green-Refactor cycle for business logic implementations.

Official
Intermediate
LaunchPadLabLaunchPadLab
1

feature-review

Review feature specifications for completeness and generate missing Gherkin scenarios.

Official
Intermediate
HonigbartHonigbart
1

quick-plan

Write executable plans to .ai/plans/<slug>/final_plan.md.

Community
Basic