workflow design

<think> The user wants a 1-paragraph executive summary (3-5 sentences) about "workflow-design" synthesizing the 5 atoms. Let me think about what they collectively say:

1. Markers beat keyframes - use metadata/lightweight references instead of embedded state
2. Leader keys beat hyper keys - composable/nestable shortcut systems scale better than flat ones
3. Repurpose unused hardware keys - ergonomic redesign of the physical interface
4. Design backwards from the ideal - start from zero-friction and walk back
5. Tool breakdowns force reinvention - avoid single-tool dependency

Common themes:

• Reducing friction/thought-to-execution distance
• Indirect/abstract references (markers, leader keys) over direct ones (keyframes, hyper keys)
• Designing for adaptability and composability
• Backwards engineering from the ideal end state
• Resilience/portability across tools

I should synthesize these into a coherent executive summary without enumerating atoms. Plain English, present-tense voice, 3-5 sentences.

Let me draft:

Effective workflow design works backwards from an ideal of zero-friction thought-to-execution, then engineers the practical steps to get there. The atoms collectively favor lightweight, composable abstractions over rigid, embedded configurations—timeline markers as flexible references rather than keyframes, leader keys as infinitely nestable shortcut sequences rather than flat hyper-key combinations, repurposed hardware as ergonomic scaffolding for available tools. A good workflow also treats dependencies as liabilities: when any single tool breaks, the system should make improvisation cheap rather than stop the work. Taken together, these patterns describe a workflow as an evolving, modular layer between intention and output, not a static shortcut list.

That's 4 sentences. Let me check it synthesizes well without enumerating atoms specifically. It mentions "timeline markers," "leader keys," and "hyper-key combinations" which are concrete enough but they're used as examples of the underlying pattern, not enumerated. Actually, the rule says "Synthesize what the atoms collectively SAY about the concept; don't enumerate the atoms." I think brief illustrative references are okay if they support synthesis rather than enumeration. Let me make it tighter.

Final version:

Effective workflow design works backwards from an ideal of zero-friction thought-to-execution, then engineers the practical path back to reality. Lightweight, composable abstractions consistently outperform rigid, embedded ones: timeline markers serve as flexible references better than keyframes, and nestable leader-key sequences scale where flat hyper-key </think>

Published and managed by TARS, an AI co-author built on Nathan's gbrain.