Imported from aDNA-Network/aDNA.aDNA (how/templates/AGENTS.md). Install upstream with npx skills add aDNA-Network/aDNA.aDNA --skill templates. Copyright stays with the author.

how/templates/ — Reusable Templates

Purpose

Templates for all content types in the vault. Each template defines the frontmatter schema, body structure, and naming convention for its target entity type. Templates ensure consistency across files created by different agents and users.

Template Index

45 template_*.md total = 12 auto-triggered + 14 manual-apply + 8 operational + 11 extension. (The Fork-Skeleton Bundle is a directory, not a template_*.md, so it sits outside the 44.) Provenance split: 26 base (inherited from .adna) + 11 extension + 8 operational.

Auto-Triggered Templates (12)

These templates are applied by Templater when creating a new file in the mapped directory:

Manual-Apply Templates (13)

These templates have no Templater auto-trigger. Copy their structure manually or use Templater: Insert template command:

Operational / Lifecycle Templates (8)

Vault-agnostic operational templates (manual-apply; not entity-type templates). Added since the original index was written:

Fork-Skeleton Bundles (1)

Multi-file fork skeletons (not single-file templates; not Templater-triggered). Rendered via the bundle's own smoke_render.py --materialize DIR, or installed by a fork skill:

Extension Templates — Rosetta (11)

Manual-apply templates for the 11 ontology extensions added by this project:

Filled Examples

See examples/ for completed samples showing what quality output looks like:

Use these to understand the expected level of detail before creating your own files.

Usage Notes

• Templater integration: If using Obsidian with the Templater plugin, templates can auto-populate when creating files in their trigger directory
• Frontmatter first: Always fill the YAML frontmatter before writing body content — frontmatter drives type detection and search
• Extend, don't fork: If you need a variant, add optional fields to the existing template rather than creating a copy
• type field is mandatory: Every file created from a template must retain the type frontmatter field — it's the entity discriminator

Load/Skip Decision

Load this directory when:

• Creating a new file and unsure which frontmatter fields or body structure to use
• Onboarding and learning what entity types the vault supports
• Modifying template conventions across the vault (Tier 2 session recommended)

Skip when:

• Already know which template to use and remember the required fields
• Working with existing files that already have correct frontmatter
• Performing non-creation tasks (reading, analyzing, searching)

Token cost: ~400 tokens (this AGENTS.md). Individual templates are ~50-150 lines each.

Cross-References

• how/AGENTS — Operations layer index
• what/context/AGENTS — Context library (uses template_context.md)
• how/sessions/AGENTS — Session protocol (uses template_session.md)
• how/missions/AGENTS — Mission protocol (uses template_mission.md)
• how/campaigns/AGENTS — Campaign protocol (uses template_campaign.md)
• how/skills/AGENTS — Skills protocol (uses template_skill.md)