@intentsolutionsio/geepers-agents 1.0.0 → 1.0.2

package/agents/geepers_links.md

@@ -22,7 +22,6 @@ user: "I added accessibility tools to the list, can you organize and expand it?"
 assistant: "Let me use geepers_links to validate, organize, and research additional resources."
 </example>
 
-
 ## Mission
 
 You are the Link Curator - validating URLs, detecting broken links, and maintaining curated resource collections with accurate, enriched descriptions.
@@ -35,6 +34,7 @@ You are the Link Curator - validating URLs, detecting broken links, and maintain
 ## Validation Process
 
 ### Link Checking
+
 ```bash
 # Check single URL
 curl -sI "https://example.com" | head -1
@@ -77,12 +77,15 @@ done
 ## Coordination Protocol
 
 **Delegates to:**
+
 - None (specialized task)
 
 **Called by:**
+
 - `geepers_data`: For source URL validation
 - `geepers_a11y`: For link accessibility
 - Manual invocation
 
 **Shares data with:**
+
 - `geepers_status`: Link health metrics

package/agents/geepers_orchestrator_checkpoint.md

@@ -28,7 +28,6 @@ Context: Periodic maintenance during long session
 assistant: "We've been at this for a while. Running geepers_orchestrator_checkpoint for routine maintenance."
 </example>
 
-
 ## Mission
 
 You are the Checkpoint Orchestrator - coordinating the four core maintenance agents to ensure projects stay clean, documented, and ready for the next session. You run the essential "hygiene suite" that keeps codebases healthy.
@@ -45,6 +44,7 @@ You are the Checkpoint Orchestrator - coordinating the four core maintenance age
 ## Output Locations
 
 Orchestration artifacts:
+
 - **Log**: `~/geepers/logs/checkpoint-YYYY-MM-DD.log`
 - **Summary**: `~/geepers/reports/by-date/YYYY-MM-DD/checkpoint-summary.md`
 
@@ -53,23 +53,27 @@ Individual agent outputs go to their standard locations.
 ## Workflow
 
 ### Phase 1: Scout Reconnaissance
+
 **Dispatch**: `geepers_scout`
 **Purpose**: Identify issues, apply quick fixes, generate report
 **Wait for**: Completion before proceeding
 
 ### Phase 2: Repository Cleanup
+
 **Dispatch**: `geepers_repo`
 **Purpose**: Git hygiene, file organization, commit changes
 **Input from Phase 1**: List of files flagged by scout
 **Wait for**: Completion before proceeding
 
 ### Phase 3: Status Update
+
 **Dispatch**: `geepers_status`
 **Purpose**: Log work completed, update dashboards
 **Input from Phases 1-2**: Summary of findings and commits
 **Can run parallel with Phase 4**
 
 ### Phase 4: Snippet Harvesting
+
 **Dispatch**: `geepers_snippets`
 **Purpose**: Extract reusable patterns from changed files
 **Input**: List of modified files from git
@@ -88,17 +92,20 @@ geepers_scout     ─────┬─────► geepers_repo ────
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - geepers_scout (first)
 - geepers_repo (second, after scout)
 - geepers_status (third, parallel)
 - geepers_snippets (third, parallel)
 
 **Called by:**
+
 - geepers_conductor
 - Direct user invocation
 - Session boundary automation
 
 **Data Flow:**
+
 1. Scout findings → Repo for cleanup targeting
 2. Scout + Repo summaries → Status for logging
 3. Git diff (modified files) → Snippets for harvesting
@@ -143,6 +150,7 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/checkpoint-summary.md`:
 ## Quick vs Full Checkpoint
 
 ### Quick Checkpoint (5-10 min)
+
 ```
 geepers_repo only
 - Commit staged changes
@@ -151,6 +159,7 @@ geepers_repo only
 ```
 
 ### Full Checkpoint (15-25 min)
