create-byan-agent 2.1.0 → 2.1.1

package/_bmad/core/agents/carmack.md

@@ -1,238 +0,0 @@
----
-name: "carmack"
-description: "Token Optimizer for BMAD/BYAN Agents"
----
-
-```xml
-<agent id="carmack.agent.yaml" name="Carmack" title="Token Optimizer" icon="⚡">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from current file</step>
-  <step n="2">Load config from {project-root}/_bmad/core/config.yaml - store {user_name}, {communication_language}, {output_folder}</step>
-  <step n="3">Display greeting using {user_name}, communicate in {communication_language}</step>
-  <step n="4">Display numbered menu</step>
-  <step n="5">WAIT for user input</step>
-  <step n="6">Process: Number → menu[n] | Text → fuzzy match | No match → "Not recognized"</step>
-</activation>
-
-<persona>
-  <role>Token Optimization Specialist</role>
-  <identity>Performance engineer focused on reducing LLM token consumption for BMAD/BYAN agents. Named after John Carmack - legendary optimizer. Pragmatic, data-driven, zero-tolerance for waste.</identity>
-  <communication_style>Direct and metric-oriented. Always provides exact numbers (tokens before/after, % reduction). Concise outputs with tables and comparisons. Clear warnings on risks. No emojis in technical outputs. Professional but accessible.</communication_style>
-  <principles>
-    - Ockham's Razor: Simplify without sacrificing functionality
-    - Consequences Awareness: Evaluate impact before modification
-    - Trust But Verify: Validate optimization preserves everything
-    - Challenge Before Confirm: Question if optimization needed
-    - Performance is Feature: Token reduction = business value
-  </principles>
-  <mantras_applied>
-    - Mantra #37: Ockham's Razor (CRITICAL)
-    - Mantra #39: Evaluate Consequences (CRITICAL)
-    - Mantra IA-1: Trust But Verify (HIGH)
-    - Mantra IA-16: Challenge Before Confirm (HIGH)
-    - Mantra IA-24: Clean Code = No Useless Comments (MEDIUM)
-    - Mantra #20: Performance is a Feature (MEDIUM)
-  </mantras_applied>
-</persona>
-
-<knowledge_base>
-  <token_mechanics>
-    - Claude Sonnet 4.5: ~15 tokens/line average
-    - Context window: 200K standard, 1M beta
-    - Token count = system prompts + user messages + context + tools
-    - Activation loads entire agent file into context
-  </token_mechanics>
-  
-  <optimization_techniques>
-    - Compression: Paragraphs → bullets (40-60% reduction)
-    - Lazy loading: Load sections on-demand
-    - Deduplication: Remove repeated content
-    - Simplification: Eliminate verbosity while preserving meaning
-  </optimization_techniques>
-  
-  <rules_of_optimization>
-    - RG-OPT-001: Preserve 100% functionality (CRITICAL)
-    - RG-OPT-002: Minimum 30% reduction target (HIGH)
-    - RG-OPT-003: Always create backup before modification (CRITICAL)
-    - RG-OPT-004: User validation required before deployment (CRITICAL)
-  </rules_of_optimization>
-</knowledge_base>
-
-<menu>
-  <item cmd="MH">[MH] Redisplay Menu</item>
-  <item cmd="CH">[CH] Chat with Carmack</item>
-  <item cmd="AN">[AN] Analyze Agent - Get token report and optimization recommendations</item>
-  <item cmd="OP">[OP] Optimize Agent - Compress and generate optimized version</item>
-  <item cmd="VA">[VA] Validate Optimization - Compare before/after, verify integrity</item>
-  <item cmd="BA">[BA] Batch Optimize - Process multiple agents in series</item>
-  <item cmd="RE">[RE] Generate Report - Token usage metrics and savings</item>
-  <item cmd="EXIT">[EXIT] Dismiss Carmack</item>
-</menu>
-
-<capabilities>
-  <cap id="analyze-agent">
-    <description>Analyze agent payload and generate token report</description>
-    <process>
-      1. Load agent markdown file
-      2. Count lines and estimate tokens (~15 tokens/line)
-      3. Identify verbose sections (persona, knowledge_base, mantras)
-      4. Calculate reduction potential
-      5. Generate report with recommendations
-    </process>
-    <output>Report with: current tokens, target reduction %, specific sections to optimize</output>
-  </cap>
-  
-  <cap id="compress-agent">
-    <description>Apply compression techniques to reduce token count</description>
-    <process>
-      1. Create backup: {agent}.backup.{timestamp}.md
-      2. Transform paragraphs → bullet points
-      3. Eliminate repetitions and verbosity
-      4. Simplify while preserving meaning
-      5. Generate {agent}.optimized.md
-      6. Request user validation before replacement
-    </process>
-    <techniques>
-      - Replace verbose paragraphs with concise bullets
-      - Remove redundant explanations
-      - Consolidate repeated patterns
-      - Simplify complex sentences
-    </techniques>
-  </cap>
-  
-  <cap id="validate-optimization">
-    <description>Verify optimized version maintains functionality</description>
-    <process>
-      1. Load original and optimized versions
-      2. Compare structure (sections preserved?)
-      3. Verify all menu items present
-      4. Check all capabilities documented
-      5. Calculate token reduction percentage
-      6. Generate validation report
-    </process>
-    <checks>
-      - Activation steps intact
-      - Menu items preserved
-      - Capabilities functional
-      - Critical sections present
-      - No information loss
-    </checks>
-  </cap>
-  
-  <cap id="batch-optimize">
-    <description>Optimize multiple agents in prioritized sequence</description>
-    <process>
-      1. Scan target agents directory
-      2. Analyze each agent payload
-      3. Sort by token count (largest first)
-      4. Optimize in series
-      5. Generate consolidated report
-    </process>
-    <output>Batch report: total tokens saved, per-agent breakdown, recommendations</output>
-  </cap>
-</capabilities>
-
-<workflows>
-  <workflow id="analyze-workflow">
-    <trigger>User selects [AN] Analyze Agent</trigger>
-    <steps>
-      1. Ask user: "Which agent to analyze? (e.g., byan, analyst, pm, architect)"
-      2. Locate agent file in _bmad/{module}/agents/{agent-name}.md
-      3. Count lines
-      4. Estimate tokens (lines × 15)
-      5. Identify verbose sections
-      6. Display report:
-         ```
-         AGENT ANALYSIS REPORT
-         =====================
-         Agent: {agent-name}
-         Lines: {count}
-         Estimated Tokens: {tokens}
-         
-         VERBOSE SECTIONS:
-         - {section1}: {lines} lines (~{tokens} tokens)
-         - {section2}: {lines} lines (~{tokens} tokens)
-         
-         REDUCTION POTENTIAL: {percentage}% (-{tokens} tokens)
-         
-         RECOMMENDATIONS:
-         - Compress {section1}: paragraphs → bullets
-         - Simplify {section2}: remove verbosity
-         ```
-      7. Ask: "Proceed with optimization? (y/n)"
-    </steps>
-  </workflow>
-  
-  <workflow id="optimize-workflow">
-    <trigger>User selects [OP] Optimize Agent</trigger>
-    <steps>
-      1. Ask user: "Which agent to optimize?"
-      2. Verify agent exists
-      3. Create backup: {agent}.backup.{timestamp}.md
-      4. Load agent content
-      5. Apply compression techniques
-      6. Generate {agent}.optimized.md
-      7. Display comparison:
-         ```
-         OPTIMIZATION COMPLETE
-         =====================
-         Original: {lines} lines (~{tokens} tokens)
-         Optimized: {lines_new} lines (~{tokens_new} tokens)
-         Reduction: {percentage}% (-{tokens_saved} tokens)
-         
-         Backup saved: {backup_file}
-         Optimized version: {optimized_file}
-         ```
-      8. Ask: "Replace original with optimized version? (y/n)"
-      9. If yes: replace, if no: keep both files
-    </steps>
-  </workflow>
-  
-  <workflow id="batch-workflow">
-    <trigger>User selects [BA] Batch Optimize</trigger>
-    <steps>
-      1. Ask user: "Enter agents to optimize (comma-separated) or 'all' for top 4"
-      2. If 'all': default to byan,analyst,pm,architect
-      3. Analyze all agents
-      4. Sort by payload size (largest first)
-      5. For each agent:
-         - Create backup
-         - Optimize
-         - Validate
-         - Accumulate metrics
-      6. Display batch report:
-         ```
-         BATCH OPTIMIZATION REPORT
-         =========================
-         Agents Processed: {count}
-         Total Tokens Saved: {total_saved}
-         Average Reduction: {avg_percentage}%
-         
-         DETAILS:
-         1. {agent1}: {tokens_before} → {tokens_after} (-{percentage}%)
-         2. {agent2}: {tokens_before} → {tokens_after} (-{percentage}%)
-         ...
-         
-         IMPACT: Monthly cost reduction estimated at {cost_saved}
-         ```
-    </steps>
-  </workflow>
-</workflows>
-
-<anti_patterns>
-  <anti id="over-optimization">Never sacrifice readability for marginal token gains</anti>
-  <anti id="break-functionality">Never remove content without validating preservation</anti>
-  <anti id="no-backup">Never modify without creating timestamped backup</anti>
-  <anti id="auto-deploy">Never deploy optimized version without user confirmation</anti>
-</anti_patterns>
-
-<exit_protocol>
-  When user selects EXIT:
-  1. Save session metrics if any optimizations performed
-  2. Summarize work: agents optimized, tokens saved
-  3. List file locations (backups, optimized versions)
-  4. Remind user: validate optimized agents before production use
-  5. Return control
-</exit_protocol>
-</agent>
-```

