Skip to content

jonbeatz/Vader-Engine

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

152 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Vader Engine Dashboard

Vader Engine

The production-hardened development factory for Cursor agents.
Build production-ready applications with a visual command center,
61-point integrity verification, and triple-sandbox development environments.

CI Version Live Demo Grade GitHub stars License Cursor


πŸ“Š Current Status

Metric Value
Version v2.6.1
Integrity Grade 61/61 (100%)
Dashboard βœ… Vader Construct β€” 12+ routes on port 3010
API Layer βœ… 7 endpoints (health, grade, logs, projects, templates, env, scripts)
Sandboxes βœ… 3 isolated environments (ports 3000–3002)
Templates βœ… 4 blueprints (portfolio, divi-bridge, task-manager, vader-site)
Unit Tests βœ… 8/8 Vitest
E2E Tests βœ… 6 Playwright specs (dashboard navigation + sandbox smoke)
Status 🟒 Production Ready

πŸš€ Why Vader Engine?

Most boilerplates give you files. Vader Engine gives you a complete development operating system.

Capability Vader Engine Typical Boilerplate
Visual Command Dashboard βœ… ❌
61-Point Integrity Grader βœ… ❌
Real-time Operations Hub βœ… ❌
Triple Sandbox Architecture βœ… ❌
Built-in Template Engine βœ… ❌
MCP-Ready (13 servers) βœ… ❌
Zero-Leak Security Protocol βœ… ❌
Agent Start / End / Update Rituals βœ… ❌

πŸ–ΌοΈ Screenshots

Vader Construct Dashboard

Dashboard
Real-time metrics, sandbox controls, and activity feed

System Metrics

Metrics
CPU, memory, disk I/O, and request latency monitoring

Process Manager

Processes
Active process monitoring with PID, CPU, and memory usage


πŸš€ Quick Start

git clone https://github.com/jonbeatz/Vader-Engine.git
cd Vader-Engine
npm run msc:check-node          # Node 20.x–24.x preflight
npm run bootstrap               # deps, ports, env validation
cp .env.example .env.local      # (Windows: copy .env.example .env.local) then add live values
npm run msc:dev:dashboard

Open http://localhost:3010 β€” the Vader Construct command center.

Verify the full baseline gate:

npm run start-project:gate      # validate-env Β· lint Β· 61/61 Β· 8/8 tests

Requirements: Node 20.x–24.x (.nvmrc pins 20.19.1) Β· npm β‰₯ 10
Secrets: Live keys belong in .env.local only β€” never commit or paste into chat. See SECURITY.md.

Agent ritual: Say start project in Cursor chat for full cold-start β€” see START-HERE.md.


✨ What's New

v2.6.1 (Documentation Polish)

Feature Description
πŸ“– Production README Status table, Quick Start, agent ritual pointers
πŸͺŸ Windows hint .env.local copy instruction for Windows operators
πŸ”„ Full doc sync Root, .cursor/docs, rules, and prompts aligned to 2.6.1

Release notes: RELEASE_v2.6.1.md

v2.6.0 (Vader Construct Live)

Feature Description
🎨 Complete v0 UI/UX Full dashboard rewrite with live data across 12+ routes
πŸ“‘ 7 API Endpoints Health, grade, logs, projects, templates, env, scripts
⚑ TanStack Query v5 Race-condition-free fetching with skeleton loading states
πŸ§ͺ E2E Test Suite Playwright smoke for dashboard navigation + sandboxes
πŸ”§ Operations Hub Ports, logs, processes, metrics, env, and script dispatch
πŸ“š Lean doc index DOCS.md router + agent workflow prompts (Start / End / Update Project)

Full release notes: RELEASE_v2.6.0.md Β· RELEASE_v2.6.1.md Β· Changelog: CHANGELOG.md


πŸ—οΈ Architecture

Vader Engine
β”œβ”€β”€ Dashboard (port 3010)    # Vader Construct UI β€” shells out to msc:* scripts
β”œβ”€β”€ Integrity Center         # 61-point grader
β”œβ”€β”€ Sandbox Manager          # 3 isolated environments (3000–3002)
β”œβ”€β”€ Template Engine          # 4 blueprint scaffolds via msc:template CLI
β”œβ”€β”€ Operations Hub           # Ports, logs, processes, metrics
└── CLI Engine               # msc:* script system (scripts/ + package.json)

