[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-8549cfd6-82d6-44e9-a251-05cb88d43526":3,"$fFghqI6y5tiv874m4BYjd0UHDTOY7izrn1rhREqB-K7k":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"8549cfd6-82d6-44e9-a251-05cb88d43526","senior-architect","当用户请求“设计系统架构”、“评估微服务与单体”、“创建架构图”、“分析依赖”、“选择数据库”、“规划可扩展性”、“做出技术决策”或“审查系统设计”时，应使用此技能。用于架构决策记录（ADRs）、技术栈评估、系统设计审查、依赖分析以及使用Mermaid、PlantUML或ASCII格式生成架构图。","cat_life_career","mod_other","alirezarezvani,other","---\nname: \"senior-architect\"\ndescription: 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.\n---\n\n# Senior Architect\n\nArchitecture design and analysis tools for making informed technical decisions.\n\n## Table of Contents\n\n- [Quick Start](#quick-start)\n- [Tools Overview](#tools-overview)\n  - [Architecture Diagram Generator](#1-architecture-diagram-generator)\n  - [Dependency Analyzer](#2-dependency-analyzer)\n  - [Project Architect](#3-project-architect)\n- [Decision Workflows](#decision-workflows)\n  - [Database Selection](#database-selection-workflow)\n  - [Architecture Pattern Selection](#architecture-pattern-selection-workflow)\n  - [Monolith vs Microservices](#monolith-vs-microservices-decision)\n- [Reference Documentation](#reference-documentation)\n- [Tech Stack Coverage](#tech-stack-coverage)\n- [Common Commands](#common-commands)\n\n---\n\n## Quick Start\n\n```bash\n# Generate architecture diagram from project\npython scripts\u002Farchitecture_diagram_generator.py .\u002Fmy-project --format mermaid\n\n# Analyze dependencies for issues\npython scripts\u002Fdependency_analyzer.py .\u002Fmy-project --output json\n\n# Get architecture assessment\npython scripts\u002Fproject_architect.py .\u002Fmy-project --verbose\n```\n\n---\n\n## Tools Overview\n\n### 1. Architecture Diagram Generator\n\nGenerates architecture diagrams from project structure in multiple formats.\n\n**Solves:** \"I need to visualize my system architecture for documentation or team discussion\"\n\n**Input:** Project directory path\n**Output:** Diagram code (Mermaid, PlantUML, or ASCII)\n\n**Supported diagram types:**\n- `component` - Shows modules and their relationships\n- `layer` - Shows architectural layers (presentation, business, data)\n- `deployment` - Shows deployment topology\n\n**Usage:**\n```bash\n# Mermaid format (default)\npython scripts\u002Farchitecture_diagram_generator.py .\u002Fproject --format mermaid --type component\n\n# PlantUML format\npython scripts\u002Farchitecture_diagram_generator.py .\u002Fproject --format plantuml --type layer\n\n# ASCII format (terminal-friendly)\npython scripts\u002Farchitecture_diagram_generator.py .\u002Fproject --format ascii\n\n# Save to file\npython scripts\u002Farchitecture_diagram_generator.py .\u002Fproject -o architecture.md\n```\n\n**Example output (Mermaid):**\n```mermaid\ngraph TD\n    A[API Gateway] --> B[Auth Service]\n    A --> C[User Service]\n    B --> D[(PostgreSQL)]\n    C --> D\n```\n\n---\n\n### 2. Dependency Analyzer\n\nAnalyzes project dependencies for coupling, circular dependencies, and outdated packages.\n\n**Solves:** \"I need to understand my dependency tree and identify potential issues\"\n\n**Input:** Project directory path\n**Output:** Analysis report (JSON or human-readable)\n\n**Analyzes:**\n- Dependency tree (direct and transitive)\n- Circular dependencies between modules\n- Coupling score (0-100)\n- Outdated packages\n\n**Supported package managers:**\n- npm\u002Fyarn (`package.json`)\n- Python (`requirements.txt`, `pyproject.toml`)\n- Go (`go.mod`)\n- Rust (`Cargo.toml`)\n\n**Usage:**\n```bash\n# Human-readable report\npython scripts\u002Fdependency_analyzer.py .\u002Fproject\n\n# JSON output for CI\u002FCD integration\npython scripts\u002Fdependency_analyzer.py .\u002Fproject --output json\n\n# Check only for circular dependencies\npython scripts\u002Fdependency_analyzer.py .\u002Fproject --check circular\n\n# Verbose mode with recommendations\npython scripts\u002Fdependency_analyzer.py .\u002Fproject --verbose\n```\n\n**Example output:**\n```\nDependency Analysis Report\n==========================\nTotal dependencies: 47 (32 direct, 15 transitive)\nCoupling score: 72\u002F100 (moderate)\n\nIssues found:\n- CIRCULAR: auth → user → permissions → auth\n- OUTDATED: lodash 4.17.15 → 4.17.21 (security)\n\nRecommendations:\n1. Extract shared interface to break circular dependency\n2. Update lodash to fix CVE-2020-8203\n```\n\n---\n\n### 3. Project Architect\n\nAnalyzes project structure and detects architectural patterns, code smells, and improvement opportunities.\n\n**Solves:** \"I want to understand the current architecture and identify areas for improvement\"\n\n**Input:** Project directory path\n**Output:** Architecture assessment report\n\n**Detects:**\n- Architectural patterns (MVC, layered, hexagonal, microservices indicators)\n- Code organization issues (god classes, mixed concerns)\n- Layer violations\n- Missing architectural components\n\n**Usage:**\n```bash\n# Full assessment\npython scripts\u002Fproject_architect.py .\u002Fproject\n\n# Verbose with detailed recommendations\npython scripts\u002Fproject_architect.py .\u002Fproject --verbose\n\n# JSON output\npython scripts\u002Fproject_architect.py .\u002Fproject --output json\n\n# Check specific aspect\npython scripts\u002Fproject_architect.py .\u002Fproject --check layers\n```\n\n**Example output:**\n```\nArchitecture Assessment\n=======================\nDetected pattern: Layered Architecture (confidence: 85%)\n\nStructure analysis:\n  ✓ controllers\u002F  - Presentation layer detected\n  ✓ services\u002F     - Business logic layer detected\n  ✓ repositories\u002F - Data access layer detected\n  ⚠ models\u002F       - Mixed domain and DTOs\n\nIssues:\n- LARGE FILE: UserService.ts (1,847 lines) - consider splitting\n- MIXED CONCERNS: PaymentController contains business logic\n\nRecommendations:\n1. Split UserService into focused services\n2. Move business logic from controllers to services\n3. Separate domain models from DTOs\n```\n\n---\n\n## Decision Workflows\n\n### Database Selection Workflow\n\nUse when choosing a database for a new project or migrating existing data.\n\n**Step 1: Identify data characteristics**\n| Characteristic | Points to SQL | Points to NoSQL |\n|----------------|---------------|-----------------|\n| Structured with relationships | ✓ | |\n| ACID transactions required | ✓ | |\n| Flexible\u002Fevolving schema | | ✓ |\n| Document-oriented data | | ✓ |\n| Time-series data | | ✓ (specialized) |\n\n**Step 2: Evaluate scale requirements**\n- \u003C1M records, single region → PostgreSQL or MySQL\n- 1M-100M records, read-heavy → PostgreSQL with read replicas\n- >100M records, global distribution → CockroachDB, Spanner, or DynamoDB\n- High write throughput (>10K\u002Fsec) → Cassandra or ScyllaDB\n\n**Step 3: Check consistency requirements**\n- Strong consistency required → SQL or CockroachDB\n- Eventual consistency acceptable → DynamoDB, Cassandra, MongoDB\n\n**Step 4: Document decision**\nCreate an ADR (Architecture Decision Record) with:\n- Context and requirements\n- Options considered\n- Decision and rationale\n- Trade-offs accepted\n\n**Quick reference:**\n```\nPostgreSQL → Default choice for most applications\nMongoDB    → Document store, flexible schema\nRedis      → Caching, sessions, real-time features\nDynamoDB   → Serverless, auto-scaling, AWS-native\nTimescaleDB → Time-series data with SQL interface\n```\n\n---\n\n### Architecture Pattern Selection Workflow\n\nUse when designing a new system or refactoring existing architecture.\n\n**Step 1: Assess team and project size**\n| Team Size | Recommended Starting Point |\n|-----------|---------------------------|\n| 1-3 developers | Modular monolith |\n| 4-10 developers | Modular monolith or service-oriented |\n| 10+ developers | Consider microservices |\n\n**Step 2: Evaluate deployment requirements**\n- Single deployment unit acceptable → Monolith\n- Independent scaling needed → Microservices\n- Mixed (some services scale differently) → Hybrid\n\n**Step 3: Consider data boundaries**\n- Shared database acceptable → Monolith or modular monolith\n- Strict data isolation required → Microservices with separate DBs\n- Event-driven communication fits → Event-sourcing\u002FCQRS\n\n**Step 4: Match pattern to requirements**\n\n| Requirement | Recommended Pattern |\n|-------------|-------------------|\n| Rapid MVP development | Modular Monolith |\n| Independent team deployment | Microservices |\n| Complex domain logic | Domain-Driven Design |\n| High read\u002Fwrite ratio difference | CQRS |\n| Audit trail required | Event Sourcing |\n| Third-party integrations | Hexagonal\u002FPorts & Adapters |\n\nSee `references\u002Farchitecture_patterns.md` for detailed pattern descriptions.\n\n---\n\n### Monolith vs Microservices Decision\n\n**Choose Monolith when:**\n- [ ] Team is small (\u003C10 developers)\n- [ ] Domain boundaries are unclear\n- [ ] Rapid iteration is priority\n- [ ] Operational complexity must be minimized\n- [ ] Shared database is acceptable\n\n**Choose Microservices when:**\n- [ ] Teams can own services end-to-end\n- [ ] Independent deployment is critical\n- [ ] Different scaling requirements per component\n- [ ] Technology diversity is needed\n- [ ] Domain boundaries are well understood\n\n**Hybrid approach:**\nStart with a modular monolith. Extract services only when:\n1. A module has significantly different scaling needs\n2. A team needs independent deployment\n3. Technology constraints require separation\n\n---\n\n## Reference Documentation\n\nLoad these files for detailed information:\n\n| File | Contains | Load when user asks about |\n|------|----------|--------------------------|\n| `references\u002Farchitecture_patterns.md` | 9 architecture patterns with trade-offs, code examples, and when to use | \"which pattern?\", \"microservices vs monolith\", \"event-driven\", \"CQRS\" |\n| `references\u002Fsystem_design_workflows.md` | 6 step-by-step workflows for system design tasks | \"how to design?\", \"capacity planning\", \"API design\", \"migration\" |\n| `references\u002Ftech_decision_guide.md` | Decision matrices for technology choices | \"which database?\", \"which framework?\", \"which cloud?\", \"which cache?\" |\n\n---\n\n## Tech Stack Coverage\n\n**Languages:** TypeScript, JavaScript, Python, Go, Swift, Kotlin, Rust\n**Frontend:** React, Next.js, Vue, Angular, React Native, Flutter\n**Backend:** Node.js, Express, FastAPI, Go, GraphQL, REST\n**Databases:** PostgreSQL, MySQL, MongoDB, Redis, DynamoDB, Cassandra\n**Infrastructure:** Docker, Kubernetes, Terraform, AWS, GCP, Azure\n**CI\u002FCD:** GitHub Actions, GitLab CI, CircleCI, Jenkins\n\n---\n\n## Common Commands\n\n```bash\n# Architecture visualization\npython scripts\u002Farchitecture_diagram_generator.py . --format mermaid\npython scripts\u002Farchitecture_diagram_generator.py . --format plantuml\npython scripts\u002Farchitecture_diagram_generator.py . --format ascii\n\n# Dependency analysis\npython scripts\u002Fdependency_analyzer.py . --verbose\npython scripts\u002Fdependency_analyzer.py . --check circular\npython scripts\u002Fdependency_analyzer.py . --output json\n\n# Architecture assessment\npython scripts\u002Fproject_architect.py . --verbose\npython scripts\u002Fproject_architect.py . --check layers\npython scripts\u002Fproject_architect.py . --output json\n```\n\n---\n\n## Getting Help\n\n1. Run any script with `--help` for usage information\n2. Check reference documentation for detailed patterns and workflows\n3. Use `--verbose` flag for detailed explanations and recommendations\n","","imported","https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills","user_system_seed","SkillOPIC",true,207,100,"2026-05-16 13:56:54",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"其他","other","mdi-page-next-outline","其他类型Skill",5,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"职场发展","career","mdi-briefcase-outline","面试准备、简历优化、职业规划",4,575,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"39bbfd5b-4f6e-46a0-880f-0611501b3aac","1.0.0","senior-architect.zip",35302,"uploads\u002Fskills\u002F8549cfd6-82d6-44e9-a251-05cb88d43526\u002Fsenior-architect.zip","c591ecc5888c037a425847ddca4c38df68af4c0914f10b095b014f95f054ff2b","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":10972},{\"path\":\"references\u002Farchitecture_patterns.md\",\"isDirectory\":false,\"size\":14448},{\"path\":\"references\u002Fsystem_design_workflows.md\",\"isDirectory\":false,\"size\":12130},{\"path\":\"references\u002Ftech_decision_guide.md\",\"isDirectory\":false,\"size\":12405},{\"path\":\"scripts\u002Farchitecture_diagram_generator.py\",\"isDirectory\":false,\"size\":22526},{\"path\":\"scripts\u002Fdependency_analyzer.py\",\"isDirectory\":false,\"size\":21690},{\"path\":\"scripts\u002Fproject_architect.py\",\"isDirectory\":false,\"size\":28955}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]