Skip to content

docs(onboarding): guide développeur complet (docs/onboarding/) - #26

Merged
Tbeaumont79 merged 1 commit into
mainfrom
docs/onboarding
Jul 2, 2026
Merged

Tbeaumont79 merged 1 commit into
mainfrom
docs/onboarding

Conversation

@Tbeaumont79

Copy link
Copy Markdown
Owner

Doc d'onboarding pour rendre un dev autonome rapidement et assurer la maintenabilité humaine du projet.

Contenu — docs/onboarding/ (10 fichiers)

# Fichier Sujet
— README.md Index + projet en 30 s + garde-fou « honnêteté »
01 01-demarrage.md Install, .env, run, login magic-link, piège Stripe local, scripts, gate
02 02-architecture.md Monorepo, server/, cycle d'une requête, modèle d'auth opt-in
03 03-modele-de-donnees.md Schéma Prisma modèle par modèle, soft-delete, ledger
04 04-backend-api.md Tous les endpoints (méthode/route/auth/rôle), utils, patron d'endpoint
05 05-frontend.md Pages, composants, composables, layout, i18n, styling
06 06-pipeline-candidature.md Cœur métier LLM : analyze→generate + garde-fou de provenance
07 07-billing-credits.md Stripe, ledger de crédits, webhook signé, pièges de test local
08 08-securite.md Résumé opérationnel + réflexes (renvoie à SECURITY-AUDIT.md)
09 09-conventions.md Règles d'ingé, tests, CI/gate, garde-fous produit, « où ajouter quoi »

Méthode

Écrit à partir d'une lecture réelle du code (schéma Prisma, @cvo/shared, services LLM, endpoints) + relevés en deep-dive. Factuel, orienté junior, avec les pièges concrets rencontrés.

Note : la doc relève un écart mémoire/code — FREE_GENERATIONS = 5 dans le code (et non 2). Signalé dans 05-frontend.md.

🤖 Generated with Claude Code

Dossier docs/onboarding/ (10 fichiers) documentant le projet pour un dev qui
arrive, orienté maintenabilité humaine :

- README (index) + 01 démarrage, 02 architecture, 03 modèle de données,
  04 backend & API (tous les endpoints), 05 frontend, 06 pipeline candidature
  (LLM + garde-fou provenance), 07 billing & crédits, 08 sécurité, 09 conventions.
- Factuel (lu dans le code), avec les pièges réels (Stripe listen, provenance,
  fail-fast secret) et un « où ajouter quoi ».

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@netlify

netlify Bot commented Jul 2, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for monumental-speculoos-a69398 ready!

Name Link
🔨 Latest commit 7585803
🔍 Latest deploy log https://app.netlify.com/projects/monumental-speculoos-a69398/deploys/6a4683292b50610008af4da2
😎 Deploy Preview https://deploy-preview-26--monumental-speculoos-a69398.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Tbeaumont79, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 23 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fc7ae77a-a9a5-43e0-a972-b843245c5e1e

📥 Commits

Reviewing files that changed from the base of the PR and between 24aeb6f and 7585803.

📒 Files selected for processing (10)
  • docs/onboarding/01-demarrage.md
  • docs/onboarding/02-architecture.md
  • docs/onboarding/03-modele-de-donnees.md
  • docs/onboarding/04-backend-api.md
  • docs/onboarding/05-frontend.md
  • docs/onboarding/06-pipeline-candidature.md
  • docs/onboarding/07-billing-credits.md
  • docs/onboarding/08-securite.md
  • docs/onboarding/09-conventions.md
  • docs/onboarding/README.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/onboarding

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Tbeaumont79
Tbeaumont79 merged commit 030b13a into main Jul 2, 2026
5 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant