Use this skill when writing, reviewing, or deciding where to place tests in the Next.js frontend package. Covers which project (unit / integration / storybook) to use for a given scenario, what NOT to duplicate across projects, and file placement conventions for this package.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
See guidelines.md for the full decision rules and examples.
| Project | Pattern | Environment | Purpose |
|---|---|---|---|
| unit | *.unit.test.ts(x) | happy-dom | Pure logic: utils, hooks, data transforms |
| integration | *.integration.test.tsx | happy-dom | User flows across components with MSW |
| storybook | *.stories.tsx | browser | Visual states, a11y, interaction per component |
"If this test fails, do I tell the designer or the engineer?"
- Designer → storybook
- Engineer → unit or integration
src/components/Button/Button.unit.test.tsxsrc/components/Button/Button.stories.tsxsrc/mocks/handlers/apps/nextjs/.storybook/vitest.config.ts → monorepo root (not in this package)For the full decision guide, do-not-duplicate rules, and code examples,
read guidelines.md in this directory.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write a Conventional Commits message for the staged changes, show it for review, and commit only after the user approves it.
The English summary is being prepared. Showing the original description.
Push the current branch and open a GitHub pull request whose description follows .github/PULL_REQUEST_TEMPLATE.md.
The English summary is being prepared. Showing the original description.