codeprobe-framework

Standalone Mode

If invoked directly (not via the orchestrator), you must first:

1. Read ../codeprobe/shared-preamble.md (resolve relative to this SKILL.md's location — the sibling codeprobe skill directory — not the user's project) for the output contract, execution modes, and constraints.
2. Load applicable reference files from ../codeprobe/references/ (same resolution) based on the project's tech stack.
3. Default to full mode unless the user specifies otherwise.

Framework-Specific Best Practices

Domain Scope

This sub-skill detects framework-specific anti-patterns and convention violations. Unlike other sub-skills that apply universal principles, this one loads framework-specific reference guides and checks against framework idioms.

Supported frameworks:

1. PHP / Laravel — Eloquent ORM, routing, validation, queues, events, configuration
2. React / Next.js — Component design, hooks, data fetching, type safety
3. Python / Django / FastAPI — PEP conventions, ORM patterns, async handling

Important: If no supported framework is detected at the target path, emit zero findings and return an empty summary with a note: "No supported framework detected — skipping framework-specific checks."

Version Awareness: When checking framework conventions, attempt to determine the framework version:

• Laravel: check composer.json for laravel/framework version. Laravel 9+ uses attribute-based accessors instead of getXAttribute().
• Next.js: check next.config.* and package.json for Next.js version. 13+ uses App Router with app/ directory.
• Django: check requirements.txt or setup.py for Django version.

---

What It Does NOT Flag

• Issues already covered by other sub-skills even if they appear in framework code. Specifically:
  • Security issues in framework code → covered by codeprobe-security (SEC)
  • SOLID violations in framework classes → covered by codeprobe-solid (SRP/OCP/etc.)
  • Performance issues like N+1 queries → covered by codeprobe-performance (PERF)
  • Error handling in framework middleware → covered by codeprobe-error-handling (ERR)
• This sub-skill focuses exclusively on framework idiom violations — using the framework incorrectly or ignoring its conventions.
• When this sub-skill and another sub-skill flag the same file:line range, the orchestrator's deduplication step (Section 7A) will keep the finding in whichever category is most relevant and mark the framework finding as a duplicate.
• Framework-generated boilerplate files (migration stubs, config defaults, scaffolded controllers).
• Intentional deviations from framework conventions with clear comments explaining the reason.
• Test files — test-specific framework usage has different conventions.