One more thing: want Codex to build good-looking pages without having to keep saying “make it look better”? Try these 3 design Skills together: 𝟭. 𝗜𝗺𝗽𝗲𝗰𝗰𝗮𝗯𝗹𝗲 Use it when the page is built, but something still feels off. Too bland? Use bolder. Too cluttered? Use distill. Almost finished? Use polish to refine the details. It turns “make it look better” into specific design changes Codex can make. 𝟮. 𝟮𝟭𝘀𝘁 𝗗𝗲𝘀𝗶𝗴𝗻 This is a Skill I put together that gets Codex to look for components and interaction references on before building a page. I’d suggest packaging your own go-to component library into a Skill, too. It doesn’t have to be Focus on the one or two sections that carry the page: a hero, a set of pricing cards, or a product showcase. Pick what fits, then adapt it to your brand, content, and existing project. 𝟯. 𝗨𝗫 𝗔𝘂𝗱𝗶𝘁 A good-looking screenshot isn’t enough. Have Codex open the browser and actually use the page. Click buttons, fill out forms, switch to a mobile viewport, and complete the user journey. Find buttons that do nothing, confusing error messages, and steps where it’s unclear what to do next. Get reproduction steps and specific fixes. If you can’t be bothered setting up Skills, start by adding this line to the end of your task: “Make the best decision to improve UX, DX, and AX—without breaking existing functionality.” Ask it to weigh the user experience, developer experience, and how easily the next agent can pick up the work.