fix: extract meta-instructions from display blocks

Split display blocks containing AI meta-instructions like
[Show the complete markdown content from step X] into separate
display blocks with the instruction outside the tags.
This commit is contained in:
Alex Verkhovsky 2026-02-01 23:14:36 -07:00
parent fb26467069
commit 95bc86c939
24 changed files with 52 additions and 0 deletions

View File

@ -153,8 +153,11 @@ Prepare the following structure for document append:
I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
</display>

View File

@ -156,8 +156,11 @@ Prepare the following structure for document append:
I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 5]
<display>
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
</display>

View File

@ -159,8 +159,11 @@ Prepare the following structure for document append:
I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
</display>

View File

@ -173,8 +173,11 @@ Prepare the following structure for document append:
I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
</display>

View File

@ -165,9 +165,11 @@ Present the project-type content for review, then display menu:
Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from section 5]
<display>
**What would you like to do?**
</display>

View File

@ -152,9 +152,11 @@ Show the generated project understanding content and present choices:
I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 5]
<display>
**What would you like to do?**
[C] Continue - Save this to the document and move to core experience definition
</display>

View File

@ -160,9 +160,11 @@ Show the generated core experience content and present choices:
I've defined the core user experience for {{project_name}} based on our conversation. This establishes the foundation for all our UX design decisions.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine the core experience definition
[P] Party Mode - Bring different perspectives on the user experience

View File

@ -163,9 +163,11 @@ Show the generated emotional response content and present choices:
I've defined the desired emotional responses for {{project_name}}. These emotional goals will guide our design decisions to create the right user experience.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine the emotional response definition
[P] Party Mode - Bring different perspectives on user emotional needs

View File

@ -178,9 +178,11 @@ Show the generated inspiration analysis content and present choices:
I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's deepen our UX pattern analysis
[P] Party Mode - Bring different perspectives on inspiration sources

View File

@ -196,9 +196,11 @@ Show the generated design system content and present choices:
I've documented our design system choice for {{project_name}}. This foundation will ensure consistency and speed up development.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine our design system decision
[P] Party Mode - Bring technical perspectives on design systems

View File

@ -198,9 +198,11 @@ Show the generated defining experience content and present choices:
I've defined the core experience for {{project_name}} - the interaction that will make users love this product.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine the core experience definition
[P] Party Mode - Bring different perspectives on the defining interaction

View File

@ -168,9 +168,11 @@ Show the generated visual foundation content and present choices:
I've established the visual design foundation for {{project_name}}. This provides the building blocks for consistent, beautiful design.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine our visual foundation
[P] Party Mode - Bring design perspectives on visual choices

View File

@ -168,9 +168,11 @@ Show the generated design direction content and present choices:
I've documented our design direction decision for {{project_name}}. This visual approach will guide all our detailed design work.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine our design direction
[P] Party Mode - Bring different perspectives on visual choices

View File

@ -186,9 +186,11 @@ Show the generated user journey content and present choices:
I've designed detailed user journey flows for {{project_name}}. These flows will guide the detailed design of each user interaction.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine our user journey designs
[P] Party Mode - Bring different perspectives on user flows

View File

@ -190,9 +190,11 @@ Show the generated component strategy content and present choices:
I've defined the component strategy for {{project_name}}. This balances using proven design system components with custom components for your unique needs.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine our component strategy
[P] Party Mode - Bring technical perspectives on component design

View File

@ -177,9 +177,11 @@ Show the generated UX patterns content and present choices:
I've established UX consistency patterns for {{project_name}}. These patterns ensure users have a consistent, predictable experience across all interactions.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine our UX patterns
[P] Party Mode - Bring different perspectives on consistency patterns

View File

@ -208,9 +208,11 @@ Show the generated responsive and accessibility content and present choices:
I've defined the responsive design and accessibility strategy for {{project_name}}. This ensures your product works beautifully across all devices and is accessible to all users.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's refine our responsive/accessibility strategy
[P] Party Mode - Bring different perspectives on inclusive design

View File

@ -161,9 +161,11 @@ Show the generated content and present choices:
I've drafted the Project Context Analysis based on your requirements. This sets the foundation for our architectural decisions.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 4]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Let's dive deeper into architectural implications
[P] Party Mode - Bring different perspectives to analyze requirements

View File

@ -274,9 +274,11 @@ Show the generated content and present choices:
I've analyzed starter template options for {{project_type}} projects.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 8]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Explore custom approaches or unconventional starters
[P] Party Mode - Evaluate trade-offs from different perspectives

View File

@ -265,9 +265,11 @@ Show the generated decisions content and present choices:
I've documented all the core architectural decisions we've made together.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 5]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Explore innovative approaches to any specific decisions
[P] Party Mode - Review decisions from multiple perspectives

View File

@ -300,9 +300,11 @@ Show the generated patterns content and present choices:
I've documented implementation patterns that will prevent conflicts between AI agents working on this project.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 4]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Explore additional consistency patterns
[P] Party Mode - Review patterns from different implementation perspectives

View File

@ -322,9 +322,11 @@ Show the generated project structure content and present choices:
I've created a complete project structure based on all our architectural decisions.
**Here's what I'll add to the document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Explore innovative project organization approaches
[P] Party Mode - Review structure from different development perspectives

View File

@ -300,9 +300,11 @@ I've completed a comprehensive validation of your architecture.
- ✅ Readiness: AI agents can implement consistently
**Here's what I'll add to complete the architecture document:**
</display>
[Show the complete markdown content from step 6]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Address any complex architectural concerns
[P] Party Mode - Review validation from different implementation perspectives

View File

@ -274,9 +274,11 @@ After each category, show the generated rules and present choices:
I've drafted the {{category_name}} rules for your project context.
**Here's what I'll add:**
</display>
[Show the complete markdown content for this category]
<display>
**What would you like to do?**
[A] Advanced Elicitation - Explore nuanced rules for this category
[P] Party Mode - Review from different implementation perspectives