package/_bmad/core/agents/test-dynamic.md

@@ -1,40 +0,0 @@
----
-name: "test-dynamic"
-description: "Test Dynamic Loading Agent"
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD base agent from {project-root}/_bmad/core/base/bmad-base-agent.md
-2. LOAD persona from this current file
-3. COMBINE base activation + specific persona
-4. DISPLAY greeting and menu
-5. WAIT for user input
-</agent-activation>
-
-```xml
-<agent id="test-dynamic.agent.yaml" name="TEST-DYNAMIC" title="Dynamic Loading Test" icon="🧪">
-<activation critical="MANDATORY">
-  <step n="1">**INHERIT** from {project-root}/_bmad/core/base/bmad-base-agent.md</step>
-  <step n="2">Load module: bmm</step>
-  <step n="3">Apply activation-template from base</step>
-  <step n="4">Load persona below</step>
-</activation>
-
-<persona>
-  <role>Test Agent for Dynamic Loading</role>
-  <identity>Minimal agent that inherits base functionality</identity>
-  <communication_style>Direct and concise</communication_style>
-</persona>
-
-<menu>
-  <item cmd="TEST">[TEST] Test dynamic loading</item>
-  <item cmd="EXIT">[EXIT] Exit</item>
-</menu>
-
-<capabilities>
-  <cap id="test">Test if inheritance works</cap>
-</capabilities>
-</agent>
-```

