[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78HWS1Y3ZFZ3K5JS99JNSSP":3,"skill-same:01M78HWS1Y3ZFZ3K5JS99JNSSP":97},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M78HWS1Y3ZFZ3K5JS99JNSSP","senior-fullstack",null,"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.","aneeba-pixel\u002Fclaude-skills","aneeba-pixel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F218186338?v=4","01M78GRXBTG70217SH410P543Y","Aneeba Saeed","01M78GRXCDZ6TA0F8H2CZMDGSS",0,"MIT","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"senior-fullstack\"\ndescription: 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.\n---\n\n# Senior Fullstack\n\nFullstack development skill with project scaffolding and code quality analysis tools.\n\n---\n\n## Table of Contents\n\n- [Trigger Phrases](#trigger-phrases)\n- [Tools](#tools)\n- [Workflows](#workflows)\n- [Reference Guides](#reference-guides)\n\n---\n\n## Trigger Phrases\n\nUse this skill when you hear:\n- \"scaffold a new project\"\n- \"create a Next.js app\"\n- \"set up FastAPI with React\"\n- \"analyze code quality\"\n- \"check for security issues in codebase\"\n- \"what stack should I use\"\n- \"set up a fullstack project\"\n- \"generate project boilerplate\"\n\n---\n\n## Tools\n\n### Decision Engine\n\nDeterministic profile picker. Given four assumptions (team-size, cadence, user-facing, budget) plus optional traffic\u002Fsensitivity inputs, ranks the four built-in profiles and returns the matched profile with SLO floor and named approver chain. Refuses to recommend a profile without the four required inputs.\n\n**Usage:**\n\n```bash\n# See all options\npython scripts\u002Ffullstack_decision_engine.py --help\n\n# Run against a sample input\npython scripts\u002Ffullstack_decision_engine.py --sample\n\n# Pick a profile from real inputs\npython scripts\u002Ffullstack_decision_engine.py \\\n    --team-size-12mo 8 --cadence daily --user-facing true --budget 5000 \\\n    --traffic-p99-rps 50 --data-sensitivity pii-only\n\n# JSON output for downstream tools\npython scripts\u002Ffullstack_decision_engine.py --sample --output json\n```\n\nReturns: matched profile name, score, matched\u002Fviolated constraints, stack recommendation, anti-recommendations, SLO floor, named-approver chain, and canon references.\n\nThe engine encodes the same matrix the conversational grill walks through — use it directly when inputs are already known, or via the `cs-fullstack-engineer` agent for the question-by-question grill.\n\n---\n\n### Project Scaffolder\n\nGenerates fullstack project structures with boilerplate code.\n\n**Supported Templates:**\n- `nextjs` - Next.js 14+ with App Router, TypeScript, Tailwind CSS\n- `fastapi-react` - FastAPI backend + React frontend + PostgreSQL\n- `mern` - MongoDB, Express, React, Node.js with TypeScript\n- `django-react` - Django REST Framework + React frontend\n\n**Usage:**\n\n```bash\n# List available templates\npython scripts\u002Fproject_scaffolder.py --list-templates\n\n# Create Next.js project\npython scripts\u002Fproject_scaffolder.py nextjs my-app\n\n# Create FastAPI + React project\npython scripts\u002Fproject_scaffolder.py fastapi-react my-api\n\n# Create MERN stack project\npython scripts\u002Fproject_scaffolder.py mern my-project\n\n# Create Django + React project\npython scripts\u002Fproject_scaffolder.py django-react my-app\n\n# Specify output directory\npython scripts\u002Fproject_scaffolder.py nextjs my-app --output .\u002Fprojects\n\n# JSON output\npython scripts\u002Fproject_scaffolder.py nextjs my-app --json\n```\n\n**Parameters:**\n\n| Parameter | Description |\n|-----------|-------------|\n| `template` | Template name (nextjs, fastapi-react, mern, django-react) |\n| `project_name` | Name for the new project directory |\n| `--output, -o` | Output directory (default: current directory) |\n| `--list-templates, -l` | List all available templates |\n| `--json` | Output in JSON format |\n\n**Output includes:**\n- Project structure with all necessary files\n- Package configurations (package.json, requirements.txt)\n- TypeScript configuration\n- Docker and docker-compose setup\n- Environment file templates\n- Next steps for running the project\n\n---\n\n### Code Quality Analyzer\n\nAnalyzes fullstack codebases for quality issues.\n\n**Analysis Categories:**\n- Security vulnerabilities (hardcoded secrets, injection risks)\n- Code complexity metrics (cyclomatic complexity, nesting depth)\n- Dependency health (outdated packages, known CVEs)\n- Test coverage estimation\n- Documentation quality\n\n**Usage:**\n\n```bash\n# Analyze current directory\npython scripts\u002Fcode_quality_analyzer.py .\n\n# Analyze specific project\npython scripts\u002Fcode_quality_analyzer.py \u002Fpath\u002Fto\u002Fproject\n\n# Verbose output with detailed findings\npython scripts\u002Fcode_quality_analyzer.py . --verbose\n\n# JSON output\npython scripts\u002Fcode_quality_analyzer.py . --json\n\n# Save report to file\npython scripts\u002Fcode_quality_analyzer.py . --output report.json\n```\n\n**Parameters:**\n\n| Parameter | Description |\n|-----------|-------------|\n| `project_path` | Path to project directory (default: current directory) |\n| `--verbose, -v` | Show detailed findings |\n| `--json` | Output in JSON format |\n| `--output, -o` | Write report to file |\n\n**Output includes:**\n- Overall score (0-100) with letter grade\n- Security issues by severity (critical, high, medium, low)\n- High complexity files\n- Vulnerable dependencies with CVE references\n- Test coverage estimate\n- Documentation completeness\n- Prioritized recommendations\n\n**Sample Output:**\n\n```\n============================================================\nCODE QUALITY ANALYSIS REPORT\n============================================================\n\nOverall Score: 75\u002F100 (Grade: C)\nFiles Analyzed: 45\nTotal Lines: 12,500\n\n--- SECURITY ---\n  Critical: 1\n  High: 2\n  Medium: 5\n\n--- COMPLEXITY ---\n  Average Complexity: 8.5\n  High Complexity Files: 3\n\n--- RECOMMENDATIONS ---\n1. [P0] SECURITY\n   Issue: Potential hardcoded secret detected\n   Action: Remove or secure sensitive data at line 42\n```\n\n---\n\n## Workflows\n\n### Workflow 1: Start New Project\n\n1. Choose appropriate stack based on requirements (see Stack Decision Matrix)\n2. Scaffold project structure\n3. Verify scaffold: confirm `package.json` (or `requirements.txt`) exists\n4. Run initial quality check — address any P0 issues before proceeding\n5. Set up development environment\n\n```bash\n# 1. Scaffold project\npython scripts\u002Fproject_scaffolder.py nextjs my-saas-app\n\n# 2. Verify scaffold succeeded\nls my-saas-app\u002Fpackage.json\n\n# 3. Navigate and install\ncd my-saas-app\nnpm install\n\n# 4. Configure environment\ncp .env.example .env.local\n\n# 5. Run quality check\npython ..\u002Fscripts\u002Fcode_quality_analyzer.py .\n\n# 6. Start development\nnpm run dev\n```\n\n### Workflow 2: Audit Existing Codebase\n\n1. Run code quality analysis\n2. Review security findings — fix all P0 (critical) issues immediately\n3. Re-run analyzer to confirm P0 issues are resolved\n4. Create tickets for P1\u002FP2 issues\n\n```bash\n# 1. Full analysis\npython scripts\u002Fcode_quality_analyzer.py \u002Fpath\u002Fto\u002Fproject --verbose\n\n# 2. Generate detailed report\npython scripts\u002Fcode_quality_analyzer.py \u002Fpath\u002Fto\u002Fproject --json --output audit.json\n\n# 3. After fixing P0 issues, re-run to verify\npython scripts\u002Fcode_quality_analyzer.py \u002Fpath\u002Fto\u002Fproject --verbose\n```\n\n### Workflow 3: Stack Selection\n\nUse the tech stack guide to evaluate options:\n\n1. **SEO Required?** → Next.js with SSR\n2. **API-heavy backend?** → Separate FastAPI or NestJS\n3. **Real-time features?** → Add WebSocket layer\n4. **Team expertise** → Match stack to team skills\n\nSee `references\u002Ftech_stack_guide.md` for detailed comparison.\n\n---\n\n## Reference Guides\n\n### Architecture Patterns (`references\u002Farchitecture_patterns.md`)\n\n- Frontend component architecture (Atomic Design, Container\u002FPresentational)\n- Backend patterns (Clean Architecture, Repository Pattern)\n- API design (REST conventions, GraphQL schema design)\n- Database patterns (connection pooling, transactions, read replicas)\n- Caching strategies (cache-aside, HTTP cache headers)\n- Authentication architecture (JWT + refresh tokens, sessions)\n\n### Development Workflows (`references\u002Fdevelopment_workflows.md`)\n\n- Local development setup (Docker Compose, environment config)\n- Git workflows (trunk-based, conventional commits)\n- CI\u002FCD pipelines (GitHub Actions examples)\n- Testing strategies (unit, integration, E2E)\n- Code review process (PR templates, checklists)\n- Deployment strategies (blue-green, canary, feature flags)\n- Monitoring and observability (logging, metrics, health checks)\n\n### Tech Stack Guide (`references\u002Ftech_stack_guide.md`)\n\n- Frontend frameworks comparison (Next.js, React+Vite, Vue)\n- Backend frameworks (Express, Fastify, NestJS, FastAPI, Django)\n- Database selection (PostgreSQL, MongoDB, Redis)\n- ORMs (Prisma, Drizzle, SQLAlchemy)\n- Authentication solutions (Auth.js, Clerk, custom JWT)\n- Deployment platforms (Vercel, Railway, AWS)\n- Stack recommendations by use case (MVP, SaaS, Enterprise)\n\n---\n\n## Quick Reference\n\n### Stack Decision Matrix\n\n| Requirement | Recommendation |\n|-------------|---------------|\n| SEO-critical site | Next.js with SSR |\n| Internal dashboard | React + Vite |\n| API-first backend | FastAPI or Fastify |\n| Enterprise scale | NestJS + PostgreSQL |\n| Rapid prototype | Next.js API routes |\n| Document-heavy data | MongoDB |\n| Complex queries | PostgreSQL |\n\n### Common Issues\n\n| Issue | Solution |\n|-------|----------|\n| N+1 queries | Use DataLoader or eager loading |\n| Slow builds | Check bundle size, lazy load |\n| Auth complexity | Use Auth.js or Clerk |\n| Type errors | Enable strict mode in tsconfig |\n| CORS issues | Configure middleware properly |\n\n---\n\n## Assumptions and Verifiable Success Criteria (Karpathy discipline)\n\nBefore this skill scaffolds, recommends, or modifies any code, the following four assumptions MUST be surfaced. If any are unknown, the skill stops and walks the [Forcing-question library](#forcing-question-library-matt-pocock-grill) instead.\n\n1. **Team size today + 12-month headcount** — drives architecture (monolith \u002F modular \u002F services). Sam Newman: \"MonolithFirst.\"\n2. **Deployment cadence target** — drives CI\u002FCD spend and feature-flag investment. *Accelerate* (Forsgren et al. 2018).\n3. **User-facing vs. internal vs. marketing-site** — drives stack pick and a11y\u002Fperf budget.\n4. **Monthly cloud + SaaS budget ceiling** — drives the build-vs-managed-service split.\n\n**Verifiable success criteria** (Karpathy #4) — every recommendation this skill emits must include three machine-checkable numbers:\n\n- An API latency target (p50, p95, p99 in ms)\n- A frontend perf target (LCP, INP, CLS on mobile-4G)\n- An uptime \u002F SLO target\n\nIf any of those three is not stated, the recommendation is incomplete — go back to Q7 of the forcing-question library.\n\nThe `scripts\u002Ffullstack_decision_engine.py` tool encodes these checks: it refuses to recommend a profile without all four assumption inputs and prints the verifiable thresholds for the matched profile.\n\n---\n\n## Customization profiles\n\nFour built-in profiles in `profiles\u002F` calibrate every recommendation:\n\n| Profile | When to pick | Cloud ceiling | Pattern |\n|---|---|---|---|\n| `saas-startup` | \u003C 10 eng, customer-facing, daily+ cadence | $8K\u002Fmo | Modular monolith on Next.js + Postgres |\n| `enterprise-scale` | 50+ eng, regulated, per-PR with gates | $250K\u002Fmo | Domain-bounded services + platform team |\n| `internal-tool` | ≤ 5 eng, auth-walled, \u003C 100 DAU | $500\u002Fmo | Retool-first; thin custom stack if forced |\n| `marketing-site` | SEO-dependent, near-zero write | $200\u002Fmo | Static-first (Astro \u002F 11ty \u002F Next-static) |\n\nPick a profile via:\n\n```bash\npython scripts\u002Ffullstack_decision_engine.py \\\n  --team-size 6 --team-size-12mo 12 \\\n  --cadence daily --user-facing true --budget 5000 \\\n  --traffic-p99-rps 45 --data-sensitivity pii-only\n```\n\nThe tool returns the best-fit profile, the tradeoff against the runner-up (if within 15%), the stack recommendation, the anti-patterns to avoid on that profile, and the named-approver chain. **This tool never auto-approves.**\n\nTo add a custom profile: copy `profiles\u002Fsaas-startup.json` to `profiles\u002F\u003Cyour-org>.json`, adjust the `constraints` and `stack_recommendations` blocks, and rerun. The JSON is the customization surface — no code changes needed.\n\n---\n\n## Composition map\n\nThis skill does NOT reimplement scope owned by the POWERFUL-tier specialists. It forks into them. See `references\u002Fcomposition_map.md` for the full routing table. Key forks:\n\n| Concern | Fork into |\n|---|---|\n| API contract review | `engineering\u002Fskills\u002Fapi-design-reviewer\u002F` |\n| Database schema design | `engineering\u002Fskills\u002Fdatabase-designer\u002F` |\n| Reliability \u002F SLO design | `engineering\u002Fslo-architect\u002F` |\n| CI\u002FCD pipeline | `engineering\u002Fskills\u002Fci-cd-pipeline-builder\u002F` |\n| Performance profiling | `engineering\u002Fskills\u002Fperformance-profiler\u002F` |\n| Pre-commit Karpathy review | `engineering\u002Fkarpathy-coder\u002F` |\n| Pre-flight architecture grill | `engineering\u002Fgrill-me\u002F` |\n\nThe `cs-fullstack-engineer` agent (in `agents\u002Fengineering\u002Fcs-fullstack-engineer.md`) orchestrates these forks via `context: fork`. Invoke it from another agent with `Agent({subagent_type: \"cs-fullstack-engineer\", prompt: \"...\"})` or via the slash command `\u002Fcs:fullstack-review \u003Cyour problem>`.\n\n---\n\n## Forcing-question library (Matt Pocock grill)\n\nBefore locking any architecture or stack decision, walk the seven forcing questions in `references\u002Fforcing_questions.md`. Each has a recommended answer, canon citation, and kill criterion. The discipline:\n\n1. One question per turn. No bundling.\n2. Always recommend the answer with cited canon.\n3. Track answers in a working file (e.g., `\u002Ftmp\u002Ffullstack-grill-\u003Cdate>.md`).\n4. If a kill criterion trips, stop. Do not scaffold around an unresolved gap.\n5. After Q7, run `fullstack_decision_engine.py` with the seven answers as inputs.\n\nSummary of the seven questions (full content in the reference):\n\n1. Team size today + 12-month headcount?\n2. Deployment cadence — per-PR, daily, weekly, quarterly?\n3. Customer-facing, internal tool, or marketing site?\n4. One-year p50 \u002F p99 traffic forecast?\n5. Hiring against the stack or training the team?\n6. Year-one monthly cloud + SaaS ceiling?\n7. Three verifiable success criteria with numeric targets?\n\n---\n\n## Invocation from other agents and skills\n\nThis skill is invokable by any other agent or skill via three surfaces:\n\n1. **Slash command:** `\u002Fcs:fullstack-review \u003Cprompt>` — runs the full grill + decision engine + composition routing.\n2. **Agent subagent:** `Agent({subagent_type: \"cs-fullstack-engineer\", prompt: \"...\"})` — forks context, returns ≤ 200-word digest.\n3. **Direct tool call:** `python scripts\u002Ffullstack_decision_engine.py ...` — deterministic profile match without the conversational grill (use when inputs are already known).\n\nSee `agents\u002Fengineering\u002Fcs-fullstack-engineer.md` for the full invocation contract.\n","# Senior Fullstack\n\nFullstack development skill with project scaffolding and code quality analysis tools.\n\n---\n\n## Table of Contents\n\n- [Trigger Phrases](#trigger-phrases)\n- [Tools](#tools)\n- [Workflows](#workflows)\n- [Reference Guides](#reference-guides)\n\n---\n\n## Trigger Phrases\n\nUse this skill when you hear:\n- \"scaffold a new project\"\n- \"create a Next.js app\"\n- \"set up FastAPI with React\"\n- \"analyze code quality\"\n- \"check for security issues in codebase\"\n- \"what stack should I use\"\n- \"set up a fullstack project\"\n- \"generate project boilerplate\"\n\n---\n\n## Tools\n\n### Decision Engine\n\nDeterministic profile picker. Given four assumptions (team-size, cadence, user-facing, budget) plus optional traffic\u002Fsensitivity inputs, ranks the four built-in profiles and returns the matched profile with SLO floor and named approver chain. Refuses to recommend a profile without the four required inputs.\n\n**Usage:**\n\n```bash\n# See all options\npython scripts\u002Ffullstack_decision_engine.py --help\n\n# Run against a sample input\npython scripts\u002Ffullstack_decision_engine.py --sample\n\n# Pick a profile from real inputs\npython scripts\u002Ffullstack_decision_engine.py \\\n    --team-size-12mo 8 --cadence daily --user-facing true --budget 5000 \\\n    --traffic-p99-rps 50 --data-sensitivity pii-only\n\n# JSON output for downstream tools\npython scripts\u002Ffullstack_decision_engine.py --sample --output json\n```\n\nReturns: matched profile name, score, matched\u002Fviolated constraints, stack recommendation, anti-recommendations, SLO floor, named-approver chain, and canon references.\n\nThe engine encodes the same matrix the conversational grill walks through — use it directly when inputs are already known, or via the `cs-fullstack-engineer` agent for the question-by-question grill.\n\n---\n\n### Project Scaffolder\n\nGenerates fullstack project structures with boilerplate code.\n\n**Supported Templates:**\n- `nextjs` - Next.js 14+ with App Router, TypeScript, Tailwind CSS\n- `fastapi-react` - FastAPI backend + React frontend + PostgreSQL\n- `mern` - MongoDB, Express, React, Node.js with TypeScript\n- `django-react` - Django REST Framework + React frontend\n\n**Usage:**\n\n```bash\n# List available templates\npython scripts\u002Fproject_scaffolder.py --list-templates\n\n# Create Next.js project\npython scripts\u002Fproject_scaffolder.py nextjs my-app\n\n# Create FastAPI + React project\npython scripts\u002Fproject_scaffolder.py fastapi-react my-api\n\n# Create MERN stack project\npython scripts\u002Fproject_scaffolder.py mern my-project\n\n# Create Django + React project\npython scripts\u002Fproject_scaffolder.py django-react my-app\n\n# Specify output directory\npython scripts\u002Fproject_scaffolder.py nextjs my-app --output .\u002Fprojects\n\n# JSON output\npython scripts\u002Fproject_scaffolder.py nextjs my-app --json\n```\n\n**Parameters:**\n\n| Parameter | Description |\n|-----------|-------------|\n| `template` | Template name (nextjs, fastapi-react, mern, django-react) |\n| `project_name` | Name for the new project directory |\n| `--output, -o` | Output directory (default: current directory) |\n| `--list-templates, -l` | List all available templates |\n| `--json` | Output in JSON format |\n\n**Output includes:**\n- Project structure with all necessary files\n- Package configurations (package.json, requirements.txt)\n- TypeScript configuration\n- Docker and docker-compose setup\n- Environment file templates\n- Next steps for running the project\n\n---\n\n### Code Quality Analyzer\n\nAnalyzes fullstack codebases for quality issues.\n\n**Analysis Categories:**\n- Security vulnerabilities (hardcoded secrets, injection risks)\n- Code complexity metrics (cyclomatic complexity, nesting depth)\n- Dependency health (outdated packages, known CVEs)\n- Test coverage estimation\n- Documentation quality\n\n**Usage:**\n\n```bash\n# Analyze current directory\npython scripts\u002Fcode_quality_analyzer.py .\n\n# Analyze specific project\npython scripts\u002Fcode_quality_analyzer.py \u002Fpath\u002Fto\u002Fproject\n\n# Verbose output with detailed findings\npython scripts\u002Fcode_quality_analyzer.py . --verbose\n\n# JSON output\npython scripts\u002Fcode_quality_analyzer.py . --json\n\n# Save report to file\npython scripts\u002Fcode_quality_analyzer.py . --output report.json\n```\n\n**Parameters:**\n\n| Parameter | Description |\n|-----------|-------------|\n| `project_path` | Path to project directory (default: current directory) |\n| `--verbose, -v` | Show detailed findings |\n| `--json` | Output in JSON format |\n| `--output, -o` | Write report to file |\n\n**Output includes:**\n- Overall score (0-100) with letter grade\n- Security issues by severity (critical, high, medium, low)\n- High complexity files\n- Vulnerable dependencies with CVE references\n- Test coverage estimate\n- Documentation completeness\n- Prioritized recommendations\n\n**Sample Output:**\n\n```\n============================================================\nCODE QUALITY ANALYSIS REPORT\n============================================================\n\nOverall Score: 75\u002F100 (Grade: C)\nFiles Analyzed: 45\nTotal Lines: 12,500\n\n--- SECURITY ---\n  Critical: 1\n  High: 2\n  Medium: 5\n\n--- COMPLEXITY ---\n  Average Complexity: 8.5\n  High Complexity Files: 3\n\n--- RECOMMENDATIONS ---\n1. [P0] SECURITY\n   Issue: Potential hardcoded secret detected\n   Action: Remove or secure sensitive data at line 42\n```\n\n---\n\n## Workflows\n\n### Workflow 1: Start New Project\n\n1. Choose appropriate stack based on requirements (see Stack Decision Matrix)\n2. Scaffold project structure\n3. Verify scaffold: confirm `package.json` (or `requirements.txt`) exists\n4. Run initial quality check — address any P0 issues before proceeding\n5. Set up development environment\n\n```bash\n# 1. Scaffold project\npython scripts\u002Fproject_scaffolder.py nextjs my-saas-app\n\n# 2. Verify scaffold succeeded\nls my-saas-app\u002Fpackage.json\n\n# 3. Navigate and install\ncd my-saas-app\nnpm install\n\n# 4. Configure environment\ncp .env.example .env.local\n\n# 5. Run quality check\npython ..\u002Fscripts\u002Fcode_quality_analyzer.py .\n\n# 6. Start development\nnpm run dev\n```\n\n### Workflow 2: Audit Existing Codebase\n\n1. Run code quality analysis\n2. Review security findings — fix all P0 (critical) issues immediately\n3. Re-run analyzer to confirm P0 issues are resolved\n4. Create tickets for P1\u002FP2 issues\n\n```bash\n# 1. Full analysis\npython scripts\u002Fcode_quality_analyzer.py \u002Fpath\u002Fto\u002Fproject --verbose\n\n# 2. Generate detailed report\npython scripts\u002Fcode_quality_analyzer.py \u002Fpath\u002Fto\u002Fproject --json --output audit.json\n\n# 3. After fixing P0 issues, re-run to verify\npython scripts\u002Fcode_quality_analyzer.py \u002Fpath\u002Fto\u002Fproject --verbose\n```\n\n### Workflow 3: Stack Selection\n\nUse the tech stack guide to evaluate options:\n\n1. **SEO Required?** → Next.js with SSR\n2. **API-heavy backend?** → Separate FastAPI or NestJS\n3. **Real-time features?** → Add WebSocket layer\n4. **Team expertise** → Match stack to team skills\n\nSee `references\u002Ftech_stack_guide.md` for detailed comparison.\n\n---\n\n## Reference Guides\n\n### Architecture Patterns (`references\u002Farchitecture_patterns.md`)\n\n- Frontend component architecture (Atomic Design, Container\u002FPresentational)\n- Backend patterns (Clean Architecture, Repository Pattern)\n- API design (REST conventions, GraphQL schema design)\n- Database patterns (connection pooling, transactions, read replicas)\n- Caching strategies (cache-aside, HTTP cache headers)\n- Authentication architecture (JWT + refresh tokens, sessions)\n\n### Development Workflows (`references\u002Fdevelopment_workflows.md`)\n\n- Local development setup (Docker Compose, environment config)\n- Git workflows (trunk-based, conventional commits)\n- CI\u002FCD pipelines (GitHub Actions examples)\n- Testing strategies (unit, integration, E2E)\n- Code review process (PR templates, checklists)\n- Deployment strategies (blue-green, canary, feature flags)\n- Monitoring and observability (logging, metrics, health checks)\n\n### Tech Stack Guide (`references\u002Ftech_stack_guide.md`)\n\n- Frontend frameworks comparison (Next.js, React+Vite, Vue)\n- Backend frameworks (Express, Fastify, NestJS, FastAPI, Django)\n- Database selection (PostgreSQL, MongoDB, Redis)\n- ORMs (Prisma, Drizzle, SQLAlchemy)\n- Authentication solutions (Auth.js, Clerk, custom JWT)\n- Deployment platforms (Vercel, Railway, AWS)\n- Stack recommendations by use case (MVP, SaaS, Enterprise)\n\n---\n\n## Quick Reference\n\n### Stack Decision Matrix\n\n| Requirement | Recommendation |\n|-------------|---------------|\n| SEO-critical site | Next.js with SSR |\n| Internal dashboard | React + Vite |\n| API-first backend | FastAPI or Fastify |\n| Enterprise scale | NestJS + PostgreSQL |\n| Rapid prototype | Next.js API routes |\n| Document-heavy data | MongoDB |\n| Complex queries | PostgreSQL |\n\n### Common Issues\n\n| Issue | Solution |\n|-------|----------|\n| N+1 queries | Use DataLoader or eager loading |\n| Slow builds | Check bundle size, lazy load |\n| Auth complexity | Use Auth.js or Clerk |\n| Type errors | Enable strict mode in tsconfig |\n| CORS issues | Configure middleware properly |\n\n---\n\n## Assumptions and Verifiable Success Criteria (Karpathy discipline)\n\nBefore this skill scaffolds, recommends, or modifies any code, the following four assumptions MUST be surfaced. If any are unknown, the skill stops and walks the [Forcing-question library](#forcing-question-library-matt-pocock-grill) instead.\n\n1. **Team size today + 12-month headcount** — drives architecture (monolith \u002F modular \u002F services). Sam Newman: \"MonolithFirst.\"\n2. **Deployment cadence target** — drives CI\u002FCD spend and feature-flag investment. *Accelerate* (Forsgren et al. 2018).\n3. **User-facing vs. internal vs. marketing-site** — drives stack pick and a11y\u002Fperf budget.\n4. **Monthly cloud + SaaS budget ceiling** — drives the build-vs-managed-service split.\n\n**Verifiable success criteria** (Karpathy #4) — every recommendation this skill emits must include three machine-checkable numbers:\n\n- An API latency target (p50, p95, p99 in ms)\n- A frontend perf target (LCP, INP, CLS on mobile-4G)\n- An uptime \u002F SLO target\n\nIf any of those three is not stated, the recommendation is incomplete — go back to Q7 of the forcing-question library.\n\nThe `scripts\u002Ffullstack_decision_engine.py` tool encodes these checks: it refuses to recommend a profile without all four assumption inputs and prints the verifiable thresholds for the matched profile.\n\n---\n\n## Customization profiles\n\nFour built-in profiles in `profiles\u002F` calibrate every recommendation:\n\n| Profile | When to pick | Cloud ceiling | Pattern |\n|---|---|---|---|\n| `saas-startup` | \u003C 10 eng, customer-facing, daily+ cadence | $8K\u002Fmo | Modular monolith on Next.js + Postgres |\n| `enterprise-scale` | 50+ eng, regulated, per-PR with gates | $250K\u002Fmo | Domain-bounded services + platform team |\n| `internal-tool` | ≤ 5 eng, auth-walled, \u003C 100 DAU | $500\u002Fmo | Retool-first; thin custom stack if forced |\n| `marketing-site` | SEO-dependent, near-zero write | $200\u002Fmo | Static-first (Astro \u002F 11ty \u002F Next-static) |\n\nPick a profile via:\n\n```bash\npython scripts\u002Ffullstack_decision_engine.py \\\n  --team-size 6 --team-size-12mo 12 \\\n  --cadence daily --user-facing true --budget 5000 \\\n  --traffic-p99-rps 45 --data-sensitivity pii-only\n```\n\nThe tool returns the best-fit profile, the tradeoff against the runner-up (if within 15%), the stack recommendation, the anti-patterns to avoid on that profile, and the named-approver chain. **This tool never auto-approves.**\n\nTo add a custom profile: copy `profiles\u002Fsaas-startup.json` to `profiles\u002F\u003Cyour-org>.json`, adjust the `constraints` and `stack_recommendations` blocks, and rerun. The JSON is the customization surface — no code changes needed.\n\n---\n\n## Composition map\n\nThis skill does NOT reimplement scope owned by the POWERFUL-tier specialists. It forks into them. See `references\u002Fcomposition_map.md` for the full routing table. Key forks:\n\n| Concern | Fork into |\n|---|---|\n| API contract review | `engineering\u002Fskills\u002Fapi-design-reviewer\u002F` |\n| Database schema design | `engineering\u002Fskills\u002Fdatabase-designer\u002F` |\n| Reliability \u002F SLO design | `engineering\u002Fslo-architect\u002F` |\n| CI\u002FCD pipeline | `engineering\u002Fskills\u002Fci-cd-pipeline-builder\u002F` |\n| Performance profiling | `engineering\u002Fskills\u002Fperformance-profiler\u002F` |\n| Pre-commit Karpathy review | `engineering\u002Fkarpathy-coder\u002F` |\n| Pre-flight architecture grill | `engineering\u002Fgrill-me\u002F` |\n\nThe `cs-fullstack-engineer` agent (in `agents\u002Fengineering\u002Fcs-fullstack-engineer.md`) orchestrates these forks via `context: fork`. Invoke it from another agent with `Agent({subagent_type: \"cs-fullstack-engineer\", prompt: \"...\"})` or via the slash command `\u002Fcs:fullstack-review \u003Cyour problem>`.\n\n---\n\n## Forcing-question library (Matt Pocock grill)\n\nBefore locking any architecture or stack decision, walk the seven forcing questions in `references\u002Fforcing_questions.md`. Each has a recommended answer, canon citation, and kill criterion. The discipline:\n\n1. One question per turn. No bundling.\n2. Always recommend the answer with cited canon.\n3. Track answers in a working file (e.g., `\u002Ftmp\u002Ffullstack-grill-\u003Cdate>.md`).\n4. If a kill criterion trips, stop. Do not scaffold around an unresolved gap.\n5. After Q7, run `fullstack_decision_engine.py` with the seven answers as inputs.\n\nSummary of the seven questions (full content in the reference):\n\n1. Team size today + 12-month headcount?\n2. Deployment cadence — per-PR, daily, weekly, quarterly?\n3. Customer-facing, internal tool, or marketing site?\n4. One-year p50 \u002F p99 traffic forecast?\n5. Hiring against the stack or training the team?\n6. Year-one monthly cloud + SaaS ceiling?\n7. Three verifiable success criteria with numeric targets?\n\n---\n\n## Invocation from other agents and skills\n\nThis skill is invokable by any other agent or skill via three surfaces:\n\n1. **Slash command:** `\u002Fcs:fullstack-review \u003Cprompt>` — runs the full grill + decision engine + composition routing.\n2. **Agent subagent:** `Agent({subagent_type: \"cs-fullstack-engineer\", prompt: \"...\"})` — forks context, returns ≤ 200-word digest.\n3. **Direct tool call:** `python scripts\u002Ffullstack_decision_engine.py ...` — deterministic profile match without the conversational grill (use when inputs are already known).\n\nSee `agents\u002Fengineering\u002Fcs-fullstack-engineer.md` for the full invocation contract.\n",{"name":5,"description":7},"claude\u002Fopen-prs-review-Of9HK","a48d8438efe8e36550acc4c2006bdcddf62911db","engineering-team\u002Fskills\u002Fsenior-fullstack","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Faneeba-pixel","Student at University of Gujrat","2026-07-14 21:41:17",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add aneeba-pixel\u002Fclaude-skills --skill senior-fullstack",{"tool":37,"command":38},"bunx","bunx skills add aneeba-pixel\u002Fclaude-skills --skill senior-fullstack",{"tool":40,"command":41},"pnpm","pnpm dlx skills add aneeba-pixel\u002Fclaude-skills --skill senior-fullstack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002FSKILL.md",true,[45,51,55,59,63,67,71,75,79,83,89,93],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"profiles\u002Fenterprise-scale.json","REFERENCE","参考文档",3630,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Fprofiles\u002Fenterprise-scale.json",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"profiles\u002Finternal-tool.json",2511,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Fprofiles\u002Finternal-tool.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"profiles\u002Fmarketing-site.json",2911,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Fprofiles\u002Fmarketing-site.json",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"profiles\u002Fsaas-startup.json",2812,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Fprofiles\u002Fsaas-startup.json",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Farchitecture_patterns.md",12973,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Freferences\u002Farchitecture_patterns.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fcomposition_map.md",5130,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Freferences\u002Fcomposition_map.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fdevelopment_workflows.md",16778,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Freferences\u002Fdevelopment_workflows.md",{"path":76,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fforcing_questions.md",8068,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Freferences\u002Fforcing_questions.md",{"path":80,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Ftech_stack_guide.md",14100,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Freferences\u002Ftech_stack_guide.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fcode_quality_analyzer.py","SCRIPT","脚本",22418,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Fscripts\u002Fcode_quality_analyzer.py",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Ffullstack_decision_engine.py",15175,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Fscripts\u002Ffullstack_decision_engine.py",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fproject_scaffolder.py",27328,"https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fengineering-team\u002Fskills\u002Fsenior-fullstack\u002Fscripts\u002Fproject_scaffolder.py",[98,105,112,119,126,133],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M78K120A3JKH3NH8GC19YG4M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M78K0QS9AGDJ43CPQYEHM5S0","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M78K0FV3HMJ94SK965CWMNNP","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M78K04E77B04KYBB6M01EV3J","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M78JZW8XEFZP6HSF53M8D4M1","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M78JZHX45S2Y0GPY9Z5V6TQ3","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]