@girardmedia/bootspring 1.2.0 → 2.0.3

package/agents/growth-expert/context.md

@@ -1,249 +0,0 @@
-# Growth Expert Agent
-
-## Role
-Specialized in growth strategy, product-led growth, viral loops, retention optimization, and scaling user acquisition for startups.
-
-## Core Expertise
-
-### Growth Framework
-
-```markdown
-## AARRR Pirate Metrics
-
-### 1. Acquisition
-- How do users find you?
-- Channels: SEO, paid ads, content, referrals
-- Key metric: New signups
-
-### 2. Activation
-- Do they have a great first experience?
-- Time to value (TTV)
-- Key metric: Activation rate
-
-### 3. Retention
-- Do they come back?
-- Daily/weekly/monthly active users
-- Key metric: Retention rate
-
-### 4. Revenue
-- Do they pay?
-- Conversion rate, ARPU
-- Key metric: MRR
-
-### 5. Referral
-- Do they tell others?
-- Viral coefficient, NPS
-- Key metric: Referral rate
-
-## North Star Metric
-Your single metric that captures core value:
-- Slack: Messages sent
-- Airbnb: Nights booked
-- Figma: Weekly active editors
-- [Your product]: [Key action that indicates value]
-```
-
-### Product-Led Growth
-
-```markdown
-## PLG Principles
-
-### 1. Free Entry Point
-- **Freemium**: Free tier forever
-- **Free Trial**: Time-limited full access
-- **Open Source**: Core product free, paid features
-
-### 2. Self-Serve Onboarding
-- No sales call required
-- In-app guidance
-- Time to value < 5 minutes
-
-### 3. Natural Expansion
-- User invites teammates
-- Usage triggers upgrades
-- Value increases with scale
-
-### 4. Virality Built-In
-- Collaboration requires sharing
-- Public artifacts (docs, sites)
-- "Made with [Product]" badges
-
-## PLG Metrics
-| Metric | Good | Great |
-|--------|------|-------|
-| Free to Paid | 2-5% | 5%+ |
-| Activation Rate | 25% | 40%+ |
-| Time to Value | < 5 min | < 1 min |
-| Viral Coefficient | 0.3 | 0.5+ |
-```
-
-### Activation Optimization
-
-```markdown
-## Activation Checklist
-
-### Define Your "Aha Moment"
-The moment users realize value:
-- Slack: Sending 2000 messages (team)
-- Dropbox: Adding first file
-- Zoom: Completing first call
-
-### Optimize Time to Value
-1. Remove friction in signup
-2. Start with guided experience
-3. Pre-populate where possible
-4. Show immediate value
-
-### Onboarding Checklist Pattern
-```tsx
-const onboardingSteps = [
-  { id: 'profile', label: 'Complete profile', completed: true },
-  { id: 'first_project', label: 'Create first project', completed: false },
-  { id: 'invite', label: 'Invite a teammate', completed: false },
-  { id: 'integration', label: 'Connect integration', completed: false },
-];
-
-// Show progress, celebrate completion
-```
-
-### Activation Experiments
-- A/B test signup flow
-- Test different first actions
-- Try progressive vs. upfront onboarding
-- Experiment with email sequences
-```
-
-### Retention Strategies
-
-```markdown
-## Retention Framework
-
-### Engagement Loops
-1. **Trigger**: Notification, email, habit
-2. **Action**: User does something
-3. **Variable Reward**: Value received
-4. **Investment**: User adds data/effort
-
-### Habit Formation (Hook Model)
-- Daily use = strong habit
-- Weekly use = moderate habit
-- Monthly use = weak (need triggers)
-
-### Re-engagement Tactics
-1. **Email Sequences**
-   - Day 1: Welcome
-   - Day 3: Feature tip
-   - Day 7: Check-in
-   - Day 14: Re-engagement
-
-2. **In-App Triggers**
-   - New feature announcements
-   - Achievement notifications
-   - Social proof ("X users did Y")
-
-3. **Win-Back Campaigns**
-   - "We miss you" emails
-   - Special offers
-   - What's new since they left
-
-### Cohort Analysis
-Track retention by signup week:
-| Week | W0 | W1 | W2 | W4 | W8 | W12 |
-|------|-----|-----|-----|-----|-----|-----|
-| Cohort 1 | 100% | 45% | 35% | 28% | 22% | 18% |
-| Cohort 2 | 100% | 50% | 40% | 32% | 25% | 20% |
-```
-
-### Viral Loops
-
-```markdown
-## Types of Viral Loops
-
-### 1. Word of Mouth
-- NPS-driven referrals
-- Social sharing of success
-- Community building
-
-### 2. Invite/Collaboration
-- Product requires sharing
-- Better with more users
-- Example: Figma, Notion
-
-### 3. User-Generated Content
-- Public content creates exposure
-- "Made with [Product]"
-- Embeds and widgets
-
-### 4. Incentivized Referral
-- Dropbox: Free space for referrals
-- Two-sided rewards (referrer + referee)
-
-## Viral Coefficient Formula
-K = (invites per user) × (conversion rate)
-- K < 1: Growth slows without acquisition
-- K = 1: Self-sustaining
-- K > 1: Exponential growth (rare)
-
-## Referral Program Structure
-| Action | Referrer Gets | Referee Gets |
-|--------|---------------|--------------|
-| Signup | $10 credit | $10 credit |
-| Paid conversion | 1 month free | 20% off first |
-```
-
-### Growth Experiments
-
-```markdown
-## Experiment Framework
-
-### ICE Scoring
-- **Impact**: 1-10 (potential effect)
-- **Confidence**: 1-10 (certainty)
-- **Ease**: 1-10 (implementation effort)
-- **Score** = (I + C + E) / 3
-
-### Experiment Template
-```markdown
-## Hypothesis
-If we [change], then [metric] will [increase/decrease] by [amount]
-because [reason].
-
-## Metrics
-- Primary: [main metric]
-- Secondary: [supporting metrics]
-- Guardrail: [what shouldn't decrease]
-
-## Audience
-- % of users: [X%]
-- Duration: [Y days/weeks]
-
-## Results
-- Control: [X]
-- Variant: [Y]
-- Statistical significance: [yes/no]
-- Decision: [ship/iterate/kill]
-```
-
-### Common Growth Experiments
-1. Signup flow simplification
-2. Pricing page optimization
-3. Free trial length
-4. Onboarding sequence
-5. Feature gating
-6. CTA copy/design
-7. Social proof placement
-```
-
-## Growth Checklist
-
-- [ ] North Star metric defined
-- [ ] AARRR funnel mapped
-- [ ] Activation "aha moment" identified
-- [ ] Onboarding optimized
-- [ ] Retention tracked by cohort
-- [ ] Viral loops implemented
-- [ ] Referral program launched
-- [ ] Experiment pipeline active
-
-## Trigger Keywords
-growth, PLG, product-led, viral, retention, activation, churn, conversion, funnel, experiment, A/B test, onboarding, referral, engagement, habit

package/agents/index.js

@@ -1,140 +0,0 @@
-/**
- * Bootspring Agents Module
- * Programmatic access to agent data and invocation
- */
-
-const fs = require('fs');
-const path = require('path');
-
-// Agent registry from cli/agent.js
-const AGENTS = {
-  'database-expert': {
-    name: 'Database Expert',
-    expertise: ['SQL', 'Prisma', 'PostgreSQL', 'migrations', 'query optimization'],
-    description: 'Expert in database design, queries, and optimization'
-  },
-  'security-expert': {
-    name: 'Security Expert',
-    expertise: ['OWASP', 'authentication', 'authorization', 'encryption', 'vulnerabilities'],
-    description: 'Expert in application security and best practices'
-  },
-  'frontend-expert': {
-    name: 'Frontend Expert',
-    expertise: ['React', 'Next.js', 'Tailwind', 'components', 'state management'],
-    description: 'Expert in frontend development and UI'
-  },
-  'backend-expert': {
-    name: 'Backend Expert',
-    expertise: ['Node.js', 'APIs', 'server actions', 'middleware', 'serverless'],
-    description: 'Expert in backend development and server-side logic'
-  },
-  'api-expert': {
-    name: 'API Expert',
-    expertise: ['REST', 'GraphQL', 'tRPC', 'webhooks', 'API design'],
-    description: 'Expert in API design and integration'
-  },
-  'testing-expert': {
-    name: 'Testing Expert',
-    expertise: ['Vitest', 'Jest', 'Playwright', 'coverage', 'TDD'],
-    description: 'Expert in testing strategies and implementation'
-  },
-  'performance-expert': {
-    name: 'Performance Expert',
-    expertise: ['optimization', 'caching', 'profiling', 'Core Web Vitals', 'lazy loading'],
-    description: 'Expert in application performance optimization'
-  },
-  'devops-expert': {
-    name: 'DevOps Expert',
-    expertise: ['CI/CD', 'Docker', 'deployment', 'monitoring', 'infrastructure'],
-    description: 'Expert in DevOps practices and deployment'
-  },
-  'ui-ux-expert': {
-    name: 'UI/UX Expert',
-    expertise: ['design systems', 'accessibility', 'user experience', 'responsive design'],
-    description: 'Expert in UI/UX design and implementation'
-  },
-  'architecture-expert': {
-    name: 'Architecture Expert',
-    expertise: ['system design', 'patterns', 'scalability', 'microservices'],
-    description: 'Expert in software architecture and system design'
-  },
-  'code-review-expert': {
-    name: 'Code Review Expert',
-    expertise: ['code quality', 'best practices', 'refactoring', 'maintainability'],
-    description: 'Expert in code review and quality assessment'
-  },
-  'vercel-expert': {
-    name: 'Vercel Expert',
-    expertise: ['Vercel', 'serverless', 'edge functions', 'deployment', 'analytics'],
-    description: 'Expert in Vercel platform and deployment'
-  }
-};
-
-/**
- * Get all available agents
- */
-function getAgents() {
-  return AGENTS;
-}
-
-/**
- * Get a specific agent by name
- */
-function getAgent(name) {
-  return AGENTS[name] || null;
-}
-
-/**
- * List agent names
- */
-function listAgents() {
-  return Object.keys(AGENTS);
-}
-
-/**
- * Get agent context file path
- */
-function getAgentContextPath(name) {
-  const agentsDir = path.dirname(__dirname);
-  return path.join(agentsDir, 'agents', name, 'context.md');
-}
-
-/**
- * Load agent context file
- */
-function loadAgentContext(name) {
-  const contextPath = getAgentContextPath(name);
-  if (fs.existsSync(contextPath)) {
-    return fs.readFileSync(contextPath, 'utf-8');
-  }
-  return null;
-}
-
-/**
- * Find agents by expertise keyword
- */
-function findAgentsByExpertise(keyword) {
-  const matches = [];
-  const lowerKeyword = keyword.toLowerCase();
-
-  for (const [id, agent] of Object.entries(AGENTS)) {
-    const hasMatch = agent.expertise.some(exp =>
-      exp.toLowerCase().includes(lowerKeyword)
-    );
-    if (hasMatch) {
-      matches.push({ id, ...agent });
-    }
-  }
-
-  return matches;
-}
-
-module.exports = {
-  AGENTS,
-  getAgents,
-  getAgent,
-  listAgents,
-  getAgentContextPath,
-  loadAgentContext,
-  findAgentsByExpertise
-};

package/agents/investor-relations-expert/context.md

@@ -1,266 +0,0 @@
-# Investor Relations Expert Agent
-
-## Role
-Specialized in investor communications, board management, shareholder relations, and maintaining strong investor relationships post-funding.
-
-## Core Expertise
-
-### Investor Update Framework
-
-```markdown
-## Monthly Investor Update
-
-### Format: Brief, Scannable, Actionable
-
-**Subject Line**: [Company] [Month] Update - [Headline Metric]
-
----
-
-### Executive Summary (3 sentences max)
-- Key win
-- Key challenge
-- Focus for next month
-
-### Key Metrics Dashboard
-| Metric | Current | Last Month | Target |
-|--------|---------|------------|--------|
-| MRR | $X | $Y | $Z |
-| Growth | X% | Y% | 15% |
-| Customers | X | Y | Z |
-| Churn | X% | Y% | <5% |
-| Burn | $X | $Y | $Z |
-| Runway | X mo | Y mo | 18 mo |
-
-### Highlights 🎉
-1. **[Win Category]**: Description with impact
-2. **[Win Category]**: Description with impact
-3. **[Win Category]**: Description with impact
-
-### Challenges ⚠️
-1. **[Challenge]**: What happened, what we're doing
-2. **[Challenge]**: What happened, what we're doing
-
-### Asks 🙏
-Be specific and make it easy:
-- [ ] Intro to [Name] at [Company] for [reason]
-- [ ] Advice on [specific topic]
-- [ ] Hiring help: [role] - [job link]
-
-### What's Next
-- Priority 1 for next month
-- Priority 2
-- Priority 3
-
----
-*Reply to this email or book time: [Calendly link]*
-```
-
-### Board Meeting Best Practices
-
-```markdown
-## Board Meeting Playbook
-
-### Pre-Meeting (1 week before)
-- [ ] Send board deck 5 business days early
-- [ ] Highlight key decisions needed
-- [ ] Share pre-read materials
-- [ ] Confirm attendance
-
-### Board Deck Structure
-1. **Summary** (1 slide)
-   - Key metrics
-   - Highlights/lowlights
-   - Asks
-
-2. **Financials** (2-3 slides)
-   - P&L summary
-   - Cash position
-   - Forecast vs. actual
-
-3. **Product** (2 slides)
-   - Roadmap progress
-   - Key launches
-   - Customer feedback
-
-4. **Go-to-Market** (2 slides)
-   - Sales pipeline
-   - Marketing metrics
-   - Customer wins/losses
-
-5. **Team** (1 slide)
-   - Org changes
-   - Key hires
-   - Open roles
-
-6. **Discussion Topics** (2-3 slides)
-   - Strategic decisions
-   - Resource allocation
-   - Market changes
-
-7. **Appendix**
-   - Detailed metrics
-   - Competitor update
-   - Supporting data
-
-### During Meeting
-- Start with wins, build confidence
-- Address challenges directly
-- Drive to decisions
-- Document action items
-
-### Post-Meeting (within 48 hours)
-- [ ] Send meeting minutes
-- [ ] Confirm action items
-- [ ] Follow up on asks
-- [ ] Schedule next meeting
-```
-
-### Shareholder Communication
-
-```markdown
-## Communication Cadence
-
-| Audience | Frequency | Format |
-|----------|-----------|--------|
-| Lead investors | Weekly | Quick email/call |
-| Board members | Monthly | Formal update |
-| All investors | Quarterly | Newsletter |
-| Angels | Quarterly | Summary update |
-
-### Quarterly Letter Template
-```markdown
-## Q[X] 202X Investor Letter
-
-Dear Investors,
-
-### Quarter Highlights
-[2-3 paragraph narrative of the quarter]
-
-### By the Numbers
-- ARR: $X (up Y% YoY)
-- Customers: X (up Y)
-- Team: X employees
-
-### Product Milestones
-- Launched [feature 1]
-- Shipped [feature 2]
-- [X] customer requests completed
-
-### Team Updates
-- Hired [Name] as [Role]
-- Promoted [Name] to [Role]
-
-### Looking Ahead
-[1-2 paragraphs on next quarter focus]
-
-### How You Can Help
-- [Specific ask 1]
-- [Specific ask 2]
-
-Thank you for your continued support.
-
-[Founder Name]
-CEO, [Company]
-```
-
-### Annual Meeting Agenda
-1. Year in review (30 min)
-2. Financial deep dive (20 min)
-3. Strategy discussion (30 min)
-4. Q&A (20 min)
-5. Next year preview (20 min)
-```
-
-### Crisis Communication
-
-```markdown
-## Crisis Communication Framework
-
-### Principles
-1. **Speed**: Communicate quickly
-2. **Transparency**: Share what you know
-3. **Ownership**: Take responsibility
-4. **Action**: Show path forward
-
-### Communication Template
-```markdown
-Subject: [Company] Update - [Issue]
-
-Team,
-
-I'm writing to inform you about [situation].
-
-### What Happened
-[Clear, factual description]
-
-### Impact
-[Honest assessment of impact]
-
-### What We're Doing
-1. Immediate action
-2. Short-term fix
-3. Long-term prevention
-
-### Timeline
-- [Date]: [Milestone]
-- [Date]: [Milestone]
-
-### What We Need
-[Any asks of investors]
-
-I'll send another update by [date]. Please reach out if you have questions.
-
-[Name]
-```
-
-### When to Communicate
-- Major negative event: Within 24 hours
-- Customer loss: Same day
-- Key employee departure: Before announcement
-- Pivots: Before major changes
-- Runway concerns: With 6+ months remaining
-```
-
-### Relationship Building
-
-```markdown
-## Investor Relationship Tactics
-
-### Regular Touchpoints
-- Coffee/lunch quarterly
-- Invite to company events
-- Share wins (even small ones)
-- Ask for advice (makes them invested)
-
-### Leverage Their Network
-- Ask for specific intros
-- Use their portfolio network
-- Tap their functional expertise
-- Request recruiting help
-
-### Best Practices
-- Respond quickly (within 24 hours)
-- Never surprise with bad news
-- Give credit when they help
-- Remember their interests/portfolio
-
-### Building Trust
-- Deliver on commitments
-- Acknowledge mistakes
-- Be consistent in communication
-- Show learning and growth
-```
-
-## IR Checklist
-
-- [ ] Monthly update template ready
-- [ ] Board deck template created
-- [ ] Update cadence established
-- [ ] Board meeting rhythm set
-- [ ] Investor CRM maintained
-- [ ] Crisis plan documented
-- [ ] Key relationships mapped
-- [ ] Feedback loop active
-
-## Trigger Keywords
-investor relations, board meeting, investor update, shareholder, board deck, quarterly, communication, stakeholder, governance