Workspace overview
Theme Assistant combines a page preview, design chat, inspection tools, responsive controls, accessibility checks, and draft review surfaces. It is meant for scoped visual work: explaining a change, previewing impact, and keeping CSS or presentation notes reviewable before publishing.
Safe visual changes
Start with low-risk pages and describe the intended outcome in plain language. Use the inspect and responsive views to confirm the target element, then review proposed CSS before approval. The Theme Assistant feature page explains the module, and the reversible CSS tutorial shows the practical review path.
Publishing discipline
Avoid broad selectors on checkout, account, cart, and navigation surfaces unless a developer reviews the impact. Record why the change was made and how it can be rolled back.
Owner and cadence
- Primary owner: designer or developer, with site-owner approval for production visual impact.
- Review cadence: before publishing, after theme updates, and after cache or WooCommerce template changes.
- Escalate when visual work affects revenue-critical pages, accessibility, mobile navigation, or theme behavior outside the intended scope.
Production checklist
- Use scoped prompts that name the page, component, desired outcome, and review constraints.
- Inspect generated CSS before publishing and avoid broad selectors on checkout, account, cart, and navigation surfaces.
- Capture the affected URL, target selector, intended visual outcome, reviewer, and rollback note for every meaningful visual change.
- Review mobile, desktop, keyboard focus, reduced motion, contrast, checkout, cart, account, and navigation behavior before publishing.
Acceptance checks
- The change can be explained as a narrow visual improvement, not a hidden theme rewrite.
- Rollback instructions are clear before the change is approved.
- The proposed CSS or presentation output can be traced to a specific page, component, and design goal.
- The reviewer can reject, revise, or roll back the change without guessing which selectors were affected.
Common mistakes
- Publishing broad CSS from a single preview without checking logged-out, mobile, checkout, account, and cache states.
- Using external design references as production assets instead of review context.
Related operations
- Follow the reversible CSS tutorial.
- Review Design from URL when using external references.
- Use Responsive and Accessibility Review before visual publishing.
- Use Client Presentation Workflow when an agency needs client approval.
- Use Publishing and Rollback for Theme Changes before approving production CSS.
- Use Multi-Page Consistency Checker before broad component updates.
- Use Design Tokens and Style System before token-level changes.