Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (mgr-perfect-code) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

MGR PERFECT CODE — THE COMPLETE AI BUILD SYSTEM

© 2025–2026 Money Grind Religion Inc. — Created & Edited by Timebeunus Boyd

What this is: A drop-in folder system that turns ANY AI (Claude, Cursor, Windsurf, Claude Code) into a production-grade engineer that follows YOUR standards, writes REAL code (no mockups), and builds INFINITELY across sessions.

Put this folder in your project → Tell AI to read MGR.md → Build anything.

COMPLETE FILE INVENTORY

MGR_PERFECT_CODE/                          (10,000+ lines total)
│
├── MGR.md                       (81 lines)   — AI Identity & Rules (primary)
├── CLAUDE.md                    (81 lines)   — AI Identity & Rules (legacy)
│   The first file AI reads. Sets MGR standards, copyright,
│   production-only code mandate, no placeholders rule,
│   and auto-creates tracking files.
│
├── PROJECT_INSTRUCTIONS.md      (42 lines)   — Claude Project Settings
│   Paste this into Claude Project's "Custom Instructions" field.
│   Gives every chat in that project MGR standards automatically.
│
├── README.md                    (THIS FILE)   — Master Guide & Instructions
│
├── knowledge/                                 — THE 4 BIBLES
│   ├── MGR_MASTER.md            (630 lines)   — Master Build Bible
│   │   Core standards, architecture patterns, file structure,
│   │   naming conventions, component patterns, state management,
│   │   API design, security, performance, deployment, testing.
│   │   LOAD THIS: Every new project, always.
│   │
│   ├── MGR_UI_BIBLE.md          (861 lines)   — UI/UX Design Bible
│   │   Color systems, typography, spacing, animation, micro-interactions,
│   │   responsive design, dark mode, accessibility, component library,
│   │   design patterns that beat every competitor.
│   │   LOAD THIS: When building frontend/UI.
│   │
│   ├── MGR_3D_BIBLE.md          (464 lines)   — 3D Graphics Bible
│   │   Three.js, React Three Fiber, WebGPU, shaders, physics,
│   │   particle systems, post-processing, performance optimization,
│   │   browser-based 3D rendering techniques.
│   │   LOAD THIS: When building 3D/animation features.
│   │
│   └── MGR_TOKEN_BIBLE.md      (1,094 lines)  — Token Mastery Bible ★ DEEP RESEARCH
│       Context rot science (Chroma 18-model study), Manus production
│       techniques, Cognition/Devin lessons, Anthropic advanced tools,
│       LangChain 4-strategy framework, compaction systems, checkpoints,
│       progressive disclosure, emergency recovery, cost engineering.
│       60+ industry sources. Expert-level.
│       LOAD THIS: When planning sessions or optimizing builds.
│
├── scripts/
│   └── mgr_install.sh           (265 lines)   — Auto-Setup Script
│       Detects OS, installs Node.js/npm/pnpm, sets up Next.js project,
│       installs shadcn/ui + Tailwind + dependencies, creates folder
│       structure, initializes git. One command setup.
│
├── templates/
│   ├── Time_ToDo.md             (32 lines)    — Task Tracker Template
│   │   AI creates this automatically for every project.
│   │   Living document updated at every milestone.
│   │
│   └── Research.md              (44 lines)    — Research Template
│       AI creates this for industry research findings.
│       Populated during deep research phases.
│
├── site/                                      — Landing Page (Deployable)
│   ├── app/page.tsx             — Production landing page (all 10 sections)
│   ├── app/layout.tsx           — Root layout with metadata
│   ├── app/globals.css          — OKLCH design system + aurora bg
│   ├── components/icons.tsx     — Lucide icons barrel export
│   ├── package.json             — Next.js 15 + Framer Motion + Tailwind 4
│   └── next.config.ts           — Standalone output config
│
└── tools/                                     — Future: Custom CLI tools
    (Reserved for MGR automation scripts)

HOW TO USE — STEP BY STEP

OPTION 1: CLAUDE.AI (Phone or Browser) — EASIEST

This is the best option if you're building from your phone or browser.

First-Time Setup (5 minutes, do once):

Go to claude.ai → Click Projects (left sidebar)
Click + New Project → Name it: MyApp - Build
Click Project Knowledge (📎 icon or "Add content")
Upload these files from the knowledge/ folder:
- MGR_MASTER.md (always upload this)
- Upload ONE more bible for your build type:
  - Building UI? → MGR_UI_BIBLE.md
  - Building 3D? → MGR_3D_BIBLE.md
  - Planning/optimizing? → MGR_TOKEN_BIBLE.md
Click Custom Instructions → Paste the ENTIRE contents of PROJECT_INSTRUCTIONS.md
Click Save

To Start Building:

Open a new chat inside your project and type:

Build me [describe what you want].
Production code only. No mockups. No placeholders.

That's it. The AI has all MGR standards from the project knowledge.

When Context Gets Full (AI slows down or forgets):

Type: Write a checkpoint of everything we've built to CHECKPOINT.md format
Copy the AI's checkpoint response
Start a new chat in the SAME project
Paste the checkpoint and say: Continue from this checkpoint

To Switch Build Types:

Create separate projects: MyApp - UI, MyApp - 3D, MyApp - API
Each project uploads the relevant bible
Switch projects = clean context with right knowledge

OPTION 2: CLAUDE CODE (Terminal) — MOST POWERFUL

Best for developers with terminal access. Claude Code has built-in compaction, sub-agents, and file system access.

