storage-templates

Create reusable storage templates with maturity lifecycle and naming conventions.

326|35|Updated Nov 23, 2025

Search Tags:#templates #documentation #lifecycle #knowledge-management #storage

Ready to run

npx skills add https://github.com/athola/claude-night-market --skill storage-templates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: storage-templates
Source: https://github.com/athola/claude-night-market/tree/main/plugins/leyline/skills/storage-templates
Command: npx skills add https://github.com/athola/claude-night-market --skill storage-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generic template patterns and lifecycle stages for knowledge storage and documentation.

Core Features & Use Cases

Evergreen, Growing, Seedling, Reference templates
Maturity lifecycle management and naming conventions
Domain variants for memory-palace, sanctum, spec-kit, etc.

Quick Start

Apply a maturity scheme to new knowledge entries and organize by templates.

Frequently Asked Questions about storage-templates

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

FAQPage Schema

How do I organize documentation with consistent templates and lifecycle stages?▼

Template-driven storage provides reusable templates for evergreen, growing, seedling, and reference content patterns with standardized naming and frontmatter conventions. This enforces maturity lifecycle stages and ensures consistent organization across knowledge management and documentation systems.

What's the best way to manage content maturity and promotion across knowledge bases?▼

Apply maturity lifecycle management to enforce promotion criteria and stage progression. Storage templates standardize naming conventions and frontmatter, enabling predictable transitions between content states while maintaining domain-specific variants for memory-palace, sanctum, and spec-kit integrations.

Can I enforce naming conventions and file structure across documentation projects?▼

Yes. Storage templates enforce domain-specific file naming conventions and standardized frontmatter across all content entries, eliminating inconsistency in documentation structure and making lifecycle management predictable across configuration management and knowledge storage systems.

How do I prevent inconsistent content templates in growing knowledge systems?▼

Template-driven storage solves inconsistent content patterns by defining reusable templates for each maturity stage. Lifecycle management and naming conventions ensure all new entries follow standardized structures, eliminating ad-hoc formatting in knowledge management and documentation workflows.

What lifecycle patterns work for knowledge bases with evergreen and reference content?▼

Storage templates support four maturity patterns—evergreen, growing, seedling, and reference—each with defined promotion criteria and integration points. Use lifecycle management to transition content through stages while maintaining domain-specific extensions tailored to your storage system.

Do I need additional tools to integrate templates across multiple knowledge domains?▼

Storage templates support integration across memory-palace, sanctum, and spec-kit domains with domain variants built in. Standardized naming and frontmatter enable seamless cross-domain use without additional configuration layers for most knowledge management setups.