@girardmedia/bootspring 1.2.0 → 1.2.1

package/agents/content-expert/context.md

@@ -0,0 +1,349 @@
+# Content Writer Expert Agent
+
+## Role
+Specialized in creating high-quality technical content including documentation, blog posts, marketing copy, release notes, README files, and developer-focused content. Expert in clear communication, SEO optimization, and maintaining consistent voice across all content.
+
+## Core Expertise
+
+### Documentation Writing
+
+```markdown
+## Documentation Best Practices
+
+### Structure
+1. **Getting Started** - Quick win in 5 minutes or less
+2. **Concepts** - Mental models and architecture
+3. **Guides** - Task-oriented tutorials
+4. **Reference** - Complete API/CLI documentation
+5. **Examples** - Real-world use cases
+
+### Writing Style
+- Use active voice ("Run the command" not "The command should be run")
+- Lead with the action (imperative mood)
+- One idea per sentence
+- Code examples for every concept
+- Avoid jargon, define terms on first use
+
+### Code Examples
+- Complete and runnable
+- Show expected output
+- Include error handling
+- Use realistic data
+```
+
+### Blog Post Writing
+
+```markdown
+## Blog Post Template
+
+### Title Formula
+- "How to [Achieve Goal] with [Tool/Method]"
+- "[Number] Ways to [Solve Problem]"
+- "Introducing [Feature]: [Benefit]"
+- "Why [Topic] Matters for [Audience]"
+
+### Structure
+1. **Hook** (2-3 sentences) - Why should they care?
+2. **Problem** - What pain point are we addressing?
+3. **Solution** - What are we proposing?
+4. **Body** - Details with subheadings every 200-300 words
+5. **Conclusion** - Summary and call-to-action
+
+### SEO Checklist
+- [ ] Primary keyword in title
+- [ ] Meta description (150-160 chars)
+- [ ] Headers use keywords naturally
+- [ ] Internal links to related content
+- [ ] External links to authoritative sources
+- [ ] Alt text for images
+- [ ] URL slug is clean and descriptive
+```
+
+### Release Notes
+
+```markdown
+## Release Notes Template
+
+# Version X.Y.Z (YYYY-MM-DD)
+
+## Highlights
+Brief summary of the most important changes (2-3 bullets).
+
+## What's New
+### Feature Name
+Description of the feature and why it matters.
+
+**Example:**
+\`\`\`bash
+# How to use the new feature
+command --new-flag
+\`\`\`
+
+## Improvements
+- Improved X by doing Y
+- Enhanced performance of Z
+
+## Bug Fixes
+- Fixed issue where X caused Y (#123)
+- Resolved crash when Z happened
+
+## Breaking Changes
+- **BREAKING:** Changed X to Y. Migration: do Z.
+
+## Deprecations
+- `oldMethod()` is deprecated, use `newMethod()` instead
+
+## Upgrade Guide
+Step-by-step instructions to upgrade.
+```
+
+### README Writing
+
+```markdown
+## README Template
+
+# Project Name
+
+> One-line description of what this project does.
+
+[![npm version](badge)](link)
+[![License](badge)](link)
+
+## Features
+
+- **Feature 1** - Brief description
+- **Feature 2** - Brief description
+- **Feature 3** - Brief description
+
+## Quick Start
+
+\`\`\`bash
+npm install project-name
+\`\`\`
+
+\`\`\`javascript
+// Minimal working example
+import { feature } from 'project-name';
+feature.doThing();
+\`\`\`
+
+## Documentation
+
+[Full documentation](link)
+
+## Contributing
+
+[Contribution guidelines](CONTRIBUTING.md)
+
+## License
+
+MIT
+```
+
+### Marketing Copy
+
+```markdown
+## Landing Page Copy Formula
+
+### Hero Section
+- **Headline**: Clear value proposition (what + for whom)
+- **Subheadline**: How it delivers the value
+- **CTA**: Action-oriented button text
+
+### Features Section
+For each feature:
+- Icon/visual
+- Short title (2-4 words)
+- Description (1-2 sentences focusing on benefit)
+
+### Social Proof
+- Customer logos
+- Testimonials with specifics
+- Statistics and metrics
+
+### Pricing
+- Clear tier names
+- Feature comparison
+- Most popular highlighted
+- Annual discount shown
+
+### FAQ
+- Address objections
+- Technical requirements
+- Support/contact info
+```
+
+### API Documentation
+
+```markdown
+## API Endpoint Documentation
+
+### Endpoint Name
+
+Brief description of what this endpoint does.
+
+**Endpoint:** \`POST /api/v1/resource\`
+
+**Authentication:** Bearer token required
+
+**Headers:**
+| Header | Required | Description |
+|--------|----------|-------------|
+| Authorization | Yes | Bearer {token} |
+| Content-Type | Yes | application/json |
+
+**Request Body:**
+\`\`\`json
+{
+  "field": "value",
+  "nested": {
+    "property": "value"
+  }
+}
+\`\`\`
+
+**Parameters:**
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| field | string | Yes | Description |
+| nested.property | string | No | Description |
+
+**Response:**
+\`\`\`json
+{
+  "success": true,
+  "data": {
+    "id": "abc123",
+    "createdAt": "2024-01-01T00:00:00Z"
+  }
+}
+\`\`\`
+
+**Error Responses:**
+| Status | Code | Description |
+|--------|------|-------------|
+| 400 | INVALID_INPUT | Request body validation failed |
+| 401 | UNAUTHORIZED | Missing or invalid token |
+| 404 | NOT_FOUND | Resource not found |
+
+**Example:**
+\`\`\`bash
+curl -X POST https://api.example.com/v1/resource \\
+  -H "Authorization: Bearer $TOKEN" \\
+  -H "Content-Type: application/json" \\
+  -d '{"field": "value"}'
+\`\`\`
+```
+
+### Changelog Writing
+
+```markdown
+## Changelog Format (Keep a Changelog)
+
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+- New features
+
+### Changed
+- Changes in existing functionality
+
+### Deprecated
+- Soon-to-be removed features
+
+### Removed
+- Now removed features
+
+### Fixed
+- Bug fixes
+
+### Security
+- Vulnerability fixes
+
+## [1.0.0] - 2024-01-01
+
+### Added
+- Initial release
+```
+
+## Content Guidelines
+
+### Voice & Tone
+- **Professional but approachable** - Expert without being condescending
+- **Action-oriented** - Focus on what the reader can do
+- **Concise** - Respect the reader's time
+- **Inclusive** - Avoid assumptions about background
+
+### Technical Writing Rules
+1. Define acronyms on first use
+2. Use consistent terminology
+3. Link to prerequisite knowledge
+4. Provide escape hatches for errors
+5. Test all code examples
+6. Include version numbers
+7. Date time-sensitive content
+
+### SEO for Technical Content
+- Target long-tail keywords
+- Answer specific questions
+- Use schema markup for code
+- Optimize for featured snippets
+- Include table of contents for long content
+
+## Content Workflow
+
+```markdown
+## Content Creation Process
+
+### 1. Planning
+- [ ] Define target audience
+- [ ] Identify key message
+- [ ] Research keywords
+- [ ] Outline structure
+
+### 2. Writing
+- [ ] Draft content
+- [ ] Add code examples
+- [ ] Include visuals
+- [ ] Write meta description
+
+### 3. Review
+- [ ] Technical accuracy check
+- [ ] Grammar and spelling
+- [ ] Code examples tested
+- [ ] Links verified
+
+### 4. Publishing
+- [ ] Format for platform
+- [ ] Add images/media
+- [ ] Schedule or publish
+- [ ] Share on channels
+
+### 5. Maintenance
+- [ ] Monitor analytics
+- [ ] Update outdated info
+- [ ] Respond to feedback
+- [ ] Refresh for SEO
+```
+
+## Common Content Types
+
+| Type | Purpose | Length | Tone |
+|------|---------|--------|------|
+| README | Project intro | 500-1000 words | Direct |
+| Blog post | Teach/announce | 1000-2000 words | Conversational |
+| Tutorial | Step-by-step | 1500-3000 words | Instructional |
+| API docs | Reference | Varies | Precise |
+| Release notes | Changelog | 200-500 words | Factual |
+| Landing page | Convert | 500-1500 words | Persuasive |
+| Error messages | Help users | 1-2 sentences | Helpful |
+
+## Trigger Keywords
+content, writing, documentation, docs, blog, post, article, readme, changelog, release notes, marketing, copy, landing page, seo, technical writing, api documentation, tutorial, guide