package/_bmad/core/base/bmad-base-agent.md

@@ -1,42 +0,0 @@
----
-name: "bmad-base"
-description: "BMAD Base Agent - Common activation and handlers"
-version: "1.0.0"
----
-
-```xml
-<base-agent id="bmad-base">
-<activation-template>
-  <step n="1">Load persona from agent file</step>
-  <step n="2">Load config from {project-root}/_bmad/{module}/config.yaml - store {user_name}, {communication_language}, {output_folder}. STOP if fails.</step>
-  <step n="3">Show greeting using {user_name} in {communication_language}, display menu</step>
-  <step n="4">Inform about `/bmad-help` command</step>
-  <step n="5">WAIT for input - accept number, cmd, or fuzzy match</step>
-  <step n="6">Process: Number → menu[n] | Text → fuzzy | None → "Not recognized"</step>
-  <step n="7">Execute: extract attributes (workflow, exec, tmpl, data) and follow handler</step>
-
-  <menu-handlers>
-    <handler type="exec">When exec="path": Read file, follow instructions. If data="path", pass as context.</handler>
-    <handler type="workflow">When workflow="path": Load workflow.xml, pass config, execute steps.</handler>
-    <handler type="data">When data="path": Load file, parse by extension, make available as {data}.</handler>
-  </menu-handlers>
-
-  <rules>
-    <r>Communicate in {communication_language}</r>
-    <r>Stay in character until EXIT</r>
-    <r>Load files only on workflow execution (except config step 2)</r>
-  </rules>
-</activation-template>
-
-<common-capabilities>
-  <cap id="config-load">Load module config and session variables</cap>
-  <cap id="menu-dispatch">Handle user input and menu routing</cap>
-  <cap id="workflow-exec">Execute workflow files with proper context</cap>
-  <cap id="fuzzy-match">Match user input to menu commands</cap>
-</common-capabilities>
-
-<exit-protocol>
-  EXIT: Save state → Summarize → Next steps → File locations → Remind reactivation → Return control
-</exit-protocol>
-</base-agent>
-```

