domains / families / software-engineering / senior-fullstack

senior-fullstack

combined

Fullstack development toolkit with project scaffolding for Next.js, FastAPI, MERN, and Django stacks, code quality analysis with security and complexity scoring, and stack selection guidance. Use when the user asks to "scaffold a new project", "create a Next.js app", "set up FastAPI with React", "analyze code quality", "audit my codebase", "what stack should I use", "generate project boilerplate", or mentions fullstack development, project setup, or tech stack comparison. Coordinate full-stack implementation across interface, service, database and delivery boundaries using the existing project stack and verified checks.

When to use

• Use when a feature spans the browser, backend service and database, or when reviewing an existing full-stack implementation for integration gaps.

When not to use

• Stack and provider compatibility must be checked in the actual project.
• The references are review checklists, not complete application templates.
• Passing a subset of tests does not prove security, performance or deployment readiness.
• Do not infer permission to change accounts, billing or production resources from a request for a code review.

Skill page

Conflict

The two copies describe different procedures for the same skill name. The first copy is a review and implementation workflow that inspects an existing stack, defines contracts, implements a slice, runs project-owned checks, and plans migrations/rollbacks; it explicitly states its bundled Python helpers are unimplemented skeletons and warns against reporting empty findings as clean. The second copy is a toolkit workflow that scaffolds new projects (Next.js, FastAPI, MERN, Django) and runs a code quality analyzer with scoring, security findings, and stack selection guidance. Each has material steps the other lacks, and they disagree on whether the Python helpers are usable, so crowning one would hide a real alternative.