frontend-helper/CLAUDE.md

frontend-helper

Minnect feed browser. A web app where each person signs in with their own Minnect email and password, then reads and writes the expert home feed. Minnect tokens stay on the server.

• CRM project: Minnect (9aw9m1ka4), module Feed browser.
• Original contract: docs/minnect-feed-browser.spec.md.
• Redesign build contract: docs/minnect-feed-redesign.spec.md (copied from the Minnect workspace docs/). It covers the feed browser redesign and is the single source for the redesign tasks.
• Stack: Next.js App Router. Route handlers are the same-origin server that holds sessions.

Rules

1. Never put a token, password or session id in the repo, the frontend bundle, a query string or a log line.
2. Never call a Minnect route whose path contains /admin/, feed POST /api/v1/auth/login, or POST /api/v4/auth/external-services/auth-user.

Branching (project override of the crm-milestone skill)

This repo uses one branch per milestone, not one branch per task.

1. Each milestone starts with a branch cut from develop: feature/feed-browser-<milestone-slug> (for example, feature/feed-browser-sign-in).
2. Tasks run one at a time, in dependency order, on that branch. Each commit is <task-uid>: <imperative sentence>, with no AI attribution.
3. When every task in the milestone is done, merge the branch into develop with a merge commit (git merge --no-ff). Never squash.
4. Move the milestone's tasks to Validation. This board has no In Review or Dev Check status.
5. After validation, merge develop into main and move the tasks to Done. Only a person merges into main.

Every module has a Mobilization milestone (requirements, ADRs, spikes; sign-off before build) and a Finalization milestone (acceptance pass and handoff).