# Kalei — Claude Code Implementation Instructions > **Purpose:** This document tells Claude Code everything it needs to know to build, modify, improve, and polish pixel-perfect interactive HTML mockups for every screen in the Kalei app. > > **For agent teams:** This is the single source of truth. Read this file completely before touching any screen. Follow the agent workflow in Section 2, the quality standards in Section 15, and the review protocol in Section 20. --- ## 1. What You're Building You are building **76 interactive HTML mockup screens** for Kalei, a mobile mental wellness app (64 original + 12 Guide screens). Each screen is a standalone `.html` file that: - Renders at **390 × 844px** (iPhone 14 viewport) inside a rounded device frame - Uses the shared `design-system.css` for all tokens, typography, components, and layout - References SVG assets from the `assets/` folder for icons, patterns, decorations, and visualizations - Includes micro-interactions and state transitions using CSS animations + minimal vanilla JS - Can be viewed in any browser by opening the file directly (no build step, no server) - Is **fully self-contained** — all SVGs are inlined or referenced from the local `assets/` folder. No external image URLs, no CDN dependencies for icons or illustrations. Only Google Fonts and the local `design-system.css` are external dependencies. **Output format:** Single-file HTML per screen. All CSS beyond `design-system.css` goes in a `