senior-architect
Design Scalable Software Architecture
Também disponível em: davila7,alirezarezvani
Senior developers struggle to design systems that scale and remain maintainable over time. This skill provides architecture patterns, system design workflows, and technical decision frameworks to build enterprise-grade applications.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "senior-architect". Design an e-commerce platform that handles 100k daily orders with real-time inventory
Resultado esperado:
- Recommended Architecture: Event-Driven Microservices
- Core Components: API Gateway, Order Service, Inventory Service, Payment Service, Notification Service
- Database Strategy: PostgreSQL for transactional data, Redis for caching, Separate read replicas
- Scalability: Horizontal scaling with Kubernetes, Auto-scaling based on CPU/memory
- Security: JWT authentication, API rate limiting, Input validation, SQL injection prevention
A utilizar "senior-architect". Compare React vs Vue vs Angular for a large enterprise dashboard application
Resultado esperado:
- Recommendation: React for enterprise dashboards
- 理由: Larger ecosystem, more hiring pool, flexible architecture, strong enterprise support
- Considerations: Team learning curve, state management needs, long-term maintenance
Auditoria de Segurança
SeguroSecurity audit completed. Static findings are false positives: external_commands (33) triggered by markdown code blocks, filesystem access is legitimate output functionality, sensitive finding is standard .env setup. No actual security risks identified. Skill is safe for marketplace publication.
Problemas de Risco Médio (3)
Problemas de Baixo Risco (2)
Pontuação de qualidade
O Que Você Pode Construir
Architect New SaaS Platform
Design the architecture for a new multi-tenant SaaS application including frontend, backend, database, and infrastructure choices
Review Existing System Design
Analyze an existing codebase and provide architecture improvements for scalability and maintainability
Technology Stack Selection
Evaluate and select appropriate technologies for a project based on requirements, team expertise, and long-term maintainability
Tente Estes Prompts
I need to design a [type of application] that handles [number] users. What architecture patterns would you recommend? Consider [specific requirement].
Design a system architecture for a [description of system]. Include: 1) Component diagram 2) Data flow 3) API design 4) Database schema 5) Security considerations. The system must handle [scale requirements].
I am building a [application type] with these requirements: [list requirements]. Compare [Technology A] vs [Technology B] vs [Technology C] for the [component]. Recommend the best choice with rationale.
Review the architecture of my existing [system description]. Identify: 1) Scalability bottlenecks 2) Security vulnerabilities 3) Maintainability issues 4) Performance concerns. Provide specific recommendations for improvement.
Melhores Práticas
- Start with requirements before choosing architecture - understand scale, complexity, and team capabilities first
- Document architecture decisions with pros, cons, and trade-offs using Architecture Decision Records (ADRs)
- Design for failure - plan for component failures and have graceful degradation strategies
Evitar
- Over-engineering early - do not apply microservices patterns to simple applications that could work as monoliths
- Ignoring non-functional requirements - performance, security, and scalability must be considered from the start
- Technology hopping - avoid switching tech stacks frequently as it creates technical debt and slows delivery