docs: require storybook coverage for visual slices

2026-09-08 21:52:48 -04:00
parent 9bb4a16e9e
commit 0d286f09a8
2 changed files with 33 additions and 1 deletions
@@ -52,3 +52,22 @@ The documentation is the source of truth. Do not invent requirements when an aut
 Prefer small, focused changes. Avoid unrelated refactoring.

 When a decision changes the architecture or requirements, update the relevant documentation before or with the implementation.
+
+## Vertical slice completion
+
+Each vertical slice must be complete before it is committed and pushed:
+
+- A new or changed Vue visual component must have a colocated Storybook story or an updated existing story covering its meaningful states.
+- Stories must use representative fixture data and must not introduce production domain behavior solely for visual coverage.
+- Visual slices must pass the web tests, production build, Storybook build, and Storybook interaction/accessibility runner before commit:
+
+	```sh
+	npm run test --workspace=@pokemon-inventory/web
+	npm run build --workspace=@pokemon-inventory/web
+	npm run build-storybook --workspace=@pokemon-inventory/web
+	npm run test-storybook
+	```
+
+- Storybook stories must cover relevant loading, empty, error, selected, disabled, responsive, light/dark theme, and keyboard states when those states exist in the component.
+- Backend-only slices do not require Storybook changes unless they alter a user-facing visual contract.
+- The final commit gate includes the appropriate API/domain/integration tests plus all applicable web and Storybook checks.