Files
ECC/.kiro/steering/performance.md
T
Eric BellavanceandClaude Opus 5.5 1e895858d0 docs(kiro): use always inclusion for always-on steering files
Kiro only loads steering files automatically in every conversation when
they use `inclusion: always`; `auto` loads them only when the request
matches the description. Switch the always-on steering files to
`always` and update README, install.sh and docs accordingly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 13:23:13 -04:00

1.4 KiB

inclusion, name, description
inclusion name description
always performance Performance optimization guidelines including model selection strategy, context window management, and build troubleshooting

Performance Optimization

Model Selection Strategy

Claude Haiku 4.5 (90% of Sonnet capability, 3x cost savings):

  • Lightweight agents with frequent invocation
  • Pair programming and code generation
  • Worker agents in multi-agent systems

Claude Sonnet 5 (Best coding model):

  • Main development work
  • Orchestrating multi-agent workflows
  • Complex coding tasks

Claude Opus 5 (Deepest reasoning):

  • Complex architectural decisions
  • Maximum reasoning requirements
  • Research and analysis tasks

Context Window Management

Avoid last 20% of context window for:

  • Large-scale refactoring
  • Feature implementation spanning multiple files
  • Debugging complex interactions

Lower context sensitivity tasks:

  • Single-file edits
  • Independent utility creation
  • Documentation updates
  • Simple bug fixes

Extended Thinking

Extended thinking is enabled by default in Kiro, reserving tokens for internal reasoning.

For complex tasks requiring deep reasoning:

  1. Ensure extended thinking is enabled
  2. Use structured approach for planning
  3. Use multiple critique rounds for thorough analysis
  4. Use sub-agents for diverse perspectives

Build Troubleshooting

If build fails:

  1. Use build-error-resolver agent
  2. Analyze error messages
  3. Fix incrementally
  4. Verify after each fix