@mrtrinhvn/ag-kit 1.0.11 → 1.1.1

package/.agent/skills/app-builder/project-detection.md

@@ -1,34 +0,0 @@
-# Project Type Detection
-
-> Analyze user requests to determine project type and template.
-
-## Keyword Matrix
-
-| Keywords | Project Type | Template |
-|----------|--------------|----------|
-| blog, post, article | Blog | astro-static |
-| e-commerce, product, cart, payment | E-commerce | nextjs-saas |
-| dashboard, panel, management | Admin Dashboard | nextjs-fullstack |
-| api, backend, service, rest | API Service | express-api |
-| python, fastapi, django | Python API | python-fastapi |
-| mobile, android, ios, react native | Mobile App (RN) | react-native-app |
-| flutter, dart | Mobile App (Flutter) | flutter-app |
-| portfolio, personal, cv | Portfolio | nextjs-static |
-| crm, customer, sales | CRM | nextjs-fullstack |
-| saas, subscription, stripe | SaaS | nextjs-saas |
-| landing, promotional, marketing | Landing Page | nextjs-static |
-| docs, documentation | Documentation | astro-static |
-| extension, plugin, chrome | Browser Extension | chrome-extension |
-| desktop, electron | Desktop App | electron-desktop |
-| cli, command line, terminal | CLI Tool | cli-tool |
-| monorepo, workspace | Monorepo | monorepo-turborepo |
-
-## Detection Process
-
-```
-1. Tokenize user request
-2. Extract keywords
-3. Determine project type
-4. Detect missing information → forward to conversation-manager
-5. Suggest tech stack
-```

package/.agent/skills/app-builder/scaffolding.md

@@ -1,118 +0,0 @@
-# Project Scaffolding
-
-> Directory structure and core files for new projects.
-
----
-
-## Next.js Full-Stack Structure (2025 Optimized)
-
-```
-project-name/
-├── src/
-│   ├── app/                        # Routes only (thin layer)
-│   │   ├── layout.tsx
-│   │   ├── page.tsx
-│   │   ├── globals.css
-│   │   ├── (auth)/                 # Route group - auth pages
-│   │   │   ├── login/page.tsx
-│   │   │   └── register/page.tsx
-│   │   ├── (dashboard)/            # Route group - dashboard layout
-│   │   │   ├── layout.tsx
-│   │   │   └── page.tsx
-│   │   └── api/
-│   │       └── [resource]/route.ts
-│   │
-│   ├── features/                   # Feature-based modules
-│   │   ├── auth/
-│   │   │   ├── components/
-│   │   │   ├── hooks/
-│   │   │   ├── actions.ts          # Server Actions
-│   │   │   ├── queries.ts          # Data fetching
-│   │   │   └── types.ts
-│   │   ├── products/
-│   │   │   ├── components/
-│   │   │   ├── actions.ts
-│   │   │   └── queries.ts
-│   │   └── cart/
-│   │       └── ...
-│   │
-│   ├── shared/                     # Shared utilities
-│   │   ├── components/ui/          # Reusable UI components
-│   │   ├── lib/                    # Utils, helpers
-│   │   └── hooks/                  # Global hooks
-│   │
-│   └── server/                     # Server-only code
-│       ├── db/                     # Database client (Prisma)
-│       ├── auth/                   # Auth config
-│       └── services/               # External API integrations
-│
-├── prisma/
-│   ├── schema.prisma
-│   ├── migrations/
-│   └── seed.ts
-│
-├── public/
-├── .env.example
-├── .env.local
-├── package.json
-├── tailwind.config.ts
-├── tsconfig.json
-└── README.md
-```
-
----
-
-## Structure Principles
-
-| Principle | Implementation |
-|-----------|----------------|
-| **Feature isolation** | Each feature in `features/` with its own components, hooks, actions |
-| **Server/Client separation** | Server-only code in `server/`, prevents accidental client imports |
-| **Thin routes** | `app/` only for routing, logic lives in `features/` |
-| **Route groups** | `(groupName)/` for layout sharing without URL impact |
-| **Shared code** | `shared/` for truly reusable UI and utilities |
-
----
-
-## Core Files
-
-| File | Purpose |
-|------|---------|
-| `package.json` | Dependencies |
-| `tsconfig.json` | TypeScript + path aliases (`@/features/*`) |
-| `tailwind.config.ts` | Tailwind config |
-| `.env.example` | Environment template |
-| `README.md` | Project documentation |
-| `.gitignore` | Git ignore rules |
-| `prisma/schema.prisma` | Database schema |
-
----
-
-## Path Aliases (tsconfig.json)
-
-```json
-{
-  "compilerOptions": {
-    "paths": {
-      "@/*": ["./src/*"],
-      "@/features/*": ["./src/features/*"],
-      "@/shared/*": ["./src/shared/*"],
-      "@/server/*": ["./src/server/*"]
-    }
-  }
-}
-```
-
----
-
-## When to Use What
-
-| Need | Location |
-|------|----------|
-| New page/route | `app/(group)/page.tsx` |
-| Feature component | `features/[name]/components/` |
-| Server action | `features/[name]/actions.ts` |
-| Data fetching | `features/[name]/queries.ts` |
-| Reusable button/input | `shared/components/ui/` |
-| Database query | `server/db/` |
-| External API call | `server/services/` |