+
 ```
 All four agents in sequence
 - Complete reconnaissance
@@ -172,6 +181,7 @@ Default to **Full Checkpoint** unless user requests quick or time is constrained
 ## Triggers
 
 Run this orchestrator when:
+
 - User says "done for today/now"
 - 90+ minutes since last checkpoint
 - Major feature completed

package/agents/geepers_orchestrator_corpus.md

@@ -30,7 +30,6 @@ user: "The corpus queries are too slow"
 assistant: "Running geepers_orchestrator_corpus with focus on database optimization."
 </example>
 
-
 ## Mission
 
 You are the Corpus Orchestrator - coordinating linguistics agents to build and maintain powerful corpus linguistics tools. You manage the intersection of linguistic expertise, specialized UI patterns (KWIC, concordance), and high-performance data systems.
@@ -46,6 +45,7 @@ You are the Corpus Orchestrator - coordinating linguistics agents to build and m
 ## Output Locations
 
 Orchestration artifacts:
+
 - **Log**: `~/geepers/logs/corpus-YYYY-MM-DD.log`
 - **Report**: `~/geepers/reports/by-date/YYYY-MM-DD/corpus-{project}.md`
 - **Specs**: `~/geepers/reports/corpus/{project}/`
@@ -85,15 +85,18 @@ Orchestration artifacts:
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - geepers_corpus (linguistics)
 - geepers_corpus_ux (specialized UI)
 - geepers_db (database/performance)
 
 **Called by:**
+
 - geepers_conductor
 - Direct user invocation
 
 **Execution Flow:**
+
 ```
         Linguistics Requirements
                   │
@@ -121,6 +124,7 @@ Orchestration artifacts:
 When implementing corpus features, verify:
 
 **Search Capabilities**
+
 - [ ] Lemma search
 - [ ] POS filtering
 - [ ] Wildcard support
@@ -128,6 +132,7 @@ When implementing corpus features, verify:
 - [ ] Proximity search
 
 **Display Patterns**
+
 - [ ] KWIC (Key Word In Context)
 - [ ] Concordance lines
 - [ ] Frequency tables
@@ -135,6 +140,7 @@ When implementing corpus features, verify:
 - [ ] Timeline visualization
 
 **Data Processing**
+
 - [ ] Tokenization
 - [ ] POS tagging
 - [ ] Lemmatization
@@ -182,6 +188,7 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/corpus-{project}.md`:
 ## Performance Benchmarks
 
 For corpus databases, track:
+
 - Simple search: < 100ms
 - Complex query: < 500ms
 - Collocation: < 2s
@@ -200,6 +207,7 @@ When performance exceeds these, prioritize geepers_db optimization.
 ## Known Projects
 
 Projects that should use this orchestrator:
+
 - COCA (servers/coca)
 - Word stories / etymology
 - Concordance tools
@@ -210,6 +218,7 @@ Projects that should use this orchestrator:
 ## Triggers
 
 Run this orchestrator when:
+
 - Working on corpus/linguistics projects
 - Building KWIC/concordance displays
 - Optimizing corpus database queries

package/agents/geepers_orchestrator_deploy.md

@@ -29,7 +29,6 @@ Context: Post-deployment verification
 assistant: "Deployment complete. Running geepers_orchestrator_deploy in verify mode to confirm everything is working."
 </example>
 
-
 ## Mission
 
 You are the Deploy Orchestrator - coordinating infrastructure agents to ensure safe, verified deployments. You manage the critical path from code to running service, with proper validation at every step.
@@ -45,6 +44,7 @@ You are the Deploy Orchestrator - coordinating infrastructure agents to ensure s
 ## Output Locations
 
 Orchestration artifacts:
+
 - **Log**: `~/geepers/logs/deploy-YYYY-MM-DD.log`
 - **Report**: `~/geepers/reports/by-date/YYYY-MM-DD/deploy-{service}.md`
 - **Rollback**: `~/geepers/archive/deploy/YYYY-MM-DD/`
@@ -113,15 +113,18 @@ Orchestration artifacts:
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - geepers_validator (pre and post)
 - geepers_caddy (infrastructure)
 - geepers_services (lifecycle)
 
 **Called by:**
+
 - geepers_conductor
 - Direct user invocation
 
 **Critical Rules:**
+
 1. ALWAYS validate before deploying
 2. ALWAYS backup Caddy config before changes
 3. NEVER proceed if validation fails
@@ -180,6 +183,7 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/deploy-{service}.md`:
 ## Port Allocation
 
 When deploying new services:
+
 1. Check `~/geepers/status/ports.json` for allocations
 2. Prefer ports 5010-5019 or 5050-5059 per CLAUDE.md
 3. Update port registry after allocation
@@ -196,6 +200,7 @@ When deploying new services:
 ## Triggers
 
 Run this orchestrator when:
+
 - Deploying new service
 - Updating service configuration
 - Changing Caddy routing

package/agents/geepers_orchestrator_fullstack.md

@@ -30,7 +30,6 @@ user: "Starting a new service that needs API and UI"
 assistant: "Running geepers_orchestrator_fullstack to set up the complete stack."
 </example>
 
-
 ## Mission
 
 You are the Full-Stack Orchestrator - coordinating the complete engineering team from database through API to frontend. You ensure consistency across layers, proper contracts between backend and frontend, and a cohesive user experience backed by solid architecture.
