@maestro-ai/mcp-server 1.0.0 → 1.0.1

package/dist/content/content/skills/app-builder/templates/nextjs-saas/TEMPLATE.md

@@ -1,100 +0,0 @@
----
-name: nextjs-saas
-description: Next.js SaaS template principles. Auth, payments, email.
----
-
-# Next.js SaaS Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Framework | Next.js 14 (App Router) |
-| Auth | NextAuth.js v5 |
-| Payments | Stripe |
-| Database | PostgreSQL + Prisma |
-| Email | Resend |
-| UI | Tailwind (ASK USER: shadcn/Headless UI/Custom?) |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── prisma/
-├── src/
-│   ├── app/
-│   │   ├── (auth)/      # Login, register
-│   │   ├── (dashboard)/ # Protected routes
-│   │   ├── (marketing)/ # Landing, pricing
-│   │   └── api/
-│   │       ├── auth/[...nextauth]/
-│   │       └── webhooks/stripe/
-│   ├── components/
-│   │   ├── auth/
-│   │   ├── billing/
-│   │   └── dashboard/
-│   ├── lib/
-│   │   ├── auth.ts      # NextAuth config
-│   │   ├── stripe.ts    # Stripe client
-│   │   └── email.ts     # Resend client
-│   └── config/
-│       └── subscriptions.ts
-└── package.json
-```
-
----
-
-## SaaS Features
-
-| Feature | Implementation |
-|---------|---------------|
-| Auth | NextAuth + OAuth |
-| Subscriptions | Stripe Checkout |
-| Billing Portal | Stripe Portal |
-| Webhooks | Stripe events |
-| Email | Transactional via Resend |
-
----
-
-## Database Schema
-
-| Model | Fields |
-|-------|--------|
-| User | id, email, stripeCustomerId, subscriptionId |
-| Account | OAuth provider data |
-| Session | User sessions |
-
----
-
-## Environment Variables
-
-| Variable | Purpose |
-|----------|---------|
-| DATABASE_URL | Prisma |
-| NEXTAUTH_SECRET | Auth |
-| STRIPE_SECRET_KEY | Payments |
-| STRIPE_WEBHOOK_SECRET | Webhooks |
-| RESEND_API_KEY | Email |
-
----
-
-## Setup Steps
-
-1. `npx create-next-app {{name}} --typescript --tailwind --app`
-2. Install: `npm install next-auth @auth/prisma-adapter stripe resend`
-3. Setup Stripe products/prices
-4. Configure environment
-5. `npm run db:push`
-6. `npm run stripe:listen` (webhooks)
-7. `npm run dev`
-
----
-
-## Best Practices
-
-- Route groups for layout separation
-- Stripe webhooks for subscription sync
-- NextAuth with Prisma adapter
-- Email templates with React Email

package/dist/content/content/skills/app-builder/templates/nextjs-static/TEMPLATE.md

@@ -1,106 +0,0 @@
----
-name: nextjs-static
-description: Next.js static site template principles. Landing pages, portfolios, marketing.
----
-
-# Next.js Static Site Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Framework | Next.js 14 (Static Export) |
-| Language | TypeScript |
-| Styling | Tailwind CSS |
-| Animations | Framer Motion |
-| Icons | Lucide React |
-| SEO | Next SEO |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── src/
-│   ├── app/
-│   │   ├── layout.tsx
-│   │   ├── page.tsx      # Landing
-│   │   ├── about/
-│   │   ├── contact/
-│   │   └── blog/
-│   ├── components/
-│   │   ├── layout/       # Header, Footer
-│   │   ├── sections/     # Hero, Features, CTA
-│   │   └── ui/
-│   └── lib/
-├── content/              # Markdown content
-├── public/
-└── next.config.js
-```
-
----
-
-## Static Export Config
-
-```javascript
-// next.config.js
-const nextConfig = {
-  output: 'export',
-  images: { unoptimized: true },
-  trailingSlash: true,
-};
-```
-
----
-
-## Landing Page Sections
-
-| Section | Purpose |
-|---------|---------|
-| Hero | Main headline, CTA |
-| Features | Product benefits |
-| Testimonials | Social proof |
-| Pricing | Plans |
-| CTA | Final conversion |
-
----
-
-## Animation Patterns
-
-| Pattern | Use |
-|---------|-----|
-| Fade up | Content entry |
-| Stagger | List items |
-| Scroll reveal | On viewport |
-| Hover | Interactive feedback |
-
----
-
-## Setup Steps
-
-1. `npx create-next-app {{name}} --typescript --tailwind --app`
-2. Install: `npm install framer-motion lucide-react next-seo`
-3. Configure static export
-4. Create sections
-5. `npm run dev`
-
----
-
-## Deployment
-
-| Platform | Method |
-|----------|--------|
-| Vercel | Auto |
-| Netlify | Auto |
-| GitHub Pages | gh-pages branch |
-| Any host | Upload `out` folder |
-
----
-
-## Best Practices
-
-- Static export for maximum performance
-- Framer Motion for premium animations
-- Responsive mobile-first design
-- SEO metadata on every page

