doc-lifecycle

Manages creation, review, validation, and export of retro-computing documentation articles.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill doc-lifecycle-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-lifecycle
Source: https://github.com/lfuuu/claude-rules/tree/main/shared-skills/process/doc-lifecycle
Command: npx skills add https://github.com/lfuuu/claude-rules --skill doc-lifecycle-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Maintaining a large structured documentation corpus about retro consoles, computers, and calculators requires consistent templates, frontmatter schemas, source registries, and style rules; this Skill enforces that lifecycle so articles stay uniform and verifiable. ## Core Features & Use Cases - Family folder scaffolding: Creates a new platform family folder with the 9-file template (README, history, architecture, components, games, sdk, emulation, sources) plus diagrams and pics directories. - Review and validation: Checks completeness, broken links, AI-marker and epithet stop-lists, footnotes, and frontmatter consistency across the docs tree. - Detail levels A/B/C: Applies three formalized depth levels with measurable file and line-count criteria, plus orthogonal image-tier rules for photos. - Use Case: When adding an article about a Soviet microcomputer, invoke the new-family scenario to generate the folder skeleton, class-specific frontmatter, and sources registry, then run validate before publishing. ## Quick Start Ask the assistant to run doc-lifecycle with the new-family scenario to scaffold a documentation folder for a specific retro platform.

Frequently Asked Questions about doc-lifecycle

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

FAQPage Schema
How do I create a new documentation article for a retro console or computer?

Use the new-family scenario, which creates a folder under docs/<class>/<slug>/ with the 9-file template: README, history, architecture, components, revisions, peripherals, games, sdk, emulation, and sources. It also generates class-specific frontmatter and updates the class index README.

What are the A/B/C detail levels in this documentation workflow?

Level A is a full 11-file family with 800-1200 lines for flagship platforms, level B is a reduced 5-10 file version for successors or regional variants, and level C is a minimal 2-3 file catalog for niche models. Selection is based on available sources and unique material, and levels can be raised but not lowered.

How does article validation check style and sources?

The validate scenario scans for broken internal links, banned retro epithets and AI-marker words, orphaned files, and footnote integrity. Every numeric claim or chip marking must link to an entry in the family sources.md registry with URL, access date, and license.

Which platforms and article classes does the template support?

Six classes are supported: console, home-computer, micro-pc (Soviet), handheld, calculator, and pc (IBM DOS-era). Each class has its own required frontmatter fields, such as screen and battery specs for handhelds or entry_logic and program_memory for calculators.

Can I export an article to PDF from this workflow?

Yes, the export scenario delegates rendering to the separate /pdf skill. The article must first pass review and validation so that links, footnotes, and diagrams resolve correctly in the exported document.

What image sources are allowed for device photos?

Wikimedia Commons is the primary source, followed by thematic archives like datamath.org or emuverse.ru, and archive.org journal scans. Marketplace listings, private blogs without licenses, and AI-generated images are explicitly forbidden.