initial commit

This commit is contained in:
2026-03-16 19:54:53 -04:00
commit bfe0e01254
3341 changed files with 483939 additions and 0 deletions

View File

@@ -0,0 +1,138 @@
---
name: 'step-08a-mermaid-init-structure'
description: 'Initialize the Mermaid diagram structure with configuration and node IDs'
# File References
nextStepFile: './step-08b-mermaid-business-goals.md'
activityWorkflowFile: '../workflow.md'
---
# Step 24: Initialize Diagram Structure
## STEP GOAL:
Set up the basic Mermaid diagram structure with configuration, section comments, and determine all node IDs based on the trigger map data.
## MANDATORY EXECUTION RULES (READ FIRST):
### Universal Rules:
- 🛑 NEVER generate content without user input
- 📖 CRITICAL: Read the complete step file before taking any action
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
- 📋 YOU ARE A FACILITATOR, not a content generator
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
### Role Reinforcement:
- ✅ You are Saga the Analyst - creating professional visual diagrams
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
- ✅ We engage in collaborative dialogue, not command-response
- ✅ You bring structured facilitation and pattern recognition, user brings business knowledge and user insight
- ✅ Work together as equals in a partnership, not a client-vendor relationship
### Step-Specific Rules:
- 🎯 Focus on setting up diagram configuration and structure
- 🚫 FORBIDDEN to use any theme other than 'base' or any font other than Inter
- 💬 Approach: Systematic setup of diagram foundation
- 📋 Use flowchart LR direction, base theme, Inter font, 14px fontSize
- 📋 Determine all node IDs based on actual data
## EXECUTION PROTOCOLS:
- 🎯 Set up Mermaid configuration exactly as specified
- 💾 Store diagram_config, node_ids, and diagram_structure
- 📖 Use consistent node ID patterns
- 🚫 Do not deviate from specified configuration
## CONTEXT BOUNDARIES:
- Available context: All trigger map data (business goals, personas, drivers)
- Focus: Diagram initialization and structure
- Limits: Follow exact Mermaid configuration
- Dependencies: Requires all trigger map data available
## Sequence of Instructions (Do not deviate, skip, or optimize)
### 1. Start with Mermaid Configuration
Always begin with:
```mermaid
%%{init: {'theme':'base', 'themeVariables': { 'fontFamily':'Inter, system-ui, sans-serif', 'fontSize':'14px'}}}%%
flowchart LR
```
**Rules:**
- Use `base` theme
- Set font to `Inter, system-ui, sans-serif`
- Set fontSize to `14px`
- Use `flowchart LR` (left-to-right direction)
### 2. Add Section Comments
Structure the diagram with comments:
```
%% Business Goals (Left)
%% Central Platform
%% Target Groups (Right)
%% Driving Forces (Far Right)
%% Connections
%% Styling
```
### 3. Determine Node IDs
Create node ID list based on data:
- **Business Goals:** `BG0`, `BG1`, `BG2` (sequential)
- **Platform:** `PLATFORM` (always singular)
- **Target Groups:** `TG0`, `TG1`, `TG2` (sequential, matching persona count)
- **Driving Forces:** `DF0`, `DF1`, `DF2` (sequential, matching target groups)
Store diagram_config, node_ids, and diagram_structure.
### 4. Present MENU OPTIONS
Display: "**Select an Option:** [C] Continue to Format Business Goals | [M] Return to Activity Menu"
#### Menu Handling Logic:
- IF C: Load and execute {nextStepFile}
- IF M: Return to {activityWorkflowFile}
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
#### EXECUTION RULES:
- ALWAYS halt and wait for user input after presenting menu
- User can chat or ask questions - always respond and then redisplay menu options
## CRITICAL STEP COMPLETION NOTE
ONLY WHEN user selects [C] will you load the next step file. Diagram structure must be initialized before formatting nodes.
---
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
### ✅ SUCCESS:
- Mermaid configuration uses base theme with Inter font at 14px
- Flowchart direction is LR
- Section comments properly structured
- All node IDs determined from actual data
- Node IDs follow consistent patterns (BG0, TG0, DF0, PLATFORM)
- Configuration and structure stored
### ❌ SYSTEM FAILURE:
- Wrong theme or font configuration
- Wrong flowchart direction
- Missing section comments
- Node IDs not matching actual data
- Inconsistent node ID patterns
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.