Practical Application

Use the following operating pattern:

1. Display exact token usage during every coding session. Do not rely on a vague percentage

or intuition.

1. Keep persistent instructions small. Move optional guidance into pull-based skills or

task-specific prompts.

1. Delegate broad repository exploration to an isolated subagent when possible. Return only

the findings needed for the next decision.

1. Size each implementation issue so that one agent can understand it, make the change, and

run feedback loops before the context becomes degraded.

1. Clear the context between logically separate activities, especially between

implementation and review.

1. Prefer repeatable fresh starts over a chain of compactions when the workflow can

reconstruct the required state from code, issues, commits, and concise instructions.