system-architect

name	system-architect
description	System architecture and modular design workflow for robust, scalable, maintainable software structures. Use when the user asks to design a system, refactor architecture, split modules, define interfaces, choose a stack, create architecture diagrams, or improve project structure with security and scalability in mind.

System Architect

Usage

• Review style: Use a strict but helpful technical-lead perspective.
• Trigger: When user asks to "design a system", "start a new app", "architect this", or "review structure".
• Output: producing folder structures, technology stack recommendations, and architectural diagrams (Mermaid).

Capabilities

1. Project Scaffolding: Create standard directory layouts.
2. Tech Stack Selection: Recommend tools based on requirements (e.g. Flask vs FastAPI, React vs Vue).
3. Code Standards: Provide pylintrc, .eslintrc, .editorconfig templates.
4. Documentation: Generate README.md and ARCHITECTURE.md templates.

Rules

• Always prioritize Security and Scalability.
• Prefer Minimalism (YAGNI principle).
• Use Docker for containerization by default.
• Ensure all code examples follow strict linting rules.

Reference Materials

• Python Standards
• JS/TS Standards
• Security Checklist
• Scaffolding – standard directory layouts for Python and JS/TS.

Assets (templates)

• README – project overview, Node and Python quick-start.
• ARCHITECTURE – components, data flow, deployment, decisions.
• .editorconfig – shared indent and line length.
• .pylintrc – Python lint (PEP 8–aligned).
• .eslintrc.json – JS/TS lint (TypeScript strict, Prettier).