beforemerge-fullstack-architecture-review
Automated code review for layered TypeScript architectures, focusing on SOLID principles and security.
Install
mkdir -p .claude/skills/beforemerge-fullstack-architecture-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18367" && unzip -o skill.zip -d .claude/skills/beforemerge-fullstack-architecture-review && rm skill.zipInstalls to .claude/skills/beforemerge-fullstack-architecture-review
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Code review rules for DRY/SOLID layered architecture in fullstack TypeScript applications. Covers dependency direction, service/repository patterns, factory injection, domain entities, security hardening, performance optimization, and code quality patterns. Use this skill when reviewing, writing, or refactoring fullstack TypeScript code with layered architecture — especially before merging pull requests. Triggers on tasks involving code review, architecture review, SOLID principles, clean architecture, or quality checks for fullstack TypeScript projects.Key capabilities
- →Review pull requests for fullstack TypeScript projects
- →Design or refactor service/repository layers
- →Audit API routes for separation of concerns
- →Build new features following clean architecture principles
- →Run pre-merge quality checks on layered codebases
- →Assess security, performance, architecture, and quality
How it works
The skill provides a knowledge base of rules for DRY/SOLID layered architecture in fullstack TypeScript applications. It categorizes these rules by priority and impact, focusing on security, performance, architecture, and quality.
Inputs & outputs
When to use beforemerge-fullstack-architecture-review
- →Reviewing TypeScript pull requests
- →Refactoring service and repository layers
- →Auditing API routes for concerns
About this skill
BeforeMerge: Fullstack Architecture Review
Code review knowledge base for DRY/SOLID layered architecture in fullstack TypeScript applications. Contains rules across 4 categories — security, performance, architecture, and quality — prioritized by impact. Framework-agnostic principles illustrated with Next.js + Supabase examples.
When to Apply
Reference these rules when:
- Reviewing pull requests for fullstack TypeScript projects
- Designing or refactoring service/repository layers
- Auditing API routes for proper separation of concerns
- Building new features following clean architecture principles
- Running pre-merge quality checks on layered codebases
Rule Categories by Priority
| Priority | Category | Impact | Prefix | Focus |
|---|---|---|---|---|
| 1 | Security | CRITICAL | sec- | Thin controllers, rate limiting, CSRF, error handling |
| 2 | Performance | HIGH | perf- | Parallel fetching, minimal client components, streaming |
| 3 | Architecture | CRITICAL-MEDIUM | arch- | SOLID patterns, dependency direction, layered design |
| 4 | Quality | MEDIUM-HIGH | qual- | DRY, consistency, logging, discoverability |
How to Use
Read individual rule files in rules/ for detailed explanations and code examples.
Each rule contains:
- Brief explanation of why it matters
- Incorrect code example with explanation
- Correct code example with explanation
- CWE/OWASP mapping where applicable
- References to official documentation
For the complete compiled guide: AGENTS.md
When not to use it
- →When the project is not a fullstack TypeScript application
- →When the architecture is not layered
- →When not performing code review, architecture review, or quality checks
Limitations
- →Code review knowledge base for DRY/SOLID layered architecture in fullstack TypeScript applications.
- →Framework-agnostic principles illustrated with Next.js + Supabase examples.
- →Use this skill when reviewing, writing, or refactoring fullstack TypeScript code with layered architecture
How it compares
This skill offers a structured, prioritized set of rules specifically for fullstack TypeScript layered architecture, providing detailed explanations and code examples for each rule, which is more targeted than a general code review.
Compared to similar skills
beforemerge-fullstack-architecture-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| beforemerge-fullstack-architecture-review (this skill) | 0 | 4mo | No flags | Advanced |
| reviewing-nextjs-16-patterns | 11 | 8mo | Review | Intermediate |
| vercel-reference-architecture | 3 | 10d | Review | Intermediate |
| vercel-policy-guardrails | 0 | 10d | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
reviewing-nextjs-16-patterns
djankies
Review code for Next.js 16 compliance - security patterns, caching, breaking changes. Use when reviewing Next.js code, preparing for migration, or auditing for violations.
vercel-reference-architecture
jeremylongshore
Implement Vercel reference architecture with best-practice project layout. Use when designing new Vercel integrations, reviewing project structure, or establishing architecture standards for Vercel applications. Trigger with phrases like "vercel architecture", "vercel best practices", "vercel project structure", "how to organize vercel", "vercel layout".
vercel-policy-guardrails
jeremylongshore
Implement Vercel lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Vercel integrations, implementing pre-commit hooks, or configuring CI policy checks for Vercel best practices. Trigger with phrases like "vercel policy", "vercel lint", "vercel guardrails", "vercel best practices check", "vercel eslint".
code-review
gh0stfrk
Review code changes in this Next.js portfolio/blog for correctness, security, performance, and maintainability
codex-code-review
tyrchen
Perform comprehensive code reviews using OpenAI Codex CLI. This skill should be used when users request code reviews, want to analyze diffs/PRs, need security audits, performance analysis, or want automated code quality feedback. Supports reviewing staged changes, specific files, entire directories, or git diffs.
vercel-known-pitfalls
jeremylongshore
Execute identify and avoid Vercel anti-patterns and common integration mistakes. Use when reviewing Vercel code for issues, onboarding new developers, or auditing existing Vercel integrations for best practices violations. Trigger with phrases like "vercel mistakes", "vercel anti-patterns", "vercel pitfalls", "vercel what not to do", "vercel code review".