julien-ref-doc-production

Name: julien-ref-doc-production
Availability: InStock
Author: theflysurfer

Standardize software documentation with YAML metadata and cross-file references.

Updated Aug 27, 2026

Search Tags:#template #documentation #DRY #guidance #metadata

Ready to run

npx skills add https://github.com/theflysurfer/claude-skills-marketplace --skill julien-ref-doc-production

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: julien-ref-doc-production
Source: https://github.com/theflysurfer/claude-skills-marketplace/tree/main/skills/julien-ref-doc-production
Command: npx skills add https://github.com/theflysurfer/claude-skills-marketplace --skill julien-ref-doc-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill documents production methodologies with DRY principles, including 8 document types and YAML metadata.

Core Features & Use Cases

Document structure guidance: living docs, event-based docs, and consistent naming
Metadata-driven: YAML headers with versioning and authors
Progressive disclosure: references directory recommended for in-depth docs

Quick Start

Create an evolving guide under docs/ and add corresponding YAML metadata at the top of the document.

Frequently Asked Questions about julien-ref-doc-production

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize documentation across multiple document types in a project?▼

This Skill standardizes documentation production by enforcing consistent folder structure, naming conventions, and YAML metadata headers across eight document types: GUIDE, INCIDENT, SESSION, AUDIT, RECHERCHE, RECOMMANDATIONS, MIGRATION, PERFORMANCE, and SECURITE. Apply DRY principles with cross-referenced living documents to maintain single sources of truth.

What should I include in YAML metadata for living documentation?▼

Each document requires a complete YAML header containing title, version, created, updated, authors, audience, level, status, tags, and related fields. This metadata enables versioning, author tracking, audience targeting, and cross-file references while supporting event-based workflows that evolve with your documentation.

How do I organize documentation to avoid duplication and maintain DRY principles?▼

Structure documents in a defined folder hierarchy with consistent naming conventions and establish cross-references between files. A references directory holds in-depth docs while progressive disclosure keeps primary documents lean, eliminating redundancy and reducing maintenance burden across your doc system.

Can I use this approach for different documentation contexts like incident reports and security guides?▼

Yes. The Skill supports eight specialized document types designed for distinct contexts: INCIDENT captures events, SECURITE addresses security, PERFORMANCE covers optimization, MIGRATION documents transitions, and others. Each type uses the same YAML structure and naming conventions, enabling scalable documentation across varied project needs.

What's the difference between living docs and static documentation?▼

Living documentation evolves with your project through event-based workflows tracked via YAML metadata. Version, updated, and status fields capture change history automatically. Static docs become outdated; living docs stay current by design, reducing staleness and keeping guidance actionable.

Do I need existing documentation to start using this structure?▼

No. Begin by creating a new guide under docs/ and add YAML metadata at the top. The Skill provides the structure and conventions to apply incrementally—start with one document type and expand as your documentation grows, applying DRY and metadata consistency from the start.