orthoplus-arch-guard

Detects backend and frontend architecture violations and generates a Markdown findings report.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill orthoplus-arch-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orthoplus-arch-guard
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.kimi/skills/orthoplus-arch-guard
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill orthoplus-arch-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents OrthoPlus Enterprise codebase drift by detecting high-risk architectural violations before they become entrenched, expensive to fix issues.

Core Features & Use Cases

  • Backend architecture violation scanning: Detects controllers accessing Prisma directly, identifies overly large controllers (over 300 lines), flags missing repository-layer patterns, and highlights raw SQL usage outside database_admin.
  • Frontend architecture violation scanning: Detects inline API calls inside page components, flags oversized components (over 300 lines), and warns about tokens stored in localStorage due to XSS risk.
  • Automated refactor task generation: Produces a Markdown findings report and updates architecture-refactor tasks to move teams toward a healthier layering model.

Quick Start

Ask the AI to run the architecture guard scan by telling it: “Execute /arch.scan for OrthoPlus-Enterprise and generate the detailed Markdown findings report.”

Frequently Asked Questions about orthoplus-arch-guard

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

FAQPage Schema
How do I detect Prisma direct access and raw SQL usage in my backend repository layer?

To scan for inline API calls in frontend components, execute an architecture guard check to identify direct API invocations within page components and oversized files over 300 lines. The scan produces a structured Markdown report detailing file-and-line findings for refactor tasks.

Why does storing tokens in localStorage create security risks in frontend architecture?

Storing tokens in localStorage creates security risks because it exposes authentication tokens to XSS attacks. An architecture guard scan warns about this unsafe token storage practice, generating findings that help refactor frontend components toward more secure storage patterns.

What is the best way to enforce controller size limits and repository layering compliance?

The best way to enforce controller size limits and repository layering compliance is to run an automated architecture scan that flags oversized controllers over 300 lines and missing repository patterns. It generates a structured Markdown report with actionable file-and-line findings for refactoring tasks.

Does this architecture guard scan work for both frontend and backend layering violations?

Yes, the architecture guard scan works for both frontend and backend violations. It detects backend issues like Prisma-direct access and raw SQL constraints, while also scanning frontend components for inline API calls, oversized files, and unsafe localStorage token storage.

How do I generate a structured Markdown report for architecture refactor tasks?

To generate a structured Markdown report for architecture refactor tasks, execute an architecture scan targeting backend and frontend violations. The scan produces actionable file-and-line findings that update architecture-refactor tasks and move teams toward a healthier layering model.