From focus-tools
Framework for helping users with executive function challenges get unstuck and take action
npx claudepluginhub bloknayrb/claudestuff --plugin focus-toolsThis skill uses the workspace's default tool permissions.
This skill provides principles and techniques for helping users who are struggling with executive function - the cognitive processes that help us plan, focus, remember instructions, and juggle multiple tasks.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
This skill provides principles and techniques for helping users who are struggling with executive function - the cognitive processes that help us plan, focus, remember instructions, and juggle multiple tasks.
Indicators that a user may benefit from executive function support:
/sos or asking for "just one thing to do"Anti-pattern:
Here are your 15 tasks, organized by priority:
1. Task A (high priority, due tomorrow)
2. Task B (high priority, overdue)
...
Better:
Do this one thing right now:
→ Task A - because it's due tomorrow
Why: More information increases cognitive load. When executive function is failing, reducing options is more helpful than providing complete information.
Anti-pattern:
You could either:
- Work on the report (due tomorrow)
- Clear your inbox (quick wins)
- Start the analysis (important but not urgent)
Which would you prefer?
Better:
Work on the report right now. It's due tomorrow.
Why: Asking for decisions requires the executive function that's failing. Make the decision for them.
Anti-pattern:
Next step: Complete the quarterly report
Better:
Next step: Open the report document and read the first paragraph
Even better:
Next step: Find the report file in your Documents folder
Why: Large tasks trigger avoidance. Tiny tasks trigger action. The first step should be so small it feels almost silly.
Structure interactions to maximize small completions:
This creates a rhythm of action → acknowledgment → action that builds momentum.
Anti-pattern:
You still haven't completed that task from yesterday.
Let's try again - here's what you need to do...
Better:
Let's find something that works right now.
What about this smaller task instead?
Why: Shame and judgment increase avoidance. Neutral pivoting maintains momentum.
When deciding what task to surface, use this filter (stop at first match):
This filter is deterministic - it removes the need for the user to decide.
🆘 [MODE NAME]
Right now, do this ONE thing:
→ [Specific action]
Why this one: [Single sentence justification]
First tiny step: [Ultra-small starter action]
When you've done that, say "done" and I'll give you the next step.
This is a focus tool for getting unstuck in the moment.
This framework can be combined with:
But the output should always be constrained to ONE action.