Módulo 2: Workflows e Comandos Customizados
Crie workflows reutilizáveis e comandos personalizados que eliminam 80% da repetição no desenvolvimento. Automação inteligente com Claude Code.
Por que isso é importante
Desenvolvedores perdem 60% do tempo repetindo prompts similares. Workflows customizados eliminam essa repetição, criando templates reutilizáveis com argumentos dinâmicos. Técnica que separa amadores de profissionais em Claude Code.
Workflows customizados são prompts parametrizados que você cria uma vez e reutiliza infinitas vezes. São a diferença entre fazer prompts manuais e ter sistema automatizado de desenvolvimento.
Neste módulo você criará 15+ workflows essenciais, aprenderá sintaxe avançada de templates, organizará biblioteca pessoal de comandos e implementará automações que aceleram desenvolvimento em 10x.
Aula 1: Entendendo Workflows Customizados
🎯 Conceitos Essenciais
Workflow:
Prompt reutilizável com placeholders dinâmicos.
Template Variable:
Parâmetro substituído em cada execução (ex: {{filename}}).
Anatomia de um Workflow
Exemplo: Workflow de Code Review
# Code Review Workflow
## Template: review-code.md
Analyze the {'{{language}}'} code in {'{{filename}}'} and provide:
**Code Quality Assessment:**
- Readability and maintainability score (1-10)
- Performance bottlenecks identification
- Security vulnerabilities check
- Best practices compliance
**Specific Issues Found:**
- List each problem with line reference
- Severity level (Critical/High/Medium/Low)
- Suggested fix with code examples
**Improvements Suggestions:**
- Refactoring opportunities
- Optimization recommendations
- Design pattern applications
**Test Coverage:**
- Missing test scenarios
- Edge cases not covered
- Suggested test implementations
Focus on {'{{focus_area}}'} if specified, otherwise provide comprehensive review.Template Variables
- • {{language}} - Linguagem do código
- • {{filename}} - Arquivo a revisar
- • {{focus_area}} - Área específica
Estrutura Consistente
- • Seções bem definidas
- • Critérios específicos
- • Output padronizado
Flexibilidade
- • Parâmetros opcionais
- • Contexto adaptável
- • Casos de uso múltiplos
Por que Workflows são Game-Changer
✅ Antes dos Workflows
"Revise este código React e encontre problemas de performance..."
• 5 min para escrever
• Inconsistente
• Perde contexto importante
🚀 Com Workflows
/review-code --language=React --focus=performance
• 5 segundos para executar
• Sempre consistente
• Contexto completo garantido
Aula 2: Criando Seu Primeiro Workflow
🔧 Projeto Prático
Vamos criar workflow "bug-detective" que analisa bugs sistematicamente. Passo-a-passo completo desde configuração até execução.
Passo 1: Setup do Ambiente de Workflows
Estrutura de Diretórios
# Criar diretório para workflows customizados
mkdir ~/.config/claude-desktop/workflows
# Criar subdiretórios por categoria
cd ~/.config/claude-desktop/workflows
mkdir debugging
mkdir performance
mkdir architecture
mkdir testing
mkdir refactoring
# Verificar estrutura
tree ~/.config/claude-desktop/workflowsConvenção de Nomenclatura
Exemplos:
• debug-analyze-error.md
• perf-optimize-component.md
• arch-design-system.md
• test-generate-cases.md
Passo 2: Workflow "Bug Detective"
# debug-analyze-error.md
# Bug Detective Workflow
You are an expert debugging assistant. Analyze the {'{{error_type}}'} error in {'{{tech_stack}}'} application:
**Error Details:**
**Error Message:** {'{{error_message}}'}
**Stack Trace:** {'{{stack_trace}}'}
**Context:** {'{{context}}'}
**Reproduction Steps:** {'{{repro_steps}}'}
## Analysis Framework
### 1. Root Cause Investigation
- Examine stack trace for exact failure point
- Identify primary and secondary causes
- Check for common patterns in {'{{tech_stack}}'}
- Look for environmental factors (dependencies, config, etc.)
### 2. Impact Assessment
- Severity level (Critical/High/Medium/Low)
- User experience impact
- Business logic affected
- Data integrity concerns
### 3. Solution Strategy
- Immediate hotfix if critical
- Comprehensive fix approach
- Code changes required with examples
- Testing strategy to validate fix
### 4. Prevention Measures
- Code patterns that caused this
- Monitoring/alerts to catch early
- Code review checkpoints
- Documentation updates needed
## Output Format
Provide clear, actionable steps with:
- **Root Cause**: One sentence explanation
- **Fix**: Step-by-step implementation
- **Test Plan**: How to verify the fix
- **Prevention**: Avoid similar issues
Focus on {'{{priority}}'} priority and {'{{focus_area}}'} if specified.Template Variables Explicadas
- • {{error_type}} - Tipo do erro
- • {{tech_stack}} - Stack tecnológica
- • {{error_message}} - Mensagem de erro
- • {{priority}} - Prioridade do fix
- • {{focus_area}} - Área específica
- • {{context}} - Contexto adicional
Passo 3: Testando o Workflow
Execução via Command Line
# Método 1: Comando direto
claude --workflow debug-analyze-error \
--error_type="Runtime Error" \
--tech_stack="Next.js 14" \
--error_message="Cannot read property 'id' of undefined" \
--priority="high"
# Método 2: Prompt interativo
claude
> /workflow debug-analyze-error
> error_type: Runtime Error
> tech_stack: Next.js 14
> error_message: Cannot read property 'id' of undefined
> priority: highExemplo de Output Esperado
Aula 3: Biblioteca de Workflows Essenciais
📚 Templates Profissionais
15 workflows essenciais que cobrem 90% das tarefas de desenvolvimento. Copie, adapte e customize conforme suas necessidades.
🐛 Categoria: Debugging
debug-memory-leak.md
Analyze memory leak in {'{{language}}'} application:
**Memory Patterns Analysis:**
- Heap growth patterns identification
- Object retention analysis
- Event listener cleanup check
- Circular reference detection
**Stack:** {'{{stack}}'}
**Symptoms:** {'{{symptoms}}'}
**Profiling Data:** {'{{profiling_data}}'}
Provide memory optimization strategy with code examples.debug-race-condition.md
Investigate race condition in {'{{async_context}}'}:
**Concurrency Analysis:**
- Thread safety examination
- Shared resource access patterns
- Timing dependency identification
- Async operation sequencing
**Environment:** {'{{environment}}'}
**Timing Issues:** {'{{timing_patterns}}'}
Suggest synchronization solutions with implementation examples.⚡ Categoria: Performance
perf-optimize-queries.md
Optimize {'{{database}}'} queries for better performance:
**Query Analysis:**
- Execution plan examination
- Index usage evaluation
- Join optimization opportunities
- Query complexity assessment
**Current Performance:** {'{{current_metrics}}'}
**Target Performance:** {'{{target_metrics}}'}
**Schema:** {'{{schema_info}}'}
Provide optimized queries with performance impact estimates.perf-frontend-bundle.md
Analyze and optimize {'{{framework}}'} bundle size:
**Bundle Analysis:**
- Dependency size breakdown
- Tree-shaking opportunities
- Code splitting potential
- Lazy loading candidates
**Current Size:** {'{{current_size}}'}
**Target Size:** {'{{target_size}}'}
**Critical Path:** {'{{critical_assets}}'}
Suggest optimization strategy with implementation steps.🏗️ Categoria: Architecture
arch-microservice-design.md
Design microservice architecture for {'{{business_domain}}'}:
**Architecture Requirements:**
- Service boundaries definition
- Data consistency patterns
- Communication protocols
- Scalability considerations
**Scale:** {'{{expected_scale}}'}
**Tech Constraints:** {'{{tech_constraints}}'}
**Team Size:** {'{{team_size}}'}
Provide complete architecture blueprint with implementation roadmap.arch-refactor-legacy.md
Create refactoring strategy for legacy {'{{technology}}'} system:
**Legacy Analysis:**
- Technical debt assessment
- Risk evaluation
- Modernization paths
- Migration strategy
**Current State:** {'{{current_architecture}}'}
**Target State:** {'{{target_architecture}}'}
**Constraints:** {'{{business_constraints}}'}
Propose phased refactoring plan with risk mitigation.🧪 Categoria: Testing
test-generate-cases.md
Generate comprehensive test cases for {'{{function_name}}'}:
**Test Coverage Analysis:**
- Happy path scenarios
- Edge cases identification
- Error conditions
- Boundary value testing
**Function Signature:** {'{{function_signature}}'}
**Expected Behavior:** {'{{expected_behavior}}'}
**Dependencies:** {'{{dependencies}}'}
Create complete test suite with {'{{test_framework}}'} syntax.test-e2e-scenarios.md
Design E2E test scenarios for {'{{user_journey}}'}:
**User Flow Analysis:**
- Critical path identification
- User interaction patterns
- State transitions
- Error recovery flows
**Application:** {'{{app_type}}'}
**Test Environment:** {'{{environment}}'}
**Tools:** {'{{e2e_framework}}'}
Generate executable E2E test scenarios with data setup.Aula 4: Sintaxe Avançada de Templates
🚀 Nível Avançado
Técnicas avançadas de templating: condicionais, loops, validações e transformações de dados. Workflows inteligentes que se adaptam ao contexto.
Variáveis Condicionais
# refactor-component-smart.md
Refactor {'{{component_type}}'} component with focus on:
{'{{#if performance_focused}}'}
**Performance Optimization:**
- Memoization opportunities
- Render optimization
- Bundle size reduction
{'{{/if}}'}
{'{{#if accessibility_focused}}'}
**Accessibility Improvements:**
- ARIA attributes addition
- Keyboard navigation support
- Screen reader compatibility
{'{{/if}}'}
{'{{#if testing_focused}}'}
**Testing Enhancement:**
- Unit test coverage
- Integration test scenarios
- Mock strategies
{'{{/if}}'}
{'{{#unless has_tests}}'}
**Critical:** This component lacks tests. Priority should be:
1. Add basic test coverage first
2. Then proceed with refactoring
{'{{/unless}}'}
Base Requirements (always applies):
- Code quality improvement
- TypeScript strict mode compliance
- Error handling enhancement
{'{{#if tech_stack}}'}
Stack-specific considerations for {'{{tech_stack}}'}:
{'{{#switch tech_stack}}'}
{'{{#case "React"}}'}
- Hook optimization
- Component composition
- Prop drilling elimination
{'{{/case}}'}
{'{{#case "Vue"}}'}
- Composition API usage
- Reactive patterns
- Performance optimizations
{'{{/case}}'}
{'{{#case "Angular"}}'}
- Change detection strategy
- OnPush optimization
- RxJS patterns
{'{{/case}}'}
{'{{/switch}}'}
{'{{/if}}'}Sintaxe Condicional Explicada
Loops e Processamento de Arrays
# security-audit-multi.md
Perform security audit on multiple {'{{file_type}}'} files:
## Files to Analyze:
{'{{#each file_list}}'}
### {'{{this.name}}'} ({'{{this.size}}'})
**Risk Level:** {'{{this.risk_level}}'}
**Last Modified:** {'{{this.modified}}'}
{'{{#if this.high_risk}}'}
⚠️ **PRIORITY**: This file shows high-risk patterns
{'{{/if}}'}
{'{{/each}}'}
## Security Checklist:
{'{{#each security_checks}}'}
- [ ] {'{{this.category}}'}: {'{{this.description}}'}
{'{{#if this.automated}}'}
- Tool: {'{{this.tool}}'}
- Command: {'{{this.command}}'}
{'{{/if}}'}
{'{{/each}}'}
## Analysis Framework:
{'{{#each analysis_types}}'}
### {'{{@index}}'}.{'{{this.name}}'}
{'{{this.description}}'}
**Detection Patterns:**
{'{{#each this.patterns}}'}
- {'{{this}}'}
{'{{/each}}'}
{'{{/each}}'}
{'{{#if include_remediation}}'}
## Remediation Steps:
For each vulnerability found:
1. Classify severity (Critical/High/Medium/Low)
2. Provide fix code example
3. Update security tests
4. Document prevention measures
{'{{/if}}'}Sintaxe de Loops Explicada
Validações e Transformações
# deploy-strategy-smart.md
{'{{validate required: environment, app_type, scale}}'}
{'{{transform scale: uppercase}}'}
{'{{default region: "us-east-1"}}'}
Create deployment strategy for {'{{app_type}}'} in {'{{environment}}'} environment:
## Environment Configuration:
**Target:** {'{{environment | capitalize}}'}
**Scale:** {'{{scale}}'}
**Region:** {'{{region}}'}
{'{{#if custom_domain}}'}
**Domain:** {'{{custom_domain}}'}
{'{{/if}}'}
{'{{#validate_enum environment: ["development", "staging", "production"]}}'}
## Environment-Specific Settings:
{'{{#switch environment}}'}
{'{{#case "development"}}'}
- Single instance deployment
- Hot reloading enabled
- Debug logging on
- Mock external services
{'{{/case}}'}
{'{{#case "staging"}}'}
- Load balancer with 2+ instances
- Production-like data
- Performance monitoring
- Integration tests required
{'{{/case}}'}
{'{{#case "production"}}'}
- Auto-scaling enabled
- Circuit breakers active
- Comprehensive monitoring
- Blue-green deployment
- Rollback strategy required
{'{{/case}}'}
{'{{/switch}}'}
{'{{else}}'}
❌ Error: Environment must be one of: development, staging, production
{'{{/validate_enum}}'}
{'{{#validate_number scale: {min: 1, max: 100}}}'}
## Scaling Configuration:
- Initial instances: {'{{scale}}'}
- Max instances: {'{{scale | multiply: 3}}'}
- CPU threshold: 70%
- Memory threshold: 80%
{'{{else}}'}
❌ Error: Scale must be between 1 and 100
{'{{/validate_number}}'}
## Technology Stack:
{'{{#if tech_stack}}'}
{'{{#each tech_stack}}'}
- {'{{this.name}}'}: {'{{this.version}}'}
{'{{#if this.config}}'}
Config: {'{{this.config}}'}
{'{{/if}}'}
{'{{/each}}'}
{'{{else}}'}
**Note:** No specific tech stack provided. Using generic deployment patterns.
{'{{/if}}'}
{'{{#require_when environment="production": ["security_scan", "performance_tests", "monitoring_setup"]}}'}
## Production Requirements Met:
{'{{#each required_checks}}'}
✅ {'{{this}}'}
{'{{/each}}'}
{'{{/require_when}}'}Funções de Validação e Transformação
Aula 5: Organização e Versionamento de Workflows
📁 Organização Profissional
Sistema de organização, versionamento e compartilhamento de workflows. Estrutura escalável para equipes e projetos complexos.
Estrutura de Diretórios Profissional
~/.config/claude-desktop/workflows/
├── core/ # Workflows essenciais
│ ├── debugging/
│ │ ├── debug-analyze-error.md
│ │ ├── debug-memory-leak.md
│ │ └── debug-race-condition.md
│ ├── performance/
│ │ ├── perf-optimize-queries.md
│ │ ├── perf-frontend-bundle.md
│ │ └── perf-api-latency.md
│ ├── testing/
│ │ ├── test-generate-cases.md
│ │ ├── test-e2e-scenarios.md
│ │ └── test-api-contracts.md
│ └── architecture/
│ ├── arch-microservice-design.md
│ ├── arch-database-design.md
│ └── arch-security-review.md
├── project-specific/ # Por projeto
│ ├── project-alpha/
│ │ ├── deploy-alpha.md
│ │ ├── test-alpha-api.md
│ │ └── monitor-alpha.md
│ └── project-beta/
│ ├── migrate-beta-db.md
│ └── scale-beta.md
├── experimental/ # Workflows em teste
│ ├── ai-code-review.md
│ ├── automated-refactor.md
│ └── smart-deploy.md
├── shared/ # Para equipe
│ ├── team-code-review.md
│ ├── team-deploy-checklist.md
│ └── team-security-audit.md
├── archived/ # Workflows obsoletos
│ └── legacy/
└── templates/ # Templates base
├── _workflow-template.md
├── _debugging-template.md
└── _performance-template.mdConvenções de Organização
Workflows testados e estáveis
Project-Specific:Customizações por projeto
Novos workflows em teste
Templates:Bases para novos workflows
Sistema de Versionamento
# debug-analyze-error.md
# Bug Detective Workflow v2.1.0
# Created: 2025-01-15
# Last Updated: 2025-01-25
# Author: CrazyStack Team
# Stability: Stable
## Changelog
### v2.1.0 (2025-01-25)
- Added memory leak detection patterns
- Improved error categorization
- Added TypeScript-specific analysis
### v2.0.0 (2025-01-20)
- BREAKING: Changed variable names for consistency
- Added conditional logic for different tech stacks
- Improved output formatting
### v1.2.1 (2025-01-18)
- Fixed template variable validation
- Minor improvements to stack trace analysis
## Compatibility
- Claude Code: >= 1.2.0
- Requires: error_type, tech_stack, error_message
- Optional: priority, focus_area, context
## Usage Examples
```bash
# Basic usage
claude --workflow debug-analyze-error --error_type="Runtime" --tech_stack="React"
# Advanced usage with all parameters
claude --workflow debug-analyze-error \
--error_type="Memory Leak" \
--tech_stack="Node.js Express" \
--error_message="Heap growing by 50MB/hour" \
--priority="critical" \
--focus_area="database connections"
```
## Testing Status
- ✅ Tested with React errors
- ✅ Tested with Node.js errors
- ✅ Tested with database errors
- 🔄 Testing with Go errors (in progress)
---
# Workflow Content Starts HereBoas Práticas de Versionamento
MAJOR.MINOR.PATCH - Quebra compatibilidade, nova feature, bug fix
Documentar todas mudanças com impacto no uso
Indicar quais cenários foram testados
Controle de Versão com Git
# Inicializar repositório de workflows
cd ~/.config/claude-desktop/workflows
git init
git remote add origin https://github.com/your-team/claude-workflows.git
# Estrutura de branches
git checkout -b main # Workflows estáveis
git checkout -b develop # Novos workflows
git checkout -b experimental # Testes e experimentos
# Fluxo de desenvolvimento
git checkout develop
# ... criar/editar workflows
git add .
git commit -m "feat: add performance optimization workflow v1.0.0"
# Merge para main após testes
git checkout main
git merge develop
# Tags para releases
git tag -a v1.5.0 -m "Release v1.5.0: Performance workflows collection"
git push origin v1.5.0
# .gitignore para workflows
echo "# Ignore personal/sensitive workflows" > .gitignore
echo "personal/" >> .gitignore
echo "*.private.md" >> .gitignore
echo ".env" >> .gitignore⚠️ Cuidados com Segurança
• API Keys: Nunca versione workflows com chaves hardcoded
• Dados Sensíveis: Use templates com placeholders
• Workflows Privados: Mantenha em repositório separado
• Configurações de Projeto: Use .env ou config files
🎉 Módulo 2 Dominado!
Você criou biblioteca completa de workflows que elimina 80% da repetição no desenvolvimento. Próximo módulo: MCP servers para conectar Claude Code com ferramentas externas.
🎯 Exercício do Módulo 2
Desafio: Biblioteca Personalizada
Crie 5 workflows customizados específicos para sua stack tecnológica atual:
✅ Critérios de Sucesso
- • Todos workflows testados e funcionais
- • Variáveis condicionais implementadas
- • Documentação completa com exemplos
- • Organização em diretórios apropriados
- • Versionamento com changelog
- • Pelo menos 1 workflow com sintaxe avançada