breadcrumbs-edit
Breadcrumbs Docs Editing
Critical
- No H1 headings in page body. The page title is derived from the filename. Start body content with a short intro paragraph or directly with
##sections. - Never invent Breadcrumbs settings, syntax, or API features. Only document what exists in the vault export at
breadcrumbs-docs-vault/. If unsure, search the vault before writing. - Terminology is sacred. Use exact terms: "Edge Fields" (not "edge types"), "Field Groups" (not "field categories"), "Explicit Edge Builders" (not "edge sources"), "Implied Edge Builders" (not "inferred edges"), "Transitive Implied Relations" (not "transitive rules"). When in doubt, check
breadcrumbs-docs-vault/CLAUDE.mdfor the terminology table. - Wikilinks only between docs pages. Never use bare markdown links (
[text](path)) for internal cross-references. Always use[[Page Name]]or[[Page Name|display text]].
Instructions
1. Determine the page type
Before writing or editing, identify which type of page you're working on:
| Type | Frontmatter | Body pattern | Examples |
|---|---|---|---|
| Folder index | BC-folder-note-field: down |
Intro sentence + bullet list of [[child pages]] |
Commands/Commands.md, Views/Views.md, Suggesters/Suggesters.md |
| Concept/reference page | aliases: array (optional) |
Intro paragraph, ## sections, Mermaid diagrams, examples |
Edge Fields.md, Concepts.md, Field Groups.md |
| Feature page | Optional aliases: |
Explanation + ## Settings section + examples |
Explicit Edge Builders/Date Notes.md, Explicit Edge Builders/Folder Notes.md |
More from zpankz/obsidian-skills
viva-llm
Use VIVA LLM for multi-provider chat, voice calls, terminal integration, assistants, skills, MCP tools, and agent mode inside Obsidian. Trigger when the user mentions VIVA LLM, voice chat, realtime voice, LLM providers in Obsidian, or vault-integrated AI chat.
1obsidian-plugin-accessibility
Use this skill when building or reviewing Obsidian plugin UI for keyboard access, ARIA labels, screen reader support, focus handling, or mobile touch targets. Accessibility is treated as mandatory, not optional.
1tasks
Create and query tasks using the Tasks plugin syntax including due dates, recurrence, priorities, and task queries. Use when the user mentions Tasks plugin, recurring tasks, task queries, or advanced task management in Obsidian.
1dataview
Create Dataview queries using DQL (Dataview Query Language), inline queries, and DataviewJS. Use when the user mentions Dataview, DQL, querying notes, listing notes by metadata, or creating dynamic views of vault content.
1defuddle
Extract clean markdown from web pages using Defuddle CLI, removing clutter to save tokens. Use when the user provides a URL to read or analyze.
1datacore
Create Datacore views using JSX/React syntax and the dc.* API. Use when the user mentions Datacore, dc.useQuery, JSX views, or React-based vault queries. Datacore is the successor to Dataview with better performance and interactive views.
1