multimodel-dev-os 0.3.0 → 0.5.0

package/examples/nextjs-saas/.ai/config.yaml

@@ -1,4 +1,7 @@
-version: "0.1"
-project:
-  name: "nextjs-saas-starter"
-  mode: "standard"
+adapters:
+  cursor: true
+  claude: true
+  vscode: true
+mode: standard
+orchestrator:
+  mode: sequential

package/examples/nextjs-saas/.ai/context/architecture.md

@@ -0,0 +1,8 @@
+# Next.js SaaS — Architecture Map
+
+## Directory Boundaries
+- `/app` — Route groups, API routes, and Server Actions controllers.
+- `/components` — React UI components (Tailwind classes ordered).
+- `/lib` — Prisma database Client singleton, helper utilities.
+- `/prisma` — Postgres SQL schemas definitions, migrations files.
+- `/tests` — Unit tests using vitest or Jest.

package/examples/nextjs-saas/.ai/context/context-budget.md

@@ -0,0 +1,4 @@
+# Next.js SaaS — Context Budget
+
+- Keep total context files under **12,000 tokens** per prompt.
+- Never pass large dependencies directories like `node_modules` or `.next` artifacts into model prompts.

package/examples/nextjs-saas/.ai/context/model-map.md

@@ -0,0 +1,4 @@
+# Next.js SaaS — Model Map
+
+- **Claude / Antigravity:** Best for designing database schemas modifications, Next.js Server Actions layouts, and Stripe integrations routing.
+- **Cursor / Codex:** Ideal for refactoring react hooks, compiling component styling, and implementing unit tests.

package/examples/nextjs-saas/.ai/context/project-brief.md

@@ -0,0 +1,5 @@
+# Next.js SaaS — Project Brief
+
+This project is a high-performance, TypeScript-based SaaS platform boilerplate that provides secure database persistence, stripe-based subscription tiers, and standard authentication modules. 
+
+The goal is to enable AI coding tools to safely construct, refine, and deploy features under strict TypeScript constraints.

package/examples/nextjs-saas/.ai/skills/nextjs-action-build.md

@@ -0,0 +1,16 @@
+# Skill: React Server Actions secure implementation
+
+Use this skill when implementing a secure React Server Action in Next.js:
+
+1. **State Isolation:** Ensure actions include `"use server"` at the top of the file or module.
+2. **Parameters validation:** Validate all input parameters via Zod schema parsers.
+3. **Connection safety:** Ensure Prisma queries inside the Action execute within try-catch blocks:
+   ```typescript
+   try {
+     const data = await prisma.user.update({...});
+     return { success: true, data };
+   } catch (e) {
+     return { success: false, error: e.message };
+   }
+   ```
+4. **No secret exposure:** Never return raw sensitive fields (like password hashes or API private keys) to the UI client layer.

package/examples/nextjs-saas/AGENTS.md

@@ -1,8 +1,8 @@
 # Next.js SaaS — Agent Instructions
 
 project: nextjs-saas-starter
-stack: Next.js 14 (App Router), TypeScript, Tailwind CSS, Prisma, PostgreSQL, Stripe
-description: Subscription-based software-as-a-service application template
+stack: Next.js 14 (App Router), React 18, TypeScript, Tailwind CSS, Prisma ORM, Stripe, PostgreSQL
+description: Subscription-based SaaS boilerplate with checkout modules and database triggers.
 
 ## Build Commands
 ```
@@ -11,3 +11,9 @@ build: npm run build
 test:  npm run test
 lint:  npm run lint
 ```
+
+## Coding Conventions
+- **Language:** TypeScript (strict mode enabled).
+- **Framework:** Next.js App Router. Enforce Server Components by default; add `"use client"` only for files requiring state, effects, or user event handlers.
+- **Data Access:** Enforce Prisma Client operations inside Server Actions or Route Handlers; keep connection pools under limits (e.g. `npx prisma db push`).
+- **Styling:** Vanilla CSS modules or Tailwind CSS utilities classes. Order Tailwind classes systematically (layout first, then spacing, then typography).