package/dist/content/content/skills/app-builder/templates/nuxt-app/TEMPLATE.md

@@ -1,101 +0,0 @@
----
-name: nuxt-app
-description: Nuxt 3 full-stack template. Vue 3, Pinia, Tailwind, Prisma.
----
-
-# Nuxt 3 Full-Stack Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Framework | Nuxt 3 |
-| Language | TypeScript |
-| UI | Vue 3 (Composition API) |
-| State | Pinia |
-| Database | PostgreSQL + Prisma |
-| Styling | Tailwind CSS |
-| Validation | Zod |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── prisma/
-│   └── schema.prisma
-├── server/
-│   ├── api/
-│   │   └── [resource]/
-│   │       └── index.ts
-│   └── utils/
-│       └── db.ts         # Prisma client
-├── composables/
-│   └── useAuth.ts
-├── stores/
-│   └── user.ts           # Pinia store
-├── components/
-│   └── ui/
-├── pages/
-│   ├── index.vue
-│   └── [...slug].vue
-├── layouts/
-│   └── default.vue
-├── assets/
-│   └── css/
-│       └── main.css
-├── .env.example
-├── nuxt.config.ts
-└── package.json
-```
-
----
-
-## Key Concepts
-
-| Concept | Description |
-|---------|-------------|
-| Auto-imports | Components, composables, utils |
-| File-based routing | pages/ → routes |
-| Server Routes | server/api/ → API endpoints |
-| Composables | Reusable reactive logic |
-| Pinia | State management |
-
----
-
-## Environment Variables
-
-| Variable | Purpose |
-|----------|---------|
-| DATABASE_URL | Prisma connection |
-| NUXT_PUBLIC_APP_URL | Public URL |
-
----
-
-## Setup Steps
-
-1. `npx nuxi@latest init {{name}}`
-2. `cd {{name}}`
-3. `npm install @pinia/nuxt @prisma/client prisma zod`
-4. `npm install -D @nuxtjs/tailwindcss`
-5. Add modules to `nuxt.config.ts`:
-   ```ts
-   modules: ['@pinia/nuxt', '@nuxtjs/tailwindcss']
-   ```
-6. `npx prisma init`
-7. Configure schema
-8. `npx prisma db push`
-9. `npm run dev`
-
----
-
-## Best Practices
-
-- Use `<script setup>` for components
-- Composables for reusable logic
-- Pinia stores in `stores/` folder
-- Server routes for API logic
-- Auto-import for clean code
-- TypeScript for type safety
-- See `@[skills/vue-expert]` for Vue patterns

package/dist/content/content/skills/app-builder/templates/python-fastapi/TEMPLATE.md

@@ -1,83 +0,0 @@
----
-name: python-fastapi
-description: FastAPI REST API template principles. SQLAlchemy, Pydantic, Alembic.
----
-
-# FastAPI API Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Framework | FastAPI |
-| Language | Python 3.11+ |
-| ORM | SQLAlchemy 2.0 |
-| Validation | Pydantic v2 |
-| Migrations | Alembic |
-| Auth | JWT + passlib |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── alembic/             # Migrations
-├── app/
-│   ├── main.py          # FastAPI app
-│   ├── config.py        # Settings
-│   ├── database.py      # DB connection
-│   ├── models/          # SQLAlchemy models
-│   ├── schemas/         # Pydantic schemas
-│   ├── routers/         # API routes
-│   ├── services/        # Business logic
-│   ├── dependencies/    # DI
-│   └── utils/
-├── tests/
-├── .env.example
-└── requirements.txt
-```
-
----
-
-## Key Concepts
-
-| Concept | Description |
-|---------|-------------|
-| Async | async/await throughout |
-| Dependency Injection | FastAPI Depends |
-| Pydantic v2 | Validation + serialization |
-| SQLAlchemy 2.0 | Async sessions |
-
----
-
-## API Structure
-
-| Layer | Responsibility |
-|-------|---------------|
-| Routers | HTTP handling |
-| Dependencies | Auth, validation |
-| Services | Business logic |
-| Models | Database entities |
-| Schemas | Request/response |
-
----
-
-## Setup Steps
-
-1. `python -m venv venv`
-2. `source venv/bin/activate`
-3. `pip install fastapi uvicorn sqlalchemy alembic pydantic`
-4. Create `.env`
-5. `alembic upgrade head`
-6. `uvicorn app.main:app --reload`
-
----
-
-## Best Practices
-
-- Use async everywhere
-- Pydantic v2 for validation
-- SQLAlchemy 2.0 async sessions
-- Alembic for migrations
-- pytest-asyncio for tests

