brainforge-ai 1.2.1 → 1.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,863 +1,326 @@
1
- # ⚡ BrainForge
2
-
3
- > Transform any idea into a structured, AI-assisted project with agents, slash commands, a phase roadmap, persistent memory, a live dashboard, and **83 Claude Code skills** pre-wired for every task.
4
-
5
- [![npm version](https://img.shields.io/npm/v/brainforge-ai.svg)](https://www.npmjs.com/package/brainforge-ai)
6
- [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)
7
- [![Node.js >= 16](https://img.shields.io/badge/node-%3E%3D16-brightgreen)](https://nodejs.org)
8
-
9
- ```bash
10
- npx brainforge-ai init
11
- ```
12
-
13
- ---
14
-
15
- ## Dashboard Preview
16
-
17
- ![BrainForge dashboard preview](./assets/screenshots/dashboard.png)
18
-
19
- ---
20
-
21
- ## What is BrainForge?
22
-
23
- BrainForge is a CLI that installs a **structured AI development system** into any project directory.
24
-
25
- Instead of vibing and hoping the AI does the right thing, BrainForge forces a clean workflow:
26
-
27
- ```
28
- Idea Plan Research Execute Test → Review → Commit → Repeat
29
- ```
30
-
31
- It works with any AI tool: **Claude Code**, **GitHub Copilot**, **Gemini CLI**, **Codex**, **Cursor**, **OpenCode**.
32
-
33
- ---
34
-
35
- ## Why use it?
36
-
37
- | Without BrainForge | With BrainForge |
38
- |--------------------|-----------------|
39
- | AI codes everything at once | AI follows a phase plan |
40
- | No memory between sessions | Persistent project memory |
41
- | Hard to explain your code | `/explain-my-code` generates your defense speech |
42
- | Code looks too AI-perfect | Code Level Engine adapts to your real level |
43
- | No tests | `/write-tests` generates the right tests for your level |
44
- | No version history | Automatic git checkpoints |
45
- | Lost in files | Live dashboard with auto-reload |
46
- | AI ignores best practices | 83 skills enforce the right patterns per task |
47
-
48
- ---
49
-
50
- ## Installation
51
-
52
- ### Run directly (no install needed)
53
-
54
- ```bash
55
- npx brainforge-ai init
56
- ```
57
-
58
- ### Install globally
59
-
60
- ```bash
61
- npm install -g brainforge-ai
62
- brainforge init
63
- ```
64
-
65
- ---
66
-
67
- ## Quick Start
68
-
69
- ### 1. Initialize BrainForge in your project
70
-
71
- ```bash
72
- mkdir my-project
73
- cd my-project
74
- npx brainforge-ai init
75
- ```
76
-
77
- Answer the questions:
78
- - Project name and description
79
- - Project type (web app, API, fullstack, mobile…)
80
- - Stack (React, Node.js, PostgreSQL…)
81
- - Your actual coding level
82
- - Target code level
83
- - Whether it's a school project
84
-
85
- BrainForge generates the full structure and makes the first git commit automatically.
86
-
87
- **Non-interactive mode** — skip all prompts with defaults:
88
-
89
- ```bash
90
- npx brainforge-ai init --yes
91
- npx brainforge-ai init --preset student --yes
92
- ```
93
-
94
- Useful for CI pipelines, automated tests, or quick demos.
95
-
96
- ---
97
-
98
- ### 2. Open your AI tool and start working
99
-
100
- Open **Claude Code**, **Cursor**, or any AI tool in the project folder.
101
-
102
- The AI reads `AGENTS.md` and `CLAUDE.md` automatically, which includes a mandatory skills table telling it exactly which skill file to load for every type of task.
103
-
104
- ---
105
-
106
- ### 3. Follow the workflow with slash commands
107
-
108
- #### Step 1Document the project
109
- ```
110
- /start-project
111
- ```
112
- Describe your idea. The AI asks questions and fills in `.brainforge/project.md`.
113
-
114
- #### Step 2 Create the roadmap
115
- ```
116
- /create-roadmap
117
- ```
118
- Breaks the project into phases with tasks and checklists.
119
-
120
- #### Step 3 — Prepare a phase (before coding)
121
- ```
122
- /initiate-phase 1
123
- ```
124
- Research + planning. The AI proposes an approach and waits for your confirmation.
125
-
126
- #### Step 4 — Execute the phase
127
- ```
128
- /execute-phase 1
129
- ```
130
- The AI codes **only what was planned**. Nothing more.
131
-
132
- #### Step 5 — Write tests
133
- ```
134
- /write-tests
135
- ```
136
- Generates tests adapted to your stack and code level.
137
-
138
- #### Step 6 — Review the phase
139
- ```
140
- /review-phase 1
141
- ```
142
- Checks for bugs, dead code, complexity, and level-appropriateness.
143
-
144
- #### Step 7 — Save your progress
145
- ```
146
- /checkpoint
147
- ```
148
- Creates a local git commit. Never pushes automatically.
149
-
150
- #### Step 8 Watch the dashboard update live
151
- ```bash
152
- brainforge serve
153
- ```
154
- Opens `localhost:3000` — reloads automatically as you work.
155
-
156
- Repeat steps 3–8 for each phase.
157
-
158
- ---
159
-
160
- ## What BrainForge actually generates
161
-
162
- After `brainforge init`, here is the core structure you really get:
163
-
164
- ```text
165
- project-root/
166
- .brainforge/
167
- config.json
168
- project.md
169
- brain.md ← master context file, load this at session start
170
- roadmap.md
171
- memory/ 8 persistent memory files
172
- phases/
173
- agents/ ← 41 specialized AI agents
174
- commands/ ← 15+ slash command prompt files
175
- reports/ ← generated reports (professor-check, simplify…)
176
- dashboard/
177
- .claude/
178
- skills/ ← 83 Claude Code skill files
179
- AGENTS.md
180
- CLAUDE.md
181
- GEMINI.md
182
- OPENAI.md
183
- ```
184
-
185
- ---
186
-
187
- ## CLI Commands
188
-
189
- | Command | Description |
190
- |---------|-------------|
191
- | `brainforge init` | Initialize BrainForge in the current directory |
192
- | `brainforge init --yes` | Non-interactive init with student defaults |
193
- | `brainforge status` | Show compact project summary (phases, git, features) |
194
- | `brainforge simplify` | Generate a prompt to simplify code to your level |
195
- | `brainforge professor-check` | Generate a prompt to detect AI-looking code patterns |
196
- | `brainforge update` | Refresh all agents, commands, and skills to latest version |
197
- | `brainforge serve` | Live dashboard on localhost:3000 (auto-reloads) |
198
- | `brainforge dashboard` | Open the static HTML dashboard in the browser |
199
- | `brainforge update-dashboard` | Refresh dashboard data from project state |
200
- | `brainforge doctor` | Health check — verify all files and setup |
201
- | `brainforge guide` | Show all CLI and slash commands with project status |
202
- | `brainforge version` | Show version info |
203
-
204
- ---
205
-
206
- ## `brainforge status`
207
-
208
- Get a quick read on your project without opening a browser:
209
-
210
- ```bash
211
- brainforge status
212
- ```
213
-
214
- Shows:
215
- - Project name, type, stack, code level, academic flag
216
- - Phase progress bar and status of each phase (pending / in-progress / done)
217
- - Enabled features (Docker, database, auth…)
218
- - Recent git commits and working tree state
219
- - Created / updated timestamps
220
-
221
- ---
222
-
223
- ## `brainforge simplify`
224
-
225
- Generates a structured simplification workflow for your current project:
226
-
227
- ```bash
228
- brainforge simplify
229
- ```
230
-
231
- This command does **two things**:
232
-
233
- 1. Prints a context-aware prompt you can paste into Claude / Codex / Gemini to simplify your code to match your declared code level.
234
- 2. Writes workflow files into your project brain:
235
- - `.brainforge/commands/simplify-codebase.md` — the `/simplify-codebase` slash command
236
- - `.brainforge/reports/simplify-plan.md` — a report template the AI fills in
237
-
238
- **Important:** `brainforge simplify` does not rewrite your code by itself. It generates the instructions your AI tool needs to do the simplification correctly, with the right rules for your level.
239
-
240
- Then in your AI tool:
241
- ```
242
- /simplify-codebase
243
- ```
244
-
245
- ---
246
-
247
- ## `brainforge professor-check`
248
-
249
- Generates an academic explainability review workflow:
250
-
251
- ```bash
252
- brainforge professor-check
253
- ```
254
-
255
- This command does **two things**:
256
-
257
- 1. Prints a prompt you can paste into your AI tool to detect code that looks suspiciously over-engineered or AI-generated.
258
- 2. Writes workflow files into your project brain:
259
- - `.brainforge/commands/professor-check.md` the `/professor-check` slash command
260
- - `.brainforge/reports/professor-check.md` a scored report template
261
-
262
- **Important:** This command does not fake authorship or encourage academic dishonesty. It checks whether your code is understandable and defensible at your declared level — so you can walk a professor through it confidently.
263
-
264
- Then in your AI tool:
265
- ```
266
- /professor-check
267
- ```
268
-
269
- The AI fills in the report with a realism score, flagged files, suspicious patterns, suggested simplifications, and likely oral defense questions with suggested answers.
270
-
271
- ---
272
-
273
- ## Claude Code Skills — 83 Pre-Wired Best-Practice Guides
274
-
275
- Every project initialized with BrainForge gets **83 skill files** installed in `.claude/skills/`. Claude Code reads these automatically when you trigger a matching task.
276
-
277
- Every agent and the `CLAUDE.md` instruction file include a mandatory skills table — Claude **must** read the relevant skill before starting any task. No exceptions.
278
-
279
- ### How it works
280
-
281
- ```
282
- You type: /execute-phase 1 (which involves React + TypeScript + API)
283
-
284
- Coder agent reads its skills table
285
-
286
- Loads: react-best-practices.md + typescript-patterns.md + api-design.md
287
-
288
- Codes with enforced best practices for all three technologies
289
- ```
290
-
291
- ### Skills by Category
292
-
293
- #### Core Engineering
294
- | Skill | What it enforces |
295
- |-------|-----------------|
296
- | `software-architecture` | System design, folder structure, module boundaries |
297
- | `typescript-patterns` | Strict typing, generics, discriminated unions |
298
- | `ag-clean-code` | SOLID principles, naming conventions, refactoring |
299
- | `ag-systematic-debugging` | Hypothesis-driven, evidence-first debugging |
300
- | `error-handling` | Result types, typed errors, retry logic |
301
- | `environment-config` | `.env` management, secrets, Zod validation |
302
- | `logging-observability` | Structured logging, tracing, OpenTelemetry |
303
- | `static-analysis` | ESLint, Semgrep, CodeQL, CVE scanning |
304
-
305
- #### Frontend & UI
306
- | Skill | What it enforces |
307
- |-------|-----------------|
308
- | `react-best-practices` | Components, hooks, state management patterns |
309
- | `next-best-practices` | Routing, SSR, caching, server actions |
310
- | `tailwind-css` | Utility classes, responsive design, dark mode |
311
- | `ag-tailwind-v4` | Tailwind v4 specifics, new API surface |
312
- | `web-performance` | Core Web Vitals, bundle size, lazy loading |
313
- | `accessibility` | WCAG 2.1, ARIA, keyboard navigation |
314
- | `ag-frontend-design` | Component layout, UX patterns |
315
- | `ag-web-design-guidelines` | Visual hierarchy, spacing, typography rules |
316
- | `figma-to-code` | Design handoff, CSS mapping from Figma |
317
- | `seo-optimization` | Meta tags, schema markup, Open Graph |
318
- | `internationalization` | i18n, locale detection, date/currency formatting |
319
- | `svelte-sveltekit` | Svelte 5, SvelteKit routes and actions |
320
- | `vue-nuxt` | Vue 3, Nuxt 3, Pinia, composables |
321
- | `angular-development` | Angular 17+, signals, standalone components |
322
- | `ag-mobile-design` | Mobile UI, React Native, Expo patterns |
323
-
324
- #### Backend & APIs
325
- | Skill | What it enforces |
326
- |-------|-----------------|
327
- | `api-design` | REST API design, OpenAPI, status codes |
328
- | `ag-api-patterns` | REST/RPC patterns, versioning, contracts |
329
- | `ag-nodejs-best-practices` | Node.js streams, modules, async patterns |
330
- | `ag-python-patterns` | Python packaging, type hints, idioms |
331
- | `ag-rust-pro` | Rust ownership, lifetimes, async, traits |
332
- | `graphql-api` | GraphQL schema, Apollo, DataLoader |
333
- | `websockets-realtime` | WebSockets, SSE, real-time architecture |
334
- | `event-driven-arch` | Pub/sub, message queues, BullMQ |
335
- | `rate-limiting` | Throttling, abuse prevention strategies |
336
- | `file-uploads` | S3, multipart, image processing |
337
- | `email-service` | Transactional email, Resend, templates |
338
- | `caching-redis` | Redis, TTL strategies, cache invalidation |
339
- | `monorepo` | Turborepo, pnpm workspaces, shared packages |
340
-
341
- #### Database
342
- | Skill | What it enforces |
343
- |-------|-----------------|
344
- | `database-queries` | Queries, migrations, ORM patterns |
345
- | `ag-database-design` | Schema design, normalization, ER modeling |
346
- | `postgres-best-practices` | PostgreSQL, indexes, RLS, query optimization |
347
-
348
- #### Security & Auth
349
- | Skill | What it enforces |
350
- |-------|-----------------|
351
- | `security-review` | Auth, access control, input validation |
352
- | `authentication-oauth` | JWT, OAuth2, session flows |
353
- | `better-auth` | Better Auth setup, OAuth providers, 2FA |
354
- | `ag-vulnerability-scanner` | OWASP Top 10, CVE scanning, threat modeling |
355
- | `ag-red-team-tactics` | Threat modeling, adversarial testing |
356
-
357
- #### Testing
358
- | Skill | What it enforces |
359
- |-------|-----------------|
360
- | `test-driven-development` | TDD cycles, test structure, coverage |
361
- | `ag-tdd-workflow` | Red-green-refactor discipline |
362
- | `ag-testing-patterns` | Mocks, fixtures, factories, coverage |
363
- | `webapp-testing` | Browser/UI testing, Playwright |
364
- | `api-testing` | Integration tests, Supertest patterns |
365
- | `property-based-testing` | Fuzz testing, generative test cases |
366
-
367
- #### DevOps & Deployment
368
- | Skill | What it enforces |
369
- |-------|-----------------|
370
- | `docker-devops` | Docker, compose, multi-stage builds |
371
- | `terraform-infrastructure` | IaC, Terraform, cloud provisioning |
372
- | `ag-deployment-procedures` | Deployment runbooks, rollback plans |
373
- | `ag-server-management` | nginx, systemd, server hardening |
374
- | `vercel-deployment` | Vercel deployment, edge middleware |
375
- | `netlify-deployment` | Netlify functions, forms, deployment |
376
- | `cloudflare-workers` | Cloudflare Workers, KV, Wrangler |
377
- | `github-workflow` | GitHub PRs, code review, CI/CD |
378
-
379
- #### Cloud Services & SaaS
380
- | Skill | What it enforces |
381
- |-------|-----------------|
382
- | `supabase` | Supabase auth, DB, storage, realtime |
383
- | `stripe-integration` | Stripe payments, subscriptions, webhooks |
384
- | `openai-integration` | OpenAI API, embeddings, tool use |
385
- | `huggingface-ml` | Hugging Face models, inference |
386
- | `sentry-monitoring` | Error tracking, alerts, performance |
387
- | `sanity-cms` | Sanity CMS, GROQ queries, schema |
388
- | `web-scraping` | Firecrawl, Playwright extraction |
389
- | `connect` | Third-party API integration patterns |
390
- | `composio-connect` | 1000+ SaaS integrations via Composio |
391
-
392
- #### Documentation & Process
393
- | Skill | What it enforces |
394
- |-------|-----------------|
395
- | `documentation` | Inline docs, README, JSDoc |
396
- | `content-writing` | Technical writing, copywriting |
397
- | `ag-documentation-templates` | Spec templates, ADR format |
398
- | `changelog` | Changelog format, release notes |
399
- | `deep-research` | Multi-step research with citations |
400
- | `prompt-engineering` | AI prompt crafting, optimization |
401
- | `subagent-development` | Parallel agents, task decomposition |
402
-
403
- #### Architecture & Planning
404
- | Skill | What it enforces |
405
- |-------|-----------------|
406
- | `ag-architecture` | High-level architecture decisions, ADRs |
407
- | `ag-app-builder` | Full app scaffolding, feature planning |
408
- | `ag-plan-writing` | Technical specs, scope documents |
409
- | `ag-intelligent-routing` | Agent routing, task delegation |
410
- | `ag-parallel-agents` | Parallel task splitting, fan-out patterns |
411
- | `ag-brainstorming` | Idea generation, creative problem solving |
412
-
413
- #### Language & Platform Specific
414
- | Skill | What it enforces |
415
- |-------|-----------------|
416
- | `ag-bash-linux` | Bash scripting, Linux CLI, shell automation |
417
- | `ag-powershell-windows` | PowerShell scripting, Windows automation |
418
- | `ag-mcp-builder` | MCP server and tool building |
419
- | `ag-game-development` | Game loops, physics, entity systems |
420
- | `ag-geo-fundamentals` | GIS, coordinates, spatial queries |
421
- | `ag-performance-profiling` | Flame graphs, APM, bottleneck analysis |
422
- | `code-review` | Code review process and quality gates |
423
- | `git-workflow` | Git operations, branching, commit conventions |
424
- | `ag-lint-and-validate` | Linting pipelines, formatting enforcement |
425
- | `ag-code-review-checklist` | PR checklists, review standards |
426
- | `ag-behavioral-modes` | Agent persona and mode switching |
427
-
428
- ---
429
-
430
- ## 41 Specialized Agents
431
-
432
- BrainForge installs **41 agent files** in `.brainforge/agents/`. Every agent has a `## Skills — Read BEFORE Starting` section that specifies exactly which skill files to load before starting work.
433
-
434
- ### Core Workflow Agents
435
-
436
- | Agent | Role |
437
- |-------|------|
438
- | `architect` | System design, folder structure, architecture decisions |
439
- | `researcher` | Pre-implementation technical research |
440
- | `planner` | Phase planning and task breakdown |
441
- | `coder` | Implementation — reads 40+ skills based on task type |
442
- | `reviewer` | Code review — bugs, security, level-appropriateness |
443
- | `teacher` | Explain code, prepare for presentations/defenses |
444
- | `git-agent` | Local commits and checkpoints (never pushes) |
445
- | `dashboard-agent` | Keep the live dashboard up to date |
446
-
447
- ### Advanced Agents (brainforge-*)
448
-
449
- These agents handle complex workflows: atomic code fixes, adversarial reviews, AI framework selection, UI auditing, security verification, and more.
450
-
451
- | Agent | Role |
452
- |-------|------|
453
- | `brainforge-advisor-researcher` | Research gray-area decisions — returns comparison tables |
454
- | `brainforge-ai-researcher` | AI/LLM framework implementation guidance |
455
- | `brainforge-assumptions-analyzer` | Extract codebase assumptions with evidence |
456
- | `brainforge-code-fixer` | Atomic fix application with rollback and verification |
457
- | `brainforge-code-reviewer` | Adversarial review → structured REVIEW.md |
458
- | `brainforge-codebase-mapper` | Analyze codebase: tech, arch, quality, concerns |
459
- | `brainforge-debug-session-manager` | Multi-cycle debug session orchestration |
460
- | `brainforge-debugger` | Scientific root cause investigation |
461
- | `brainforge-doc-classifier` | Classify planning docs: ADR/PRD/SPEC/DOC/UNKNOWN |
462
- | `brainforge-doc-synthesizer` | Merge classified docs, surface conflicts |
463
- | `brainforge-doc-verifier` | Verify doc claims against live codebase |
464
- | `brainforge-doc-writer` | Codebase-verified documentation writing |
465
- | `brainforge-domain-researcher` | AI system domain and eval criteria research |
466
- | `brainforge-eval-auditor` | Retroactive AI evaluation coverage audit |
467
- | `brainforge-eval-planner` | AI evaluation strategy design |
468
- | `brainforge-executor` | Atomic PLAN.md execution with TDD support |
469
- | `brainforge-framework-selector` | AI/LLM framework selection interview |
470
- | `brainforge-integration-checker` | Verify cross-phase wiring end-to-end |
471
- | `brainforge-intel-updater` | Generate structured codebase intel files |
472
- | `brainforge-nyquist-auditor` | Adversarial test gap closure |
473
- | `brainforge-pattern-mapper` | Map new files to existing code analogs |
474
- | `brainforge-phase-researcher` | Pre-planning domain investigation |
475
- | `brainforge-plan-checker` | 12-dimension plan verification |
476
- | `brainforge-planner` | Goal-backward phase plan creation |
477
- | `brainforge-project-researcher` | Ecosystem research before roadmap |
478
- | `brainforge-research-synthesizer` | Synthesize parallel researcher outputs |
479
- | `brainforge-roadmapper` | Requirements → phase roadmap |
480
- | `brainforge-security-auditor` | Threat model mitigation verification |
481
- | `brainforge-ui-auditor` | 6-pillar frontend implementation audit |
482
- | `brainforge-ui-checker` | UI-SPEC.md quality gate |
483
- | `brainforge-ui-researcher` | UI design contract creation |
484
- | `brainforge-user-profiler` | Analyze developer behavior across 8 dimensions |
485
- | `brainforge-verifier` | Goal-backward phase completion verification |
486
-
487
- ---
488
-
489
- ## Slash Commands
490
-
491
- These are prompt files in `.brainforge/commands/` — paste the command name into your AI tool.
492
-
493
- ### Project Setup
494
-
495
- | Command | What it does |
496
- |---------|-------------|
497
- | `/start-project` | Document your idea and gather all project info |
498
- | `/create-roadmap` | Break project into phases (Epic › Feature › Task) |
499
-
500
- ### Phase Workflow
501
-
502
- | Command | What it does |
503
- |---------|-------------|
504
- | `/initiate-phase N` | Research + plan phase N before any coding |
505
- | `/execute-phase N` | Code phase N following the plan exactly |
506
- | `/review-phase N` | Quality review — bugs, level check, academic check |
507
- | `/checkpoint` | Local git commit (never pushes automatically) |
508
-
509
- ### Code Quality
510
-
511
- | Command | What it does |
512
- |---------|-------------|
513
- | `/write-tests` | Generate tests for a file, function, or phase |
514
- | `/humanize-code` | Adapt code to match your real coding level |
515
- | `/debug-issue` | Systematic bug analysis and fix |
516
-
517
- ### Student Tools
518
-
519
- | Command | What it does |
520
- |---------|-------------|
521
- | `/explain-my-code` | Generate an explanation for your professor or team |
522
- | `/professor-check` | Detect code that looks suspiciously AI-generated |
523
- | `/generate-report` | Generate an academic report template |
524
-
525
- ### Documentation & UI
526
-
527
- | Command | What it does |
528
- |---------|-------------|
529
- | `/design-system` | Create a UI/UX design system guide |
530
- | `/generate-docs` | Generate README and docs/ folder |
531
- | `/update-dashboard` | Refresh the HTML dashboard data |
532
-
533
- ---
534
-
535
- ## The Live Dashboard
536
-
537
- Run `brainforge serve` to open a live dashboard at `localhost:3000`.
538
-
539
- It **auto-reloads** every time a file in `.brainforge/` changes — no manual refresh needed.
540
-
541
- ```bash
542
- brainforge serve # localhost:3000
543
- brainforge serve --port 4000 # custom port
544
- ```
545
-
546
- It shows:
547
- - Project name, description, stack, and level
548
- - Phase progress bar
549
- - Status of each phase (pending / in-progress / done)
550
- - Recent git commits
551
- - Known bugs
552
- - Last architecture decisions
553
- - Git status
554
- - A green dot in the corner when live reload is active
555
-
556
- ---
557
-
558
- ## Code Level Engine
559
-
560
- BrainForge adapts all generated and reviewed code to your target level:
561
-
562
- | Level | Who it's for | What it produces |
563
- |-------|-------------|-----------------|
564
- | `beginner` | First year students | Simple functions, direct logic, FR comments |
565
- | `intermediate` | 1-3 years experience | Clean structure, reusable components |
566
- | `academic-realistic` | School / PFA projects | Credible student code — clean but explainable |
567
- | `professional` | Production projects | Typed, tested, secure, scalable |
568
-
569
- ### The `academic-realistic` level
570
-
571
- The most important level for students. It produces code that:
572
-
573
- - ✅ Is clean enough to get a good grade
574
- - ✅ Is simple enough to explain line by line in an oral defense
575
- - ✅ Has no enterprise patterns that would raise suspicion
576
- - ✅ Looks like it was written by a good student, not a senior engineer
577
- - ✅ Has natural comments — not AI-generated-sounding ones
578
-
579
- ---
580
-
581
- ## `/write-tests` — Test Generator
582
-
583
- The `/write-tests` command generates tests adapted to your project:
584
-
585
- - **Detects the right framework** automatically (Jest, Vitest, pytest, PHPUnit…)
586
- - **Adapts test complexity** to your code level
587
- - **Beginner:** 2-3 tests per function, happy path only, no mocks
588
- - **Academic-realistic:** happy path + edge cases, mocks for external services, readable names
589
- - **Professional:** full coverage, integration tests, all error paths
590
-
591
- ```
592
- /write-tests src/auth/login.ts
593
- /write-tests the login feature
594
- /write-tests phase 2
595
- ```
596
-
597
- ---
598
-
599
- ## Project Structure
600
-
601
- After `brainforge init`, your project contains:
602
-
603
- ```
604
- .brainforge/
605
- config.json ← project config (level, stack, phases…)
606
- project.md ← project definition
607
- questions.md ← answered questions from init
608
- decisions.md ← architecture decision log
609
- roadmap.md ← full roadmap
610
- memory/
611
- architecture.md ← technical notes (updated each phase)
612
- coding-style.md ← code level rules
613
- known-bugs.md ← bug tracker
614
- glossary.md ← project vocabulary
615
- design-system.md ← UI/UX guide
616
- project-context.md ← long-term context the AI should not forget
617
- constraints.md ← technical, code level, and academic constraints
618
- learning-notes.md ← concepts learned, bugs fixed, things to review
619
- phases/
620
- phase-01.md ← plan + checklist for phase 1
621
- phase-02.md
622
- agents/ ← 41 specialized AI agents
623
- architect.md
624
- researcher.md
625
- planner.md
626
- coder.md
627
- reviewer.md
628
- teacher.md
629
- git-agent.md
630
- dashboard-agent.md
631
- brainforge-advisor-researcher.md
632
- brainforge-ai-researcher.md
633
- brainforge-assumptions-analyzer.md
634
- brainforge-code-fixer.md
635
- brainforge-code-reviewer.md
636
- brainforge-codebase-mapper.md
637
- brainforge-debug-session-manager.md
638
- brainforge-debugger.md
639
- brainforge-doc-classifier.md
640
- brainforge-doc-synthesizer.md
641
- brainforge-doc-verifier.md
642
- brainforge-doc-writer.md
643
- brainforge-domain-researcher.md
644
- brainforge-eval-auditor.md
645
- brainforge-eval-planner.md
646
- brainforge-executor.md
647
- brainforge-framework-selector.md
648
- brainforge-integration-checker.md
649
- brainforge-intel-updater.md
650
- brainforge-nyquist-auditor.md
651
- brainforge-pattern-mapper.md
652
- brainforge-phase-researcher.md
653
- brainforge-plan-checker.md
654
- brainforge-planner.md
655
- brainforge-project-researcher.md
656
- brainforge-research-synthesizer.md
657
- brainforge-roadmapper.md
658
- brainforge-security-auditor.md
659
- brainforge-ui-auditor.md
660
- brainforge-ui-checker.md
661
- brainforge-ui-researcher.md
662
- brainforge-user-profiler.md
663
- brainforge-verifier.md
664
- commands/
665
- start-project.md
666
- create-roadmap.md
667
- initiate-phase.md
668
- execute-phase.md
669
- review-phase.md
670
- write-tests.md
671
- humanize-code.md
672
- explain-my-code.md
673
- professor-check.md ← generated by brainforge professor-check
674
- simplify-codebase.md ← generated by brainforge simplify
675
- checkpoint.md
676
- debug-issue.md
677
- design-system.md
678
- generate-docs.md
679
- generate-report.md
680
- update-dashboard.md
681
- reports/
682
- README.md ← index of generated reports
683
- professor-check.md ← filled by AI after /professor-check
684
- simplify-plan.md ← filled by AI after /simplify-codebase
685
- dashboard/
686
- index.html ← visual dashboard
687
- style.css
688
- data.json
689
- .claude/
690
- skills/ ← 83 Claude Code skill files (auto-loaded by agents)
691
- software-architecture.md
692
- typescript-patterns.md
693
- react-best-practices.md
694
- next-best-practices.md
695
- api-design.md
696
- database-queries.md
697
- security-review.md
698
- git-workflow.md
699
- test-driven-development.md
700
- code-review.md
701
- … (83 total)
702
- AGENTS.md ← instructions for all AI agents
703
- CLAUDE.md ← Claude Code config + mandatory skills table
704
- GEMINI.md ← Gemini CLI config
705
- OPENAI.md ← OpenAI / Codex config
706
- ```
707
-
708
- ---
709
-
710
- ## Screenshots
711
-
712
- ### `.brainforge/` snapshot
713
- ![.brainforge snapshot](./assets/screenshots/brainforge-tree.png)
714
-
715
- ### `CLAUDE.md` snapshot
716
- ![CLAUDE.md snapshot](./assets/screenshots/claude-md.png)
717
-
718
- ### `AGENTS.md` snapshot
719
- ![AGENTS.md snapshot](./assets/screenshots/agents-md.png)
720
-
721
- ### Dashboard snapshot
722
- ![Dashboard snapshot](./assets/screenshots/dashboard.png)
723
-
724
- ---
725
-
726
- ## Keeping Skills & Agents Up to Date
727
-
728
- Run `brainforge update` at any time to refresh all agent files, skill files, and slash commands to the latest version — without touching your project data (project.md, phases/, memory/, decisions.md are never modified).
729
-
730
- ```bash
731
- brainforge update
732
- ```
733
-
734
- ---
735
-
736
- ## Multi-AI Compatibility
737
-
738
- BrainForge generates config files for every major AI tool:
739
-
740
- | File | Tool |
741
- |------|------|
742
- | `CLAUDE.md` | Claude Code (with full 83-skill mandatory table) |
743
- | `GEMINI.md` | Gemini CLI |
744
- | `OPENAI.md` | Codex / ChatGPT |
745
- | `AGENTS.md` | All tools (universal) |
746
-
747
- Each file tells the AI: what the project is, what code level to use, how to follow the workflow, what files to update, and git rules (never push).
748
-
749
- ---
750
-
751
- ## Git Rules
752
-
753
- | Action | Status |
754
- |--------|--------|
755
- | `git init` | ✅ Auto on first init |
756
- | `git add` + `git commit` | ✅ Via `/checkpoint` |
757
- | `git push` | ❌ Never automatic |
758
- | `git push --force` | ❌ Never |
759
-
760
- You always control when and where you push.
761
-
762
- ---
763
-
764
- ## Example Use Cases
765
-
766
- ### School / PFA project
767
- ```bash
768
- npx brainforge-ai init --yes # or run init and answer questions
769
- # → /start-project → /create-roadmap → phases
770
- # → /write-tests before each review
771
- # → brainforge simplify # clean up before submission
772
- # → brainforge professor-check # check for suspicious patterns
773
- # → /professor-check # paste into AI to get the full report
774
- # → /generate-report # generate the written report template
775
- # → brainforge status # quick sanity check before handing in
776
- ```
777
-
778
- ### Personal MVP
779
- ```bash
780
- npx brainforge-ai init
781
- # → choose "intermediate" or "professional"
782
- # → brainforge serve ← keep the dashboard open while you build
783
- ```
784
-
785
- ### Learning a new stack
786
- ```bash
787
- npx brainforge-ai init
788
- # → choose "beginner" or "intermediate"
789
- # → /explain-my-code after each phase to understand what was built
790
- ```
791
-
792
- ### AI system / LLM feature
793
- ```bash
794
- npx brainforge-ai init
795
- # → brainforge-framework-selector picks your AI framework
796
- # → brainforge-ai-researcher writes implementation guidance
797
- # → brainforge-eval-planner designs the evaluation strategy
798
- # → brainforge-eval-auditor verifies it was actually implemented
799
- ```
800
-
801
- ---
802
-
803
- ## Limitations
804
-
805
- BrainForge improves consistency and quality, but it does **not** fully control your AI assistant behavior.
806
-
807
- - It guides Claude/Cursor/Codex/Gemini with structure, prompts, and files.
808
- - The model can still ignore instructions, hallucinate, or take shortcuts.
809
- - You must review code, run tests, and validate security before shipping.
810
- - BrainForge is a workflow guardrail, not an autopilot guarantee.
811
-
812
- ---
813
-
814
- ## Requirements
815
-
816
- - Node.js >= 16
817
- - Git (optional but recommended)
818
- - An AI tool: Claude Code, Cursor, Copilot, Gemini CLI, Codex…
819
-
820
- ---
821
-
822
- ## Development
823
-
824
- ```bash
825
- git clone https://github.com/MEHDImp4/brainforge-ai
826
- cd brainforge-ai
827
- npm install
828
- npm run build
829
- npm link
830
-
831
- # Run the test suite
832
- npm test
833
-
834
- # End-to-end install verification (init → file check → doctor → status)
835
- npm run test:install
836
-
837
- # Verify the npm package contents
838
- npm run test:pack
839
-
840
- # Manual smoke test
841
- brainforge init --yes
842
- brainforge status
843
- brainforge simplify
844
- brainforge professor-check
845
- brainforge doctor
846
- brainforge serve
847
- ```
848
-
849
- ---
850
-
851
- ## Contributing
852
-
853
- Issues and PRs welcome on [GitHub](https://github.com/MEHDImp4/brainforge-ai).
854
-
855
- ---
856
-
857
- ## License
858
-
859
- MIT — free to use, modify, and share.
860
-
861
- ---
862
-
863
- *Built for students and developers who want structure, best practices, and 83 skill guides — before they start vibing.*
1
+ # ⚡ BrainForge
2
+
3
+ > Un outil qui aide ton IA à coder **correctement et dans l'ordre** au lieu de tout faire d'un coup et n'importe comment.
4
+
5
+ [![npm version](https://img.shields.io/npm/v/brainforge-ai.svg)](https://www.npmjs.com/package/brainforge-ai)
6
+ [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)
7
+ [![Node.js >= 16](https://img.shields.io/badge/node-%3E%3D16-brightgreen)](https://nodejs.org)
8
+
9
+ ---
10
+
11
+ ## C'est quoi BrainForge ?
12
+
13
+ Quand tu utilises une IA comme Claude ou Copilot pour coder, tu rencontres vite ces problèmes :
14
+
15
+ - L'IA code tout en une seule fois, et le résultat est trop complexe pour toi
16
+ - Elle oublie le contexte d'une session à l'autre
17
+ - Le code ressemble à du "code de senior" alors que tu es étudiant
18
+ - Tu ne saurais pas l'expliquer à ton prof
19
+
20
+ **BrainForge installe une structure dans ton projet** qui force l'IA à :
21
+
22
+ 1. Planifier avant de coder
23
+ 2. Suivre des phases claires (Planifier Coder Tester Réviser)
24
+ 3. Adapter le code à **ton niveau réel**
25
+ 4. Garder une mémoire persistante entre les sessions
26
+
27
+ ```
28
+ Sans BrainForge : l'IA fait tout, tu comprends rien
29
+ Avec BrainForge : l'IA suit tes instructions étape par étape
30
+ ```
31
+
32
+ ---
33
+
34
+ ## Aperçu du dashboard
35
+
36
+ ![BrainForge dashboard preview](./assets/screenshots/dashboard.png)
37
+
38
+ ---
39
+
40
+ ## Ce qu'il te faut avant de commencer
41
+
42
+ - **Node.js** (version 16 ou plus) [télécharger ici](https://nodejs.org)
43
+ - **Git** recommandé pour sauvegarder ton travail automatiquement
44
+ - Un **outil IA** : Claude Code, Cursor, GitHub Copilot, Gemini CLI, ou autre
45
+
46
+ > Tu peux vérifier si Node.js est installé en tapant `node --version` dans ton terminal.
47
+
48
+ ---
49
+
50
+ ## Démarrage rapide (5 minutes)
51
+
52
+ ### Étape 1 Lance BrainForge dans ton projet
53
+
54
+ ```bash
55
+ mkdir mon-projet
56
+ cd mon-projet
57
+ npx brainforge-ai init
58
+ ```
59
+
60
+ L'outil va te poser quelques questions simples :
61
+ - Nom et description du projet
62
+ - Type de projet (site web, API, app mobile…)
63
+ - Les technologies que tu utilises (React, Node.js, Python…)
64
+ - Ton niveau de code actuel
65
+ - Si c'est un projet scolaire
66
+
67
+ Ensuite il génère tout automatiquement et fait le premier commit git.
68
+
69
+ > **Pas envie de répondre aux questions ?** Utilise `--yes` pour tout passer avec les valeurs par défaut :
70
+ > ```bash
71
+ > npx brainforge-ai init --yes
72
+ > ```
73
+
74
+ ---
75
+
76
+ ### Étape 2 — Ouvre ton outil IA dans le dossier du projet
77
+
78
+ Ouvre **Claude Code**, **Cursor**, ou ton outil préféré dans le dossier que tu viens de créer.
79
+
80
+ L'IA lira automatiquement les fichiers `AGENTS.md` et `CLAUDE.md` générés par BrainForge — elle sait donc quoi faire et comment se comporter.
81
+
82
+ ---
83
+
84
+ ### Étape 3 — Suis le workflow avec des commandes
85
+
86
+ Tape ces commandes directement dans ton outil IA, dans l'ordre :
87
+
88
+ | Commande | Ce que ça fait |
89
+ |----------|---------------|
90
+ | `/start-project` | Tu décris ton idée, l'IA pose des questions et remplit le fichier projet |
91
+ | `/create-roadmap` | L'IA divise ton projet en phases avec des tâches précises |
92
+ | `/initiate-phase 1` | L'IA planifie la phase 1 et attend ta validation avant de coder |
93
+ | `/execute-phase 1` | L'IA code **uniquement ce qui était prévu** — rien de plus |
94
+ | `/write-tests` | Génère des tests adaptés à ton niveau |
95
+ | `/review-phase 1` | Vérifie les bugs, la complexité, et si le code est trop "AI-looking" |
96
+ | `/checkpoint` | Sauvegarde ton travail avec git (ne pousse jamais automatiquement) |
97
+
98
+ Répète `/initiate-phase`, `/execute-phase`, `/review-phase`, `/checkpoint` pour chaque phase.
99
+
100
+ ---
101
+
102
+ ### Étape 4 Surveille ta progression avec le dashboard
103
+
104
+ ```bash
105
+ brainforge serve
106
+ ```
107
+
108
+ Ouvre `localhost:3000` dans ton navigateur il se recharge automatiquement pendant que tu travailles.
109
+
110
+ ---
111
+
112
+ ## Commandes spéciales pour les étudiants
113
+
114
+ Si tu rends un projet scolaire, ces commandes sont faites pour toi :
115
+
116
+ ### `brainforge simplify`
117
+
118
+ ```bash
119
+ brainforge simplify
120
+ ```
121
+
122
+ Génère un prompt pour **simplifier le code** à ton niveau réel. Utile avant de rendre un projet pour que le code soit expliquable.
123
+
124
+ Ensuite dans ton outil IA :
125
+ ```
126
+ /simplify-codebase
127
+ ```
128
+
129
+ ### `brainforge professor-check`
130
+
131
+ ```bash
132
+ brainforge professor-check
133
+ ```
134
+
135
+ Génère un prompt pour **détecter les patterns qui semblent trop AI-générés**. Le but : vérifier que tu peux défendre chaque ligne devant un prof.
136
+
137
+ Ensuite dans ton outil IA :
138
+ ```
139
+ /professor-check
140
+ ```
141
+
142
+ > Ces outils ne t'aident pas à tricher — ils t'aident à t'assurer que tu comprends ton propre code.
143
+
144
+ ---
145
+
146
+ ## Les niveaux de code
147
+
148
+ BrainForge adapte le code généré à ton niveau :
149
+
150
+ | Niveau | Pour qui | Ce que ça produit |
151
+ |--------|----------|------------------|
152
+ | `beginner` | 1ère année | Fonctions simples, logique directe, commentaires en français |
153
+ | `intermediate` | 1-3 ans d'expérience | Structure propre, composants réutilisables |
154
+ | `academic-realistic` | Projets scolaires / PFA | Code propre mais expliquable ligne par ligne pas de patterns "enterprise" |
155
+ | `professional` | Projets de production | Typé, testé, sécurisé, scalable |
156
+
157
+ Le niveau **`academic-realistic`** est le plus utile pour les étudiants : le code est assez propre pour avoir une bonne note, mais assez simple pour l'expliquer en soutenance.
158
+
159
+ ---
160
+
161
+ ## Toutes les commandes CLI
162
+
163
+ ```bash
164
+ brainforge init # Initialiser BrainForge dans le dossier actuel
165
+ brainforge init --yes # Init sans questions (valeurs par défaut)
166
+ brainforge status # Voir l'état du projet en un coup d'œil
167
+ brainforge serve # Dashboard live sur localhost:3000
168
+ brainforge simplify # Générer un prompt de simplification du code
169
+ brainforge professor-check # Générer une vérification académique
170
+ brainforge update # Mettre à jour les agents et skills à la dernière version
171
+ brainforge doctor # Vérifier que tout est bien installé
172
+ brainforge guide # Voir toutes les commandes disponibles
173
+ ```
174
+
175
+ ---
176
+
177
+ ## Ce que BrainForge génère dans ton projet
178
+
179
+ Après `brainforge init`, tu obtiens cette structure :
180
+
181
+ ```
182
+ mon-projet/
183
+ .brainforge/
184
+ config.json ← tes paramètres (niveau, stack, phases…)
185
+ project.md ← description de ton projet
186
+ roadmap.md ← ton plan de travail par phases
187
+ memory/ ← mémoire persistante (l'IA s'en souvient entre sessions)
188
+ architecture.md ← notes techniques
189
+ known-bugs.md ← bugs connus
190
+ coding-style.md ← règles de style adaptées à ton niveau
191
+ phases/ ← un fichier par phase avec la checklist
192
+ agents/ ← 41 rôles d'IA spécialisés (architecte, codeur, reviewer…)
193
+ commands/ ← les fichiers de commandes slash
194
+ dashboard/ ← le dashboard HTML
195
+ .claude/
196
+ skills/ ← 83 guides de bonnes pratiques (chargés automatiquement)
197
+ AGENTS.md ← instructions pour tous les outils IA
198
+ CLAUDE.md ← config Claude Code
199
+ GEMINI.md ← config Gemini CLI
200
+ OPENAI.md ← config Codex / ChatGPT
201
+ ```
202
+
203
+ ---
204
+
205
+ ## Exemples concrets
206
+
207
+ ### Projet scolaire / PFA
208
+
209
+ ```bash
210
+ npx brainforge-ai init
211
+ # Choisir "academic-realistic" comme niveau
212
+ # Dans ton outil IA :
213
+ # → /start-project → /create-roadmap → /initiate-phase 1 → /execute-phase 1
214
+ # → /write-tests → /review-phase 1 → /checkpoint
215
+ # Avant de rendre :
216
+ # brainforge simplify (simplifier le code)
217
+ # brainforge professor-check (vérifier l'authenticité)
218
+ # /professor-check (rapport complet)
219
+ ```
220
+
221
+ ### Apprendre un nouveau langage
222
+
223
+ ```bash
224
+ npx brainforge-ai init
225
+ # Choisir "beginner" ou "intermediate"
226
+ # → /explain-my-code après chaque phase pour comprendre ce qui a été construit
227
+ ```
228
+
229
+ ### Projet personnel
230
+
231
+ ```bash
232
+ npx brainforge-ai init
233
+ # Choisir "intermediate" ou "professional"
234
+ # brainforge serve ← garder le dashboard ouvert pendant que tu codes
235
+ ```
236
+
237
+ ---
238
+
239
+ ## Règles git
240
+
241
+ BrainForge utilise git pour sauvegarder ton travail, mais **ne pousse jamais automatiquement** :
242
+
243
+ | Action | Comportement |
244
+ |--------|-------------|
245
+ | `git init` | Automatique au premier `init` |
246
+ | Commit (`/checkpoint`) | Oui, local uniquement |
247
+ | Push vers GitHub | ❌ Jamais automatique — c'est toi qui décides |
248
+
249
+ ---
250
+
251
+ ## Dépannage
252
+
253
+ **BrainForge ne se lance pas ?**
254
+ ```bash
255
+ node --version # Doit afficher v16 ou plus
256
+ brainforge doctor # Vérifie l'installation
257
+ ```
258
+
259
+ **L'IA ne suit pas les commandes ?**
260
+ - Assure-toi d'avoir ouvert ton outil IA dans le bon dossier (celui avec `.brainforge/`)
261
+ - Lance `/start-project` en premier si ce n'est pas encore fait
262
+
263
+ **Mettre à jour BrainForge :**
264
+ ```bash
265
+ brainforge update
266
+ ```
267
+
268
+ ---
269
+
270
+ ## Limitations à connaître
271
+
272
+ BrainForge guide l'IA avec des fichiers et des prompts — mais il ne **contrôle pas** ce que l'IA fait à 100%.
273
+
274
+ - L'IA peut parfois ignorer les instructions ou prendre des raccourcis
275
+ - Tu dois toujours relire le code, lancer les tests, et vérifier avant de remettre
276
+ - BrainForge est un garde-fou, pas un pilote automatique
277
+
278
+ ---
279
+
280
+ ## Infos techniques (pour les curieux)
281
+
282
+ <details>
283
+ <summary>83 guides de bonnes pratiques (skills)</summary>
284
+
285
+ Chaque projet BrainForge reçoit 83 fichiers de bonnes pratiques dans `.claude/skills/`. Ils couvrent : React, Next.js, TypeScript, Node.js, Python, Rust, PostgreSQL, Docker, Stripe, Supabase, tests, sécurité, accessibilité, et bien plus.
286
+
287
+ L'IA les charge automatiquement selon la tâche en cours — tu n'as rien à faire.
288
+
289
+ </details>
290
+
291
+ <details>
292
+ <summary>41 agents spécialisés</summary>
293
+
294
+ BrainForge installe 41 fichiers d'agents dans `.brainforge/agents/`. Chaque agent a un rôle précis : architecte, codeur, reviewer, debugger, enseignant, etc.
295
+
296
+ Les agents avancés (`brainforge-*`) gèrent des tâches complexes comme l'audit de sécurité, la vérification de couverture de tests, ou la sélection de framework IA.
297
+
298
+ </details>
299
+
300
+ <details>
301
+ <summary>Compatibilité multi-IA</summary>
302
+
303
+ BrainForge génère des fichiers de config pour tous les outils populaires :
304
+
305
+ | Fichier | Outil |
306
+ |---------|-------|
307
+ | `CLAUDE.md` | Claude Code |
308
+ | `GEMINI.md` | Gemini CLI |
309
+ | `OPENAI.md` | Codex / ChatGPT |
310
+ | `AGENTS.md` | Tous les outils (universel) |
311
+
312
+ </details>
313
+
314
+ ---
315
+
316
+ ## Contribuer
317
+
318
+ Issues et PRs bienvenus sur [GitHub](https://github.com/MEHDImp4/brainforge-ai).
319
+
320
+ ## Licence
321
+
322
+ MIT libre d'utilisation, de modification et de partage.
323
+
324
+ ---
325
+
326
+ *Fait pour les étudiants et développeurs qui veulent coder avec structure — pas juste "vibe coder" et espérer que ça marche.*