domains / software-engineering / fullstack-implementation-and-audit / senior-fullstack

senior-fullstack

Skill card

combined

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.

Repositories

Other copies

Combined skill

# Senior Full-Stack

## When to Use
Use when a feature spans the browser, backend service, and database; when reviewing an existing full-stack implementation for integration gaps; when scaffolding a new full-stack project; or when auditing a codebase for quality and security issues.

## Workflow

### 1. Inspect or Select the Stack
- For existing projects: inspect the actual stack, build commands, and conventions. Trace one user journey through interface state, API request, authorization, data access, and response handling.
- For new projects: choose a stack using the decision matrix (e.g., Next.js for SEO/SSR, FastAPI for API-heavy backends, MERN for MongoDB-centric apps, Django for Python-centric backends).

### 2. Define Contracts and Boundaries
- Define the request/response contract, permission checks, input validation, and failure states before changing code.
- Keep database migrations and external side effects explicit.

### 3. Scaffold or Implement
- For new projects: scaffold the project structure using the project scaffolder for the chosen template (nextjs, fastapi-react, mern, django-react). Verify the scaffold by confirming key files exist (e.g., package.json, requirements.txt).
- For existing projects: implement the smallest coherent slice using existing dependencies. Separate interface presentation, domain logic, and persistence; use parameterized queries and server-side authorization.

### 4. Analyze and Verify
- Run project-owned checks for the changed behavior: unit tests for rules, integration tests for permissions and persistence, and browser tests for the complete journey. Record which checks actually ran and any missing environments.
- For audits: run the code quality analyzer to assess security vulnerabilities, code complexity, dependency health, test coverage, and documentation quality. Review security findings and fix all P0 (critical) issues immediately. Re-run the analyzer to confirm P0 issues are resolved. Create tickets for P1/P2 issues.

### 5. Plan and Deploy
- Prepare a migration, rollback, and release plan where needed. Dependency installation, destructive data changes, external notifications, and deployments require authorization appropriate to that action.
- Do not create a paid subscription or modify production resources merely to test the interface.

## Conflicts
- sickn33/agentic-awesome-skills states that the bundled Python helpers are unimplemented historical skeletons that intentionally fail and do not scaffold, analyze quality, or certify a project; use the project's real tools and do not report an empty findings list as a clean audit.
- LeoYeAI/openclaw-master-skills presents project_scaffolder.py and code_quality_analyzer.py as working tools with specific usage examples, parameters, and output formats for scaffolding projects and analyzing code quality.

## Limitations
- 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.