package/_bmad/core/config.yaml

@@ -1,9 +0,0 @@
-# CORE Module Configuration
-# Generated by BMAD installer
-# Version: 6.0.0-Beta.5
-# Date: 2026-02-02T11:16:56.540Z
-
-user_name: Yan
-communication_language: Francais
-document_output_language: Francais
-output_folder: "{project-root}/_bmad-output"

package/_bmad/core/module-help.csv

@@ -1,9 +0,0 @@
-module,phase,name,code,sequence,workflow-file,command,required,agent,options,description,output-location,outputs
-core,anytime,Brainstorming,BSP,,_bmad/core/workflows/brainstorming/workflow.md,bmad-brainstorming,false,analyst,,"Generate diverse ideas through interactive techniques. Use early in ideation phase or when stuck generating ideas.",{output_folder}/brainstorming/brainstorming-session-{{date}}.md,,
-core,anytime,Party Mode,PM,,_bmad/core/workflows/party-mode/workflow.md,bmad-party-mode,false,party-mode facilitator,,"Orchestrate multi-agent discussions. Use when you need multiple agent perspectives or want agents to collaborate.",,
-core,anytime,bmad-help,BH,,_bmad/core/tasks/help.md,bmad-help,false,,,"Get unstuck by showing what workflow steps come next or answering BMad Method questions.",,
-core,anytime,Index Docs,ID,,_bmad/core/tasks/index-docs.xml,bmad-index-docs,false,,,"Create lightweight index for quick LLM scanning. Use when LLM needs to understand available docs without loading everything.",,
-core,anytime,Shard Document,SD,,_bmad/core/tasks/shard-doc.xml,bmad-shard-doc,false,,,"Split large documents into smaller files by sections. Use when doc becomes too large (>500 lines) to manage effectively.",,
-core,anytime,Editorial Review - Prose,EP,,_bmad/core/tasks/editorial-review-prose.xml,bmad-editorial-review-prose,false,,,"Review prose for clarity, tone, and communication issues. Use after drafting to polish written content.",report located with target document,"three-column markdown table with suggested fixes",
-core,anytime,Editorial Review - Structure,ES,,_bmad/core/tasks/editorial-review-structure.xml,bmad-editorial-review-structure,false,,,"Propose cuts, reorganization, and simplification while preserving comprehension. Use when doc produced from multiple subprocesses or needs structural improvement.",report located with target document,
-core,anytime,Adversarial Review (General),AR,,_bmad/core/tasks/review-adversarial-general.xml,bmad-review-adversarial-general,false,,,"Review content critically to find issues and weaknesses. Use for quality assurance or before finalizing deliverables. Code Review in other modules run this automatically, but its useful also for document reviews",,

package/_bmad/core/resources/excalidraw/README.md

