domains / families / software-engineering / senior-architect

senior-architect

combined

This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design". Use for architecture decision records (ADRs), tech stack evaluation, system design reviews, dependency analysis, and generating architecture diagrams in Mermaid, PlantUML, or ASCII format. Complete toolkit for senior architect with modern tools and best practices.

When to use

• This skill is applicable to execute the workflow or actions described in the overview.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

Both copies describe the same three scripts (architecture_diagram_generator, dependency_analyzer, project_architect) but with different levels of detail and scope. The first copy is a high-level wrapper that references generic reference docs and a broad tech stack, while the second copy provides specific CLI flags, output formats (Mermaid/PlantUML/ASCII), supported package managers, and concrete decision workflows (database selection, monolith vs microservices). The second copy is more actionable, but the first copy includes a 'Development Workflow' and 'Best Practices Summary' section that the second lacks. Because the second copy is truncated and the first copy has unique high-level guidance, combining them yields a more complete skill.