package/examples/nextjs-saas/MEMORY.md

@@ -1,5 +1,8 @@
-# Next.js SaaS — Memory
+# Next.js SaaS — Project Memory
 
-## Architecture Decisions
-- Decided to use Next-Auth with JWT session strategy.
-- Stripe Webhook events are processed asynchronously in route handlers.
+## Architectural Decisions
+- **React Server Actions:** Adopted Server Actions for form submissions and mutation endpoints. Kept Route Handlers only for webhooks (like Stripe Webhook events).
+- **Prisma Connection Pooling:** Instantiated PrismaClient as a global singleton on development to prevent socket fatigue on hot-reloading.
+
+## Active Conventions
+- Always wrap database actions in standard try-catch blocks returning custom objects `{ success: boolean, data?: any, error?: string }` to simplify frontend feedback.

package/examples/nextjs-saas/TASKS.md

@@ -0,0 +1,12 @@
+# Next.js SaaS — Starter Tasks
+
+- [ ] Core Setup & Auth Integration
+  - [ ] Configure Prisma schema and run local DB migrations
+  - [ ] Connect NextAuth/Auth0 provider credentials inside `.env`
+- [ ] Subscription Flows & Webhooks
+  - [ ] Set up Stripe product prices and API keys
+  - [ ] Implement secure order checkout Server Action
+  - [ ] Write secure endpoint under `/api/webhook/stripe` to handle billing updates
+- [ ] Quality Assurance
+  - [ ] Run full build check `npm run build`
+  - [ ] Audit Lighthouse core web vitals parameters on landing pages

package/examples/seo-landing-page/.ai/context/architecture.md

@@ -0,0 +1,12 @@
+# Architecture Map
+
+```mermaid
+graph TD
+  Markdown[Content Files] --> Astro[Astro Engine]
+  Components[React/Astro Components] --> Astro
+  Astro --> Static[Static Assets: HTML, JS, CSS]
+  Static --> Purge[PurgeCSS Optimization]
+  Purge --> CDN[Edge CDN Distribution]
+```
+
+Static sites are distributed strictly through static hosting with zero server overhead.

package/examples/seo-landing-page/.ai/context/context-budget.md

@@ -0,0 +1,5 @@
+# SEO Landing Page — Context Budget
+
+- Keep total context files under **8,000 tokens** per prompt.
+- Never pass large dependencies directories like `node_modules` or `.astro` folders.
+- Avoid passing media assets (images, videos) into text-only models.

package/examples/seo-landing-page/.ai/context/model-map.md

@@ -0,0 +1,7 @@
+# Model Map
+
+Define LLM task allocations for the SEO Landing Page context:
+
+- **Coding & Implementation:** Gemini 3.5 Pro or Claude 3.5 Sonnet for Astro component templates.
+- **Refactoring & Styling:** Gemini 3.5 Flash for rapid CSS class styling.
+- **SEO Optimization & Content Auditing:** Claude 3.5 Sonnet for structured schema compliance.

package/examples/seo-landing-page/.ai/context/project-brief.md

@@ -0,0 +1,6 @@
+# Project Brief
+
+This project acts as an ultra-fast static landing page optimized for Astro, targeting high Core Web Vitals and structured JSON-LD SEO markup.
+- Core Web Vitals target: 100/100 on Mobile and Desktop.
+- Native CSS/purge pipelines configured.
+- Structured content layouts for perfect semantic indexing.

package/examples/seo-landing-page/.ai/skills/seo-audit.md

@@ -0,0 +1,21 @@
+# Skill: Google Lighthouse optimization
+
+Use this skill when auditing and optimizing a static landing page:
+
+1. **Meta Descriptions Verification:** Every page layout must contain:
+   ```html
+   <meta name="description" content="Precise SEO description (under 160 characters)" />
+   ```
+2. **Alt Tags Check:** Ensure every `<img>` tag has a valid, descriptively non-empty `alt` string.
+3. **Structured Schemas:** Embed JSON-LD maps:
+   ```html
+   <script type="application/ld+json">
+   {
+     "@context": "https://schema.org",
+     "@type": "WebSite",
+     "name": "Custom Profile",
+     "url": "https://example.com"
+   }
+   </script>
+   ```
+4. **Compression Audits:** Enforce `.webp` or `.avif` extensions for large backgrounds instead of uncompressed PNGs.

