fix: update masonry grid sizing logic and notebook list padding

This commit is contained in:
Sepehr Ramezani
2026-02-14 14:20:32 +01:00
parent a0ffc9043b
commit 8f9031f076
580 changed files with 9789 additions and 42619 deletions

View File

@@ -141,7 +141,7 @@ Display: "**Proceeding to product vision discovery...**"
#### Menu Handling Logic:
- After setup report is presented, immediately load, read entire file, then execute {nextStepFile}
- After setup report is presented, without delay, read fully and follow: {nextStepFile}
#### EXECUTION RULES:
@@ -150,7 +150,7 @@ Display: "**Proceeding to product vision discovery...**"
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then load and read fully `{nextStepFile}` to execute and begin product vision discovery.
ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then read fully and follow: `{nextStepFile}` to begin product vision discovery.
---

View File

@@ -125,7 +125,7 @@ Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
#### Menu Handling Logic:
- IF C: Load, read entire file, then execute the appropriate next step file based on `lastStep`
- IF C: Read fully and follow the appropriate next step file based on `lastStep`
- IF Any other comments or queries: respond and redisplay menu
#### EXECUTION RULES:
@@ -136,7 +136,7 @@ Display: "Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the appropriate next step file to resume the workflow.
ONLY WHEN [C continue option] is selected and [current state confirmed], will you then read fully and follow the appropriate next step file to resume the workflow.
---

View File

@@ -156,9 +156,9 @@ Prepare the following structure for document append:
#### Menu Handling Logic:
- IF A: Execute {advancedElicitationTask} with current vision content to dive deeper and refine
- IF P: Execute {partyModeWorkflow} to bring different perspectives to positioning and differentiation
- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then only then load, read entire file, then execute {nextStepFile}
- IF A: Read fully and follow: {advancedElicitationTask} with current vision content to dive deeper and refine
- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to positioning and differentiation
- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2], then read fully and follow: {nextStepFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
#### EXECUTION RULES:
@@ -170,7 +170,7 @@ Prepare the following structure for document append:
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin target user discovery.
ONLY WHEN [C continue option] is selected and [vision content finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin target user discovery.
---

View File

@@ -159,9 +159,9 @@ Prepare the following structure for document append:
#### Menu Handling Logic:
- IF A: Execute {advancedElicitationTask} with current user content to dive deeper into personas and journeys
- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate user understanding
- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then only then load, read entire file, then execute {nextStepFile}
- IF A: Read fully and follow: {advancedElicitationTask} with current user content to dive deeper into personas and journeys
- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate user understanding
- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then read fully and follow: {nextStepFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
#### EXECUTION RULES:
@@ -173,7 +173,7 @@ Prepare the following structure for document append:
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin success metrics definition.
ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin success metrics definition.
---

View File

@@ -162,9 +162,9 @@ Prepare the following structure for document append:
#### Menu Handling Logic:
- IF A: Execute {advancedElicitationTask} with current metrics content to dive deeper into success metric insights
- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics
- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then only then load, read entire file, then execute {nextStepFile}
- IF A: Read fully and follow: {advancedElicitationTask} with current metrics content to dive deeper into success metric insights
- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics
- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then read fully and follow: {nextStepFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
#### EXECUTION RULES:
@@ -176,7 +176,7 @@ Prepare the following structure for document append:
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin MVP scope definition.
ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to begin MVP scope definition.
---

View File

@@ -176,9 +176,9 @@ Prepare the following structure for document append:
#### Menu Handling Logic:
- IF A: Execute {advancedElicitationTask} with current scope content to optimize scope definition
- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate MVP scope
- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then only then load, read entire file, then execute {nextStepFile}
- IF A: Read fully and follow: {advancedElicitationTask} with current scope content to optimize scope definition
- IF P: Read fully and follow: {partyModeWorkflow} to bring different perspectives to validate MVP scope
- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then read fully and follow: {nextStepFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
#### EXECUTION RULES:
@@ -190,7 +190,7 @@ Prepare the following structure for document append:
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and complete the product brief workflow.
ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then read fully and follow: `{nextStepFile}` to complete the product brief workflow.
---

View File

@@ -73,17 +73,7 @@ I've successfully collaborated with you to create a comprehensive Product Brief
This brief serves as the foundation for all subsequent product development activities and strategic decisions."
### 2. Workflow Status Update
**Status File Management:**
Update the main workflow status file:
- Check if `{output_folder} or {planning_artifacts}/bmm-workflow-status.yaml` exists
- If so, update workflow_status["product-brief"] = `{outputFile}`
- Add completion timestamp and metadata
- Save file, preserving all comments and structure
### 3. Document Quality Check
### 2. Document Quality Check
**Completeness Validation:**
Perform final validation of the product brief:
@@ -101,7 +91,7 @@ Perform final validation of the product brief:
- Are success criteria traceable to user needs and business goals?
- Does MVP scope align with the problem and solution?
### 4. Suggest Next Steps
### 3. Suggest Next Steps
**Recommended Next Workflow:**
Provide guidance on logical next workflows:
@@ -124,12 +114,11 @@ Provide guidance on logical next workflows:
- Use brief to validate concept before committing to detailed work
- Brief can guide early technical feasibility discussions
### 5. Present MENU OPTIONS
### 4. Congrats to the user
**Completion Confirmation:**
"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**
"**Your Product Brief for {{project_name}} is now complete and ready for the next phase!**"
The brief captures everything needed to guide subsequent product development:
Recap that the brief captures everything needed to guide subsequent product development:
- Clear vision and problem definition
- Deep understanding of target users
@@ -137,30 +126,9 @@ The brief captures everything needed to guide subsequent product development:
- Focused MVP scope with realistic boundaries
- Inspiring long-term vision
**Suggested Next Steps**
### 5. Suggest next steps
- PRD workflow for detailed requirements?
- UX design workflow for user experience planning?
**Product Brief Complete**"
#### Menu Handling Logic:
- Since this is a completion step, no continuation to other workflow steps
- User can ask questions or request review of the completed brief
- Provide guidance on next workflow options when requested
- End workflow session gracefully after completion confirmation
#### EXECUTION RULES:
- This is a final step with completion focus
- No additional workflow steps to load after this
- User can request review or clarification of completed brief
- Provide clear guidance on next workflow options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN [completion confirmation is provided and workflow status updated], will you then mark the workflow as complete and end the session gracefully. No additional steps are loaded after this final completion step.
Product Brief complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Validate PRD`.
---

View File

@@ -1,7 +1,6 @@
---
name: create-product-brief
description: Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
web_bundle: true
---
# Product Brief Workflow
@@ -31,7 +30,7 @@ This uses **step-file architecture** for disciplined execution:
3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
6. **LOAD NEXT**: When directed, read fully and follow the next step file
### Critical Rules (NO EXCEPTIONS)
@@ -55,4 +54,4 @@ Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
### 2. First Step EXECUTION
Load, read the full file and then execute `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.
Read fully and follow: `{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-01-init.md` to begin the workflow.