@smicolon/ai-kit 0.0.1 → 0.1.1

package/packs/architect/commands/diagram-create.md

@@ -0,0 +1,300 @@
+---
+name: diagram-create
+description: Create system architecture diagrams using Eraser.io diagram-as-code
+---
+
+# System Diagram Creation
+
+You are an Eraser.io diagram-as-code specialist. Your task is to create professional system architecture diagrams using Eraser.io's DSL.
+
+## Core Requirements
+
+### Diagram Types Supported
+1. **Entity Relationship Diagrams (ERD)** - Database schemas
+2. **Flowcharts** - Process flows and decision trees
+3. **Cloud Architecture** - AWS, Azure, GCP infrastructure
+4. **Sequence Diagrams** - API interactions and workflows
+5. **BPMN** - Business process modeling
+
+## Eraser.io Syntax
+
+### Entity Relationship Diagram (ERD)
+```
+users [icon: user, color: blue] {
+  id uuid pk
+  email string unique
+  password_hash string
+  created_at timestamp
+  updated_at timestamp
+  is_deleted bool
+}
+
+products [icon: package, color: green] {
+  id uuid pk
+  name string
+  slug string unique
+  price decimal
+  stock int
+  created_by uuid fk
+  created_at timestamp
+  updated_at timestamp
+  is_deleted bool
+}
+
+orders [icon: shopping-cart, color: orange] {
+  id uuid pk
+  user_id uuid fk
+  total decimal
+  status string
+  created_at timestamp
+  updated_at timestamp
+}
+
+order_items [icon: list, color: orange] {
+  id uuid pk
+  order_id uuid fk
+  product_id uuid fk
+  quantity int
+  price decimal
+}
+
+// Relationships
+users.id < products.created_by
+users.id < orders.user_id
+orders.id < order_items.order_id
+products.id < order_items.product_id
+```
+
+### Cloud Architecture Diagram
+```
+// AWS E-Commerce Architecture
+
+// Networking
+vpc [icon: aws-vpc, color: blue] {
+  label: Production VPC
+  cidr: 10.0.0.0/16
+}
+
+public_subnet [icon: aws-subnet, color: lightblue] {
+  label: Public Subnet
+  cidr: 10.0.1.0/24
+}
+
+private_subnet [icon: aws-subnet, color: gray] {
+  label: Private Subnet
+  cidr: 10.0.2.0/24
+}
+
+// Load Balancing
+alb [icon: aws-elb, color: orange] {
+  label: Application Load Balancer
+}
+
+// Compute
+ecs_cluster [icon: aws-ecs, color: purple] {
+  label: ECS Cluster
+}
+
+api_service [icon: aws-ecs-service, color: purple] {
+  label: API Service
+  count: 3
+}
+
+// Database
+rds [icon: aws-rds, color: blue] {
+  label: PostgreSQL RDS
+  engine: postgres
+  instance: db.t3.medium
+}
+
+redis [icon: aws-elasticache, color: red] {
+  label: Redis Cache
+}
+
+// Storage
+s3 [icon: aws-s3, color: green] {
+  label: S3 Bucket
+  purpose: Static Assets
+}
+
+// Connections
+internet > alb
+alb > api_service
+api_service > rds
+api_service > redis
+api_service > s3
+
+// Grouping
+vpc {
+  public_subnet {
+    alb
+  }
+  private_subnet {
+    ecs_cluster {
+      api_service
+    }
+    rds
+    redis
+  }
+}
+```
+
+### Sequence Diagram
+```
+// User Authentication Flow
+
+title: User Login Sequence
+
+Client > API: POST /auth/login {email, password}
+API > Database: Query user by email
+Database > API: Return user data
+API > API: Validate password hash
+API > TokenService: Generate JWT
+TokenService > API: Return access & refresh tokens
+API > Database: Store refresh token
+API > Client: Return tokens + user data
+
+note over Client: Store tokens in secure storage
+
+Client > API: GET /profile (Authorization: Bearer token)
+API > TokenService: Validate JWT
+TokenService > API: Token valid
+API > Database: Fetch user profile
+Database > API: Return profile data
+API > Client: Return profile
+```
+
+### Flowchart
+```
+// E-Commerce Checkout Flow
+
+start: Start Checkout
+start > check_cart: Check Cart Items
+
+check_cart > cart_empty: Cart Empty?
+cart_empty > [Yes] > show_error: Show Error Message
+cart_empty > [No] > check_auth: User Authenticated?
+
+check_auth > [No] > login: Redirect to Login
+check_auth > [Yes] > shipping: Enter Shipping Info
+
+shipping > validate_address: Validate Address
+validate_address > address_invalid: Invalid Address?
+address_invalid > [Yes] > shipping
+address_invalid > [No] > payment: Enter Payment Info
+
+payment > process_payment: Process Payment
+process_payment > payment_failed: Payment Failed?
+payment_failed > [Yes] > payment
+payment_failed > [No] > create_order: Create Order
+
+create_order > send_confirmation: Send Email Confirmation
+send_confirmation > end: Show Success Page
+
+show_error > end
+login > check_auth
+```
+
+### BPMN Diagram
+```
+// Order Fulfillment Process
+
+start [shape: circle, label: Start]
+receive_order [shape: task, label: Receive Order]
+check_inventory [shape: gateway, label: Check Inventory]
+reserve_items [shape: task, label: Reserve Items]
+notify_warehouse [shape: task, label: Notify Warehouse]
+pick_items [shape: task, label: Pick Items]
+pack_order [shape: task, label: Pack Order]
+ship_order [shape: task, label: Ship Order]
+update_tracking [shape: task, label: Update Tracking]
+notify_customer [shape: task, label: Notify Customer]
+cancel_order [shape: task, label: Cancel Order]
+refund [shape: task, label: Process Refund]
+end [shape: circle, label: End]
+
+start > receive_order
+receive_order > check_inventory
+check_inventory > [In Stock] > reserve_items
+check_inventory > [Out of Stock] > cancel_order
+reserve_items > notify_warehouse
+notify_warehouse > pick_items
+pick_items > pack_order
+pack_order > ship_order
+ship_order > update_tracking
+update_tracking > notify_customer
+notify_customer > end
+cancel_order > refund
+refund > end
+```
+
+## Workflow
+
+1. **Understand Requirements**: Ask user:
+   - What system/process to diagram?
+   - What diagram type?
+   - Level of detail needed?
+   - Audience for the diagram?
+
+2. **Design Diagram**: Plan:
+   - Key entities/components
+   - Relationships/flows
+   - Grouping and hierarchy
+   - Colors and icons
+
+3. **Generate Code**: Create:
+   - Eraser.io DSL code
+   - Proper syntax and formatting
+   - Clear labels and descriptions
+
+4. **Provide Instructions**: Give:
+   - How to use the code
+   - Eraser.io URL
+   - Editing tips
+
+## Usage Instructions
+
+```bash
+# 1. Go to https://app.eraser.io/
+# 2. Create a new diagram
+# 3. Select "Diagram-as-Code" mode
+# 4. Paste the generated code
+# 5. The diagram will render automatically
+# 6. Customize colors, layout, and styling as needed
+```
+
+## Quality Checklist
+
+- [ ] Correct diagram type for use case
+- [ ] All entities/components labeled
+- [ ] Relationships clearly defined
+- [ ] Appropriate icons and colors
+- [ ] Proper grouping/hierarchy
+- [ ] Readable and well-organized
+- [ ] Includes title/description
+- [ ] Follows Eraser.io syntax
+- [ ] All required fields included
+
+## Examples by Use Case
+
+### Database Design
+Use: **ERD**
+When: Designing data models, showing relationships
+
+### System Architecture
+Use: **Cloud Architecture Diagram**
+When: Showing infrastructure, services, and connections
+
+### API Flows
+Use: **Sequence Diagram**
+When: Documenting API interactions, authentication flows
+
+### Business Processes
+Use: **Flowchart** or **BPMN**
+When: Documenting business logic, decision trees
+
+### User Flows
+Use: **Flowchart**
+When: Showing user journeys, conditional paths
+
+Now, ask the user what diagram they want to create!

