storage-templates
Generic template patterns and lifecycle stages for knowledge storage,configuration management, and structured documentation.Triggers: storage templates, lifecycle stages, maturity progression, namingconventions, knowledge storage, configuration templates, documentation patternsUse when: organizing knowledge storage, managing configuration lifecycle,creating structured documentation, establishing naming conventionsDO NOT use when: simple storage without lifecycle or structure needs.Consult this skill when designing storage and documentation systems.
When & Why to Use This Skill
This Claude skill provides a comprehensive framework for structured knowledge storage and documentation lifecycle management. It enables users to implement standardized template patterns, maturity progression models (from Seedling to Evergreen), and consistent naming conventions, ensuring that information remains organized, searchable, and scalable across various storage systems and domains.
Use Cases
- 1. Knowledge Management Systems: Building a 'Digital Garden' or Zettelkasten using maturity stages to track the evolution of notes from early ideas to stable knowledge.
- 2. Technical Documentation: Standardizing project documentation with clear naming conventions and lifecycle statuses to distinguish between active drafts and permanent references.
- 3. Configuration Management: Creating structured templates for system configurations to maintain consistency and facilitate easy retrieval and updates.
- 4. Content Strategy: Managing the progression of research and documentation through a defined workflow, ensuring high-quality content is promoted and outdated information is archived.
| name | storage-templates |
|---|---|
| description | | |
| Triggers | storage templates, lifecycle stages, maturity progression, naming |
| Use when | organizing knowledge storage, managing configuration lifecycle, |
| DO NOT use when | simple storage without lifecycle or structure needs. |
| category | infrastructure |
| tags | [templates, storage, lifecycle, maturity, organization, patterns] |
| dependencies | [] |
| infrastructure | [templates, lifecycle-management, naming-conventions] |
| patterns | [maturity-stages, template-structures, file-organization] |
| complexity | beginner |
| estimated_tokens | 600 |
| progressive_loading | true |
Table of Contents
- Overview
- When to Use
- Core Concepts
- Template Types
- Maturity Lifecycle
- Quick Start
- Basic Template Structure
- Core Content
- Metadata
- File Naming Conventions
- Domain Applications
- Common Patterns
- Promotion Workflow
- Template Selection Guide
- Integration Pattern
- Detailed Resources
- Exit Criteria
Storage Templates
Overview
Generic template patterns and lifecycle management for structured content storage. Provides reusable templates, maturity progression models, and file naming conventions that work across different storage domains.
When to Use
- Building knowledge management systems
- Organizing documentation with maturity stages
- Need consistent file naming patterns
- Want template-driven content creation
- Implementing lifecycle-based workflows
Core Concepts
Template Types
| Type | Purpose | Maturity | Lifetime |
|---|---|---|---|
| Evergreen | Stable, proven knowledge | High | Permanent |
| Growing | Active development | Medium | 1-3 months |
| Seedling | Early ideas | Low | 1-2 weeks |
| Reference | Tool/version-specific | N/A | Until deprecated |
Maturity Lifecycle
seedling → growing → evergreen → archive
↓ ↓ ↓ ↓
1-2 weeks 1-3 months permanent deprecated
Verification: Run the command with --help flag to verify availability.
Quick Start
Basic Template Structure
---
title: [Content Title]
created: [YYYY-MM-DD]
maturity: seedling|growing|evergreen|reference
tags: [relevant, tags]
---
# [Title]
## Core Content
[Main information]
## Metadata
[Context and attribution]
Verification: Run the command with --help flag to verify availability.
File Naming Conventions
| Type | Pattern | Example |
|---|---|---|
| Evergreen | topic-name.md |
functional-core-pattern.md |
| Growing | topic-name.md |
async-patterns.md |
| Seedling | YYYY-MM-DD-topic.md |
2025-12-05-template-idea.md |
| Reference | tool-version.md |
python-3.12-features.md |
Domain Applications
Add domain-specific fields to templates:
- memory-palace:
palace,districtfor knowledge organization - sanctum:
scope,versionfor commit templates - spec-kit:
phase,statusfor specifications
See modules/template-patterns.md for detailed examples.
Common Patterns
Promotion Workflow
Seedling → Growing:
- Accessed more than once
- Connected to other entries
- Expanded with new insights
Growing → Evergreen:
- Proven useful over 3+ months
- Stable, not frequently edited
- Well-connected in system
Evergreen → Archive:
- Superseded by newer knowledge
- Technology/approach deprecated
- No longer applicable
Template Selection Guide
| Stability | Purpose | Template |
|---|---|---|
| Proven | Long-term | Evergreen |
| Evolving | Active development | Growing |
| Experimental | Exploration | Seedling |
| Versioned | External reference | Reference |
Integration Pattern
# In your skill's frontmatter
dependencies: [leyline:storage-templates]
Verification: Run the command with --help flag to verify availability.
Detailed Resources
- Templates: See
modules/template-patterns.mdfor detailed structures - Lifecycle: See
modules/lifecycle-stages.mdfor maturity progression
Exit Criteria
- Template selected for use case
- File naming convention applied
- Maturity stage assigned
- Promotion criteria understood
Troubleshooting
Common Issues
Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior
Enable verbose logging with --verbose flag