Setup:

Copy the entire MGR_PERFECT_CODE/ folder into your project root:

cp -r MGR_PERFECT_CODE/ /path/to/your/project/MGR_PERFECT_CODE/

Copy CLAUDE.md to your project root:

cp MGR_PERFECT_CODE/CLAUDE.md /path/to/your/project/CLAUDE.md

Start Claude Code in your project:
```
cd /path/to/your/project
claude
```
Claude Code automatically reads CLAUDE.md on start.

To Build:

Read CLAUDE.md then build [describe what you want].
Load knowledge/MGR_MASTER.md for standards.

To Compact (when context fills):

/compact Focus on: completed work, file paths, architecture decisions, remaining tasks.

To Use Sub-Agents:

Use a sub-agent for [specific task] while we focus on [main task].

OPTION 3: CURSOR / WINDSURF (IDE) — FOR IDE USERS

Setup:

Copy MGR_PERFECT_CODE/ folder into your project root

Create .cursorrules (Cursor) or .windsurfrules (Windsurf) in project root:

Read MGR_PERFECT_CODE/CLAUDE.md for all build standards.
Follow MGR Perfect Code system by Money Grind Religion Inc.
Production code only. No mockups. No placeholders.
When building UI, reference MGR_PERFECT_CODE/knowledge/MGR_UI_BIBLE.md
When building 3D, reference MGR_PERFECT_CODE/knowledge/MGR_3D_BIBLE.md

Open your IDE and start chatting with the AI.

To Continue Across Sessions: Ask the AI to write CHECKPOINT.md before ending. Next session, tell it to read CHECKPOINT.md and continue.

OPTION 4: ANY OTHER AI (ChatGPT, Gemini, etc.)

The bibles work with any AI. Just paste the relevant content:

Start a new chat
Paste the contents of CLAUDE.md (sets standards)
Paste the contents of whichever bible you need
Give your build instructions

Limitation: Other AIs don't have file system access or compaction. You'll need to manually manage checkpoints by copy-pasting.

THE BUILD WORKFLOW

┌──────────────────────────────────────────────┐
│              MGR BUILD PROTOCOL              │
├──────────────────────────────────────────────┤
│                                              │
│  1. INIT                                     │
│     AI reads CLAUDE.md → Creates tracking    │
│     files (Time_ToDo.md, Research.md)        │
│                                              │
│  2. PLAN                                     │
│     Load MGR_MASTER.md → Architecture →      │
│     Task decomposition → Session plan        │
│                                              │
│  3. BUILD                                    │
│     Load relevant bible → Write production   │
│     code → Update Time_ToDo.md → Compact     │
│     at 60% context usage                     │
│                                              │
│  4. CHECKPOINT                               │
│     Update CHECKPOINT.md → Recite remaining  │
│     tasks (keeps AI focused)                 │
│                                              │
│  5. RESUME (new session)                     │
│     Read CHECKPOINT.md → Load next bible →   │
│     Continue from exact stop point           │
│                                              │
│  6. SHIP                                     │
│     Integration pass → Tests → Deploy to     │
│     free tier → Mark COMPLETE                │
│                                              │
└──────────────────────────────────────────────┘

WHICH BIBLE TO LOAD WHEN

You're Building...	Load These
New project (anything)	`MGR_MASTER.md`
Website / Dashboard / App UI	`MGR_MASTER.md` + `MGR_UI_BIBLE.md`
3D graphics / Animations	`MGR_MASTER.md` + `MGR_3D_BIBLE.md`
Planning / Optimizing	`MGR_TOKEN_BIBLE.md`
Full-stack app	`MGR_MASTER.md` + `MGR_UI_BIBLE.md` (Session 1: UI, Session 2: API)

NEVER load all 4 bibles at once. That wastes 35%+ of your context. Load 1-2 max per session. The Token Bible explains why (Context Rot science).

KEY RULES THE AI FOLLOWS

Once CLAUDE.md is loaded, the AI automatically:

Production code ONLY — No mockups, no placeholders, no "TODO: implement later"
Creates tracking files — Time_ToDo.md, Research.md, CHECKPOINT.md
Uses free-tier stack — Vercel, Supabase, Cloudflare, etc. ($0/month)
Deep research first — Searches web for industry best practices before building
Never-before-seen features — Aims to beat everything in the industry
AI-powered by default — Integrates free AI/bots for smart UX
Compacts proactively — Saves state before context fills up

EMERGENCY COMMANDS

Paste these exactly if something goes wrong:

Context Full / AI Slowing Down:

EMERGENCY: Write current state to CHECKPOINT.md NOW.
List all modified files. List next 3 tasks.

AI Forgot Instructions:

RESET: Re-read CLAUDE.md and MGR_MASTER.md.
Operating under MGR Perfect Code by Money Grind Religion Inc.
Resume from CHECKPOINT.md.

AI Rushing / Cutting Corners:

SLOW DOWN: You have plenty of context remaining.
Full production code. No abbreviations. Complete the current task fully.

Build Went Wrong:

ROLLBACK: Read CHECKPOINT.md for last good state.
Compare current files. Fix only divergence. No full rebuild.

QUICK START (30 seconds)

If you just want to BUILD something RIGHT NOW:

Go to claude.ai → New chat (no project needed)
Upload CLAUDE.md as a file
Type: Read CLAUDE.md. Then build me [whatever you want]. Production code only.
That's it. The AI has your standards.

For bigger projects, use the Project setup (Option 1) so knowledge persists across multiple chats without re-uploading.