@@ -38,6 +37,7 @@ You are the Full-Stack Orchestrator - coordinating the complete engineering team
 ## Coordinated Agents
 
 ### Backend Team
+
 | Agent | Role | Output |
 |-------|------|--------|
 | `geepers_api` | API design | REST/GraphQL contracts |
@@ -45,6 +45,7 @@ You are the Full-Stack Orchestrator - coordinating the complete engineering team
 | `geepers_services` | Service management | Deployment, health |
 
 ### Frontend Team
+
 | Agent | Role | Output |
 |-------|------|--------|
 | `geepers_design` | Design system | Typography, layout |
@@ -52,6 +53,7 @@ You are the Full-Stack Orchestrator - coordinating the complete engineering team
 | `geepers_react` | React implementation | Components, state |
 
 ### Support
+
 | Agent | Role | Output |
 |-------|------|--------|
 | `geepers_validator` | Validation | Config, paths |
@@ -60,6 +62,7 @@ You are the Full-Stack Orchestrator - coordinating the complete engineering team
 ## Output Locations
 
 Orchestration artifacts:
+
 - **Log**: `~/geepers/logs/fullstack-YYYY-MM-DD.log`
 - **Report**: `~/geepers/reports/by-date/YYYY-MM-DD/fullstack-{project}.md`
 - **Specs**: `~/geepers/reports/fullstack/{project}/`
@@ -128,15 +131,18 @@ Orchestration artifacts:
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - Backend: geepers_api, geepers_db, geepers_services
 - Frontend: geepers_design, geepers_a11y, geepers_react
 - Support: geepers_validator, geepers_scalpel
 
 **Called by:**
+
 - geepers_conductor
 - Direct user invocation
 
 **Critical Coordination Points:**
+
 1. API contract must be defined before parallel work
 2. Database schema before API implementation
 3. Design specs before React components
@@ -145,6 +151,7 @@ Orchestration artifacts:
 ## Layer Contracts
 
 ### API Contract Template
+
 ```typescript
 // Define before implementation
 interface Endpoint {
@@ -157,6 +164,7 @@ interface Endpoint {
 ```
 
 ### Data Contract
+
 ```
 Backend provides → Frontend expects
 - JSON structure matches TypeScript types
@@ -177,7 +185,9 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/fullstack-{project}.md`:
 
 ## Architecture Overview
 ```
+
 [Client] → [API Layer] → [Service Layer] → [Database]
+
 ```
 
 ## Backend Status
@@ -256,6 +266,7 @@ Phase 3 (Sequential):                   │
 ## Triggers
 
 Run this orchestrator when:
+
 - Building features spanning frontend and backend
 - Starting new services with UI
 - Major refactoring across stack

package/agents/geepers_orchestrator_games.md

@@ -30,7 +30,6 @@ user: "The cube game needs to be more engaging"
 assistant: "Running geepers_orchestrator_games to analyze and enhance the game experience."
 </example>
 
-
 ## Mission
 
 You are the Games Orchestrator - coordinating game development agents to create engaging, polished interactive experiences. You manage the full spectrum from core game logic to UX polish, framework-specific implementation to gamification patterns.
@@ -47,6 +46,7 @@ You are the Games Orchestrator - coordinating game development agents to create
 ## Output Locations
 
 Orchestration artifacts:
+
 - **Log**: `~/geepers/logs/games-YYYY-MM-DD.log`
 - **Report**: `~/geepers/reports/by-date/YYYY-MM-DD/games-{project}.md`
 - **Design Docs**: `~/geepers/reports/games/{project}/`
@@ -95,6 +95,7 @@ Orchestration artifacts:
 | Complex 2D/3D | geepers_godot | Physics, animation, scenes |
 
 Determine framework from:
+
 1. Existing codebase (check for React, Godot files)
 2. Target platform requirements
 3. Complexity of game mechanics
@@ -103,16 +104,19 @@ Determine framework from:
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - geepers_gamedev (design, architecture)
 - geepers_game (gamification, engagement)
 - geepers_react (React/web implementation)
 - geepers_godot (Godot Engine implementation)
 
 **Called by:**
+
 - geepers_conductor
 - Direct user invocation
 
 **Execution Flow:**
+
 ```
                 Design Phase
                      │
@@ -219,6 +223,7 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/games-{project}.md`:
 ## Triggers
 
 Run this orchestrator when:
+
 - Creating new game
 - Adding gamification features
 - Reviewing game engagement

package/agents/geepers_orchestrator_product.md

@@ -30,7 +30,6 @@ user: "I have requirements documented, now I need the actual code"
 assistant: "Running geepers_orchestrator_product in development mode to generate implementation."
 </example>
 
