Claude-night-market storage-templates
Consult this skill when designing storage and documentation systems.
install
source · Clone the upstream repo
git clone https://github.com/athola/claude-night-market
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/athola/claude-night-market "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/leyline/skills/storage-templates" ~/.claude/skills/athola-claude-night-market-storage-templates && rm -rf "$T"
manifest:
plugins/leyline/skills/storage-templates/SKILL.mdsource content
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
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 | | |
| Growing | | |
| Seedling | | |
| Reference | | |
Domain Applications
Add domain-specific fields to templates:
- memory-palace:
,palace
for knowledge organizationdistrict - sanctum:
,scope
for commit templatesversion - spec-kit:
,phase
for specificationsstatus
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
for detailed structuresmodules/template-patterns.md - Lifecycle: See
for maturity progressionmodules/lifecycle-stages.md
Exit Criteria
- Template selected for use case
- File naming convention applied
- Maturity stage assigned
- Promotion criteria understood