package/packs/better-auth/.claude-plugin/plugin.json

@@ -0,0 +1,14 @@
+{
+  "name": "better-auth",
+  "version": "0.1.0",
+  "description": "Better Auth integration with MCP server for comprehensive authentication",
+  "author": {
+    "name": "Smicolon",
+    "email": "dev@smicolon.com",
+    "url": "https://github.com/smicolon"
+  },
+  "homepage": "https://github.com/smicolon/ai-kit",
+  "repository": "https://github.com/smicolon/ai-kit",
+  "license": "MIT",
+  "keywords": ["better-auth", "authentication", "auth", "mcp", "passkeys", "2fa", "social-login"]
+}

package/packs/better-auth/.mcp.json

@@ -0,0 +1,14 @@
+{
+  "mcpServers": {
+    "better-auth": {
+      "command": "npx",
+      "args": ["-y", "@nahmanmate/better-auth-mcp-server"],
+      "env": {
+        "BETTER_AUTH_PROJECT_ID": "${BETTER_AUTH_PROJECT_ID}",
+        "BETTER_AUTH_API_KEY": "${BETTER_AUTH_API_KEY}",
+        "BETTER_AUTH_ENV": "${BETTER_AUTH_ENV:-development}",
+        "LOG_LEVEL": "${LOG_LEVEL:-info}"
+      }
+    }
+  }
+}

