[ItayTheDar]

Summary

• Adds CLAUDE.md at the repo root — loaded automatically by Claude Code every session, covering full architecture (modules, DI, controllers, guards, DB providers, testing, common mistakes)
• Adds .claude/commands/pynest-resource.md — /project:pynest-resource scaffolds a complete resource (5 files) and wires it into AppModule, then verifies the import chain boots
• Adds .claude/commands/pynest-explain.md — /project:pynest-explain explains any PyNest concept by reading the actual nest/ source before answering
• Adds .claude/settings.json — allowlists common read/dev commands (find, grep, pytest, uvicorn, pynest) to reduce permission prompts during development

Why

AI coding assistants (Claude Code, Copilot, Cursor, etc.) are now part of the standard development workflow. Without CLAUDE.md, every AI session starts cold with no knowledge of PyNest's conventions — leading to generated code that breaks DI rules, uses wrong file naming, or misses the module wiring step. This PR makes the repo AI-native out of the box.

Test plan

• Open a new Claude Code session in this repo — confirm CLAUDE.md is acknowledged in the context
• Run /project:pynest-resource products in Claude Code — confirm 5 files are created and AppModule is updated
• Run /project:pynest-explain guards — confirm it reads nest/core/decorators/guards.py before answering
• Confirm no existing tests are broken (pytest tests/)

🤖 Generated with Claude Code

[ItayTheDar]

Reviewed the current diff and green CI. Two documentation examples need correction before this is merge-ready:

1. CLAUDE.md presents DatabaseModule as an existing importable module, but main has no database_module implementation (the separate [codex] add DatabaseModule root registration #133 proposal is still draft). Please use an API that exists on main, or clearly mark this as future/pseudocode.
2. The testing example registers FakeUsersService while UsersController.__init__ requests UsersService. The DI container resolves by that type, so this does not demonstrate replacing the dependency and may fail. Please show a tested override or a fake bound to the requested type.

I did not merge: required review is still outstanding, and these examples are not source-accurate.

[ItayTheDar]

Updated CLAUDE.md in 3cc94c7 to address the two examples from the prior review: removed the nonexistent DatabaseModule import, and replaced the mismatched fake-provider example with a self-contained test registering the exact UsersService token requested by the controller. Executed the documentation test snippet against this PR head; it passed. Leaving the PR open for the required review and fresh CI.

[ItayTheDar]

Reviewing the current diff against main, I found another blocker in .claude/commands/pynest-resource.md: both SQL entity templates inherit from AsyncOrmProvider.Base / OrmProvider.Base. Base is assigned only on a provider instance in BaseOrmProvider.__init__; neither provider class exposes that attribute, so generated SQL entity modules fail on import. Please use the exported Base from nest.core.database.orm_provider (or a configured provider instance’s .Base) and exercise the generated SQL import path for both sync and async. The command also says it always creates five files, but the none path skips the entity file (four files). I have not merged: branch protection still requires an approving review, and the current head has a failed Python 3.11 check.