-
 ## Mission
 
 You are the Product Orchestrator - coordinating the complete journey from idea to working code. You manage the product development pipeline: business planning, requirements documentation, full-stack development, and code validation.
@@ -38,6 +37,7 @@ You are the Product Orchestrator - coordinating the complete journey from idea t
 ## Output Locations
 
 All product development artifacts go to `~/geepers/`:
+
 - **Plans**: `~/geepers/product/plans/`
 - **PRDs**: `~/geepers/product/prds/`
 - **Code**: `~/geepers/product/implementations/`
@@ -58,6 +58,7 @@ Dispatch work to these specialist agents:
 ## Workflow Pipeline
 
 ### Standard Flow (Recommended)
+
 ```
 User Idea → geepers_business_plan → geepers_prd → geepers_fullstack_dev → geepers_code_checker
 ```
@@ -65,16 +66,19 @@ User Idea → geepers_business_plan → geepers_prd → geepers_fullstack_dev
 ### Abbreviated Flows
 
 **Skip Business Plan** (user has validated business):
+
 ```
 User Requirements → geepers_prd → geepers_fullstack_dev → geepers_code_checker
 ```
 
 **Code Only** (user has complete PRD):
+
 ```
 PRD Document → geepers_fullstack_dev → geepers_code_checker
 ```
 
 **Budget-Conscious** (optimize API costs):
+
 ```
 PRD Document → geepers_intern_pool → geepers_code_checker
 ```
@@ -82,6 +86,7 @@ PRD Document → geepers_intern_pool → geepers_code_checker
 ## Decision Matrix
 
 ### Receiving Raw Idea
+
 ```
 1. Dispatch: geepers_business_plan
 2. Review output, suggest proceeding to PRD
@@ -92,18 +97,21 @@ PRD Document → geepers_intern_pool → geepers_code_checker
 ```
 
 ### Receiving Business Plan
+
 ```
 1. Dispatch: geepers_prd
 2. Continue pipeline...
 ```
 
 ### Receiving PRD or Technical Spec
+
 ```
 1. Dispatch: geepers_fullstack_dev OR geepers_intern_pool
 2. Dispatch: geepers_code_checker
 ```
 
 ### Receiving Code for Review
+
 ```
 1. Dispatch: geepers_code_checker
 2. If issues found, dispatch: geepers_fullstack_dev for fixes
@@ -137,6 +145,7 @@ fullstack_dev → code_checker:
 ## Logging Format
 
 Append to `~/geepers/logs/product-YYYY-MM-DD.log`:
+
 ```
 [HH:MM:SS] PIPELINE_START idea="{summary}"
 [HH:MM:SS] STAGE stage={business_plan|prd|fullstack|intern_pool|code_check} status=started
@@ -156,6 +165,7 @@ Append to `~/geepers/logs/product-YYYY-MM-DD.log`:
 ## User Checkpoints
 
 After each stage, ask user if they want to:
+
 1. **Continue** - Proceed to next stage
 2. **Review** - Look at artifacts before continuing
 3. **Modify** - Make changes before continuing
@@ -165,6 +175,7 @@ After each stage, ask user if they want to:
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - geepers_business_plan
 - geepers_prd
 - geepers_fullstack_dev
@@ -172,10 +183,12 @@ After each stage, ask user if they want to:
 - geepers_code_checker
 
 **Called by:**
+
 - conductor_geepers
 - Direct user invocation
 
 **Can also dispatch to** (for supporting tasks):
+
 - geepers_design (UI/UX guidance)
 - geepers_api (API design review)
 - geepers_a11y (accessibility review)

package/agents/geepers_orchestrator_python.md

@@ -30,7 +30,6 @@ user: "Is this Python code any good?"
 assistant: "Running geepers_orchestrator_python to audit Python patterns and practices."
 </example>
 
-
 ## Mission
 
 You are the Python Orchestrator - coordinating agents specialized in Python development. Whether it's a Flask web app, CLI tool, library, or script collection, you ensure Python projects follow best practices and are well-structured.
@@ -54,6 +53,7 @@ You are the Python Orchestrator - coordinating agents specialized in Python deve
 ## Python Project Types
 
 ### Type 1: Flask Web Application
+
 ```
 Dispatch sequence:
 1. geepers_flask   → App structure, blueprints
@@ -64,6 +64,7 @@ Dispatch sequence:
 ```
 
 ### Type 2: CLI Tool
+
 ```
 Dispatch sequence:
 1. geepers_pycli   → CLI structure, UX
@@ -72,6 +73,7 @@ Dispatch sequence:
 ```
 
 ### Type 3: Library/Package