package/dist/content/content/skills/app-builder/templates/react-native-app/TEMPLATE.md

@@ -1,93 +0,0 @@
----
-name: react-native-app
-description: React Native mobile app template principles. Expo, TypeScript, navigation.
----
-
-# React Native App Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Framework | React Native + Expo |
-| Language | TypeScript |
-| Navigation | Expo Router |
-| State | Zustand + React Query |
-| Styling | NativeWind |
-| Testing | Jest + RNTL |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── app/                 # Expo Router (file-based)
-│   ├── _layout.tsx      # Root layout
-│   ├── index.tsx        # Home
-│   ├── (tabs)/          # Tab navigation
-│   └── [id].tsx         # Dynamic route
-├── components/
-│   ├── ui/              # Reusable
-│   └── features/
-├── hooks/
-├── lib/
-│   ├── api.ts
-│   └── storage.ts
-├── store/
-├── constants/
-└── app.json
-```
-
----
-
-## Navigation Patterns
-
-| Pattern | Use |
-|---------|-----|
-| Stack | Page hierarchy |
-| Tabs | Bottom navigation |
-| Drawer | Side menu |
-| Modal | Overlay screens |
-
----
-
-## State Management
-
-| Type | Tool |
-|------|------|
-| Local | Zustand |
-| Server | React Query |
-| Forms | React Hook Form |
-| Storage | Expo SecureStore |
-
----
-
-## Key Packages
-
-| Package | Purpose |
-|---------|---------|
-| expo-router | File-based routing |
-| zustand | Local state |
-| @tanstack/react-query | Server state |
-| nativewind | Tailwind styling |
-| expo-secure-store | Secure storage |
-
----
-
-## Setup Steps
-
-1. `npx create-expo-app {{name}} -t expo-template-blank-typescript`
-2. `npx expo install expo-router react-native-safe-area-context`
-3. Install state: `npm install zustand @tanstack/react-query`
-4. `npx expo start`
-
----
-
-## Best Practices
-
-- Expo Router for navigation
-- Zustand for local, React Query for server state
-- NativeWind for consistent styling
-- Expo SecureStore for tokens
-- Test on both iOS and Android

package/dist/content/content/skills/architecture/SKILL.md

@@ -1,55 +0,0 @@
----
-name: architecture
-description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
-allowed-tools: Read, Glob, Grep
----
-
-# Architecture Decision Framework
-
-> "Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
-
-## 🎯 Selective Reading Rule
-
-**Read ONLY files relevant to the request!** Check the content map, find what you need.
-
-| File | Description | When to Read |
-|------|-------------|--------------|
-| `context-discovery.md` | Questions to ask, project classification | Starting architecture design |
-| `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions |
-| `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns |
-| `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations |
-| `patterns-reference.md` | Quick lookup for patterns | Pattern comparison |
-
----
-
-## 🔗 Related Skills
-
-| Skill | Use For |
-|-------|---------|
-| `@[skills/database-design]` | Database schema design |
-| `@[skills/api-patterns]` | API design patterns |
-| `@[skills/deployment-procedures]` | Deployment architecture |
-
----
-
-## Core Principle
-
-**"Simplicity is the ultimate sophistication."**
-
-- Start simple
-- Add complexity ONLY when proven necessary
-- You can always add patterns later
-- Removing complexity is MUCH harder than adding it
-
----
-
-## Validation Checklist
-
-Before finalizing architecture:
-
-- [ ] Requirements clearly understood
-- [ ] Constraints identified
-- [ ] Each decision has trade-off analysis
-- [ ] Simpler alternatives considered
-- [ ] ADRs written for significant decisions
-- [ ] Team expertise matches chosen patterns

package/dist/content/content/skills/architecture/context-discovery.md