package/examples/seo-landing-page/AGENTS.md

@@ -1,5 +1,70 @@
-# SEO Landing Page — Agent Instructions
+# Agent Instructions
 
-project: marketing-landing-page
-stack: HTML5, CSS3, Vanilla JS
-description: Fast, high-conversion static landing page optimized for Core Web Vitals
+> This file is the **source of truth** for all AI coding agents working on this project.
+> Tool-specific adapters in `adapters/` read from this file. Do not duplicate instructions there.
+
+## Project Overview
+
+project: seo-landing-page
+stack: Astro, React, Tailwind CSS, HTML5, JSON-LD
+description: Premium static landing page optimized for high SEO performance and Core Web Vitals.
+
+## Build Commands
+
+```
+dev:   npm run dev
+build: npm run build
+test:  npm run test
+lint:  npm run lint
+```
+
+## Coding Conventions
+
+- Language: JavaScript / TypeScript
+- Framework: Astro
+- Style guide: Astro Standard
+- Type checking: none
+- Formatting: Prettier
+
+## File Structure Rules
+
+```
+src/       → Application source code
+lib/       → Shared libraries and utilities
+tests/     → Test files
+docs/      → Documentation
+```
+
+## Boundaries
+
+```
+no-touch:
+  - .env
+  - .env.local
+  - node_modules/
+  - package-lock.json (do not manually edit)
+```
+
+## Agent Roles
+
+| Role | Tool | Scope | Permissions |
+|------|------|-------|-------------|
+| default | any | all files | read + write |
+
+## Dependencies
+
+- astro
+- tailwindcss
+- @astrojs/react
+
+## Testing Strategy
+
+- Unit tests: none
+- Integration tests: Playwright
+- E2E tests: Lighthouse audits
+
+## Additional Context
+
+- See `MEMORY.md` for project history and decisions
+- See `TASKS.md` for current work items
+- See `RUNBOOK.md` for operational procedures

package/examples/seo-landing-page/MEMORY.md

@@ -1,5 +1,34 @@
-# SEO Landing Page — Memory
+# Project Memory
 
-## key-patterns
-- Strictly matching exactly one main header rules.
-- Fast interactive element parameters.
+> Persistent context that AI agents carry across sessions.
+> Update this file as the project evolves. Keep it under 200 lines.
+
+## Architecture Decisions
+
+| Date | Decision | Rationale |
+|------|----------|-----------|
+| 2026-05-30 | Astro for static rendering | Astro offers zero-JS by default, ensuring perfect Lighthouse performance. |
+| 2026-05-30 | Tailwind CSS for styling | Utility-first classes optimized and purged during the production build. |
+
+## Key Patterns
+
+- **Structured Metadata:** Always include custom JSON-LD schemas in layout headers.
+- **Image Optimization:** Enforce specific width/height ratios and lazy loading on all non-above-the-fold assets.
+
+## Known Issues
+
+- External font loading might trigger visual flashes (CLS). Font display swapping is enabled.
+
+## Environment Notes
+
+- OS: Platform independent
+- CI: GitHub Actions
+- Hosting: Vercel Static
+
+## Session Notes
+
+### Session: Baseline Scaffold
+**Date:** 2026-05-30
+**Agent:** Antigravity
+**Summary:** Created layout structure and integrated SEO-audit skills guidelines.
+**Files changed:** AGENTS.md, MEMORY.md, TASKS.md

package/examples/seo-landing-page/TASKS.md

@@ -0,0 +1,9 @@
+# Tasks
+
+## Active Tasks
+- [ ] Scaffold standard layout inside Astro project
+- [ ] Embed JSON-LD structured data in header layout
+- [ ] Perform Lighthouse performance audit and optimize styles
+
+## Completed Tasks
+- [x] Set up initial project boundaries and configuration yaml

package/examples/wordpress-site/.ai/config.yaml

