storage-templates
Scannednpx machina-cli add skill athola/claude-night-market/storage-templates --openclawTable 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
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
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
Source
git clone https://github.com/athola/claude-night-market/blob/master/plugins/leyline/skills/storage-templates/SKILL.mdView on GitHub Overview
Storage templates provide generic template patterns and lifecycle management for structured content storage. They offer reusable templates, maturity progression models, and file naming conventions that work across storage domains, helping knowledge management and documentation systems stay consistent and scalable.
How This Skill Works
Templates are categorized into Evergreen, Growing, Seedling, and Reference, each with a defined maturity and lifetime. The approach includes a maturity lifecycle seedling → growing → evergreen → archive and a YAML-based Basic Template Structure for content, plus naming conventions and domain-specific fields. Verification steps, such as running commands with --help, ensure availability and correct usage.
When to Use It
- Building knowledge-management systems
- Organizing documentation with maturity stages
- Need consistent file naming patterns
- Template-driven content creation
- Implementing lifecycle-based workflows in configuration and documentation
Quick Start
- Step 1: Create a YAML skeleton with title, created date, maturity, and tags.
- Step 2: Select a template type (seedling, growing, evergreen, reference) and fill Core Content and Metadata.
- Step 3: Apply the file naming convention and run verification (e.g., --help) to verify availability.
Best Practices
- Define a clear set of template types and map them to lifetimes
- Adopt consistent file naming conventions per maturity
- Use domain-specific fields where applicable (memory-palace sanctum spec-kit)
- Document promotion criteria for moving entries through Seedling to Evergreen
- Regularly review templates to retire or archive obsolete content
Example Use Cases
- Knowledge base article aligned with Evergreen in a product domain
- Seedling template used to prototype a new process
- Growing template for an active API feature with 1-3 months lifetime
- Reference template for a tool version like python-3.12-features
- Documentation package applying domain fields for knowledge organization
Frequently Asked Questions
Related Skills
terraform
chaterm/terminal-skills
Terraform 基础设施即代码
makefile-generation
athola/claude-night-market
Generate language-specific Makefiles with testing, linting, and automation targets. Use for project initialization and workflow standardization. Skip if Makefile exists.
precommit-setup
athola/claude-night-market
Configure three-layer pre-commit system with linting, type checking, and testing hooks. Use for quality gate setup and code standards. Skip if pre-commit is optimally configured.
error-patterns
athola/claude-night-market
'Standardized error handling patterns with classification, recovery,
risk-classification
athola/claude-night-market
'Inline risk classification for agent tasks using a 4-tier model. Hybrid
quota-management
athola/claude-night-market
'Quota tracking, threshold monitoring, and graceful degradation for rate-limited