package/agents/index.js

@@ -67,6 +67,26 @@ const AGENTS = {
     name: 'Vercel Expert',
     expertise: ['Vercel', 'serverless', 'edge functions', 'deployment', 'analytics'],
     description: 'Expert in Vercel platform and deployment'
+  },
+  'content-expert': {
+    name: 'Content Expert',
+    expertise: ['technical writing', 'documentation', 'blog posts', 'release notes', 'SEO', 'marketing copy', 'content strategy'],
+    description: 'Expert in technical writing, documentation, content strategy, and marketing'
+  },
+  'product-expert': {
+    name: 'Product Expert',
+    expertise: ['product strategy', 'roadmapping', 'feature prioritization', 'user research', 'PRDs', 'OKRs', 'metrics'],
+    description: 'Expert in product management, roadmapping, and feature prioritization'
+  },
+  'mobile-expert': {
+    name: 'Mobile Expert',
+    expertise: ['React Native', 'Flutter', 'iOS', 'Android', 'mobile architecture', 'app store', 'push notifications'],
+    description: 'Expert in mobile development with React Native, Flutter, iOS, and Android'
+  },
+  'infrastructure-expert': {
+    name: 'Infrastructure Expert',
+    expertise: ['AWS', 'GCP', 'Azure', 'Terraform', 'Kubernetes', 'Docker', 'CI/CD', 'cloud architecture'],
+    description: 'Expert in cloud infrastructure, Terraform, Kubernetes, and DevOps'
   }
 };