Community design feedback (2026-08-23) around the TechTalk discussion of AI-designed sites pointed at a concrete gap: sona.fast's themes and color palettes live inline per site rather than in a library, so each new surface gets a one-shot design pass and drifts toward stock Claude aesthetics.
What to do
- Extract the existing color palettes and themes into a shared library that all Sona sites consume.
- Move the components already duplicated across sites into the same library.
- Point future UI work (including agent-driven work) at the library instead of generating new styles per screen, so the visual identity stays consistent and deliberately designed rather than regenerated each time.
Why
- Reviewers can tell when each page is styled from scratch; a curated component set is the structural fix for the "reads as AI-designed" critique, not another restyle pass.
- The fleet ships from one codebase across six-plus forks; shared components mean a design improvement lands everywhere instead of per-page.
Notes
- The marketing page's current UI representation is acknowledged as not the end state; this issue is the foundation for that rework, not the rework itself.
- Suggested working approach from the feedback: iterate components one at a time (wireframe first) and build the library up, rather than one-shotting screens.
Community design feedback (2026-08-23) around the TechTalk discussion of AI-designed sites pointed at a concrete gap: sona.fast's themes and color palettes live inline per site rather than in a library, so each new surface gets a one-shot design pass and drifts toward stock Claude aesthetics.
What to do
Why
Notes