Loaded Vibes Framework

Framework Development Workspace

Bad Vibes – Clean Code – Solid Infra – Sharded Loads

---

🌎 About This Workspace

This is the framework development environment for Loaded Vibes—an enterprise-grade Agentic TypeScript Web Development Framework. Use this workspace to author, test, and maintain the framework itself before shipping to end users.

⚠️ Maintainers Only: This README covers framework authoring. For end-user documentation, see dist/README.md.

🛠️ Development Stack

• Framework Core: GenAIScript orchestrator, DevCycle engine, CLI tooling
• Frontend: Next.js 15 (App Router, RSC), React 19, Tailwind CSS 4, shadcn/ui
• Data: PostgreSQL (Neon), Prisma ORM, Redis cache layers
• Auth & Security: Clerk, JWT, ABAC/RBAC, Bad Vibes Firewall
• Tooling: Vitest, Playwright, ESLint, Prettier, GitHub Actions CI/CD
• AI Integration: GitHub Copilot Agent Mode, MCP servers, GenAIScript extension

📁 Directory Structure

Development Folders

├── .github/          # Copilot instructions & governance (DEV ONLY)
├── .vscode/          # Editor settings & extensions (DEV ONLY)
├── docs/             # PRD, Tech Requirements, architecture guides
├── spec/             # SPEC-ARCH, SPEC-CLI, SPEC-ENGINE, etc.
├── templates/        # Asset templates for generating shipped artifacts
├── decisions/        # Architecture Decision Records (ADRs)
└── app/              # Marketing site (loadedvibes.vercel.app)

Shipped Artifacts (dist/)

dist/
├── .github/          # End-user agents, prompts, instructions, toolsets
├── .vscode/          # End-user VS Code settings & MCP config
├── genaiscript/      # Orchestrator engine & DevCycle manifest
├── cli/              # CLI commands (init, doctor, dashboard, devcycle)
├── docs/             # End-user documentation
└── src/              # Generated user project output

🧭 Spec-Driven Workflow

All framework development follows the Analyze → Design → Implement → Validate → Reflect → Handoff loop:

🚀 Framework Development Quickstart

Prerequisites

• Node.js ≥ 20
• pnpm (package manager)
• VS Code with GenAIScript extension
• GitHub Copilot (Agent Mode enabled)

Setup

# Clone the repository
git clone https://github.com/DigitalHerencia/LoadedVibes.git
cd LoadedVibes

# Install dependencies
pnpm install

# Run the marketing site locally
pnpm dev

# Validate framework manifests
pnpm run build

Key Commands

🔧 DevCycle Governance

Loaded Vibes orchestrates development through 18 canonical DevCycles:

Manifest: dist/genaiscript/devcycles.config.json

🔒 Security & Quality Gates

• Bad Vibes Firewall: Destructive operations require human approval with logged signatures
• SHA256 Verification: All releases are cryptographically signed
• Secret Redaction: Telemetry exports sanitize sensitive data
• ABAC/RBAC: Role-based access control throughout

🤖 CI Workflows

Manifest Validation

Verifies all DevCycle entries resolve to valid instruction/toolset/prompt files.

• Trigger: Push/PR to dist/genaiscript/devcycles.config.json
• Reference: TECH_REQUIREMENTS §7, SPEC-ARTIFACTS §3

Settings Guard

Ensures VS Code settings only reference development-layer assets (never dist/**).

• Trigger: Push/PR to .vscode/settings.json
• Reference: PRD §4.3, SPEC-ARCH §3

🤝 Contributing

See CONTRIBUTING.md for guidelines. All contributions must:

1. Follow the Spec-Driven Workflow
2. Include requirement citations (PRD/TECH clauses)
3. Update TODO.md and CHANGELOG.md
4. Pass CI validation

📚 Resources

"Bad Vibes, Clean Code, Solid Infra, Sharded Loads."