ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improve developer experience with shared tooling, cleaner docs. (#170)

Browse Source 
* docs: add headers and improve formatting for BMAD orchestrator agent documentation

## CHANGES

- Add configuration header to cfg file
- Improve numbered list formatting consistency
- Add proper heading punctuation throughout
- Enhance readability with cleaner structure
- Standardize markdown formatting conventions

* gitignore update

* Plaform Engineer role for a robust infrastructure (#135)

* Add Platform Engineer role to support a robust and validated infrastructure

* Platform Engineer and Architect boundaries, confidence levels, domain expertise

* remove duplicate task, leftover artifact

* Consistency, workflow, feedback loops between architect and PE

* PE customization generalized, updated Architect, consistency check

* style: add VSCode integration and standardize document formatting

CHANGES
- Introduce VSCode recommended extensions and project-specific settings.
- Update `.gitignore` to track the `.vscode` directory.
- Apply consistent markdown formatting to all checklist documents.
- Standardize spacing, list styles, and headers in personas.
- Refine formatting and sectioning in task definition files.
- Ensure newline termination for all modified text files.
- Correct code block specifiers and minor textual content.

* docs: remove exclamation from header

* fix: spacing at end of line

---------

Co-authored-by: Brian Madison <brianmadison@Brians-MacBook-Pro.local>
Co-authored-by: Sebastian Ickler <icklers@users.noreply.github.com>
This commit is contained in:
Kayvan Sylvan
2025-06-05 05:42:07 -07:00
committed by GitHub
parent cffbb59941
commit fa470c92fd
22 changed files with 217 additions and 108 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
bmad-agent/checklists/frontend-architecture-checklist.md
View File

@@ -1,6 +1,7 @@
# Frontend Architecture Document Review Checklist
## Purpose
This checklist is for the Design Architect to use after completing the "Frontend Architecture Mode" and populating the `front-end-architecture-tmpl.txt` (or `.md`) document. It ensures all sections are comprehensively covered and meet quality standards before finalization.
---
@@ -34,10 +35,12 @@ This checklist is for the Design Architect to use after completing the "Frontend
## IV. Component Breakdown & Implementation Details
### Component Naming & Organization
- [ ] Are conventions for naming components (e.g., PascalCase) described?
- [ ] Is the organization of components on the filesystem clearly explained (reiterating from directory structure if needed)?
### Template for Component Specification
- [ ] Is the "Template for Component Specification" itself complete and well-defined?
- [ ] Does it include fields for: Purpose, Source File(s), Visual Reference?
- [ ] Does it include a table structure for Props (Name, Type, Required, Default, Description)?
@@ -50,6 +53,7 @@ This checklist is for the Design Architect to use after completing the "Frontend
- [ ] Is there a clear statement that this template should be used for most feature-specific components?
### Foundational/Shared Components (if any specified upfront)
- [ ] If any foundational/shared UI components are specified, do they follow the "Template for Component Specification"?
- [ ] Is the rationale for specifying these components upfront clear?
@@ -146,4 +150,4 @@ This checklist is for the Design Architect to use after completing the "Frontend
- [ ] Have all placeholders (e.g., `{Project Name}`, `{e.g., ...}`) been filled in or removed where appropriate?
- [ ] Has the document been reviewed for clarity, consistency, and completeness by the Design Architect?
- [ ] Are all linked documents (Main Architecture, UI/UX Spec) finalized or stable enough for this document to rely on?
- [ ] Is the document ready to be shared with the development team?
- [ ] Is the document ready to be shared with the development team?