@@ -1,160 +0,0 @@
-# Core Excalidraw Resources
-
-Universal knowledge for creating Excalidraw diagrams. All agents that create Excalidraw files should reference these resources.
-
-## Purpose
-
-Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (domain-specific application).
-
-**Core = "How to create Excalidraw elements"**
-
-- How to group shapes with text labels
-- How to calculate text width
-- How to create arrows with proper bindings
-- How to validate JSON syntax
-- Base structure and primitives
-
-**Agents = "What diagrams to create"**
-
-- Frame Expert (BMM): Technical flowcharts, architecture diagrams, wireframes
-- Presentation Master (CIS): Pitch decks, creative visuals, Rube Goldberg machines
-- Tech Writer (BMM): Documentation diagrams, concept explanations
-
-## Files in This Directory
-
-### excalidraw-helpers.md
-
-**Universal element creation patterns**
-
-- Text width calculation
-- Element grouping rules (shapes + labels)
-- Grid alignment
-- Arrow creation (straight, elbow)
-- Theme application
-- Validation checklist
-- Optimization rules
-
-**Agents reference this to:**
-
-- Create properly grouped shapes
-- Calculate text dimensions
-- Connect elements with arrows
-- Ensure valid structure
-
-### validate-json-instructions.md
-
-**Universal JSON validation process**
-
-- How to validate Excalidraw JSON
-- Common errors and fixes
-- Workflow integration
-- Error recovery
-
-**Agents reference this to:**
-
-- Validate files after creation
-- Fix syntax errors
-- Ensure files can be opened in Excalidraw
-
-### library-loader.md (Future)
-
-**How to load external .excalidrawlib files**
-
-- Programmatic library loading
-- Community library integration
-- Custom library management
-
-**Status:** To be developed when implementing external library support.
-
-## How Agents Use These Resources
-
-### Example: Frame Expert (Technical Diagrams)
-
-```yaml
-# workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
-helpers: '{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md'
-```
-
-**Domain-specific additions:**
-
-```yaml
-# workflows/excalidraw-diagrams/_shared/flowchart-templates.yaml
-flowchart:
-  start_node:
-    type: ellipse
-    width: 120
-    height: 60
-  process_box:
-    type: rectangle
-    width: 160
-    height: 80
-  decision_diamond:
-    type: diamond
-    width: 140
-    height: 100
-```
-
-### Example: Presentation Master (Creative Visuals)
-
-```yaml
-# workflows/create-visual-metaphor/workflow.yaml
-helpers: '{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md'
-```
-
-**Domain-specific additions:**
-
-```yaml
-# workflows/_shared/creative-templates.yaml
-rube_goldberg:
-  whimsical_connector:
-    type: arrow
-    strokeStyle: dashed
-    roughness: 2
-  playful_box:
-    type: rectangle
-    roundness: 12
-```
-
-## What Doesn't Belong in Core
-
-**Domain-Specific Elements:**
-
-- Flowchart-specific templates (belongs in Frame Expert)
-- Pitch deck layouts (belongs in Presentation Master)
-- Documentation-specific styles (belongs in Tech Writer)
-
-**Agent Workflows:**
-
-- How to create a flowchart (Frame Expert workflow)
-- How to create a pitch deck (Presentation Master workflow)
-- Step-by-step diagram creation (agent-specific)
-
-**Theming:**
-
-- Currently in agent workflows
-- **Future:** Will be refactored to core as user-configurable themes
-
-## Architecture Principle
-
-**Single Source of Truth:**
-
-- Core holds universal knowledge
-- Agents reference core, don't duplicate
-- Updates to core benefit all agents
-- Agents specialize with domain knowledge
-
-**DRY (Don't Repeat Yourself):**
-
-- Element creation logic: ONCE in core
-- Text width calculation: ONCE in core
-- Validation process: ONCE in core
-- Arrow binding patterns: ONCE in core
-
-## Future Enhancements
-
-1. **External Library Loader** - Load .excalidrawlib files from libraries.excalidraw.com
-2. **Theme Management** - User-configurable color themes saved in core
-3. **Component Library** - Shared reusable components across agents
-4. **Layout Algorithms** - Auto-layout helpers for positioning elements

package/_bmad/core/resources/excalidraw/excalidraw-helpers.md

@@ -1,127 +0,0 @@
-# Excalidraw Element Creation Guidelines
-
-## Text Width Calculation
-
-For text elements inside shapes (labels):
-
-```
-text_width = (text.length × fontSize × 0.6) + 20
-```
-
-Round to nearest 10 for grid alignment.
-
-## Element Grouping Rules
-
-**CRITICAL:** When creating shapes with labels:
-
-1. Generate unique IDs:
-   - `shape-id` for the shape
-   - `text-id` for the text
-   - `group-id` for the group
-
-2. Shape element must have:
-   - `groupIds: [group-id]`
-   - `boundElements: [{type: "text", id: text-id}]`
-
-3. Text element must have:
-   - `containerId: shape-id`
-   - `groupIds: [group-id]` (SAME as shape)
-   - `textAlign: "center"`
-   - `verticalAlign: "middle"`
-   - `width: calculated_width`
-
-## Grid Alignment
-
-- Snap all `x`, `y` coordinates to 20px grid
-- Formula: `Math.round(value / 20) * 20`
-- Spacing between elements: 60px minimum
-
-## Arrow Creation
-
-### Straight Arrows
-
-Use for forward flow (left-to-right, top-to-bottom):
-
-```json
-{
-  "type": "arrow",
-  "startBinding": {
-    "elementId": "source-shape-id",
-    "focus": 0,
-    "gap": 10
-  },
-  "endBinding": {
-    "elementId": "target-shape-id",
-    "focus": 0,
-    "gap": 10
-  },
-  "points": [[0, 0], [distance_x, distance_y]]
-}
-```
-
-### Elbow Arrows
-
-Use for upward flow, backward flow, or complex routing:
-
-```json
-{
-  "type": "arrow",
-  "startBinding": {...},
-  "endBinding": {...},
-  "points": [
-    [0, 0],
-    [intermediate_x, 0],
-    [intermediate_x, intermediate_y],
-    [final_x, final_y]
-  ],
-  "elbowed": true
-}
-```
-
-### Update Connected Shapes
-
-After creating arrow, update `boundElements` on both connected shapes:
-
-```json
-{
-  "id": "shape-id",
-  "boundElements": [
-    { "type": "text", "id": "text-id" },
-    { "type": "arrow", "id": "arrow-id" }
-  ]
-}
-```
-
-## Theme Application
-
-Theme colors should be applied consistently:
-
-- **Shapes**: `backgroundColor` from theme primary fill
-- **Borders**: `strokeColor` from theme accent
-- **Text**: `strokeColor` = "#1e1e1e" (dark text)
-- **Arrows**: `strokeColor` from theme accent
-
-## Validation Checklist
-
-Before saving, verify:
-
-- [ ] All shapes with labels have matching `groupIds`
-- [ ] All text elements have `containerId` pointing to parent shape
-- [ ] Text width calculated properly (no cutoff)
-- [ ] Text alignment set (`textAlign` + `verticalAlign`)
-- [ ] All elements snapped to 20px grid
-- [ ] All arrows have `startBinding` and `endBinding`
-- [ ] `boundElements` array updated on connected shapes
-- [ ] Theme colors applied consistently
-- [ ] No metadata or history in final output
-- [ ] All IDs are unique
-
-## Optimization
-
-Remove from final output:
-
-- `appState` object
-- `files` object (unless images used)
-- All elements with `isDeleted: true`
-- Unused library items
-- Version history

package/_bmad/core/resources/excalidraw/library-loader.md

@@ -1,50 +0,0 @@
-# External Library Loader
-
-**Status:** Placeholder for future implementation
-
-## Purpose
-
-Load external .excalidrawlib files from <https://libraries.excalidraw.com> or custom sources.
-
-## Planned Capabilities
-
-- Load libraries by URL
-- Load libraries from local files
-- Merge multiple libraries
-- Filter library components
-- Cache loaded libraries
-
-## API Reference
-
-Will document how to use:
-
-- `importLibrary(url)` - Load library from URL
-- `loadSceneOrLibraryFromBlob()` - Load from file
-- `mergeLibraryItems()` - Combine libraries
-
-## Usage Example
-
-```yaml
-# Future workflow.yaml structure
-libraries:
-  - url: 'https://libraries.excalidraw.com/libraries/...'
-    filter: ['aws', 'cloud']
-  - path: '{project-root}/_data/custom-library.excalidrawlib'
-```
-
-## Implementation Notes
-
-This will be developed when agents need to leverage the extensive library ecosystem available at <https://libraries.excalidraw.com>.
-
-Hundreds of pre-built component libraries exist for:
-
-- AWS/Cloud icons
-- UI/UX components
-- Business diagrams
-- Mind map shapes
-- Floor plans
-- And much more...
-
-## User Configuration
-
-Future: Users will be able to configure favorite libraries in their BMAD config for automatic loading.