Agent skill
storage-templates
Generic template patterns and lifecycle stages for knowledge storage, configuration management, and structured documentation. Triggers: storage templates, lifecycle stages, maturity progression, naming conventions, knowledge storage, configuration templates, documentation patterns Use when: organizing knowledge storage, managing configuration lifecycle, creating structured documentation, establishing naming conventions DO NOT use when: simple storage without lifecycle or structure needs. Consult this skill when designing storage and documentation systems.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/documents/storage-templates-athola-claude-night-market
SKILL.md
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
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]
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]
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?