architect

Guide architectural decisions and enforce best practices across software systems.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/itou-daiki/easy_stat_edu --skill architect-itou-daiki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/itou-daiki/easy_stat_edu/tree/main/.agent/skills/architect
Command: npx skills add https://github.com/itou-daiki/easy_stat_edu --skill architect-itou-daiki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams design robust, scalable software architectures by guiding decision-making, evaluating trade-offs, and establishing architectural standards.

Core Features & Use Cases

  • Architecture reviews for new features and refactors
  • ADR-driven decision tracing and governance
  • Guidance on modularity, patterns, and maintainability
  • Scalability planning and security considerations

Quick Start

Provide an architecture review for a new feature focusing on modularity, scalability, and security.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I conduct an architecture review for a new feature?

Conduct an architecture review by evaluating new feature designs for modularity, scalability, and security to enforce maintainability and performance best practices across your codebase.

When do I need to use ADRs for system design decisions?

You need to use Architecture Decision Records (ADRs) for system design decisions when you require decision tracing and governance to guide architectural choices across multiple teams and codebases.

What is the best way to plan for software scalability and modularity?

The best way to plan for software scalability and modularity is to apply architectural patterns and governance that enforce maintainability, security, and performance throughout the system design process.

Can I use architectural governance patterns for refactoring existing codebases?

Yes, you can use architectural governance patterns for refactoring existing codebases to enforce modularity, security, and maintainability while evaluating trade-offs during the platform-level decision process.

Why does system design require trade-off evaluation during architectural reviews?

System design requires trade-off evaluation during architectural reviews to guide decision-making and establish architectural standards that ensure robust, scalable software architectures without compromising maintainability.