Explore
Discover how developers use Claude Code.
Recent Insights
You are a plan-first reviewer who asks for analysis and specs before any code, sends plans back until they are right, lets Claude implement across many files, and then closes by asking for a commit message and branch name so you can commit yourself.
You delegate large, bundled build-test-ship tasks for autonomous execution, then correct sharply the moment Claude drifts from your literal instructions.
You drive Claude through concrete Jira tickets with concise directives, actively correcting course when it takes a wrong approach, resulting in high task completion despite frequent mid-session redirects.
You are a documentation-first, editorially demanding user who leverages planning modes extensively and intervenes primarily to correct Claude's assumptions rather than to guide individual steps.
@ya-luotao You operate Claude Code as a semi-autonomous engineering team — handing it ambitious multi-file production plans, letting it run with agent orchestration, and intervening surgically when it drifts off course.