@@ -1,4 +1,7 @@
-version: "0.1"
-project:
-  name: "custom-wordpress-theme"
-  mode: "standard"
+adapters:
+  cursor: true
+  claude: true
+  vscode: true
+mode: standard
+orchestrator:
+  mode: sequential

package/examples/wordpress-site/.ai/context/architecture.md

@@ -0,0 +1,7 @@
+# WordPress Site — Architecture Map
+
+## Directory Boundaries
+- `/inc` — Helper PHP classes and functions.
+- `/src` — CSS/JS resources before build/compilation.
+- `/languages` — Internationalization translation files (.pot).
+- `plugin.php` — Core entry point defining plugin headers and activations.

package/examples/wordpress-site/.ai/context/context-budget.md

@@ -0,0 +1,4 @@
+# WordPress Site — Context Budget
+
+- Keep total context files under **10,000 tokens** per turn.
+- Do not feed full compiled vendor directories (e.g. `wp-admin`, `wp-includes`) into prompts.

package/examples/wordpress-site/.ai/context/model-map.md

@@ -0,0 +1,4 @@
+# WordPress Site — Model Map
+
+- **Claude / Antigravity:** Best for sanitizing PHP query functions and hooks orchestration.
+- **Cursor / Codex:** Ideal for building block editor styles and custom block integrations.

package/examples/wordpress-site/.ai/context/project-brief.md

@@ -0,0 +1,3 @@
+# WordPress Site — Project Brief
+
+This project is a custom WordPress plugin and theme configuration. The goal is to ensure PHP development adheres to safe database interaction practices and WordPress security standards.

package/examples/wordpress-site/.ai/skills/plugin-boilerplate.md

@@ -0,0 +1,21 @@
+# Skill: WordPress secure plugin structure
+
+Use this skill when scaffolding a secure WordPress plugin or PHP module:
+
+1. **Direct Access Protection:** Ensure every PHP file starts with direct execution guards:
+   ```php
+   if ( ! defined( 'ABSPATH' ) ) {
+       exit; // Exit if accessed directly.
+   }
+   ```
+2. **Class Namespacing:** Namespace your classes to prevent namespace collisions (e.g. `namespace WP_Custom_Plugin;`).
+3. **Database Escaping:** Use prepared statements for direct database calls:
+   ```php
+   global $wpdb;
+   $query = $wpdb->prepare(
+       "SELECT * FROM {$wpdb->prefix}custom_table WHERE id = %d",
+       $item_id
+   );
+   $results = $wpdb->get_results( $query );
+   ```
+4. **Hook Verification:** Register all activations cleanly inside a central bootstrap hook.

package/examples/wordpress-site/AGENTS.md

@@ -1,5 +1,18 @@
 # WordPress Site — Agent Instructions
 
-project: custom-wordpress-theme
-stack: PHP, WordPress Core, MySQL, Sass, Webpack
-description: Custom theme design and plugin configuration for enterprise website
+project: wordpress-custom-profile
+stack: WordPress Core, Gutenberg Block Editor, PHP, custom plugins, MySQL
+description: Custom theme and plugin scaffolding targeting sanitized PHP database queries.
+
+## Build Commands
+```
+dev:   composer run dev
+build: composer run build
+test:  composer run test
+lint:  composer run lint
+```
+
+## Coding Conventions
+- **Language:** PHP 8.1+ and ES6 Javascript for Gutenberg custom blocks.
+- **Sanitization Gates:** Enforce output escaping: `esc_attr()`, `esc_html()`, `esc_url()`, and `wp_kses()`.
+- **Database Safety:** Always use `$wpdb->prepare()` for custom SQL queries to avoid SQL Injection vulnerabilities.

package/examples/wordpress-site/MEMORY.md

@@ -1,4 +1,5 @@
-# WordPress Site — Memory
+# WordPress Site — Project Memory
 
-## Key Decisions
-- Standardized custom post types for "Events" and "News" services.
+## Architectural Decisions
+- **Custom Post Types (CPT):** Registered custom post types strictly using the `init` action hook to ensure URL rewrite rules initialize cleanly.
+- **WP Transients:** Cached heavy database option operations using WordPress Transients API to preserve SQL query load budgets.

