← ~/articles

Prompt-driven theme development: what actually works

cover image 16:9Prompt-driven theme development: what actually works

Three client theme builds this quarter started as prompts, not PSDs. The drafts were 70% of the way there in an hour. The interesting part is which 30% never survived.

What survived code review

Structure, tokens, and the boring parts: template hierarchy, enqueue logic, accessibility scaffolding. The model is genuinely good at the parts developers rush.

What got rewritten

Anything with taste: spacing rhythm, type scale, hover behavior. And anything touching the client’s actual data model — the model confidently invents custom fields that don’t exist.

The workflow that stuck

Prompt for the skeleton, hand-finish the design layer, and never let generated code merge without reading every line. Same rule as junior PRs, faster turnaround.