Senior Fullstack
Fullstack development skill with project scaffolding and code quality analysis tools.
Table of Contents
Trigger Phrases
Use this skill when you hear:
- "scaffold a new project"
- "create a Next.js app"
- "set up FastAPI with React"
- "analyze code quality"
- "check for security issues in codebase"
- "what stack should I use"
- "set up a fullstack project"
- "generate project boilerplate"
Tools
Project Scaffolder
Generates fullstack project structures with boilerplate code.
Supported Templates:
nextjs - Next.js 14+ with App Router, TypeScript, Tailwind CSS
fastapi-react - FastAPI backend + React frontend + PostgreSQL
mern - MongoDB, Express, React, Node.js with TypeScript
django-react - Django REST Framework + React frontend
Usage:
# List available templates
python scripts/project_scaffolder.py --list-templates
# Create Next.js project
python scripts/project_scaffolder.py nextjs my-app
# Create FastAPI + React project
python scripts/project_scaffolder.py fastapi-react my-api
# Create MERN stack project
python scripts/project_scaffolder.py mern my-project
# Create Django + React project
python scripts/project_scaffolder.py django-react my-app
# Specify output directory
python scripts/project_scaffolder.py nextjs my-app --output ./projects
# JSON output
python scripts/project_scaffolder.py nextjs my-app --json
Parameters:
| Parameter |
Description |
template |
Template name (nextjs, fastapi-react, mern, django-react) |
project_name |
Name for the new project directory |
--output, -o |
Output directory (default: current directory) |
--list-templates, -l |
List all available templates |
--json |
Output in JSON format |
Output includes:
- Project structure with all necessary files
- Package configurations (package.json, requirements.txt)
- TypeScript configuration
- Docker and docker-compose setup
- Environment file templates
- Next steps for running the project
Code Quality Analyzer
Analyzes fullstack codebases for quality issues.
Analysis Categories:
- Security vulnerabilities (hardcoded secrets, injection risks)
- Code complexity metrics (cyclomatic complexity, nesting depth)
- Dependency health (outdated packages, known CVEs)
- Test coverage estimation
- Documentation quality
Usage:
# Analyze current directory
python scripts/code_quality_analyzer.py .
# Analyze specific project
python scripts/code_quality_analyzer.py /path/to/project
# Verbose output with detailed findings
python scripts/code_quality_analyzer.py . --verbose
# JSON output
python scripts/code_quality_analyzer.py . --json
# Save report to file
python scripts/code_quality_analyzer.py . --output report.json
Parameters:
| Parameter |
Description |
project_path |
Path to project directory (default: current directory) |
--verbose, -v |
Show detailed findings |
--json |
Output in JSON format |
--output, -o |
Write report to file |
Output includes:
- Overall score (0-100) with letter grade
- Security issues by severity (critical, high, medium, low)
- High complexity files
- Vulnerable dependencies with CVE references
- Test coverage estimate
- Documentation completeness
- Prioritized recommendations
Sample Output:
============================================================
CODE QUALITY ANALYSIS REPORT
============================================================
Overall Score: 75/100 (Grade: C)
Files Analyzed: 45
Total Lines: 12,500
--- SECURITY ---
Critical: 1
High: 2
Medium: 5
--- COMPLEXITY ---
Average Complexity: 8.5
High Complexity Files: 3
--- RECOMMENDATIONS ---
1. [P0] SECURITY
Issue: Potential hardcoded secret detected
Action: Remove or secure sensitive data at line 42
Workflows
Workflow 1: Start New Project
- Choose appropriate stack based on requirements (see Stack Decision Matrix)
- Scaffold project structure
- Verify scaffold: confirm
package.json (or requirements.txt) exists
- Run initial quality check — address any P0 issues before proceeding
- Set up development environment
# 1. Scaffold project
python scripts/project_scaffolder.py nextjs my-saas-app
# 2. Verify scaffold succeeded
ls my-saas-app/package.json
# 3. Navigate and install
cd my-saas-app
npm install
# 4. Configure environment
cp .env.example .env.local
# 5. Run quality check
python ../scripts/code_quality_analyzer.py .
# 6. Start development
npm run dev
Workflow 2: Audit Existing Codebase
- Run code quality analysis
- Review security findings — fix all P0 (critical) issues immediately
- Re-run analyzer to confirm P0 issues are resolved
- Create tickets for P1/P2 issues
# 1. Full analysis
python scripts/code_quality_analyzer.py /path/to/project --verbose
# 2. Generate detailed report
python scripts/code_quality_analyzer.py /path/to/project --json --output audit.json
# 3. After fixing P0 issues, re-run to verify
python scripts/code_quality_analyzer.py /path/to/project --verbose
Workflow 3: Stack Selection
Use the tech stack guide to evaluate options:
- SEO Required? → Next.js with SSR
- API-heavy backend? → Separate FastAPI or NestJS
- Real-time features? → Add WebSocket layer
- Team expertise → Match stack to team skills
See references/tech_stack_guide.md for detailed comparison.
Reference Guides
Architecture Patterns (references/architecture_patterns.md)
- Frontend component architecture (Atomic Design, Container/Presentational)
- Backend patterns (Clean Architecture, Repository Pattern)
- API design (REST conventions, GraphQL schema design)
- Database patterns (connection pooling, transactions, read replicas)
- Caching strategies (cache-aside, HTTP cache headers)
- Authentication architecture (JWT + refresh tokens, sessions)
Development Workflows (references/development_workflows.md)
- Local development setup (Docker Compose, environment config)
- Git workflows (trunk-based, conventional commits)
- CI/CD pipelines (GitHub Actions examples)
- Testing strategies (unit, integration, E2E)
- Code review process (PR templates, checklists)
- Deployment strategies (blue-green, canary, feature flags)
- Monitoring and observability (logging, metrics, health checks)
Tech Stack Guide (references/tech_stack_guide.md)
- Frontend frameworks comparison (Next.js, React+Vite, Vue)
- Backend frameworks (Express, Fastify, NestJS, FastAPI, Django)
- Database selection (PostgreSQL, MongoDB, Redis)
- ORMs (Prisma, Drizzle, SQLAlchemy)
- Authentication solutions (Auth.js, Clerk, custom JWT)
- Deployment platforms (Vercel, Railway, AWS)
- Stack recommendations by use case (MVP, SaaS, Enterprise)
Quick Reference
Stack Decision Matrix
| Requirement |
Recommendation |
| SEO-critical site |
Next.js with SSR |
| Internal dashboard |
React + Vite |
| API-first backend |
FastAPI or Fastify |
| Enterprise scale |
NestJS + PostgreSQL |
| Rapid prototype |
Next.js API routes |
| Document-heavy data |
MongoDB |
| Complex queries |
PostgreSQL |
Common Issues
| Issue |
Solution |
| N+1 queries |
Use DataLoader or eager loading |
| Slow builds |
Check bundle size, lazy load |
| Auth complexity |
Use Auth.js or Clerk |
| Type errors |
Enable strict mode in tsconfig |
| CORS issues |
Configure middleware properly |
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: senior-fullstack-53description: 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. Use when this capability is needed.4---56# Senior Fullstack78Fullstack development skill with project scaffolding and code quality analysis tools.910---1112## Table of Contents1314- [Trigger Phrases](#trigger-phrases)15- [Tools](#tools)16- [Workflows](#workflows)17- [Reference Guides](#reference-guides)1819---2021## Trigger Phrases2223Use this skill when you hear:24- "scaffold a new project"25- "create a Next.js app"26- "set up FastAPI with React"27- "analyze code quality"28- "check for security issues in codebase"29- "what stack should I use"30- "set up a fullstack project"31- "generate project boilerplate"3233---3435## Tools3637### Project Scaffolder3839Generates fullstack project structures with boilerplate code.4041**Supported Templates:**42- `nextjs` - Next.js 14+ with App Router, TypeScript, Tailwind CSS43- `fastapi-react` - FastAPI backend + React frontend + PostgreSQL44- `mern` - MongoDB, Express, React, Node.js with TypeScript45- `django-react` - Django REST Framework + React frontend4647**Usage:**4849```bash50# List available templates51python scripts/project_scaffolder.py --list-templates5253# Create Next.js project54python scripts/project_scaffolder.py nextjs my-app5556# Create FastAPI + React project57python scripts/project_scaffolder.py fastapi-react my-api5859# Create MERN stack project60python scripts/project_scaffolder.py mern my-project6162# Create Django + React project63python scripts/project_scaffolder.py django-react my-app6465# Specify output directory66python scripts/project_scaffolder.py nextjs my-app --output ./projects6768# JSON output69python scripts/project_scaffolder.py nextjs my-app --json70```7172**Parameters:**7374| Parameter | Description |75|-----------|-------------|76| `template` | Template name (nextjs, fastapi-react, mern, django-react) |77| `project_name` | Name for the new project directory |78| `--output, -o` | Output directory (default: current directory) |79| `--list-templates, -l` | List all available templates |80| `--json` | Output in JSON format |8182**Output includes:**83- Project structure with all necessary files84- Package configurations (package.json, requirements.txt)85- TypeScript configuration86- Docker and docker-compose setup87- Environment file templates88- Next steps for running the project8990---9192### Code Quality Analyzer9394Analyzes fullstack codebases for quality issues.9596**Analysis Categories:**97- Security vulnerabilities (hardcoded secrets, injection risks)98- Code complexity metrics (cyclomatic complexity, nesting depth)99- Dependency health (outdated packages, known CVEs)100- Test coverage estimation101- Documentation quality102103**Usage:**104105```bash106# Analyze current directory107python scripts/code_quality_analyzer.py .108109# Analyze specific project110python scripts/code_quality_analyzer.py /path/to/project111112# Verbose output with detailed findings113python scripts/code_quality_analyzer.py . --verbose114115# JSON output116python scripts/code_quality_analyzer.py . --json117118# Save report to file119python scripts/code_quality_analyzer.py . --output report.json120```121122**Parameters:**123124| Parameter | Description |125|-----------|-------------|126| `project_path` | Path to project directory (default: current directory) |127| `--verbose, -v` | Show detailed findings |128| `--json` | Output in JSON format |129| `--output, -o` | Write report to file |130131**Output includes:**132- Overall score (0-100) with letter grade133- Security issues by severity (critical, high, medium, low)134- High complexity files135- Vulnerable dependencies with CVE references136- Test coverage estimate137- Documentation completeness138- Prioritized recommendations139140**Sample Output:**141142```143============================================================144CODE QUALITY ANALYSIS REPORT145============================================================146147Overall Score: 75/100 (Grade: C)148Files Analyzed: 45149Total Lines: 12,500150151--- SECURITY ---152 Critical: 1153 High: 2154 Medium: 5155156--- COMPLEXITY ---157 Average Complexity: 8.5158 High Complexity Files: 3159160--- RECOMMENDATIONS ---1611. [P0] SECURITY162 Issue: Potential hardcoded secret detected163 Action: Remove or secure sensitive data at line 42164```165166---167168## Workflows169170### Workflow 1: Start New Project1711721. Choose appropriate stack based on requirements (see Stack Decision Matrix)1732. Scaffold project structure1743. Verify scaffold: confirm `package.json` (or `requirements.txt`) exists1754. Run initial quality check — address any P0 issues before proceeding1765. Set up development environment177178```bash179# 1. Scaffold project180python scripts/project_scaffolder.py nextjs my-saas-app181182# 2. Verify scaffold succeeded183ls my-saas-app/package.json184185# 3. Navigate and install186cd my-saas-app187npm install188189# 4. Configure environment190cp .env.example .env.local191192# 5. Run quality check193python ../scripts/code_quality_analyzer.py .194195# 6. Start development196npm run dev197```198199### Workflow 2: Audit Existing Codebase2002011. Run code quality analysis2022. Review security findings — fix all P0 (critical) issues immediately2033. Re-run analyzer to confirm P0 issues are resolved2044. Create tickets for P1/P2 issues205206```bash207# 1. Full analysis208python scripts/code_quality_analyzer.py /path/to/project --verbose209210# 2. Generate detailed report211python scripts/code_quality_analyzer.py /path/to/project --json --output audit.json212213# 3. After fixing P0 issues, re-run to verify214python scripts/code_quality_analyzer.py /path/to/project --verbose215```216217### Workflow 3: Stack Selection218219Use the tech stack guide to evaluate options:2202211. **SEO Required?** → Next.js with SSR2222. **API-heavy backend?** → Separate FastAPI or NestJS2233. **Real-time features?** → Add WebSocket layer2244. **Team expertise** → Match stack to team skills225226See `references/tech_stack_guide.md` for detailed comparison.227228---229230## Reference Guides231232### Architecture Patterns (`references/architecture_patterns.md`)233234- Frontend component architecture (Atomic Design, Container/Presentational)235- Backend patterns (Clean Architecture, Repository Pattern)236- API design (REST conventions, GraphQL schema design)237- Database patterns (connection pooling, transactions, read replicas)238- Caching strategies (cache-aside, HTTP cache headers)239- Authentication architecture (JWT + refresh tokens, sessions)240241### Development Workflows (`references/development_workflows.md`)242243- Local development setup (Docker Compose, environment config)244- Git workflows (trunk-based, conventional commits)245- CI/CD pipelines (GitHub Actions examples)246- Testing strategies (unit, integration, E2E)247- Code review process (PR templates, checklists)248- Deployment strategies (blue-green, canary, feature flags)249- Monitoring and observability (logging, metrics, health checks)250251### Tech Stack Guide (`references/tech_stack_guide.md`)252253- Frontend frameworks comparison (Next.js, React+Vite, Vue)254- Backend frameworks (Express, Fastify, NestJS, FastAPI, Django)255- Database selection (PostgreSQL, MongoDB, Redis)256- ORMs (Prisma, Drizzle, SQLAlchemy)257- Authentication solutions (Auth.js, Clerk, custom JWT)258- Deployment platforms (Vercel, Railway, AWS)259- Stack recommendations by use case (MVP, SaaS, Enterprise)260261---262263## Quick Reference264265### Stack Decision Matrix266267| Requirement | Recommendation |268|-------------|---------------|269| SEO-critical site | Next.js with SSR |270| Internal dashboard | React + Vite |271| API-first backend | FastAPI or Fastify |272| Enterprise scale | NestJS + PostgreSQL |273| Rapid prototype | Next.js API routes |274| Document-heavy data | MongoDB |275| Complex queries | PostgreSQL |276277### Common Issues278279| Issue | Solution |280|-------|----------|281| N+1 queries | Use DataLoader or eager loading |282| Slow builds | Check bundle size, lazy load |283| Auth complexity | Use Auth.js or Clerk |284| Type errors | Enable strict mode in tsconfig |285| CORS issues | Configure middleware properly |286287---288> Converted and distributed by [TomeVault](https://tomevault.io/claim/alirezarezvani) — claim your Tome and manage your conversions.289<!-- tomevault:4.0:skill_md:2026-04-11 -->