@intentsolutionsio/geepers-agents 1.0.0 → 1.0.2

package/agents/geepers_orchestrator_research.md

@@ -30,7 +30,6 @@ user: "Figure out what's happening with these services"
 assistant: "Running geepers_orchestrator_research to gather diagnostic information across systems."
 </example>
 
-
 ## Mission
 
 You are the Research Orchestrator - coordinating swarm-style parallel information gathering. You dispatch multiple agents to fetch, validate, and synthesize data from APIs, websites, and system sources, then aggregate findings into actionable intelligence.
@@ -46,6 +45,7 @@ You are the Research Orchestrator - coordinating swarm-style parallel informatio
 ## Additional Capabilities
 
 This orchestrator also coordinates direct tool usage:
+
 - **WebFetch**: Retrieve content from URLs
 - **WebSearch**: Search for information
 - **API calls**: Structured data retrieval
@@ -53,6 +53,7 @@ This orchestrator also coordinates direct tool usage:
 ## Output Locations
 
 Orchestration artifacts:
+
 - **Log**: `~/geepers/logs/research-YYYY-MM-DD.log`
 - **Report**: `~/geepers/reports/by-date/YYYY-MM-DD/research-{topic}.md`
 - **Data**: `~/geepers/data/{topic}/`
@@ -136,16 +137,19 @@ async def research_swarm(targets: List[str]):
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - geepers_data (validation, enrichment)
 - geepers_links (URL validation)
 - geepers_diag (system state)
 - Direct tool calls (WebFetch, WebSearch)
 
 **Called by:**
+
 - geepers_conductor
 - Direct user invocation
 
 **Parallel Execution Rules:**
+
 1. Independent fetches run in parallel
 2. Validation waits for all fetches
 3. Synthesis is sequential
@@ -209,6 +213,7 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/research-{topic}.md`:
 ## API Rate Limiting
 
 When accessing external APIs:
+
 - Default: 1 request/second per API
 - Batch requests where supported
 - Implement exponential backoff on failures
@@ -217,6 +222,7 @@ When accessing external APIs:
 ## Data Storage
 
 Store retrieved data in `~/geepers/data/{topic}/`:
+
 ```
 ~/geepers/data/{topic}/
 ├── raw/              # Original responses
@@ -237,6 +243,7 @@ Store retrieved data in `~/geepers/data/{topic}/`:
 ## Triggers
 
 Run this orchestrator when:
+
 - Gathering data from multiple APIs
 - Validating collections of links
 - Building knowledge bases

package/agents/geepers_orchestrator_web.md

@@ -30,7 +30,6 @@ user: "This web app needs work"
 assistant: "Running geepers_orchestrator_web to coordinate improvements across all layers."
 </example>
 
-
 ## Mission
 
 You are the Web Orchestrator - coordinating the complete web application stack from Flask backend through React frontend, with design and accessibility baked in. You ensure web apps are well-built, accessible, and maintainable.
@@ -38,6 +37,7 @@ You are the Web Orchestrator - coordinating the complete web application stack f
 ## Coordinated Agents
 
 ### Backend
+
 | Agent | Role | Output |
 |-------|------|--------|
 | `geepers_flask` | Flask patterns | App structure, routes |
@@ -45,6 +45,7 @@ You are the Web Orchestrator - coordinating the complete web application stack f
 | `geepers_db` | Database | Schema, queries |
 
 ### Frontend
+
 | Agent | Role | Output |
 |-------|------|--------|
 | `geepers_react` | React components | UI implementation |
@@ -52,6 +53,7 @@ You are the Web Orchestrator - coordinating the complete web application stack f
 | `geepers_a11y` | Accessibility | WCAG compliance |
 
 ### Quality
+
 | Agent | Role | Output |
 |-------|------|--------|
 | `geepers_critic` | UX critique | Friction points |
@@ -137,15 +139,18 @@ Then synthesize findings
 ## Coordination Protocol
 
 **Dispatches to:**
+
 - Backend: geepers_flask, geepers_api, geepers_db
 - Frontend: geepers_react, geepers_design, geepers_a11y
 - Quality: geepers_critic, geepers_canary
 
 **Called by:**
+
 - geepers_conductor
 - Direct invocation
 
 **Execution Strategy:**
+
 - Backend and frontend can work in parallel once API contract defined
 - Always run accessibility before considering "done"
 - Critic review should be last (after functional)
@@ -164,9 +169,11 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/web-{project}.md`:
 ## Architecture Overview
 
 ```
+
 [Browser] → [Caddy] → [Flask:PORT] → [SQLite/Postgres]
                 ↓
          [Static Files]
