Strong Communication
- Be specific in your prompts: Rather than asking “Fix this bug,” provide context like “Fix the memory leak in the user authentication flow that occurs after 5 login attempts”
- Provide clear objectives: Tell Exponent what you’re trying to accomplish, not just the immediate task
- Use progressive disclosure: Start with a high-level task, then add details as needed rather than overwhelming with information upfront
- Reference key files directly: Use the
@
symbol to reference specific files when asking questions about them
Effective Workflows
- Create checkpoints before significant changes: Use checkpoints to save your current state before attempting experimental changes
- Use chat summaries for long sessions: Create summaries when conversations get lengthy to maintain context and performance
- Start with manual confirmation: Begin with manual confirmation mode until you understand how Exponent approaches tasks
- Progress gradually to auto-confirm: Advance to read-only auto-confirm, then to full auto-confirm as you build trust
- Set appropriate step limits: When using auto-confirm, start with 5-10 steps and adjust based on task complexity