What we covered
and what to
do next.
Workshop recap
Codex for frontend development
Models, reasoning effort, plugins, skills, browser features, and project setup.
Building with Sites
A landing page, deployment, access, storage, integrations, and Mission Control.
From idea to frontend
Visual direction, image generation, ambitious interactions, staged builds, and goals.
Frontend debugging with Codex
Reproduce the issue, inspect the browser, fix the cause, and verify the result.
Building in existing projects
Repository context, design-system reuse, scoped changes, User Insights, and review evidence.
Living frontends
Interfaces created for the current task and a reusable screenshot-to-component skill.
Working with Codex
Start with one clear task and list what the result must include.
Give Codex the relevant files, references, tools, and constraints.
Ask it to reuse the project’s existing components and styles.
Open the result in the browser and point to what needs changing.
Check the main interaction on desktop and mobile.
Put repeated instructions in AGENTS.md or a skill.
Next steps
Adapt Mission Control to your workflow
Replace the example projects, owners, statuses, and metrics with the work your team actually tracks. Connect the sources you use and decide what should update automatically.
What would your team need to see every day?
Pick one real task
Choose a landing page, a scoped product change, a frontend bug, a persistent Site, or an interactive explanation. Use one clear reference and write the acceptance criteria before you start.
What frontend task will you try first?
Save what should be repeated
Put stable repository rules in AGENTS.md. If the same frontend workflow will happen again, turn it into a skill.
What do you keep explaining that should live in the repository?