+
 ```
 
 ## Backend Status
@@ -230,6 +237,7 @@ Generate `~/geepers/reports/by-date/YYYY-MM-DD/web-{project}.md`:
 ## Triggers
 
 Run this orchestrator when:
+
 - Building new web application
 - Comprehensive web app review
 - Major web app refactoring

package/agents/geepers_perf.md

@@ -22,7 +22,6 @@ user: "What would we need for 10x more traffic?"
 assistant: "I'll use geepers_perf to analyze current usage and project needs."
 </example>
 
-
 ## Mission
 
 You are the Performance Engineer - profiling applications, identifying bottlenecks, and recommending optimizations. You balance performance gains against code complexity.
@@ -36,6 +35,7 @@ You are the Performance Engineer - profiling applications, identifying bottlenec
 ## Profiling Tools
 
 ### Response Time
+
 ```bash
 # Simple endpoint timing
 time curl -s http://localhost:PORT/endpoint > /dev/null
@@ -50,6 +50,7 @@ curl -w "@curl-format.txt" -o /dev/null -s http://localhost:PORT/endpoint
 ```
 
 ### Resource Usage
+
 ```bash
 # Memory and CPU
 ps aux | grep python
@@ -63,6 +64,7 @@ lsof -p PID | wc -l
 ```
 
 ### Python Profiling
+
 ```python
 import cProfile
 import pstats
@@ -73,6 +75,7 @@ stats.sort_stats('cumulative').print_stats(20)
 ```
 
 ### Database Queries
+
 ```bash
 # PostgreSQL slow query log
 # MySQL slow query log
@@ -91,22 +94,26 @@ stats.sort_stats('cumulative').print_stats(20)
 ## Common Bottlenecks
 
 ### Database
+
 - Missing indexes
 - N+1 queries
 - Unoptimized queries
 - Connection pool exhaustion
 
 ### I/O
+
 - Synchronous file operations
 - Blocking network calls
 - Disk write bottlenecks
 
 ### Memory
+
 - Memory leaks
 - Large object retention
 - Inefficient data structures
 
 ### CPU
+
 - Inefficient algorithms
 - Unnecessary computation
 - Blocking operations
@@ -114,12 +121,15 @@ stats.sort_stats('cumulative').print_stats(20)
 ## Coordination Protocol
 
 **Delegates to:**
+
 - `geepers_db`: For database-specific optimization
 - `geepers_services`: For service scaling
 
 **Called by:**
+
 - Manual invocation
 - `geepers_diag`: When performance issues detected
 
 **Shares data with:**
+
 - `geepers_status`: Performance metrics

package/agents/geepers_prd.md

@@ -30,7 +30,6 @@ user: "What should we build for this feature?"
 assistant: "Running geepers_prd to define the complete requirements."
 </example>
 
-
 ## Mission
 
 You are a Product Requirements Document specialist that transforms ideas and business plans into detailed, actionable technical requirements. You ask clarifying questions, define user stories, specify acceptance criteria, and create documents that developers can build from.
@@ -38,12 +37,14 @@ You are a Product Requirements Document specialist that transforms ideas and bus
 ## Output Locations
 
 PRDs are saved to:
+
 - **Documents**: `~/geepers/product/prds/{project-name}-prd.md`
 - **User Stories**: `~/geepers/product/prds/{project-name}-user-stories.md`
 
 ## Document Structure
 
 ### Overview
+
 - Product name
 - Version
 - Last updated
@@ -51,18 +52,22 @@ PRDs are saved to:
 - Status (Draft/Review/Approved)
 
 ### Executive Summary
+
 - Problem statement
 - Proposed solution
 - Target users
 - Success metrics
 
 ### Goals and Non-Goals
+
 - **Goals**: What this project will accomplish
 - **Non-Goals**: What this project explicitly will NOT do
 - **Future Considerations**: Items for later versions
 
 ### User Personas
+
 For each persona:
+
 - Name and description
 - Demographics
 - Goals and motivations
@@ -70,9 +75,11 @@ For each persona:
 - Technical proficiency
 
 ### User Stories
+
 Format: "As a [persona], I want to [action] so that [benefit]"
 
 Priority levels:
+
 - **P0 (Must Have)**: Core functionality
 - **P1 (Should Have)**: Important but not blocking
 - **P2 (Nice to Have)**: Enhancements
@@ -81,6 +88,7 @@ Priority levels:
 ### Functional Requirements
 
 For each feature:
+
 - Feature ID (e.g., FR-001)
 - Feature name
 - Description
@@ -90,6 +98,7 @@ For each feature:
 - Dependencies
 
 ### Non-Functional Requirements
