refactor(ux): consolidate BMAD skills, update design system, and clean up Prisma generated client

.github/skills/bmad-workflow-builder/references/quality-dimensions.md

@@ -16,13 +16,13 @@ The executing agent needs enough context to make judgment calls when situations
 
 - Simple utilities need minimal context — input/output is self-explanatory
 - Interactive/complex workflows need domain understanding, user perspective, and rationale for non-obvious choices
-- When in doubt, explain *why* — an agent that understands the mission improvises better than one following blind steps
+- When in doubt, explain _why_ — an agent that understands the mission improvises better than one following blind steps
 
 ## 3. Intelligence Placement
 
 Scripts handle plumbing (fetch, transform, validate). Prompts handle judgment (interpret, classify, decide).
 
-**Test:** If a script contains an `if` that decides what content *means*, intelligence has leaked.
+**Test:** If a script contains an `if` that decides what content _means_, intelligence has leaked.
 
 **Reverse test:** If a prompt validates structure, counts items, parses known formats, compares against schemas, or checks file existence — determinism has leaked into the LLM. That work belongs in a script.
 
@@ -30,9 +30,9 @@ Scripts handle plumbing (fetch, transform, validate). Prompts handle judgment (i
 
 SKILL.md stays focused. Detail goes where it belongs.
 
-- Stage instructions → `./references/`
-- Reference data, schemas, large tables → `./references/`
-- Templates, config files → `./assets/`
+- Stage instructions → `references/`
+- Reference data, schemas, large tables → `references/`
+- Templates, config files → `assets/`
 - Multi-branch SKILL.md under ~250 lines: fine as-is
 - Single-purpose up to ~500 lines (~5000 tokens): acceptable if focused
 
@@ -40,13 +40,13 @@ SKILL.md stays focused. Detail goes where it belongs.
 
 Two parts: `[5-8 word summary]. [Use when user says 'X' or 'Y'.]`
 
-Default to conservative triggering. See `./references/standard-fields.md` for full format.
+Default to conservative triggering. See `./standard-fields.md` for full format.
 
 ## 6. Path Construction
 
-Only use `{project-root}` for `_bmad` paths. Config variables used directly — they already contain `{project-root}`.
+Use `{project-root}` for any project-scope path. Use `./` only for same-folder references; cross-directory paths are bare and relative to skill root. Config variables used directly — they already contain `{project-root}`.
 
-See `./references/standard-fields.md` for correct/incorrect patterns.
+See `./standard-fields.md` for correct/incorrect patterns.
 
 ## 7. Token Efficiency