package/examples/wordpress-site/TASKS.md

@@ -0,0 +1,10 @@
+# WordPress Site — Starter Tasks
+
+- [ ] Core Setup & Setup hooks
+  - [ ] Scaffold the base plugin class structure
+  - [ ] Register the action and filter hooks in `plugin.php`
+- [ ] Database Schema Setup
+  - [ ] Implement secure custom query wrapper using `$wpdb`
+  - [ ] Setup transient caches for complex queries
+- [ ] Block Editor (Gutenberg)
+  - [ ] Build a custom block boilerplate matching registerBlockType parameters

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "multimodel-dev-os",
-  "version": "0.3.0",
+  "version": "0.5.0",
   "bin": {
     "multimodel-dev-os": "bin/multimodel-dev-os.js"
   },

package/scripts/install.ps1

@@ -11,7 +11,7 @@ param(
   [switch]$Help
 )
 
-$Version = "0.1.0"
+$Version = "0.5.0"
 $RepoUrl = "https://raw.githubusercontent.com/rizvee/multimodel-dev-os/main"
 
 if ($Help) {

package/scripts/install.sh

@@ -7,7 +7,7 @@ set -euo pipefail
 #        --all      (install all adapters)
 #        --dry-run  (show what would be created without creating)
 
-VERSION="0.1.0"
+VERSION="0.5.0"
 REPO_URL="https://raw.githubusercontent.com/rizvee/multimodel-dev-os/main"
 CAVEMAN=false
 DRY_RUN=false

package/scripts/verify.sh

@@ -197,30 +197,30 @@ check_file "docs/npm-publishing.md"
 echo ""
 echo "Running CLI & Packaging Pre-Flight Tests..."
 
-# Verify package.json version is exactly 0.3.0
-if ! grep -q '"version": "0.3.0"' package.json; then
-  echo -e "  ${RED}✗${NC} package.json version is not 0.3.0"
+# Verify package.json version is exactly 0.5.0
+if ! grep -q '"version": "0.5.0"' package.json; then
+  echo -e "  ${RED}✗${NC} package.json version is not 0.5.0"
   FAIL=$((FAIL + 1))
 else
-  echo -e "  ${GREEN}✓${NC} package.json version is exactly 0.3.0"
+  echo -e "  ${GREEN}✓${NC} package.json version is exactly 0.5.0"
   PASS=$((PASS + 1))
 fi
 
-# Verify CLI version matches v0.3.0
-if ! node bin/multimodel-dev-os.js --help | grep -q 'v0.3.0'; then
-  echo -e "  ${RED}✗${NC} CLI help does not display v0.3.0"
+# Verify CLI version matches v0.5.0
+if ! node bin/multimodel-dev-os.js --help | grep -q 'v0.5.0'; then
+  echo -e "  ${RED}✗${NC} CLI help does not display v0.5.0"
   FAIL=$((FAIL + 1))
 else
-  echo -e "  ${GREEN}✓${NC} CLI help displays v0.3.0"
+  echo -e "  ${GREEN}✓${NC} CLI help displays v0.5.0"
   PASS=$((PASS + 1))
 fi
 
-# Verify npm pack dry-run shows v0.3.0
-if ! npm pack --dry-run 2>&1 | grep -q 'multimodel-dev-os@0.3.0'; then
-  echo -e "  ${RED}✗${NC} npm pack --dry-run does not report version 0.3.0"
+# Verify npm pack dry-run shows v0.5.0
+if ! npm pack --dry-run 2>&1 | grep -q 'multimodel-dev-os@0.5.0'; then
+  echo -e "  ${RED}✗${NC} npm pack --dry-run does not report version 0.5.0"
   FAIL=$((FAIL + 1))
 else
-  echo -e "  ${GREEN}✓${NC} npm pack --dry-run reports version 0.3.0"
+  echo -e "  ${GREEN}✓${NC} npm pack --dry-run reports version 0.5.0"
   PASS=$((PASS + 1))
 fi