fantasia-archive — Cursor Rules

• Scope: */tests/.stories.ts. • Workspace / config: Storybook runs from .storybook-workspace/ (root yarn storybook:run / yarn storybook:build). For staticDirs, Vite plugins, or global preview, edit .storybook-workspace/.storybook/—not a separate root .storybook/ tree. Static output is .storybook-workspace/storybook-static/. yarn storybook:build and yarn test:storybook:smoke run with --quiet --loglevel warn; interactive yarn storybook:run stays verbose. Storybook VRT lives beside it: playwright.storybook-visual.config.ts and visual-tests/ under .storybook-workspace/; root yarn test:storybook:visual delegates to yarn --cwd .storybook-workspace test:storybook:visual. Optional per-story VRT progress: set FA_STORYBOOK_VISUAL_VERBOSE=1 (see visual-tests/storybook.visual.playwright.test.ts). • Layouts and pages (src/layouts//tests/.stories.ts, src/pages//tests/.stories.ts): canvas-only previews (shell/routing checks). Do not add tags: ['autodocs'], autogenerated Docs, or parameters.docs.description / other docs prose. Keep parameters.docs.disable: true on meta. Do not add or generate Storybook documentation pages for layouts/pages in the future. • src/components/ stories must represent user-facing component behavior and stable contracts (autodocs allowed where already used for components). For modals, q-dialog, or anything that auto-opens on mount, set parameters.docs.story.inline: false (and a sensible iframeHeight) on that file’s meta: Autodocs renders every story on one Docs page; inline: true mounts all of them at once so multiple dialogs/menus stack and “bleed.” Each nested Docs iframe still loads the same preview bundle (Quasar + app.scss**) when preview is configured as in this repo. • Do not add stories using the A11y/* naming category. • Keep accessibility validation in Vitest/Playwright and manual QA flows, not Storybook stories. • Do not create stories that only validate or force window.faContentBridgeAPIs.extraEnvVariables.TEST_ENV === 'components'. • Do not set Storybook-only contentBridgeOverrides.extraEnvVariables.TEST_ENV = 'components' as a story scenario. • Keep TEST_ENV branch validation in Playwright/Vitest/component-test harnesses, not Storybook docs/stories.

• For Vue (.vue) and TypeScript (.ts) source files, move small file-local interfaces/type aliases into a colocated <filename>.types.ts file and import them back. • For JavaScript (.js), TypeScript (.ts), Vue (.vue), and JSON (.json, .jsonc, .json5) files, enforce expanded multi-line object literals via ESLint (object-curly-newline + object-property-newline) and keep files auto-fixable with eslint --fix.