Appearance
Design
🔵 No design exists. Owner-confirmed 2026-08-28: there is nothing in Claude Design for this feature.
This is a design REQUEST, not a design pull
CLAUDE.md draws a hard line between the two, and this feature falls on the request side. The process is explicit and gated:
- Identify the missing screen and say so rather than filling the gap in code.
- Specify it fully in prose first — purpose, the user categories served, entry points, states (loading / empty / error / partial), data contract, permissions, and the proactive-value answer.
- Record the specification as a portal page and register it in the sidebar. This directory is that record.
- Then send it to Claude Design.
- Generate, implement against the design system, and record any divergence in the drift ledger.
⚠ Step 4 must not happen yet. CLAUDE.md: "Never send an architecture-gated question to Claude Design. If the missing screen depends on an undecided contract, resolve it as a QRS-###/ADR first and put the DECIDED contract in the prompt."
What must be decided before a design is requested
Four things, all in Architecture. A design produced against any of them undecided has to be rejected and redone:
| Undecided | Why the design cannot proceed without it |
|---|---|
| Consumer identity and slug ownership | Determines whether there is a My QR Setu hub screen at all, and what the biodata's address looks like on every share surface |
| Owner vs subject | Determines whether the builder screens are "about me" or "about someone I represent" — different copy, different consent steps, different information architecture |
| Disclosure tiers | The open/requested/private split is the recipient screen's structure |
| PII posture | No indexing, no public discovery, no viewer identification — this removes screens a designer would otherwise assume (search, browse, suggested profiles) |
Which design project
⚠ There are two, and picking the wrong one wastes a round:
- QR setu prototype (
633dc069-6df8-4408-b625-068907c60c33) — the screens. This is the one. - QR setu Design System (
37245d93-4fa1-42d0-b765-53a7664d5129) — tokens and components, which the screens consume.
An absence in one proves nothing about the other (QRS-451).
Screens a specification will need to cover
Not a design, just the enumeration a prompt must contain. Every one needs its states named, because CLAUDE.md's fourth rule treats a silently-omitted state as a process failure:
Creator, in the app
- Identity / My QR Setu hub — with the biodata activated, and without
- Biodata builder — sectioned, resumable, with an import-from-PDF entry
- Disclosure control — what is open, on request, private
- Share sheet — WhatsApp, QR, copy link, and the preview as it will appear
- Requests and interests — approve, decline, respond
- Status control — open · discussing · closed · finalised
- Insights — the small analytics surface
Recipient, on the web (no account)
- The open tier
- Request-access state, and its pending / approved / declined states
- Express-interest, with the OTP step
- Closed proposal — a designed experience, not a 404
- Not-found, indistinguishable from closed-and-private
Consent
- Subject confirmation, when the creator is not the subject
- Subject's own controls, including takedown
Design constraints that are already fixed
These are not open to the design round:
- Marathi and English, Devanagari rendering via
fonts.deva(Noto Sans Devanagari) - Recipient surface is DOM, server-rendered, on
apps/web— mobile web, no install - No em dash in any user-facing copy — gated over every i18n catalogue leaf
- Never volunteer a privacy reassurance at the point of use (QRS-549) — state what the product does, never what it refrains from doing
- Tokens only, zero hard-coded colours; light and dark both defined
- Report control on every public page, from the first release
Reference material for the eventual prompt
The reference landscape establishes what the category looks like today: community- and gender-specific templates, one- and two-page layouts, traditional motifs, and standard fields including gotra, nakshatra, manglik status and rashi. A design that ignores those conventions will read as foreign to the audience; one that copies them uncritically inherits the caste-data decision by accident.