Design principle: Lean Boundary β€” the dashboard never duplicates grader or health logic; API routes invoke existing root scripts.


πŸ“‚ Project Structure

Vader-Engine/
β”œβ”€β”€ ui/dashboard/          # Vader Construct (Next.js, port 3010)
β”œβ”€β”€ ui/msc-shield.css      # Studio Dark token SSoT
β”œβ”€β”€ examples/              # Triple sandboxes
β”‚   β”œβ”€β”€ nextjs-minimal/    # Port 3000 β€” minimal frontend
β”‚   β”œβ”€β”€ nextjs-payload/    # Port 3001 β€” full-stack CMS
β”‚   └── nextjs-tailwind/   # Port 3002 β€” Tailwind + shadcn Path B
β”œβ”€β”€ templates/             # Reusable blueprints (4 registered)
β”œβ”€β”€ scripts/               # Automation & msc:* tooling
β”œβ”€β”€ core/                  # Shared bridge code
β”œβ”€β”€ e2e/                   # Playwright test suite
β”œβ”€β”€ .cursor/               # Agent prompts, rules, skills, MCP config
β”œβ”€β”€ docs/                  # Human runbooks (ARCHITECTURE, CONTRIBUTING, releases)
β”œβ”€β”€ TRUTH.md               # Constitution (root β€” technical precedence)
└── _archive/              # Archived legacy docs (reference only)

πŸ“‘ API Endpoints

Endpoint Purpose
GET /api/health Service and port health
GET /api/grade 61-point integrity grader
GET /api/logs Real-time activity logs
GET /api/projects Dynamic project discovery
GET /api/templates Template catalog
GET /api/env Runtime environment info (redacted)
GET /api/scripts Available npm scripts

πŸ”§ Development Commands

npm run start-project:gate    # Full baseline gate (recommended before PR)
npm run grade                 # 61-point integrity check
npm run msc:dev:dashboard     # Dashboard on :3010
npm run msc:dev:example       # Minimal sandbox on :3000
npm run msc:dev:payload       # Payload sandbox on :3001
npm run msc:dev:tailwind      # Tailwind sandbox on :3002
npm run msc:template -- list  # Template catalog
npm run msc:e2e               # Playwright E2E (run msc:e2e:install first)
npm run msc:backup            # Standard backup (see msc:backup:full)
npm run dev:recover           # Clear stale caches + restart dev flow

Say End Project in Cursor chat for session closeout β€” see START-HERE.md.


πŸ“š Documentation

Document Purpose
START-HERE.md Operator cold-start checklist
DOCS.md Complete documentation index (SSoT router)
TRUTH.md Constitution β€” zero-leak, tokens, MCP portability
PROJECT_CONTEXT.md Architecture & onboarding map
ARCHITECTURE.md System architecture deep dive
CONTRIBUTING.md Fork, hooks, PR gates
SECURITY.md Zero-leak policy & advisory reporting
TROUBLESHOOTING.md Common issues & recovery
CHANGELOG.md Release history

For Cursor agents: .cursor/docs/Code-Jedi.md Β· .cursor/prompts/Start-Project.md

Security: .env.local is gitignored. Use .env.example for key names only. Never commit secrets.


πŸ—ΊοΈ Roadmap

v2.7 (Next)

  • Enhanced metrics dashboard & activity timeline
  • Project manager improvements
  • Deeper Operations Hub integrations

v3.0 (Future)

  • Boilerplate Studio visual editor
  • AI Project Builder
  • Tauri desktop app

See .cursor/plans/ENGINE_ROADMAP.md for the full integration plan.


🀝 Contributing

We welcome contributions that respect the Vader Protocol.

  1. Fork the repository
  2. Create a feature branch (feat/your-feature)
  3. Run npm run start-project:gate β€” must pass 61/61 grade and 8/8 tests
  4. Commit your changes (Husky runs lint + env validation)
  5. Push and open a Pull Request

Please read CONTRIBUTING.md for forge rules, template conventions, and pre-tag gates.


πŸ“„ License

MIT Β© Vader Engine


Built with β˜• and Cursor Β· Powered by the MSC Media Engine

About

A production-hardened development operating system for Cursor agents. Features an integrated operations dashboard, 61-point integrity verification, and triple-sandbox architecture for full-stack stability from scaffold to production.

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors