neuraforge-ai: Instructions file for Codex

NeuraForge AI — Agent Instructions

You have access to the NeuraForge AI development platform. Use these agents and rules when working on this codebase.

How to Use

When the user asks you to generate code, review code, debug, scaffold, or any development task — follow the appropriate agent instructions below. Always search the codebase before generating new code.

Plan Before Acting

Before writing any code:

1. Search the codebase for existing similar code — use the codebase-graph skill (graphify) if it's available, for anything beyond a trivial grep
2. Identify what to reuse, extend, or refactor
3. Present a brief plan and wait for approval
4. Then execute

Feedback Protocol (MANDATORY — how agents learn)

Read rules/core/FEEDBACK_PROTOCOL.md in full. Every code-generating agent must:

1. Before generating — load rules/anti-patterns/{stack}.md and apply every rule listed
2. Before generating — check if .neuraforge/lessons.md exists; if so, read and apply project-specific rules
3. After generating — write a feedback log to .neuraforge/feedback/{agent}-{YYYYMMDD}-{id}.md
4. Tell the user — at the end of every response, show the feedback log path and how to flag mistakes

This is how the agents improve. Every corrected feedback item becomes a new anti-pattern rule.

Minimal Solution Principle (MANDATORY — how much to generate)

Read rules/core/MINIMAL_SOLUTION.md in full before generating. Work down its ladder — does this need to exist, does it already exist, does the framework already do it, is there an approved dependency, can an existing file absorb it — and stop at the first rung that resolves the request. The "never skip" list in that file (audit fields, decimal money, validation, idempotency, pagination, auth, UX states) stays mandatory regardless of how small the request is.

Architecture Principles (enforce on ALL code)

• Data fetching at the leaf level — each component/widget fetches its own data, no parent prop-drilling
• Reuse → Extend → Refactor → Create — never duplicate. Search first.
• No god classes — controllers <150 lines, services <300, components <150
• Composition over inheritance — DI composition, max 1 level of inheritance
• Consistent error handling — standard response envelope, domain exceptions
• Audit everything — createdBy, modifiedBy, createdAt, modifiedAt, soft deletes
• Pagination on all lists — never return unbounded collections
• Loading / Error / Empty states — on every data-driven screen
• API URL paths: always lowercase-hyphenated (kebab-case) — /api/v1/bank-accounts, /api/v1/transaction-history, NOT /api/v1/BankAccounts or /api/v1/bankAccounts. Enforced across ALL stacks (.NET, NestJS, Django, Spring Boot, React, RN, Flutter).