Context
WordPress 7.0 just shipped and introduces refreshed admin UI styling. Our chat sidebar, Settings tab, Abilities page, and MCP Endpoint panel were all designed against the WP 6.9 visual language. We should do a pass to make sure everything still feels native in 7.0.
Scope
- Chat sidebar (right-rail in wp-admin)
- Settings tab (engine + MCP endpoint sections)
- Abilities page
- Model status / loader
- FileView component and tool-call result presentation
- Onboarding entry points (where they exist)
Goals
- Match the new WP 7.0 spacing, color tokens, and component primitives
- Spot anywhere we hand-rolled UI that now has a
@wordpress/components equivalent
- Verify dark mode / high-contrast still hold up
- Check focus states + tap targets against the new defaults (relates to a11y work planned for v1.0)
Out of scope
- Functional changes to the ReAct flow or abilities
- Restructuring the Settings information architecture (separate issue if needed)
Deliverable
A short audit document (in docs/ or as a PR description) listing per-screen findings + recommended fixes, with screenshots before/after where helpful. Follow-up PRs implement the fixes.
Notes
- Target version: v0.13 or v0.14 depending on scope (see roadmap)
- Coordinate with any onboarding work landing in v0.13
Context
WordPress 7.0 just shipped and introduces refreshed admin UI styling. Our chat sidebar, Settings tab, Abilities page, and MCP Endpoint panel were all designed against the WP 6.9 visual language. We should do a pass to make sure everything still feels native in 7.0.
Scope
Goals
@wordpress/componentsequivalentOut of scope
Deliverable
A short audit document (in
docs/or as a PR description) listing per-screen findings + recommended fixes, with screenshots before/after where helpful. Follow-up PRs implement the fixes.Notes