Note: Bundled scripts ship as Markdown reference (.md) — copy the code out of the .md file to run it.
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 |
Creator: Engineering Team
License: MIT
Source Repo: neekware/dojo-skills
Source Bucket: engineering-team
Original Path: engineering-team/senior-fullstack
1---2name: senior-fullstack-23description: > **Note:** Bundled scripts ship as Markdown reference (`.md`) — copy the code out of the `.md` file to run it.4---5> **Note:** Bundled scripts ship as Markdown reference (`.md`) — copy the code out of the `.md` file to run it.67# Senior Fullstack89Fullstack development skill with project scaffolding and code quality analysis tools.1011---1213## Table of Contents1415- [Trigger Phrases](#trigger-phrases)16- [Tools](#tools)17- [Workflows](#workflows)18- [Reference Guides](#reference-guides)1920---2122## Trigger Phrases2324Use this skill when you hear:2526- "scaffold a new project"27- "create a Next.js app"28- "set up FastAPI with React"29- "analyze code quality"30- "check for security issues in codebase"31- "what stack should I use"32- "set up a fullstack project"33- "generate project boilerplate"3435---3637## Tools3839### Project Scaffolder4041Generates fullstack project structures with boilerplate code.4243**Supported Templates:**4445- `nextjs` - Next.js 14+ with App Router, TypeScript, Tailwind CSS46- `fastapi-react` - FastAPI backend + React frontend + PostgreSQL47- `mern` - MongoDB, Express, React, Node.js with TypeScript48- `django-react` - Django REST Framework + React frontend4950**Usage:**5152```bash53# List available templates54python scripts/project_scaffolder.py --list-templates5556# Create Next.js project57python scripts/project_scaffolder.py nextjs my-app5859# Create FastAPI + React project60python scripts/project_scaffolder.py fastapi-react my-api6162# Create MERN stack project63python scripts/project_scaffolder.py mern my-project6465# Create Django + React project66python scripts/project_scaffolder.py django-react my-app6768# Specify output directory69python scripts/project_scaffolder.py nextjs my-app --output ./projects7071# JSON output72python scripts/project_scaffolder.py nextjs my-app --json73```7475**Parameters:**7677| Parameter | Description |78| ---------------------- | --------------------------------------------------------- |79| `template` | Template name (nextjs, fastapi-react, mern, django-react) |80| `project_name` | Name for the new project directory |81| `--output, -o` | Output directory (default: current directory) |82| `--list-templates, -l` | List all available templates |83| `--json` | Output in JSON format |8485**Output includes:**8687- Project structure with all necessary files88- Package configurations (package.json, requirements.txt)89- TypeScript configuration90- Docker and docker-compose setup91- Environment file templates92- Next steps for running the project9394---9596### Code Quality Analyzer9798Analyzes fullstack codebases for quality issues.99100**Analysis Categories:**101102- Security vulnerabilities (hardcoded secrets, injection risks)103- Code complexity metrics (cyclomatic complexity, nesting depth)104- Dependency health (outdated packages, known CVEs)105- Test coverage estimation106- Documentation quality107108**Usage:**109110```bash111# Analyze current directory112python scripts/code_quality_analyzer.py .113114# Analyze specific project115python scripts/code_quality_analyzer.py /path/to/project116117# Verbose output with detailed findings118python scripts/code_quality_analyzer.py . --verbose119120# JSON output121python scripts/code_quality_analyzer.py . --json122123# Save report to file124python scripts/code_quality_analyzer.py . --output report.json125```126127**Parameters:**128129| Parameter | Description |130| --------------- | ------------------------------------------------------ |131| `project_path` | Path to project directory (default: current directory) |132| `--verbose, -v` | Show detailed findings |133| `--json` | Output in JSON format |134| `--output, -o` | Write report to file |135136**Output includes:**137138- Overall score (0-100) with letter grade139- Security issues by severity (critical, high, medium, low)140- High complexity files141- Vulnerable dependencies with CVE references142- Test coverage estimate143- Documentation completeness144- Prioritized recommendations145146**Sample Output:**147148```149============================================================150CODE QUALITY ANALYSIS REPORT151============================================================152153Overall Score: 75/100 (Grade: C)154Files Analyzed: 45155Total Lines: 12,500156157--- SECURITY ---158 Critical: 1159 High: 2160 Medium: 5161162--- COMPLEXITY ---163 Average Complexity: 8.5164 High Complexity Files: 3165166--- RECOMMENDATIONS ---1671. [P0] SECURITY168 Issue: Potential hardcoded secret detected169 Action: Remove or secure sensitive data at line 42170```171172---173174## Workflows175176### Workflow 1: Start New Project1771781. Choose appropriate stack based on requirements (see Stack Decision Matrix)1792. Scaffold project structure1803. Verify scaffold: confirm `package.json` (or `requirements.txt`) exists1814. Run initial quality check — address any P0 issues before proceeding1825. Set up development environment183184```bash185# 1. Scaffold project186python scripts/project_scaffolder.py nextjs my-saas-app187188# 2. Verify scaffold succeeded189ls my-saas-app/package.json190191# 3. Navigate and install192cd my-saas-app193npm install194195# 4. Configure environment196cp .env.example .env.local197198# 5. Run quality check199python ../scripts/code_quality_analyzer.py .200201# 6. Start development202npm run dev203```204205### Workflow 2: Audit Existing Codebase2062071. Run code quality analysis2082. Review security findings — fix all P0 (critical) issues immediately2093. Re-run analyzer to confirm P0 issues are resolved2104. Create tickets for P1/P2 issues211212```bash213# 1. Full analysis214python scripts/code_quality_analyzer.py /path/to/project --verbose215216# 2. Generate detailed report217python scripts/code_quality_analyzer.py /path/to/project --json --output audit.json218219# 3. After fixing P0 issues, re-run to verify220python scripts/code_quality_analyzer.py /path/to/project --verbose221```222223### Workflow 3: Stack Selection224225Use the tech stack guide to evaluate options:2262271. **SEO Required?** → Next.js with SSR2282. **API-heavy backend?** → Separate FastAPI or NestJS2293. **Real-time features?** → Add WebSocket layer2304. **Team expertise** → Match stack to team skills231232See `references/tech_stack_guide.md` for detailed comparison.233234---235236## Reference Guides237238### Architecture Patterns (`references/architecture_patterns.md`)239240- Frontend component architecture (Atomic Design, Container/Presentational)241- Backend patterns (Clean Architecture, Repository Pattern)242- API design (REST conventions, GraphQL schema design)243- Database patterns (connection pooling, transactions, read replicas)244- Caching strategies (cache-aside, HTTP cache headers)245- Authentication architecture (JWT + refresh tokens, sessions)246247### Development Workflows (`references/development_workflows.md`)248249- Local development setup (Docker Compose, environment config)250- Git workflows (trunk-based, conventional commits)251- CI/CD pipelines (GitHub Actions examples)252- Testing strategies (unit, integration, E2E)253- Code review process (PR templates, checklists)254- Deployment strategies (blue-green, canary, feature flags)255- Monitoring and observability (logging, metrics, health checks)256257### Tech Stack Guide (`references/tech_stack_guide.md`)258259- Frontend frameworks comparison (Next.js, React+Vite, Vue)260- Backend frameworks (Express, Fastify, NestJS, FastAPI, Django)261- Database selection (PostgreSQL, MongoDB, Redis)262- ORMs (Prisma, Drizzle, SQLAlchemy)263- Authentication solutions (Auth.js, Clerk, custom JWT)264- Deployment platforms (Vercel, Railway, AWS)265- Stack recommendations by use case (MVP, SaaS, Enterprise)266267---268269## Quick Reference270271### Stack Decision Matrix272273| Requirement | Recommendation |274| ------------------- | ------------------- |275| SEO-critical site | Next.js with SSR |276| Internal dashboard | React + Vite |277| API-first backend | FastAPI or Fastify |278| Enterprise scale | NestJS + PostgreSQL |279| Rapid prototype | Next.js API routes |280| Document-heavy data | MongoDB |281| Complex queries | PostgreSQL |282283### Common Issues284285| Issue | Solution |286| --------------- | ------------------------------- |287| N+1 queries | Use DataLoader or eager loading |288| Slow builds | Check bundle size, lazy load |289| Auth complexity | Use Auth.js or Clerk |290| Type errors | Enable strict mode in tsconfig |291| CORS issues | Configure middleware properly |292293> **Creator:** Engineering Team294> **License:** MIT295> **Source Repo:** `neekware/dojo-skills`296> **Source Bucket:** `engineering-team`297> **Original Path:** `engineering-team/senior-fullstack`