@Av1dlive: jev + sonnet 5.5 is f**king insane. my entire workflow got 4x faster after adding these 6 lines to CLAUDE.md. [with jev…

X AI KOLs Timeline Tools
ai-workflow claude development-tips jev sonnet-5.5 productivity

Summary

A user shares how integrating jev with sonnet 5.5 and adding 6 lines to CLAUDE.md made their workflow 4x faster, providing rules for effective Claude usage.

jev + sonnet 5.5 is f**king insane. my entire workflow got 4x faster after adding these 6 lines to CLAUDE.md. [with jev connected, paste this] 1. Before you start a Claude worker, ask Jev once to select a host-approved profile with one or two sessions. The profile must specify each session’s model and effort level. If Jev makes no selection, use the host default. 2. The host must check Jev’s selection. The host must set the model and effort before each session starts. Keep these settings fixed during the session. The host controls permissions and approvals. 3. Use Sonnet 5.5 at medium effort for clear coding tasks. Use higher effort for complex reasoning or JSON tasks. Use a second Claude only for independent research or a review that the user requested. 4. Give the second Claude the task, applicable files, limits, and completion requirements. Return its findings and evidence to the lead. 5. Complete the requested work. Ask the user only when you cannot continue without input or before an action that needs approval. Do not add features, tests, files, documentation, refactors, or review rounds that the user did not request. When the work is complete and checked, stop. Report the result. 6. Before you report completion, run a test, build, type check, or command that checks the code change. If no check can run, identify the missing check. Explain why it cannot run. same task. two timers. watch the difference.
Original Article
View Cached Full Text

Cached at: 09/29/26, 01:57 PM

jev + sonnet 5.5 is f**king insane. my entire workflow got 4x faster after adding these 6 lines to CLAUDE.md. [with jev connected, paste this] 1. Before you start a Claude worker, ask Jev once to select a host-approved profile with one or two sessions. The profile must specify each session’s model and effort level. If Jev makes no selection, use the host default. 2. The host must check Jev’s selection. The host must set the model and effort before each session starts. Keep these settings fixed during the session. The host controls permissions and approvals. 3. Use Sonnet 5.5 at medium effort for clear coding tasks. Use higher effort for complex reasoning or JSON tasks. Use a second Claude only for independent research or a review that the user requested. 4. Give the second Claude the task, applicable files, limits, and completion requirements. Return its findings and evidence to the lead. 5. Complete the requested work. Ask the user only when you cannot continue without input or before an action that needs approval. Do not add features, tests, files, documentation, refactors, or review rounds that the user did not request. When the work is complete and checked, stop. Report the result. 6. Before you report completion, run a test, build, type check, or command that checks the code change. If no check can run, identify the missing check. Explain why it cannot run. same task. two timers. watch the difference.

Avid (@Av1dlive): AX will make 1000s of millionaires in 2027.

agents are becoming the gatekeepers to software.

i broke down what to build and how to become AX engineers.

read the full article ↓

Similar Articles