# Make Atelier yours

You are extending the included Atelier workspace. Start by opening `index.html`, then inspect `app.js`, `style.css` and `data.js` before changing anything. The current app already has a coherent visual direction; preserve it.

## The outcome

Add a small **Assets** section to each project's details. A studio should be able to browse the project's matching covers, inspect one, and download the original local file.

- Start with the bundled Forma, Fieldwork and Orbit visuals. Use actual local assets, meaningful labels and clear dimensions/file types.
- Selecting an asset should open a considered preview with a download action. Keyboard focus enters the dialog and returns to the triggering control when it closes.
- Give new projects a useful empty state that explains the next step without implying an upload or image-generation service exists.
- Preserve project search, filters, favorites, task editing, new project creation and local persistence.
- Keep the app directly runnable offline. Do not add a framework, dependencies or credentials just for this exercise.

## Keep the direction

The visual language is warm white, restrained olive, fine borders, clear typography and deliberate imagery. Reuse the existing spacing, color and dialog patterns. Before fetching references or generating anything, check what the project already provides. Research once for a new direction; keep those references for follow-ups. Optional mockups are useful when changing the direction, but are unnecessary here.

If you choose to create additional visuals, define one art direction for the complete set and save the assets in the project. Record their provenance. Any paid image generation requires the user's configured provider and credits; the included sample does not require it.

## Finish the work

Read `../../skills/accessibility/keyboard-paths/SKILL.md` and `CHECKS.md`. Inspect the actual rendered result on desktop and mobile. Compare typography, composition and imagery with the original screen; fix the weak details. Verify a complete keyboard path and reduced motion. Explain what changed and what you checked.

Use the sample as a starting point for your own product, not as a claim of a measured agent-performance improvement.