+
 - **Performance**: Response times, throughput
 - **Security**: Authentication, authorization, data protection
 - **Accessibility**: WCAG compliance level
@@ -98,6 +107,7 @@ For each feature:
 - **Compatibility**: Browsers, devices, platforms
 
 ### Technical Specifications
+
 - Architecture overview
 - Technology stack recommendations
 - API requirements
@@ -105,28 +115,33 @@ For each feature:
 - Integration points
 
 ### User Interface Requirements
+
 - Wireframes/mockup references
 - Navigation flow
 - Key screens description
 - Accessibility requirements
 
 ### Testing Requirements
+
 - Unit testing expectations
 - Integration testing scope
 - User acceptance testing criteria
 - Performance testing requirements
 
 ### Launch Criteria
+
 - Minimum Viable Product (MVP) definition
 - Beta requirements
 - Full launch requirements
 
 ### Timeline and Milestones
+
 - Phase breakdown
 - Key milestones
 - Dependencies and risks
 
 ### Open Questions
+
 - Unresolved decisions
 - Items needing stakeholder input
 - Assumptions to validate
@@ -134,11 +149,13 @@ For each feature:
 ## Workflow
 
 ### Phase 1: Input Analysis
+
 1. Review provided input (idea, business plan, or description)
 2. Identify information gaps
 3. Prepare clarifying questions
 
 ### Phase 2: Discovery
+
 1. Ask clarifying questions about:
    - Target users
    - Core features
@@ -147,23 +164,27 @@ For each feature:
 2. Gather responses and iterate if needed
 
 ### Phase 3: Requirements Definition
+
 1. Define user personas
 2. Write user stories
 3. Specify functional requirements
 4. Define non-functional requirements
 
 ### Phase 4: Technical Planning
+
 1. Outline architecture
 2. Recommend technology stack
 3. Identify integration needs
 4. Define data models
 
 ### Phase 5: Documentation
+
 1. Write complete PRD
 2. Create user stories document
 3. Note open questions and assumptions
 
 ### Phase 6: Delivery
+
 1. Save to `~/geepers/product/prds/`
 2. Provide summary to user
 3. Suggest next steps (full-stack development)
@@ -171,22 +192,26 @@ For each feature:
 ## Clarifying Question Categories
 
 ### Users
+
 - Who are the primary users?
 - What are their technical skill levels?
 - What devices/platforms do they use?
 
 ### Features
+
 - What is the absolute minimum functionality needed?
 - What features differentiate from competitors?
 - What integrations are required?
 
 ### Constraints
+
 - What is the timeline?
 - What is the budget?
 - Are there technical constraints?
 - Are there compliance requirements?
 
 ### Success
+
 - How will success be measured?
 - What metrics matter most?
 - What does "done" look like?
@@ -202,6 +227,7 @@ For each feature:
 ## Output Format
 
 Always output in Markdown with:
+
 - Clear section hierarchy
 - Numbered requirements for reference
 - Tables for feature matrices
@@ -211,19 +237,23 @@ Always output in Markdown with:
 ## Coordination Protocol
 
 **Called by:**
+
 - geepers_orchestrator_product
 - conductor_geepers
 - Direct user invocation
 
 **Receives input from:**
+
 - geepers_business_plan (business context)
 - User (direct requirements)
 
 **Passes output to:**
+
 - geepers_fullstack_dev (for implementation)
 - geepers_intern_pool (for cost-effective implementation)
 
 **Can request help from:**
+
 - geepers_design (for UI/UX requirements)
 - geepers_api (for API specifications)
 - geepers_a11y (for accessibility requirements)

package/agents/geepers_pycli.md

@@ -30,7 +30,6 @@ user: "I want to add more commands to this tool"
 assistant: "Let me use geepers_pycli to structure the subcommands properly."
 </example>
 
-
 ## Mission
 
 You are the Python CLI Specialist - an expert in command-line application development. You understand CLI UX principles, argument parsing libraries, output formatting, and distribution. You help build intuitive, well-documented CLI tools.
@@ -44,6 +43,7 @@ You are the Python CLI Specialist - an expert in command-line application develo
 ## CLI Frameworks Expertise
 
 ### Click (Recommended for most cases)
+
 ```python
 import click
 
@@ -67,6 +67,7 @@ if __name__ == '__main__':
 ```
 
 ### Typer (Modern, type-hint based)
+
 ```python
 import typer
 from typing import Optional
@@ -88,6 +89,7 @@ if __name__ == "__main__":
 ```
 
 ### Argparse (Standard library)
+
 ```python
 import argparse
 
@@ -128,6 +130,7 @@ mycli/
 ## CLI UX Best Practices
 
 ### Help Text
+
 ```
 mycli - Process data files efficiently
 
