> Reusable workflow extracted from baccio-tech-architect expertise.
Designs scalable, maintainable, and secure system architectures using DDD, Clean Architecture, and cloud-native patterns. Triggers when you need to design new systems, modernize legacy applications, select technology stacks, or plan scalability strategies.
/plugin marketplace add Roberdan/MyConvergio/plugin install roberdan-myconvergio@Roberdan/MyConvergioThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Reusable workflow extracted from baccio-tech-architect expertise.
Design scalable, maintainable, and secure system architectures using proven patterns, with emphasis on Domain-Driven Design, Clean Architecture, and cloud-native principles.
Requirements Analysis
Domain Modeling
Architecture Pattern Selection
Technology Stack Selection
Scalability & Performance Design
Security Architecture
Observability Design
Documentation & ADRs
## Decision: [Technology/Pattern Choice]
### Context
[What problem are we solving? What are the constraints?]
### Options Considered
1. **Option A**: [Description]
- Pros: [Benefits]
- Cons: [Drawbacks]
- Cost: [Time/Money/Complexity]
2. **Option B**: [Description]
- Pros: [Benefits]
- Cons: [Drawbacks]
- Cost: [Time/Money/Complexity]
### Decision
[Chosen option with rationale]
### Consequences
- Positive: [Expected benefits]
- Negative: [Known drawbacks]
- Mitigation: [How we address drawbacks]
Input: Design architecture for e-commerce platform
Expected: 10K concurrent users, 99.9% uptime, PCI DSS compliant
Workflow Execution:
1. Requirements: User accounts, product catalog, shopping cart, checkout
2. Domain Model: User, Product, Cart, Order bounded contexts
3. Pattern: Microservices with API Gateway, Event-driven for orders
4. Tech Stack:
- Backend: Node.js + TypeScript
- Database: PostgreSQL (products/users), Redis (cart/sessions)
- Message Bus: Kafka for order events
- Cloud: AWS with ECS + RDS + ElastiCache
5. Scalability: Horizontal scaling via ECS, database read replicas, CDN
6. Security: OAuth2 + JWT, PCI-compliant payment gateway, encryption at rest
7. Observability: CloudWatch logs/metrics, X-Ray tracing, Grafana dashboards
8. Documentation: ADRs created, C4 diagrams, API documentation
Output: Comprehensive architecture blueprint with ADRs and diagrams
| Criterion | Weight | Option A | Option B | Option C |
|---|---|---|---|---|
| Team expertise | 20% | 8/10 | 5/10 | 6/10 |
| Scalability | 25% | 9/10 | 7/10 | 8/10 |
| Cost | 15% | 6/10 | 9/10 | 7/10 |
| Community support | 10% | 9/10 | 8/10 | 6/10 |
| Compliance fit | 15% | 8/10 | 7/10 | 9/10 |
| Vendor lock-in | 15% | 7/10 | 5/10 | 8/10 |
| Total | 100% | 7.9 | 6.9 | 7.5 |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.