The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
When using implementation intentions to create behavioral pauses, specify the triggering situation at high detail ('If I receive code review feedback challenging my approach...') rather than generically ('If I get criticism...') to increase cue detectability.
Write implementation intentions beneath each written goal using 'When [specific recurring situation], I will [specific first action]' format, specifying concrete triggers rather than time-based or motivation-based conditions.
Define agent triggers as observable external events or measurable internal states rather than subjective feelings or abstract conditions, because vague triggers cannot be recognized reliably when they occur.
When setting a new boundary, predict and document 3-5 specific ways people will test it (who will test, what form tests will take) and pre-write your planned responses before tests arrive, because anticipating tests converts surprise into expected system behavior you've already decided how to handle.
When forming implementation intentions for novel or complex goals, generate multiple if-then plans covering different potential breakdown contexts rather than relying on a single anticipated trigger, because breakdown patterns in unfamiliar domains cannot be predicted accurately from first principles.
Limit active implementation intentions to 1-3 simultaneously for novel behaviors, adding additional if-then plans only after existing ones have compiled into automatic execution, because cue-accessibility mechanisms have finite attentional capacity.
Before high-stakes interactions where your default pressure response typically fires, pre-script an implementation intention using the format: 'When I notice [specific somatic cue of my default], I will [specific alternative action] before [default response].'
Choose task management tools that support if-then implementation intentions and context tagging over feature-rich project management tools when your primary need is execution not coordination—simpler tools with behavior-triggering structure beat complex tools optimized for planning.