code-architecture-reviewer

Review recently written code for architectural consistency and system integration.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/ogprotege/Skills --skill code-architecture-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-architecture-reviewer
Source: https://github.com/ogprotege/Skills/tree/main/Categories/Code/code-architecture-reviewer
Command: npx skills add https://github.com/ogprotege/Skills --skill code-architecture-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill inspects recently written code for architecture coherence, best practices, and correct system integration, ensuring changes align with project standards and patterns.

Core Features & Use Cases

  • Type safety & patterns: Enforces TypeScript strictness and consistent patterns.
  • System integration: Verifies integration with Prisma, Node.js/Express, React, and microservices.
  • Documentation references: Points to architecture documents such as PROJECT_KNOWLEDGE.md, BEST_PRACTICES.md, TROUBLESHOOTING.md.
  • Use Case: Reviewing a new API endpoint to ensure it matches routing, controllers, and data models.

Quick Start

Review new endpoint in scope, Mode: plan, Debug: on, Goal: validate architectural fit.

Frequently Asked Questions about code-architecture-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review code for architectural consistency across TypeScript endpoints and React components?

Architectural review checks new endpoints, refactors, and UI components against project standards. It validates TypeScript strict mode, async/await patterns, PrismaService usage, JWT authentication, TanStack Query integration, and microservice boundaries to ensure alignment with established patterns.

What best practices should a new Node.js API endpoint follow?

New endpoints must enforce TypeScript strictness, use 4-space indentation, implement robust error handling, follow consistent naming conventions, integrate correctly with PrismaService and JWT cookie authentication, and respect microservice boundaries as documented in PROJECT_KNOWLEDGE.md and BEST_PRACTICES.md.

How do I ensure React components integrate correctly with TanStack Query and the backend?

Review validates that React components use TanStack Query patterns consistently, match backend endpoints, handle async states correctly, and maintain type safety. This ensures UI components align with your data-fetching architecture and error-handling standards.

Can I use this review process for Prisma schema changes and microservice integration?

Yes. The review checks PrismaService usage correctness, verifies microservice boundaries are maintained, validates WorkflowEngine V3 integration, and ensures system-level changes conform to your established architecture patterns and documentation.

What happens if my code doesn't follow TypeScript strict mode or naming conventions?

The review identifies violations of strict TypeScript settings, inconsistent naming, improper async/await usage, and formatting deviations from your 4-space standard. It points to BEST_PRACTICES.md for guidance on corrections and architectural alignment.