Waker Design
- Single responsibility: Each Waker should have a clearly defined area of expertise and avoid overly broad responsibilities. For example, a “security audit expert” is better than a “full-stack engineer.”
- Make the Identity specific: Clearly define the role, professional background, and boundaries of capability.
- Keep the Persona consistent: Define a stable communication style so the Waker’s behavior is predictable.
- Keep the Bible concise: Include only the most important rules and knowledge to avoid information overload that scatters attention.
- Be selective with Skills: Install only the necessary skills to reduce the decision-making burden.
Conversation Techniques
- Clearly describe the task goal and the expected output format.
- Use the working directory to give the Waker the correct project context.
- Break complex tasks into steps and guide the Waker through them progressively.
- Make good use of the file upload feature to provide reference materials.
- Use group collaboration to let multiple specialized Wakers work together on complex problems.
WakerFlow Usage
- Start with simple flows and add complex patterns only after confirming the logic is correct.
- Keep the number of Phases to 3-5.
- Use a schema to constrain the worker output format.
- Use an
askUsernode at key decision points. - Get the flow working with a simple worker first, then gradually add complexity.
Cost Optimization
- Use lightweight models for simple tasks and advanced models for complex reasoning.
- Schedule non-urgent tasks to run during off-peak hours.
- Keep the number of tasks in a
parallelblock moderate (3-5) to avoid resource contention. - Make good use of Memory to let the Waker remember common patterns and reduce repeated instructions.