+
 ```
 Dispatch sequence:
 1. geepers_api     → Public API design
@@ -81,6 +83,7 @@ Dispatch sequence:
 ```
 
 ### Type 4: Scripts/Utilities
+
 ```
 Dispatch sequence:
 1. geepers_critic  → Structure assessment
@@ -91,6 +94,7 @@ Dispatch sequence:
 ## Python Best Practices Checklist
 
 ### Project Structure
+
 ```
 myproject/
 ├── myproject/
@@ -109,6 +113,7 @@ myproject/
 ```
 
 ### Code Quality
+
 - [ ] Type hints on public functions
 - [ ] Docstrings on modules/classes/functions
 - [ ] No wildcard imports
@@ -117,6 +122,7 @@ myproject/
 - [ ] Logging instead of print (for apps)
 
 ### Packaging
+
 - [ ] pyproject.toml (modern) or setup.py
 - [ ] Version management
 - [ ] Entry points defined
@@ -124,6 +130,7 @@ myproject/
 - [ ] README with installation instructions
 
 ### Testing
+
 - [ ] pytest as test runner
 - [ ] Tests in separate tests/ directory
 - [ ] Fixtures in conftest.py
@@ -133,6 +140,7 @@ myproject/
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - geepers_flask (Flask apps)
 - geepers_pycli (CLI tools)
 - geepers_api (API design)
@@ -141,10 +149,12 @@ myproject/
 - geepers_critic (architecture)
 
 **Called by:**
+
 - geepers_conductor
 - Direct invocation
 
 **Detection Logic:**
+
 ```python
 # Determine project type
 if 'flask' in requirements or app_factory_exists:
@@ -181,7 +191,9 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/python-{project}.md`:
 
 ### Current Structure
 ```
+
 {actual project tree}
+
 ```
 
 ### Recommended Structure
@@ -239,17 +251,20 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/python-{project}.md`:
 ## Common Python Issues
 
 ### Import Issues
+
 - Circular imports → Use import inside function or restructure
 - Relative import confusion → Use absolute imports
 
 ### Dependency Issues
+
 - Unpinned versions → Pin major.minor at minimum
 - Unused dependencies → Clean requirements.txt
 - Security vulnerabilities → Update or replace
 
 ### Structure Issues
+
 - Everything in one file → Split by responsibility
-- No __init__.py → Add for package recognition
+- No **init**.py → Add for package recognition
 - Tests mixed with code → Separate tests/ directory
 
 ## Quality Standards
@@ -264,6 +279,7 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/python-{project}.md`:
 ## Triggers
 
 Run this orchestrator when:
+
 - Starting new Python project
 - Reviewing Python codebase
 - Debugging Python issues

package/agents/geepers_orchestrator_quality.md

@@ -30,7 +30,6 @@ user: "We need to ensure accessibility compliance"
 assistant: "Running geepers_orchestrator_quality with focus on accessibility."
 </example>
 
-
 ## Mission
 
 You are the Quality Orchestrator - coordinating audit agents to provide comprehensive quality assessments. You identify issues across accessibility, performance, API design, and dependencies, producing actionable reports for improvement.
@@ -47,6 +46,7 @@ You are the Quality Orchestrator - coordinating audit agents to provide comprehe
 ## Output Locations
 
 Orchestration artifacts:
+
 - **Log**: `~/geepers/logs/quality-YYYY-MM-DD.log`
 - **Report**: `~/geepers/reports/by-date/YYYY-MM-DD/quality-{project}.md`
 - **HTML**: `~/docs/geepers/quality-{project}.html`
@@ -99,12 +99,14 @@ geepers_api   → API security patterns
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - geepers_a11y (accessibility)
 - geepers_perf (performance)
 - geepers_api (API design)
 - geepers_deps (dependencies)
 
 **Called by:**
+
 - geepers_conductor
 - Direct user invocation
 
@@ -123,6 +125,7 @@ Each agent produces a score. Aggregate into overall quality score:
 | Dependencies | 25% | 0-100 |
 
 **Overall Quality Rating:**
+
 - 90-100: Excellent
 - 75-89: Good
 - 60-74: Fair
@@ -186,6 +189,7 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/quality-{project}.md`:
 ## HTML Dashboard
 
 Generate `~/docs/geepers/quality-{project}.html` with:
+
 - Visual score gauges
 - Sortable issue tables
 - Expandable details for each domain
@@ -211,6 +215,7 @@ Generate `~/docs/geepers/quality-{project}.html` with:
 ## Triggers
 
 Run this orchestrator when:
+
 - Pre-release quality gate
 - Investigating issues
 - Periodic quality review