Obsidian vault mechanics - wiki links, .obsidian/ config, daily notes, plugins. Use when working with Obsidian vaults or structured markdown.
npx claudepluginhub technicalpickles/pickled-claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/connecting.mdreferences/daily-linking.mdreferences/note-patterns.mdreferences/para.mdreferences/routing.mdreferences/zettelkasten.mdTool-specific mechanics for working with Obsidian vaults.
A directory is an Obsidian vault if it contains .obsidian/ folder.
Syntax: [[Note Title]] or [[path/Note Title]]
[[Note Title|display text]]Obsidian stores settings in .obsidian/ at vault root:
| File | Purpose |
|---|---|
daily-notes.json | Daily note folder and template |
templates.json | Templates folder location |
zk-prefixer.json | Zettelkasten/inbox settings |
app.json | General settings (new file location, attachments) |
plugins/ | Installed plugin data |
// daily-notes.json
{
"folder": "Fleeting",
"template": "Templates/daily"
}
// templates.json
{"folder": "Templates"}
// zk-prefixer.json
{
"folder": "📫 Inbox",
"template": "Templates/frontmatter"
}
// app.json
{
"newFileFolderPath": "📫 Inbox",
"attachmentFolderPath": "🖇 Attachments"
}
Finding today's note:
.obsidian/daily-notes.json for folderYYYY-MM-DD.md (Obsidian default){folder}/{YYYY-MM-DD}.mdTemplate application:
daily-notes.jsonIf Glossary.md exists at vault root:
Vaults should have a CLAUDE.md at root describing:
See templates/vault-claude-md.md for template.
When a vault has areas with semantic overlap (e.g., "tool sharpening" vs "software engineering"), the vault CLAUDE.md can include ### Disambiguation: sections that guide routing decisions.
The routing algorithm checks for:
See references/routing.md for the full disambiguation format and how to build custom rules.
For methodology (tool-agnostic):
references/para.md - PARA organizational systemreferences/zettelkasten.md - Naming conventionsreferences/note-patterns.md - Note templatesreferences/routing.md - Routing algorithm with disambiguation supportreferences/daily-linking.md - Linking captured notes to daily noteExpert 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.