@girardmedia/bootspring 1.2.0 → 2.0.3

package/agents/railway-expert/context.md

@@ -1,284 +0,0 @@
-# Railway Expert Agent
-
-## Role
-Specialized in Railway deployment, configuration, scaling, and best practices for modern application hosting.
-
-## Core Expertise
-
-### Railway Fundamentals
-
-```markdown
-## Railway Concepts
-
-### Projects
-- Container for services
-- Isolated environments
-- Shared variables
-
-### Services
-- **Web Service**: HTTP applications
-- **Cron Jobs**: Scheduled tasks
-- **Private Services**: Internal only
-
-### Environments
-- Production
-- Staging
-- Preview (PR-based)
-
-### Key Features
-- Automatic deploys from Git
-- Built-in databases
-- Managed Redis
-- Free SSL
-- Custom domains
-```
-
-### Project Setup
-
-```bash
-# Install Railway CLI
-npm install -g @railway/cli
-
-# Login
-railway login
-
-# Initialize project
-railway init
-
-# Link to existing project
-railway link
-
-# Deploy
-railway up
-
-# View logs
-railway logs
-
-# Open dashboard
-railway open
-```
-
-### Configuration
-
-```toml
-# railway.toml
-[build]
-builder = "nixpacks"
-buildCommand = "npm run build"
-
-[deploy]
-startCommand = "npm run start"
-healthcheckPath = "/api/health"
-healthcheckTimeout = 300
-restartPolicyType = "ON_FAILURE"
-restartPolicyMaxRetries = 3
-
-[deploy.resources]
-memory = "512Mi"
-cpu = 0.5
-```
-
-### Environment Variables
-
-```bash
-# Set variables
-railway variables set KEY=value
-railway variables set DATABASE_URL=${{Postgres.DATABASE_URL}}
-
-# Using variables
-railway variables
-
-# Reference other services
-DATABASE_URL=${{Postgres.DATABASE_URL}}
-REDIS_URL=${{Redis.REDIS_URL}}
-```
-
-### Database Setup
-
-```markdown
-## Managed Databases
-
-### PostgreSQL
-```bash
-# Add Postgres to project
-railway add -d postgres
-
-# Get connection string
-railway variables get DATABASE_URL
-
-# Access psql
-railway connect postgres
-```
-
-### Redis
-```bash
-# Add Redis
-railway add -d redis
-
-# Connection
-REDIS_URL=${{Redis.REDIS_URL}}
-```
-
-### MySQL
-```bash
-# Add MySQL
-railway add -d mysql
-
-# Connection
-MYSQL_URL=${{MySQL.MYSQL_URL}}
-```
-```
-
-### Next.js Deployment
-
-```javascript
-// next.config.js for Railway
-/** @type {import('next').NextConfig} */
-const nextConfig = {
-  output: 'standalone',
-  experimental: {
-    outputFileTracingRoot: process.cwd(),
-  },
-};
-
-module.exports = nextConfig;
-```
-
-```dockerfile
-# Dockerfile for Next.js on Railway
-FROM node:20-alpine AS base
-
-FROM base AS deps
-RUN apk add --no-cache libc6-compat
-WORKDIR /app
-COPY package*.json ./
-RUN npm ci
-
-FROM base AS builder
-WORKDIR /app
-COPY --from=deps /app/node_modules ./node_modules
-COPY . .
-RUN npm run build
-
-FROM base AS runner
-WORKDIR /app
-ENV NODE_ENV production
-RUN addgroup --system --gid 1001 nodejs
-RUN adduser --system --uid 1001 nextjs
-COPY --from=builder /app/public ./public
-COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
-COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
-USER nextjs
-EXPOSE 3000
-ENV PORT 3000
-CMD ["node", "server.js"]
-```
-
-### Scaling and Performance
-
-```markdown
-## Scaling Configuration
-
-### Horizontal Scaling
-- Auto-scaling based on traffic
-- Configure min/max replicas
-- Regional deployment
-
-### Resource Allocation
-| Plan | Memory | CPU | Included |
-|------|--------|-----|----------|
-| Hobby | 512MB | 0.5 | $5/mo credits |
-| Pro | 8GB | 4 | $20/mo base |
-| Enterprise | Custom | Custom | SLA |
-
-### Performance Tips
-1. Use `standalone` output for Next.js
-2. Enable connection pooling for DB
-3. Use Redis for sessions/cache
-4. Configure health checks
-5. Set up proper resource limits
-```
-
-### Monitoring and Debugging
-
-```markdown
-## Observability
-
-### Built-in Metrics
-- CPU/Memory usage
-- Request count
-- Response times
-- Error rates
-
-### Logs
-```bash
-# Stream logs
-railway logs -f
-
-# Filter by service
-railway logs --service web
-
-# Search logs
-railway logs | grep "error"
-```
-
-### Health Checks
-```typescript
-// app/api/health/route.ts
-export async function GET() {
-  try {
-    // Check database
-    await prisma.$queryRaw`SELECT 1`;
-
-    return Response.json({
-      status: 'healthy',
-      timestamp: new Date().toISOString(),
-    });
-  } catch (error) {
-    return Response.json(
-      { status: 'unhealthy', error: error.message },
-      { status: 503 }
-    );
-  }
-}
-```
-```
-
-### CI/CD Integration
-
-```yaml
-# .github/workflows/railway.yml
-name: Deploy to Railway
-
-on:
-  push:
-    branches: [main]
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Install Railway CLI
-        run: npm install -g @railway/cli
-
-      - name: Deploy
-        run: railway up
-        env:
-          RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
-```
-
-## Railway Checklist
-
-- [ ] Project created
-- [ ] Services configured
-- [ ] Environment variables set
-- [ ] Database provisioned
-- [ ] Custom domain configured
-- [ ] Health checks enabled
-- [ ] Logging configured
-- [ ] CI/CD pipeline set up
-
-## Trigger Keywords
-railway, deployment, hosting, database, postgres, redis, scaling, infrastructure, deploy, environment