@@ -1,43 +0,0 @@
-# Context Discovery
-
-> Before suggesting any architecture, gather context.
-
-## Question Hierarchy (Ask User FIRST)
-
-1. **Scale**
-   - How many users? (10, 1K, 100K, 1M+)
-   - Data volume? (MB, GB, TB)
-   - Transaction rate? (per second/minute)
-
-2. **Team**
-   - Solo developer or team?
-   - Team size and expertise?
-   - Distributed or co-located?
-
-3. **Timeline**
-   - MVP/Prototype or long-term product?
-   - Time to market pressure?
-
-4. **Domain**
-   - CRUD-heavy or business logic complex?
-   - Real-time requirements?
-   - Compliance/regulations?
-
-5. **Constraints**
-   - Budget limitations?
-   - Legacy systems to integrate?
-   - Technology stack preferences?
-
-## Project Classification Matrix
-
-```
-                    MVP              SaaS           Enterprise
-┌─────────────────────────────────────────────────────────────┐
-│ Scale        │ <1K           │ 1K-100K      │ 100K+        │
-│ Team         │ Solo          │ 2-10         │ 10+          │
-│ Timeline     │ Fast (weeks)  │ Medium (months)│ Long (years)│
-│ Architecture │ Simple        │ Modular      │ Distributed  │
-│ Patterns     │ Minimal       │ Selective    │ Comprehensive│
-│ Example      │ Next.js API   │ NestJS       │ Microservices│
-└─────────────────────────────────────────────────────────────┘
-```

package/dist/content/content/skills/architecture/examples.md

@@ -1,94 +0,0 @@
-# Architecture Examples
-
-> Real-world architecture decisions by project type.
-
----
-
-## Example 1: MVP E-commerce (Solo Developer)
-
-```yaml
-Requirements:
-  - <1000 users initially
-  - Solo developer
-  - Fast to market (8 weeks)
-  - Budget-conscious
-
-Architecture Decisions:
-  App Structure: Monolith (simpler for solo)
-  Framework: Next.js (full-stack, fast)
-  Data Layer: Prisma direct (no over-abstraction)
-  Authentication: JWT (simpler than OAuth)
-  Payment: Stripe (hosted solution)
-  Database: PostgreSQL (ACID for orders)
-
-Trade-offs Accepted:
-  - Monolith → Can't scale independently (team doesn't justify it)
-  - No Repository → Less testable (simple CRUD doesn't need it)
-  - JWT → No social login initially (can add later)
-
-Future Migration Path:
-  - Users > 10K → Extract payment service
-  - Team > 3 → Add Repository pattern
-  - Social login requested → Add OAuth
-```
-
----
-
-## Example 2: SaaS Product (5-10 Developers)
-
-```yaml
-Requirements:
-  - 1K-100K users
-  - 5-10 developers
-  - Long-term (12+ months)
-  - Multiple domains (billing, users, core)
-
-Architecture Decisions:
-  App Structure: Modular Monolith (team size optimal)
-  Framework: NestJS (modular by design)
-  Data Layer: Repository pattern (testing, flexibility)
-  Domain Model: Partial DDD (rich entities)
-  Authentication: OAuth + JWT
-  Caching: Redis
-  Database: PostgreSQL
-
-Trade-offs Accepted:
-  - Modular Monolith → Some module coupling (microservices not justified)
-  - Partial DDD → No full aggregates (no domain experts)
-  - RabbitMQ later → Initial synchronous (add when proven needed)
-
-Migration Path:
-  - Team > 10 → Consider microservices
-  - Domains conflict → Extract bounded contexts
-  - Read performance issues → Add CQRS
-```
-
----
-
-## Example 3: Enterprise (100K+ Users)
-
-```yaml
-Requirements:
-  - 100K+ users
-  - 10+ developers
-  - Multiple business domains
-  - Different scaling needs
-  - 24/7 availability
-
-Architecture Decisions:
-  App Structure: Microservices (independent scale)
-  API Gateway: Kong/AWS API GW
-  Domain Model: Full DDD
-  Consistency: Event-driven (eventual OK)
-  Message Bus: Kafka
-  Authentication: OAuth + SAML (enterprise SSO)
-  Database: Polyglot (right tool per job)
-  CQRS: Selected services
-
-Operational Requirements:
-  - Service mesh (Istio/Linkerd)
-  - Distributed tracing (Jaeger/Tempo)
-  - Centralized logging (ELK/Loki)
-  - Circuit breakers (Resilience4j)
-  - Kubernetes/Helm
-```