architect

Analyze dependency graphs and propose architecture improvements with impact and risk.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/g-zenr/relay-api --skill architect-g-zenr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/g-zenr/relay-api --skill architect-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and rectify architectural flaws, ensuring a maintainable, scalable, and robust codebase by systematically evaluating patterns, layers, and design decisions.

Core Features & Use Cases

  • Architecture Review: Analyzes codebase layers, dependency graphs, and design patterns.
  • Scalability Assessment: Evaluates readiness for multi-resource, multi-user, and multi-instance scenarios.
  • Technical Debt Identification: Pinpoints code in the wrong layer, missing abstractions, and configuration issues.
  • Improvement Proposals: Generates actionable recommendations with impact, effort, risk, and priority.
  • Use Case: A team is experiencing performance issues as their application scales. This Skill can be used to analyze the current architecture, identify bottlenecks, and propose refactoring strategies to improve scalability and maintainability.

Quick Start

Use the architect skill to evaluate the current codebase architecture and propose improvements.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I identify architectural flaws and technical debt in my codebase?

To identify architectural flaws and technical debt, you can analyze codebase layers, dependency graphs, and design patterns to pinpoint code in the wrong layer, missing abstractions, and configuration issues. This process ensures a maintainable and robust codebase.

What is the best way to assess codebase scalability for multi-user scenarios?

Assessing codebase scalability involves evaluating readiness for multi-resource, multi-user, and multi-instance scenarios. By analyzing current architecture and identifying bottlenecks, you can determine if the design supports growing performance demands.

How do I propose refactoring strategies with impact and risk assessment?

Proposing refactoring strategies involves generating actionable recommendations that include impact, effort, risk, and priority. This allows teams to systematically address design flaws and improve maintainability based on evaluated dependencies.

How do I document significant architecture design decisions and changes?

Document significant architecture design decisions by creating Architecture Decision Records (ADRs). This records the evaluated patterns, layers, and design decisions, ensuring transparency and tracking the evolution of your codebase.

Can I evaluate dependency graphs to find missing abstractions in my code?

Yes, evaluating dependency graphs helps find missing abstractions by analyzing codebase layers and design patterns. This analysis identifies structural flaws and configuration issues that hinder scalability.

When do I need an architecture review for my software project?

An architecture review is needed when experiencing performance issues during scaling or suspecting technical debt. It systematically evaluates patterns and layers to identify bottlenecks and propose improvements for robust codebase evolution.