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

This commit is contained in:
Sepehr Ramezani
2026-04-19 19:21:27 +02:00
parent 5296c4da2c
commit 25529a24b8
2476 changed files with 127934 additions and 101962 deletions

View File

@@ -17,12 +17,14 @@ Workflows read config from `{project-root}/_bmad/config.yaml` and `config.user.y
### Config Loading Pattern
**Module-based skills** — load with fallback and setup skill awareness:
```
Load config from {project-root}/_bmad/config.yaml ({module-code} section) and config.user.yaml.
If missing: inform user that {module-setup-skill} is available, continue with sensible defaults.
```
**Standalone skills** — load best-effort:
```
Load config from {project-root}/_bmad/config.yaml and config.user.yaml if available.
If missing: continue with defaults — no mention of setup skill.
@@ -33,6 +35,7 @@ If missing: continue with defaults — no mention of setup skill.
Load core config (user preferences, language, output locations) with sensible defaults. If the workflow creates documents, include document output language.
**Example config line for a document-producing workflow:**
```
vars: user_name:BMad,communication_language:English,document_output_language:English,output_folder:{project-root}/_bmad-output,bmad_builder_output_folder:{project-root}/bmad-builder-creations/
```
@@ -57,12 +60,12 @@ Each stage after the first reads the output document to recover context. If comp
```markdown
---
title: "Analysis: Research Topic"
status: "analysis"
title: 'Analysis: Research Topic'
status: 'analysis'
inputs:
- "{project_root}/docs/brief.md"
created: "2025-03-02T10:00:00Z"
updated: "2025-03-02T11:30:00Z"
- '{project_root}/docs/brief.md'
created: '2025-03-02T10:00:00Z'
updated: '2025-03-02T11:30:00Z'
---
```
@@ -75,6 +78,7 @@ updated: "2025-03-02T11:30:00Z"
## Sequential Progressive Disclosure
Use numbered prompt files at the skill root when:
- Multi-phase workflow with ordered stages
- Input of one phase affects the next
- Workflow is long-running and stages shouldn't be visible upfront
@@ -101,7 +105,7 @@ Each stage prompt specifies prerequisites, progression conditions, and next dest
## Module Metadata Reference
BMad module workflows require extended frontmatter metadata. See `./references/metadata-reference.md` for the metadata template and field explanations.
BMad module workflows require extended frontmatter metadata. See `./metadata-reference.md` for the metadata template and field explanations.
---
@@ -114,6 +118,6 @@ Before finalizing a BMad module workflow, verify:
- [ ] Portable paths — artifacts use `{project_root}`?
- [ ] Compaction survival — each stage writes to output document?
- [ ] Document-as-cache — YAML front matter with status and inputs?
- [ ] Progressive disclosure — stages in `./references/` with progression conditions?
- [ ] Progressive disclosure — stages in `references/` with progression conditions?
- [ ] Final polish — subagent polish step at the end?
- [ ] Recovery — can resume by reading output doc front matter?