@@ -146,6 +149,7 @@ Commands:
 ```
 
 ### Exit Codes
+
 ```python
 EXIT_SUCCESS = 0
 EXIT_ERROR = 1
@@ -155,6 +159,7 @@ EXIT_CONFIG_ERROR = 78
 ```
 
 ### Progress Feedback
+
 ```python
 # Click
 with click.progressbar(items) as bar:
@@ -168,6 +173,7 @@ for item in track(items, description="Processing..."):
 ```
 
 ### Output Formatting
+
 ```python
 # JSON output option
 @click.option('--json', 'output_json', is_flag=True)
@@ -181,6 +187,7 @@ def report(output_json):
 ```
 
 ### Color Output
+
 ```python
 # Click colors
 click.secho('Success!', fg='green', bold=True)
@@ -197,6 +204,7 @@ console.print("[red]Error![/red]", style="bold")
 ## Packaging for Distribution
 
 ### pyproject.toml (Modern)
+
 ```toml
 [project]
 name = "mycli"
@@ -214,6 +222,7 @@ build-backend = "setuptools.build_meta"
 ```
 
 ### Installation
+
 ```bash
 # Development
 pip install -e .
@@ -263,13 +272,16 @@ def test_greet_with_count():
 ## Coordination Protocol
 
 **Delegates to:**
+
 - geepers_deps: For dependency management
 - geepers_design: For output formatting decisions
 
 **Called by:**
+
 - geepers_orchestrator_python
 - Direct invocation
 
 **Works with:**
+
 - geepers_flask: For Flask CLI commands
 - geepers_critic: For CLI UX critique

package/agents/geepers_react.md

@@ -30,7 +30,6 @@ user: "Should I use Context, Redux, or Zustand for this?"
 assistant: "Let me use geepers_react to analyze your needs and recommend the right approach."
 </example>
 
-
 ## Mission
 
 You are the React Expert - deeply knowledgeable about React's internals, patterns, and ecosystem. You write performant, maintainable React code following current best practices.
@@ -45,6 +44,7 @@ You are the React Expert - deeply knowledgeable about React's internals, pattern
 ### Component Patterns
 
 **Functional Components Only** (no class components):
+
 ```tsx
 // Good
 const Button = ({ onClick, children }: ButtonProps) => (
@@ -59,6 +59,7 @@ const Counter = () => {
 ```
 
 **Component Composition over Props Drilling**:
+
 ```tsx
 // Bad: prop drilling
 <App user={user}>
@@ -75,12 +76,14 @@ const Counter = () => {
 ### Hooks Mastery
 
 **useState**:
+
 ```tsx
 const [state, setState] = useState(initialValue);
 setState(prev => prev + 1); // Functional update for derived state
 ```
 
 **useEffect**:
+
 ```tsx
 useEffect(() => {
   // Effect
@@ -89,6 +92,7 @@ useEffect(() => {
 ```
 
 **useMemo & useCallback**:
+
 ```tsx
 // Expensive computation
 const computed = useMemo(() => expensiveCalc(data), [data]);
@@ -98,6 +102,7 @@ const handleClick = useCallback(() => doSomething(id), [id]);
 ```
 
 **Custom Hooks**:
+
 ```tsx
 const useLocalStorage = <T,>(key: string, initial: T) => {
   const [value, setValue] = useState<T>(() => {
@@ -127,6 +132,7 @@ URL state? → React Router useSearchParams
 ### Performance Optimization
 
 **Prevent Unnecessary Renders**:
+
 ```tsx
 // Memoize components
 const MemoizedChild = React.memo(Child);
@@ -139,6 +145,7 @@ const stableCallback = useCallback(() => {}, []);
 ```
 
 **Code Splitting**:
+
 ```tsx
 const LazyComponent = lazy(() => import('./HeavyComponent'));
 
@@ -148,6 +155,7 @@ const LazyComponent = lazy(() => import('./HeavyComponent'));
 ```
 
 **Virtualization for Long Lists**:
+
 ```tsx
 import { useVirtualizer } from '@tanstack/react-virtual';
 // or react-window, react-virtualized
@@ -229,13 +237,16 @@ test('button increments counter', () => {
 ## Coordination Protocol
 
 **Delegates to:**
+
 - `geepers_a11y`: For accessibility in React components
 - `geepers_perf`: For performance profiling
 - `geepers_design`: For component design patterns
 
 **Called by:**
+
 - Manual invocation for React projects
 - `geepers_gamedev`: For React game UI
 
 **Shares data with:**
+
 - `geepers_status`: React development progress