Design prompts worth keeping. Copy one, paste it into your coding agent, and get a considered result instead of a generic one.
5 prompts
Scaffolds and first steps, on versions that are current.
Scaffold a fresh SvelteKit site on current versions — Svelte 5 runes, Tailwind CSS 4, TypeScript — with a skeleton layout, a design token file, and the PageSugar MCP server connected.
Find what is wrong with a page by looking at it rendered.
Score one screen out of ten against real rendered pixels, using a second model as the adversarial reviewer, then fix what it finds and re-score until the surface stops improving.
Needs a second model to act as the reviewer — the Codex MCP server, or the codex exec CLI — plus Playwright for screenshots and a dev server to point it at.
Find where a page actually breaks between 320px and 1920px — overflow, collapsed hierarchy, orphaned headings, touch targets — and fix the layout rather than bolting on another breakpoint.
Make working code systematic, accessible and consistent.
Replace the scattered hex codes and one-off spacing values in an existing project with a small, named token system in Tailwind 4's @theme — a value-preserving refactor first, with any consolidation proposed separately.
Take a component that works with a mouse and make it work with a keyboard, a screen reader and reduced motion — real focus management and semantics, not a scattering of ARIA attributes.
