# look (https://lazyfrog.dev/docs/tools/look)

{/* Generated by scripts/generate-docs.ts from the gateway's registered tools. Do not edit. */}

**{"Project look"}** · Can change or delete · actions: `get`, `propose`, `choose`, `apply`

<p>{"For reading use look_read, which is read-only and needs no approval: \"get\" here is deprecated (still works). The project's own look, so it doesn't come out generic. action \"propose\": 2 to 4 distinct directions you designed for THIS project from what the user told you (directions: colours, Google Fonts, radius, density, mood, and optionally typeScale, headingWeight, headingItalic, letterSpacing, imagery, layout, voice, motion); \"get\" first gives starting points seeded for this project so it doesn't look like every other. Propose before the plan's questions, then offer them as one of those questions (plan ask, kind: \"look\", options their names, default your recommendation), not as a separate round: the card shows each as swatches, the Plan tab as a live style tile, and the answer chooses the look. \"choose\": the one they picked (pick: its number), or a look they brought (look: their brand colours and fonts). \"apply\": write the chosen look into the code as design/tokens.css (CSS variables: colours, fonts, a fluid type scale --step--1..--step-5, spacing --space-1..8, --measure, shadows, heading style; the fonts as the project's own files; an opt-in base stylesheet with class=\"lf-base\") and design/tokens.json; import it and use the variables. \"get\": what was proposed and chosen. Optional: if the user has a design system already or doesn't care, use theirs or decide yourself."}</p>