package/.agent/skills/app-builder/tech-stack.md

@@ -1,40 +0,0 @@
-# Tech Stack Selection (2025)
-
-> Default and alternative technology choices for web applications.
-
-## Default Stack (Web App - 2025)
-
-```yaml
-Frontend:
-  framework: Next.js 16 (Stable)
-  language: TypeScript 5.7+
-  styling: Tailwind CSS v4
-  state: React 19 Actions / Server Components
-  bundler: Turbopack (Stable for Dev)
-
-Backend:
-  runtime: Node.js 23
-  framework: Next.js API Routes / Hono (for Edge)
-  validation: Zod / TypeBox
-
-Database:
-  primary: PostgreSQL
-  orm: Prisma / Drizzle
-  hosting: Supabase / Neon
-
-Auth:
-  provider: Auth.js (v5) / Clerk
-
-Monorepo:
-  tool: Turborepo 2.0
-```
-
-## Alternative Options
-
-| Need | Default | Alternative |
-|------|---------|-------------|
-| Real-time | - | Supabase Realtime, Socket.io |
-| File storage | - | Cloudinary, S3 |
-| Payment | Stripe | LemonSqueezy, Paddle |
-| Email | - | Resend, SendGrid |
-| Search | - | Algolia, Typesense |

package/.agent/skills/app-builder/templates/SKILL.md

@@ -1,39 +0,0 @@
----
-name: templates
-description: Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
-allowed-tools: Read, Glob, Grep
----
-
-# Project Templates
-
-> Quick-start templates for scaffolding new projects.
-
----
-
-## 🎯 Selective Reading Rule
-
-**Read ONLY the template matching user's project type!**
-
-| Template | Tech Stack | When to Use |
-|----------|------------|-------------|
-| [nextjs-fullstack](nextjs-fullstack/TEMPLATE.md) | Next.js + Prisma | Full-stack web app |
-| [nextjs-saas](nextjs-saas/TEMPLATE.md) | Next.js + Stripe | SaaS product |
-| [nextjs-static](nextjs-static/TEMPLATE.md) | Next.js + Framer | Landing page |
-| [express-api](express-api/TEMPLATE.md) | Express + JWT | REST API |
-| [python-fastapi](python-fastapi/TEMPLATE.md) | FastAPI | Python API |
-| [react-native-app](react-native-app/TEMPLATE.md) | Expo + Zustand | Mobile app |
-| [flutter-app](flutter-app/TEMPLATE.md) | Flutter + Riverpod | Cross-platform |
-| [electron-desktop](electron-desktop/TEMPLATE.md) | Electron + React | Desktop app |
-| [chrome-extension](chrome-extension/TEMPLATE.md) | Chrome MV3 | Browser extension |
-| [cli-tool](cli-tool/TEMPLATE.md) | Node.js + Commander | CLI app |
-| [monorepo-turborepo](monorepo-turborepo/TEMPLATE.md) | Turborepo + pnpm | Monorepo |
-| [astro-static](astro-static/TEMPLATE.md) | Astro + MDX | Blog / Docs |
-
----
-
-## Usage
-
-1. User says "create [type] app"
-2. Match to appropriate template
-3. Read ONLY that template's TEMPLATE.md
-4. Follow its tech stack and structure

package/.agent/skills/app-builder/templates/astro-static/TEMPLATE.md

