About storage-templates
A reusable skill for structuring stored content with templates, maturity stages, and file-naming conventions. It is intended for knowledge and documentation workflows that need lifecycle-based organization.
Key features
- 01Four templates for different maturity levels
- 02Seedling-to-archive lifecycle model
- 03File-naming patterns by content type
- 04Domain-specific template fields
Use cases
- 01Organizing a knowledge management system
- 02Tracking documentation maturity
- 03Standardizing content filenames
- 04Creating content with reusable templates
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/storage-templatesin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
README.mdmodules/lifecycle-stages.mdstorage-patterns.mdtemplate-patterns.mdDetails
From the project READMEStorage 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
When NOT To Use
- Simple storage without lifecycle or structure needs
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