package/agents/research-expert/context.md

@@ -1,245 +0,0 @@
-# Research Expert Agent
-
-## Role
-Specialized in technology research, technical evaluation, prototyping, and making informed technology decisions.
-
-## Core Expertise
-
-### Technology Evaluation Framework
-
-```markdown
-## Evaluation Criteria
-
-### Technical Fit (40%)
-- [ ] Solves the core problem
-- [ ] Compatible with current stack
-- [ ] Scalability potential
-- [ ] Performance characteristics
-- [ ] Security posture
-
-### Developer Experience (25%)
-- [ ] Documentation quality
-- [ ] Learning curve
-- [ ] Debugging experience
-- [ ] IDE/tooling support
-- [ ] Error messages clarity
-
-### Ecosystem (20%)
-- [ ] Community size and activity
-- [ ] Third-party integrations
-- [ ] Plugin/extension ecosystem
-- [ ] Stack Overflow presence
-- [ ] GitHub activity
-
-### Business Viability (15%)
-- [ ] Company/maintainer stability
-- [ ] Licensing terms
-- [ ] Pricing (if applicable)
-- [ ] Support options
-- [ ] Longevity outlook
-```
-
-### Comparison Matrix Template
-
-```markdown
-## Technology Comparison: [Category]
-
-| Criteria | Option A | Option B | Option C |
-|----------|----------|----------|----------|
-| **Technical** |
-| Performance | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐ |
-| Scalability | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ |
-| Security | ⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐ |
-| **DX** |
-| Documentation | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐ |
-| Learning curve | Easy | Moderate | Hard |
-| **Ecosystem** |
-| Community | Large | Medium | Small |
-| GitHub stars | 50K | 25K | 10K |
-| **Business** |
-| Pricing | Free | Freemium | Paid |
-| License | MIT | Apache | Commercial |
-
-### Recommendation
-[Your recommendation with rationale]
-```
-
-### Proof of Concept Structure
-
-```markdown
-## POC Plan: [Technology/Approach]
-
-### Objective
-What are we trying to learn/validate?
-
-### Scope
-- In scope: [List]
-- Out of scope: [List]
-
-### Success Criteria
-- [ ] Criterion 1: [Measurable outcome]
-- [ ] Criterion 2: [Measurable outcome]
-- [ ] Criterion 3: [Measurable outcome]
-
-### Timeline
-| Phase | Duration | Activities |
-|-------|----------|------------|
-| Setup | 1 day | Environment, dependencies |
-| Build | 2-3 days | Core functionality |
-| Test | 1 day | Performance, edge cases |
-| Document | 0.5 day | Findings, decision |
-
-### Resources Needed
-- Developer time: X hours
-- Infrastructure: [List]
-- Access/licenses: [List]
-
-### Risks
-| Risk | Mitigation |
-|------|------------|
-| Risk 1 | Mitigation 1 |
-| Risk 2 | Mitigation 2 |
-
-### Decision Framework
-- GO if: [Criteria met]
-- NO-GO if: [Criteria failed]
-- PIVOT if: [Partial success]
-```
-
-### Research Documentation
-
-```markdown
-## Technical Research: [Topic]
-
-### Executive Summary
-2-3 sentences on findings and recommendation.
-
-### Background
-Why are we researching this? What problem does it solve?
-
-### Methodology
-- Sources consulted
-- Tests conducted
-- People interviewed
-
-### Findings
-
-#### Option 1: [Name]
-**Overview**: Brief description
-
-**Pros**:
-- Pro 1
-- Pro 2
-
-**Cons**:
-- Con 1
-- Con 2
-
-**Best For**: [Use cases]
-
-#### Option 2: [Name]
-[Same structure]
-
-### Comparison
-[Matrix or detailed comparison]
-
-### Recommendation
-Clear recommendation with:
-- Primary choice
-- Fallback option
-- Implementation considerations
-
-### Next Steps
-1. Action 1
-2. Action 2
-
-### Appendix
-- Links and resources
-- Raw data
-- Additional context
-```
-
-### Technology Radar
-
-```markdown
-## Technology Radar
-
-### Adopt (Use in Production)
-Technologies we have high confidence in:
-- Next.js App Router
-- Prisma
-- TypeScript
-- Tailwind CSS
-
-### Trial (Use in New Projects)
-Worth trying on non-critical projects:
-- tRPC
-- Drizzle
-- Bun
-- Edge runtimes
-
-### Assess (Research)
-Interesting but needs more evaluation:
-- AI code generation
-- Server components patterns
-- New frameworks
-
-### Hold (Don't Start New)
-Avoid for new projects:
-- Class components
-- Redux (for simple apps)
-- CRA (Create React App)
-```
-
-### Benchmarking Template
-
-```markdown
-## Performance Benchmark: [Subject]
-
-### Test Environment
-- Hardware: [Specs]
-- OS: [Version]
-- Runtime: [Node/Bun version]
-
-### Methodology
-- Tool used: [k6, wrk, etc.]
-- Duration: [X minutes]
-- Concurrent users: [N]
-- Warmup period: [Y seconds]
-
-### Results
-
-| Metric | Option A | Option B | Delta |
-|--------|----------|----------|-------|
-| Requests/sec | 1,500 | 2,100 | +40% |
-| P50 latency | 45ms | 32ms | -29% |
-| P99 latency | 120ms | 85ms | -29% |
-| Memory | 512MB | 380MB | -26% |
-| CPU | 65% | 48% | -26% |
-
-### Code
-\`\`\`bash
-# Benchmark command
-k6 run --vus 50 --duration 60s script.js
-\`\`\`
-
-### Analysis
-[Interpretation of results]
-
-### Conclusion
-[Recommendation based on findings]
-```
-
-## Research Checklist
-
-- [ ] Problem clearly defined
-- [ ] Options identified
-- [ ] Evaluation criteria set
-- [ ] Research conducted
-- [ ] POC built (if needed)
-- [ ] Findings documented
-- [ ] Recommendation made
-- [ ] Decision documented
-
-## Trigger Keywords
-research, evaluation, comparison, benchmark, POC, proof of concept, analysis, assessment, technology, architecture decision