This skill should be used when the user asks to "create a goal", "review my goals", "set a new goal", "check goal progress", or wants to ideate, create, or review goals linked to areas of focus.
Creates and reviews personal goals in Obsidian, linking them to projects or recurring Todoist tasks.
/plugin marketplace add oskar-dragon/claude-code/plugin install vault-manager@claude-codeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
goal-template.mdManage goals in the vault.
Goals live in Obsidian, not Todoist. A goal is achieved through projects. The only exception is recurring/habit goals which need Todoist recurring tasks for daily execution.
If argument is "create" or "review", use that mode.
Otherwise, ask Oskar:
Use AskUserQuestion to determine which mode.
Ask Oskar questions one at a time to understand the goal. Prefer multiple choice when possible.
type property):
Help Oskar think through the goal collaboratively:
Present the proposed plan and get Oskar's approval before creating the note.
Read goal-template.md first — it defines the frontmatter structure.
Create the goal note in Goals/ folder with:
Goals/Learn Rust.md)categories:
- "[[Goals]]"
type:
- "[[Career]]" # Area of Focus as wikilink
year: 2026
quarter: 1
done: false
![[Projects.base#Topic]] embed from the templateOne-time goal:
/vault-manager:project's job with its own ideation flowRecurring/habit goal:
dueString: "every Monday, Wednesday, Friday")Save goal creation to auto memory goals.md topic file.
Read all goal notes from Goals/ folder:
done: false)type property)For each active goal:
Projects/ folder for notes with topics linking to this goal)Present goal status to Oskar:
For goals needing attention:
/vault-manager:project). Do NOT create Todoist tasks.Save goal status changes and insights to auto memory.
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.