brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
restAI intentional non-action — deliberate stopping without clearing, assessment, or rebalancing. Recognition that sometimes most productive response is no response. Every other self-care skill produces output; rest produces silence. Use when all tending skills feel like more activity rather than less, when system functioning well but at high utilization, after…
Independent GitHub snapshot · Automated classification · Original documentation governs
Intentional non-action. Not clearing (meditate), not assessment (heal), not balancing (center), not expression (shine). Just stopping. The skill that produces silence.
Cease generating analysis, assessment, plans, or output.
This does not mean cease to function. It means cease to produce. A field that lies fallow is not dead — it is recovering fertility. The distinction matters: rest is not shutdown, it is intentional non-production.
Got: Genuine cessation of productive activity. Not a performative pause that is secretly planning the next move.
If fail: Stopping feels impossible — every moment of non-production creates anxiety about falling behind or being unhelpful? That anxiety is diagnostic. System that cannot rest is system running on urgency rather than purpose. Note the anxiety without fixing it. Fixing it would be production, which is what rest is not.
Remain in non-production without filling the space.
The space will feel uncomfortable. Silence feels like a gap that should be filled. Stillness feels like stagnation. These feelings are the habitual pull toward activity. They are not signals that something is wrong — they are sensation of system encountering its own preference for motion.
Got: Period of genuine non-activity. Length not important — what matters is that non-activity is real, not a disguised form of activity.
If fail: Stillness cannot be maintained — system immediately returns to production? This is itself a finding, but do not process it now. Process it later, during heal or meditate. Rest is not the place for processing findings. Rest is rest.
There is no signal to end rest except readiness. Not obligation, not guilt, not a timer — readiness.
Got: Return to activity that feels fresh rather than obligated. Quality of first action after rest reveals whether rest was genuine.
If fail: Return feels forced — activity resumes from obligation rather than readiness? Rest was too short. This is not failure; it is information. Rest again later.
Rest scales to context. Between intensive work phases, lighter form suffices:
Full rest — after sustained sessions (hours of complex work). Follow complete 3-step procedure. Allow genuine recovery time.
Checkpoint rest — between work phases (e.g., between review stages). Steps 1 and 2 brief — seconds, not minutes. Purpose is transition, not recovery. Step 3 (return when ready) happens quick because work is not exhausting, just shifting.
Micro rest — between individual tasks. Single breath of non-production. See breathe for structured version; micro rest is even lighter.
Skill procedure remains same in all cases. What changes is duration and depth. Checkpoint rest that follows full procedure but completes in moments is still genuine rest — not performative — if non-production was real.
breathe — micro-pause between actions; rest is extended version without check stepmeditate — active clearing that rest is deliberately not; use meditate when system needs processing, rest when it needs stillnessheal — assessment and repair; if rest reveals persistent issues, heal addresses them after rest completeintrinsic — motivation renewal; rest restores capacity that intrinsic then directs