vault-structure

Enforce consistent vault folder layouts, naming conventions, and draft lifecycles.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/viditparashar96/second-brain-claude --skill vault-structure-viditparashar96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-structure
Source: https://github.com/viditparashar96/second-brain-claude/tree/main/skills/vault-structure
Command: npx skills add https://github.com/viditparashar96/second-brain-claude --skill vault-structure-viditparashar96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the memory vault consistent, discoverable, and reliable by prescribing folder locations, naming patterns, and usage rules so agents and humans avoid duplication, lost context, and messy RAG inputs.

Core Features & Use Cases

  • Defines a canonical folder layout for daily logs, meetings, projects, clients, research, content, team context, and draft lifecycles to standardize where information is stored.
  • Enforces naming conventions (date-first filenames and slugified titles), append-only daily logs, and one-entity-per-file rules to make long-term memory concise and loadable into every session.
  • Manages draft lifecycles with active, sent, and expired buckets and requires checking for existing files before creating new ones to prevent duplicates.
  • Use case: Save meeting notes to the meetings folder, keep a one-line pointer in the daily log, and keep MEMORY.md concise for fast context loading.

Quick Start

Save your sprint planning notes to meetings/2026-04-13-sprint-planning.md and add a one-line reference to today's daily log.

Frequently Asked Questions about vault-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize my AI memory vault to improve context retrieval?

To organize your AI memory vault, apply a canonical folder layout for daily logs, meetings, projects, and clients, using consistent naming conventions to ensure reliable retrieval and context loading for AI assistants.

What file naming conventions should I use for daily logs and meeting notes?

Use date-first filenames and slugified titles for meeting notes and projects. Daily logs should follow an append-only rule, while all files must enforce a one-entity-per-file rule to keep long-term memory concise and loadable.

How do I manage draft lifecycles in a knowledge management vault?

Manage draft lifecycles by separating files into active, sent, and expired buckets. Always check for existing files before creating new ones to prevent duplicates and maintain a clean, reliable knowledge management vault.

Why does my RAG context loading fail with messy vault inputs?

RAG context loading fails when vault inputs lack standardized folder locations and one-entity-per-file rules. Enforcing naming conventions and keeping MEMORY.md concise prevents duplication and ensures reliable RAG inputs.

Can I use this structure for both local and cloud memory vaults?

Yes, the prescribed folder locations, usage rules, and naming patterns apply to saving, retrieving, and organizing information in both cloud and local memory vaults for personal or team contexts.