@@ -1,76 +0,0 @@
----
-name: astro-static
-description: Astro static site template principles. Content-focused websites, blogs, documentation.
----
-
-# Astro Static Site Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Framework | Astro 4.x |
-| Content | MDX + Content Collections |
-| Styling | Tailwind CSS |
-| Integrations | Sitemap, RSS, SEO |
-| Output | Static/SSG |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── src/
-│   ├── components/      # .astro components
-│   ├── content/         # MDX content
-│   │   ├── blog/
-│   │   └── config.ts    # Collection schemas
-│   ├── layouts/         # Page layouts
-│   ├── pages/           # File-based routing
-│   └── styles/
-├── public/              # Static assets
-├── astro.config.mjs
-└── package.json
-```
-
----
-
-## Key Concepts
-
-| Concept | Description |
-|---------|-------------|
-| Content Collections | Type-safe content with Zod schemas |
-| Islands Architecture | Partial hydration for interactivity |
-| Zero JS by default | Static HTML unless needed |
-| MDX Support | Markdown with components |
-
----
-
-## Setup Steps
-
-1. `npm create astro@latest {{name}}`
-2. Add integrations: `npx astro add mdx tailwind sitemap`
-3. Configure `astro.config.mjs`
-4. Create content collections
-5. `npm run dev`
-
----
-
-## Deployment
-
-| Platform | Method |
-|----------|--------|
-| Vercel | Auto-detected |
-| Netlify | Auto-detected |
-| Cloudflare Pages | Auto-detected |
-| GitHub Pages | Build + deploy action |
-
----
-
-## Best Practices
-
-- Use Content Collections for type safety
-- Leverage static generation
-- Add islands only where needed
-- Optimize images with Astro Image

package/.agent/skills/app-builder/templates/chrome-extension/TEMPLATE.md

@@ -1,92 +0,0 @@
----
-name: chrome-extension
-description: Chrome Extension template principles. Manifest V3, React, TypeScript.
----
-
-# Chrome Extension Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Manifest | V3 |
-| UI | React 18 |
-| Language | TypeScript |
-| Styling | Tailwind CSS |
-| Bundler | Vite |
-| Storage | Chrome Storage API |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── src/
-│   ├── popup/           # Extension popup
-│   ├── options/         # Options page
-│   ├── background/      # Service worker
-│   ├── content/         # Content scripts
-│   ├── components/
-│   ├── hooks/
-│   └── lib/
-│       ├── storage.ts   # Chrome storage helpers
-│       └── messaging.ts # Message passing
-├── public/
-│   ├── icons/
-│   └── manifest.json
-└── package.json
-```
-
----
-
-## Manifest V3 Concepts
-
-| Component | Purpose |
-|-----------|---------|
-| Service Worker | Background processing |
-| Content Scripts | Page injection |
-| Popup | User interface |
-| Options Page | Settings |
-
----
-
-## Permissions
-
-| Permission | Use |
-|------------|-----|
-| storage | Save user data |
-| activeTab | Current tab access |
-| scripting | Inject scripts |
-| host_permissions | Site access |
-
----
-
-## Setup Steps
-
-1. `npm create vite {{name}} -- --template react-ts`
-2. Add Chrome types: `npm install -D @types/chrome`
-3. Configure Vite for multi-entry
-4. Create manifest.json
-5. `npm run dev` (watch mode)
-6. Load in Chrome: `chrome://extensions` → Load unpacked
-
----
-
-## Development Tips
-
-| Task | Method |
-|------|--------|
-| Debug Popup | Right-click icon → Inspect |
-| Debug Background | Extensions page → Service worker |
-| Debug Content | DevTools console on page |
-| Hot Reload | `npm run dev` with watch |
-
----
-
-## Best Practices
-
-- Use type-safe messaging
-- Wrap Chrome APIs in promises
-- Minimize permissions
-- Handle offline gracefully

package/.agent/skills/app-builder/templates/cli-tool/TEMPLATE.md

