Brief For Antho
Status: draft v0.2
Audience: Antho, Eric, Codex
Current Situation
The app now has three Antho-backed TestFlight reference surfaces in Build 84:
- Home / Accueil
- Connexion
- Mes coachs
The first rollout proved that a faithful PSD-backed surface can work when the visual shell is treated as the reference layer and the functional controls stay native. The problem is that the rest of the app still uses the older SwiftUI card system, so the design language breaks as soon as the user leaves those three screens.
The purpose of design.linecard.fr is now to turn the Build 84 reference set into a clean design resource for the remaining app.
What We Need From Antho Now
We do not need every iOS view redesigned one by one.
We need Antho to help extract the reusable design system from the three accepted surfaces:
- visual identity
- color and material rules
- typography hierarchy
- spacing rhythm
- card/panel style
- button style
- icon mood
- avatar/badge/progress treatment
- C4-DY visual presence
- motion direction
- asset rules
The next useful output is a rule pack, not another isolated screen.
Accepted Reference Set
| Reference | What Codex can reuse now | What Antho should clarify |
|---|---|---|
| Home | Full-canvas premium background, bottom menu, large action buttons, player/progress capsule, Mon Caddie and Mes coachs placement | Which parts become reusable SwiftUI components vs fixed raster layers |
| Connexion | Field placement, back action placement, calm premium login mood, native input overlay | Error/loading/keyboard states, larger-text behavior, localization-safe text zones |
| Mes coachs | Coach/student bridge mood, live counters, CTA, back action, empty-state frame | List rows, booked lesson cards, pending/invalid coach states, dense coach data treatment |
Deliverables
1. Extracted Visual Rules
One short rule board derived from the three Build 84 references:
- background/shell rules
- live text/data overlay rules
- button/tile rules
- bottom menu rules
- capsule/progress rules
- list-row rules
- CTA hierarchy
- what must stay native and live
Good LineCard words:
- premium
- precise
- training
- calm
- golf
- progress
- companion
- social
Avoid:
- casino/game UI
- generic fitness app
- luxury brochure
- too much gold
- unreadable glass effects
- over-designed score entry
- full-screen PSDs that cannot scale beyond one surface
2. Tokens
Provide actual values or sampled references when possible:
- primary background
- surface/card colors
- main green
- active green
- silver/gold/accent
- text colors
- border/glow colors
- spacing scale
- radius scale
- shadows/glows
- typography roles
- overlay opacity rules
- raster export sizes and safe zones
Codex will translate them into tokens.linecard.json and SwiftUI Theme.swift.
3. Priority Archetype Rules
These are not final production screens. They are design grammar examples.
- Atelier list + atelier detail + score entry
- Mon Caddie companion moment
- Classement / social ranking
- Badge or level unlock celebration
- Coach Studio dense professional surface
Each archetype should show:
- hierarchy
- component style
- spacing
- primary action
- empty/loading/error state if important
- any asset treatment
4. Component Examples To Fill The Gap
One or two examples for:
- primary button
- secondary button
- pill/chip
- progress card
- player card
- challenge card
- atelier card
- badge card
- Mon Caddie / C4-DY entry point
- notification/celebration surface
- dense coach row
- live-data overlay
5. Assets
If working from Photoshop, export assets as full-canvas PNG layers only when a real layer stack is needed. Otherwise prefer reusable assets:
- logos
- avatar/C4-DY assets
- badge artwork
- background texture
- medal/level treatments
- card image treatments
Asset rule:
- one preview PNG
- individual assets clearly named
- no hidden "magic" in the PSD that Codex cannot reproduce
- each text layer marked as fixed artwork or live/native text
- each tap zone marked as artwork-only, native control, or transparent hit area
Format Options
Preferred:
- PNG/JPG references
- short Markdown notes
- token values
- Figma frame only if useful
Acceptable:
- Photoshop layer exports
- screenshots with annotations
- rough sketches
Not useful:
- vague comments like "make it more premium"
- one-off full-screen visuals with no reusable rule
- Figma-only comments that do not explain intent
What Codex Will Do With This
Codex will:
- update this design folder
- build or update an HTML design atlas for team review
- translate approved rules into SwiftUI
- capture real iOS simulator screenshots
- compare before/after
- keep durable decisions in
.brain/at wrap-up
Current Antho Ask
For the next pass, Antho should answer:
- From Home, Connexion, and Mes coachs, which visual pieces are reusable system components?
- Which pieces should stay as full-canvas raster art, and which should become native SwiftUI?
- What is the Antho rule for Ateliers: list cards, detail sections, score entry, and success/failure feedback?
- What should Mon Caddie look like inside the Antho system: floating button, bottom-bar companion, dashboard card, or contextual sheet?
- How should Classement and badges inherit the premium style without becoming a casino/game UI?
- Does Coach Studio keep the same dark premium grammar, or does it get a denser professional variant?
- What are the exact token values for green, dark background, silver/gold accent, glow, borders, radii, and typography?