add-feature

Add a new feature to this Quiver app: $ARGUMENTS

The argument is a feature name and optional brief description (e.g. blog — list and read blog posts, cart — add items and checkout).

Follow this process:

Step 1 — Plan (do this first, before writing any code)

Analyse the feature request and produce a short plan covering:

• Pages needed — list each route and its purpose
• State module(s) needed — list each store and its key data/actions
• Component(s) needed — list any new reusable components
• Nav links — does MenuLayout sidebar need a new link?
• Tests — what E2E scenarios cover the happy path?

Present the plan to the developer and wait for confirmation before proceeding.

Step 2 — Implement

Execute the plan in this order:

1. State module(s) — create src/state/<name>.js as a module-scope reactive({...}) object. Export as singleton. See existing src/state/userState.js as the reference pattern.

2. Component(s) — create each in src/components/<Name>.js; import them directly from their files where used (there is no barrel).

3. Pages — create each in src/pages/<path>.js. Structure:

   import { html } from '@arrow-js/core'
   import { useMeta } from '../framework/index.js'
   export const meta = { layout: 'menu', title: 'Page Title' }
   function FeaturePage() {
     useMeta({ title: 'Page Title' })
     return html`...`
   }
   export default FeaturePage
   

4. Nav link — if needed, add a Link entry to src/layouts/MenuLayout.js matching the pattern of existing nav links.

5. E2E test — create tests/e2e/<feature>.test.js covering the main user flow. Use role-based Playwright selectors; add data-testid attributes where needed.

Step 3 — Verify

Run bun run dev and confirm the feature works end-to-end in the browser. Then run the full gate and fix any failures before reporting done:

bun run typecheck && bun run test && bun run test:e2e

Arrow.js rules (apply throughout)