@@ -1,88 +0,0 @@
----
-name: cli-tool
-description: Node.js CLI tool template principles. Commander.js, interactive prompts.
----
-
-# CLI Tool Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Runtime | Node.js 20+ |
-| Language | TypeScript |
-| CLI Framework | Commander.js |
-| Prompts | Inquirer.js |
-| Output | chalk + ora |
-| Config | cosmiconfig |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── src/
-│   ├── index.ts         # Entry point
-│   ├── cli.ts           # CLI setup
-│   ├── commands/        # Command handlers
-│   ├── lib/
-│   │   ├── config.ts    # Config loader
-│   │   └── logger.ts    # Styled output
-│   └── types/
-├── bin/
-│   └── cli.js           # Executable
-└── package.json
-```
-
----
-
-## CLI Design Principles
-
-| Principle | Description |
-|-----------|-------------|
-| Subcommands | Group related actions |
-| Options | Flags with defaults |
-| Interactive | Prompts when needed |
-| Non-interactive | Support --yes flags |
-
----
-
-## Key Components
-
-| Component | Purpose |
-|-----------|---------|
-| Commander | Command parsing |
-| Inquirer | Interactive prompts |
-| Chalk | Colored output |
-| Ora | Spinners/loading |
-| Cosmiconfig | Config file discovery |
-
----
-
-## Setup Steps
-
-1. Create project directory
-2. `npm init -y`
-3. Install deps: `npm install commander @inquirer/prompts chalk ora cosmiconfig`
-4. Configure bin in package.json
-5. `npm link` for local testing
-
----
-
-## Publishing
-
-```bash
-npm login
-npm publish
-```
-
----
-
-## Best Practices
-
-- Provide helpful error messages
-- Support both interactive and non-interactive modes
-- Use consistent output styling
-- Validate inputs with Zod
-- Exit with proper codes (0 success, 1 error)

package/.agent/skills/app-builder/templates/electron-desktop/TEMPLATE.md

@@ -1,88 +0,0 @@
----
-name: electron-desktop
-description: Electron desktop app template principles. Cross-platform, React, TypeScript.
----
-
-# Electron Desktop App Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Framework | Electron 28+ |
-| UI | React 18 |
-| Language | TypeScript |
-| Styling | Tailwind CSS |
-| Bundler | Vite + electron-builder |
-| IPC | Type-safe communication |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── electron/
-│   ├── main.ts          # Main process
-│   ├── preload.ts       # Preload script
-│   └── ipc/             # IPC handlers
-├── src/
-│   ├── App.tsx
-│   ├── components/
-│   │   ├── TitleBar.tsx # Custom title bar
-│   │   └── ...
-│   └── hooks/
-├── public/
-└── package.json
-```
-
----
-
-## Process Model
-
-| Process | Role |
-|---------|------|
-| Main | Node.js, system access |
-| Renderer | Chromium, React UI |
-| Preload | Bridge, context isolation |
-
----
-
-## Key Concepts
-
-| Concept | Purpose |
-|---------|---------|
-| contextBridge | Safe API exposure |
-| ipcMain/ipcRenderer | Process communication |
-| nodeIntegration: false | Security |
-| contextIsolation: true | Security |
-
----
-
-## Setup Steps
-
-1. `npm create vite {{name}} -- --template react-ts`
-2. Install: `npm install -D electron electron-builder vite-plugin-electron`
-3. Create electron/ directory
-4. Configure main process
-5. `npm run electron:dev`
-
----
-
-## Build Targets
-
-| Platform | Output |
-|----------|--------|
-| Windows | NSIS, Portable |
-| macOS | DMG, ZIP |
-| Linux | AppImage, DEB |
-
----
-
-## Best Practices
-
-- Use preload script for main/renderer bridge
-- Type-safe IPC with typed handlers
-- Custom title bar for native feel
-- Handle window state (maximize, minimize)
-- Auto-updates with electron-updater

package/.agent/skills/app-builder/templates/express-api/TEMPLATE.md

@@ -1,83 +0,0 @@
----
-name: express-api
-description: Express.js REST API template principles. TypeScript, Prisma, JWT.
----
-
-# Express.js API Template
-
-## Tech Stack
-
-| Component | Technology |
-|-----------|------------|
-| Runtime | Node.js 20+ |
-| Framework | Express.js |
-| Language | TypeScript |
-| Database | PostgreSQL + Prisma |
-| Validation | Zod |
-| Auth | JWT + bcrypt |
-
----
-
-## Directory Structure
-
-```
-project-name/
-├── prisma/
-│   └── schema.prisma
-├── src/
-│   ├── app.ts           # Express setup
-│   ├── config/          # Environment
-│   ├── routes/          # Route handlers
-│   ├── controllers/     # Business logic
-│   ├── services/        # Data access
-│   ├── middleware/
-│   │   ├── auth.ts      # JWT verify
-│   │   ├── error.ts     # Error handler
-│   │   └── validate.ts  # Zod validation
-│   ├── schemas/         # Zod schemas
-│   └── utils/
-└── package.json
-```
-
----
-
-## Middleware Stack
-
-| Order | Middleware |
-|-------|------------|
-| 1 | helmet (security) |
-| 2 | cors |
-| 3 | morgan (logging) |
-| 4 | body parsing |
-| 5 | routes |
-| 6 | error handler |
-
----
-
-## API Response Format
-
-| Type | Structure |
-|------|-----------|
-| Success | `{ success: true, data: {...} }` |
-| Error | `{ error: "message", details: [...] }` |
-
----
-
-## Setup Steps
-
-1. Create project directory
-2. `npm init -y`
-3. Install deps: `npm install express prisma zod bcrypt jsonwebtoken`
-4. Configure Prisma
-5. `npm run db:push`
-6. `npm run dev`
-
----
-
-## Best Practices
-
-- Layer architecture (routes → controllers → services)
-- Validate all inputs with Zod
-- Centralized error handling
-- Environment-based config
-- Use Prisma for type-safe DB access