domains / software-engineering / architecture-design-analysis / senior-architect
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.
| Repository | Path |
|---|---|
| sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills-claude/skills/senior-architect/SKILL.md |
| LeoYeAI/openclaw-master-skills | skills/senior-architect/SKILL.md |
| Role | Repository | Path |
|---|---|---|
| peer | sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills-claude/skills/senior-architect/SKILL.md |
| peer | LeoYeAI/openclaw-master-skills | skills/senior-architect/SKILL.md |
| adapter | sickn33/agentic-awesome-skills | plugins/agentic-awesome-skills/skills/senior-architect/SKILL.md |
| adapter | sickn33/agentic-awesome-skills | plugins/agentic-bundle-architecture-design/skills/senior-architect/SKILL.md |
| adapter | sickn33/agentic-awesome-skills | skills/senior-architect/SKILL.md |
--- name: senior-architect description: "Complete toolkit for senior architect with modern tools and best practices. Use for architecture decision records (ADRs), tech stack evaluation, system design reviews, dependency analysis, and generating architecture diagrams in Mermaid, PlantUML, or ASCII format." --- # Senior Architect Architecture design and analysis tools for making informed technical decisions. ## Quick Start ```bash # Generate architecture diagram from project python scripts/architecture_diagram_generator.py ./my-project --format mermaid # Analyze dependencies for issues python scripts/dependency_analyzer.py ./my-project --output json # Get architecture assessment python scripts/project_architect.py ./my-project --verbose ``` ## Core Capabilities ### 1. Architecture Diagram Generator Generates architecture diagrams from project structure in multiple formats. **Supported diagram types:** - `component` - Shows modules and their relationships - `layer` - Shows architectural layers (presentation, business, data) - `deployment` - Shows deployment topology **Usage:** ```bash # Mermaid format (default) python scripts/architecture_diagram_generator.py ./project --format mermaid --type component # PlantUML format python scripts/architecture_diagram_generator.py ./project --format plantuml --type layer # ASCII format (terminal-friendly) python scripts/architecture_diagram_generator.py ./project --format ascii # Save to file python scripts/architecture_diagram_generator.py ./project -o architecture.md ``` ### 2. Dependency Analyzer Analyzes project dependencies for coupling, circular dependencies, and outdated packages. **Supported package managers:** - npm/yarn (`package.json`) - Python (`requirements.txt`, `pyproject.toml`) - Go (`go.mod`) - Rust (`Cargo.toml`) **Usage:** ```bash # Human-readable report python scripts/dependency_analyzer.py ./project # JSON output for CI/CD integration python scripts/dependency_analyzer.py ./project --output json # Check only for circular dependencies python scripts/dependency_analyzer.py ./project --check circular ``` ### 3. Project Architect Analyzes project structure and detects architectural patterns, code smells, and improvement opportunities. **Usage:** ```bash # Full assessment python scripts/project_architect.py ./project # Verbose with detailed recommendations python scripts/project_architect.py ./project --verbose # JSON output python scripts/project_architect.py ./project --output json ``` ## Decision Workflows ### Database Selection Use when choosing a database for a new project or migrating existing data. **Step 1: Identify data characteristics** | Characteristic | Points to SQL | Points to NoSQL | |----------------|---------------|-----------------| | Structured with relationships | ✓ | | | ACID transactions required | ✓ | | | Flexible/evolving schema | | ✓ | ### Architecture Pattern Selection Evaluate patterns such as MVC, layered, hexagonal, or microservices based on team size, scalability needs, and deployment complexity. ### Monolith vs Microservices Consider microservices when independent scaling, team autonomy, or technology diversity is required. Otherwise, prefer a modular monolith for simplicity. ## Best Practices Summary ### Code Quality - Follow established patterns - Write comprehensive tests - Document decisions - Review regularly ### Performance - Measure before optimizing - Use appropriate caching - Optimize critical paths - Monitor in production ### Security - Validate all inputs - Use parameterized queries - Implement proper authentication - Keep dependencies updated ### Maintainability - Write clear code - Use consistent naming - Add helpful comments - Keep it simple ## Tech Stack Coverage **Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin **Frontend:** React, Next.js, React Native, Flutter **Backend:** Node.js, Express, GraphQL, REST APIs **Database:** PostgreSQL, Prisma, NeonDB, Supabase **DevOps:** Docker, Kubernetes, Terraform, GitHub Actions, CircleCI **Cloud:** AWS, GCP, Azure ## Common Commands ```bash # Development npm run dev npm run build npm run test npm run lint # Analysis python scripts/project_architect.py . python scripts/dependency_analyzer.py --analyze # Deployment docker build -t app:latest . docker-compose up -d kubectl apply -f k8s/ ``` ## Limitations - 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.