# B2B E-Commerce Frontend — Detailed AI-Agent Specification

This package defines the **frontend-only e-commerce scope**.

It deliberately excludes ERP, accounting, warehouse management, inventory management, procurement, manufacturing, HR, finance, and other non-e-commerce ERP modules.

## Required stack

- Nuxt
- Nuxt UI
- Vue 3
- Vite (through Nuxt; no separate Vite application)
- Bun
- Tailwind CSS
- Axios
- TypeScript

## Required skills

Use these skills when available:
- `design-taste-frontend`
- `ui-ux-pro-max`
- `nuxt-ui`
- `impeccable`

Per the global AGENTS.md, these are always active on every task:
- `i-have-adhd` — task execution, focus, progress, response structure
- `rtk-ai` / `rtk` — tool and command output reduction
- `caveman` — unnecessary prose/context reduction
- `ponytail` — unnecessary code and architectural complexity reduction

## UI rule

Nuxt UI is the primary component library.

Use:
1. Nuxt UI directly
2. Nuxt UI with props/slots
3. Thin domain-specific components composed from Nuxt UI
4. Fully custom UI only when Nuxt UI genuinely cannot satisfy the requirement

Do not rebuild standard Nuxt UI components with raw Tailwind.

## Scope rule

The complete feature inventory is in `docs/FEATURES.md`.

The traceability matrix is in `docs/FEATURE-MATRIX.md`.

Acceptance criteria are in `docs/ACCEPTANCE-CRITERIA.md`.

Implementation phases are in `tasks/`.

Every feature must be traceable from:
Feature → screen/workflow → UI components → API dependency → states → acceptance criteria → implementation phase.

## First agent prompt

The global opencode AGENTS.md
(`C:\Users\Admin\.config\opencode\AGENTS.md`) is authoritative for
engineering, security, skill, and output standards. This repo's `AGENTS.md`
layers project-specific rules on top of it. Read both.

Read all of:
- AGENTS.md
- SPEC.md
- ASSUMPTIONS.md
- docs/FEATURES.md
- docs/FEATURE-MATRIX.md
- docs/ACCEPTANCE-CRITERIA.md
- docs/UI-RULES.md
- docs/ARCHITECTURE.md
- docs/ROUTES.md
- docs/AXIOS.md
- docs/AUTH.md
- docs/STATE.md
- docs/SKILLS.md
- docs/TESTING.md
- every task file
- the actual `design-taste-frontend`, `ui-ux-pro-max`, `nuxt-ui`, and
  `impeccable` skills if available

Release notes for this repo and the other three are consolidated in
`CHANGELOG_CLIENT.txt` at the workspace root (outside this repository).

Do not code yet.

Perform a discovery pass:
1. Validate the feature inventory.
2. Separate confirmed requirements from assumptions.
3. Identify missing backend/API contracts.
4. Map each feature to routes/screens.
5. Map each screen to Nuxt UI components.
6. Identify the genuinely necessary custom domain components.
7. Define API services/types/composables.
8. Define auth/session and permission behavior.
9. Define loading/empty/error/validation states.
10. Produce an implementation plan.

Do not silently remove features.

Do not add ERP features.

Do not invent backend behavior.

Stop and wait for approval before implementation.

## Engineering and security standards

Follow the global AGENTS.md engineering and security standards: security-first
development, backend-authoritative authorization, safe error handling, and the
global definition of done. Never treat frontend guards or hidden controls as
security boundaries.