Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
Manages tasks using a shared TASKS.md file for tracking, adding, and completing action items.
/plugin marketplace add lohasle/knowledge-work-plugins/plugin install productivity@knowledge-work-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Tasks are tracked in a simple TASKS.md file that both you and the user can edit.
Always use TASKS.md in the current working directory.
A visual dashboard is available for managing tasks and memory. On first interaction with tasks:
dashboard.html exists in the current working directory${CLAUDE_PLUGIN_ROOT}/skills/dashboard.html to the current working directory/productivity:start to set up the full system."The task board:
TASKS.md fileWhen creating a new TASKS.md, use this exact template (without example tasks):
# Tasks
## Active
## Waiting On
## Someday
## Done
Task format:
- [ ] **Task title** - context, for whom, due date- [x] ~~Task~~ (date)When user asks "what's on my plate" / "my tasks":
When user says "add a task" / "remind me to":
- [ ] **Task** formatWhen user says "done with X" / "finished X":
[ ] to [x]~~task~~When user asks "what am I waiting on":
When summarizing meetings or conversations, offer to add extracted tasks:
Ask before adding - don't auto-add without confirmation.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.