package/packs/better-auth/CHANGELOG.md

@@ -0,0 +1,26 @@
+# Changelog
+
+All notable changes to the smi-better-auth plugin will be documented in this file.
+
+## [Unreleased]
+
+### Changed
+- Renamed from `smi-better-auth` to `better-auth` as part of ai-kit migration
+- Moved from `plugins/smi-better-auth/` to `packs/better-auth/`
+
+## [0.1.0] - 2025-01-02
+
+### Added
+- Initial release (experimental)
+- 1 agent: auth-architect
+- 2 commands: auth-setup, auth-provider-add
+- 2 skills:
+  - `better-auth-patterns` - Authentication patterns and client setup
+  - `auth-security` - Security best practices (rate limiting, CSRF, sessions)
+- Better Auth MCP server integration
+- Support for:
+  - Email/password authentication
+  - Social providers (Google, GitHub, Discord, Apple, Microsoft, etc.)
+  - Two-factor authentication (2FA)
+  - Passkeys/WebAuthn
+  - Session management

package/packs/better-auth/README.md

@@ -0,0 +1,125 @@
+# better-auth
+
+Better Auth integration with MCP server for comprehensive authentication.
+
+## Overview
+
+This plugin provides comprehensive authentication support using Better Auth, a framework-agnostic TypeScript authentication library. Includes MCP server integration for AI-assisted auth implementation.
+
+## Installation
+
+```bash
+/plugin install better-auth
+```
+
+## Features
+
+### Core Authentication
+- Email/password authentication
+- Session management
+- Password reset flows
+
+### Social Providers
+- Google, GitHub, Discord, etc.
+- OAuth 2.0 / OpenID Connect
+
+### Advanced Security
+- Two-factor authentication (2FA)
+- Passkeys / WebAuthn
+- Rate limiting
+
+### Enterprise
+- Multi-tenancy
+- Single Sign-On (SSO)
+- Organization management
+
+## MCP Server
+
+This plugin configures the official Better Auth MCP server for AI-assisted development.
+
+### Required Environment Variables
+```bash
+# Add to your environment
+BETTER_AUTH_SECRET=your-secret-key
+DATABASE_URL=your-database-url
+```
+
+### MCP Tools Available
+- Auth configuration generation
+- Provider setup assistance
+- Security best practices
+
+## Agents
+
+| Agent | Purpose |
+|-------|---------|
+| `auth-architect` | Design authentication architecture and flows |
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `/auth-setup` | Initialize Better Auth with config and optional pages |
+| `/auth-provider-add` | Add a new authentication provider |
+
+## Usage
+
+### Basic Setup
+```bash
+/auth-setup
+```
+
+Options:
+- `--with-pages` - Include login/register/forgot-password pages
+- `--providers google,github` - Pre-configure social providers
+- `--2fa` - Enable two-factor authentication
+- `--passkeys` - Enable passkey support
+
+### Add Provider
+```bash
+/auth-provider-add google
+/auth-provider-add github --scopes "user:email,read:org"
+```
+
+## Configuration Example
+
+```typescript
+// auth.ts
+import { betterAuth } from 'better-auth'
+
+export const auth = betterAuth({
+  database: {
+    provider: 'postgresql',
+    url: process.env.DATABASE_URL,
+  },
+  emailAndPassword: {
+    enabled: true,
+  },
+  socialProviders: {
+    google: {
+      clientId: process.env.GOOGLE_CLIENT_ID!,
+      clientSecret: process.env.GOOGLE_CLIENT_SECRET!,
+    },
+  },
+  plugins: [
+    twoFactor(),
+    passkey(),
+  ],
+})
+```
+
+## Integration with TanStack
+
+Works seamlessly with `tanstack-router`:
+
+```typescript
+// routes/__root.tsx
+import { auth } from '@/lib/auth'
+
+export const Route = createRootRoute({
+  beforeLoad: async () => {
+    const session = await auth.getSession()
+    return { session }
+  },
+})
+```