docs-general

Enforces directory layout and frontmatter requirements while archiving outdated documents and updating TODO.md and README.md links.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Genuineh/fus --skill docs-general
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-general
Source: https://github.com/Genuineh/fus/tree/main/skills/docs-general
Command: npx skills add https://github.com/Genuineh/fus --skill docs-general

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of your project's documentation, ensuring it remains organized, up-to-date, and adheres to established standards.

Core Features & Use Cases

  • Structure Enforcement: Maintains a consistent and logical documentation hierarchy.
  • Archiving: Manages the lifecycle of documents by archiving outdated or superseded content.
  • Hygiene & Sync: Ensures documentation stays synchronized with code changes and project progress.
  • Use Case: When a feature is completed, use this skill to archive the draft design documents, update the TODO.md file, and ensure the main README.md links are current.

Quick Start

Use the docs-general skill to archive the document 'old-design.md' and update the TODO list.

Frequently Asked Questions about docs-general

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

FAQPage Schema
How do I keep repository documentation synchronized with code changes?

Documentation sync is maintained by enforcing a standard directory layout and requiring change tracking for all updates. This ensures your repository documentation stays organized and aligned with code modifications.

What is the best way to archive outdated project documents?

Archiving outdated documents involves moving superseded content to a designated archive structure while updating active files like TODO.md and README.md. This maintains documentation hygiene across the project lifecycle.

How do I enforce a standard directory layout for project documentation?

Enforcing a standard directory layout requires applying structural rules to your documentation hierarchy and mandating specific frontmatter metadata for all files. This creates consistent organization across the repository.

Do I need specific frontmatter metadata to maintain documentation hygiene?

Yes, frontmatter metadata is required for all documentation updates. Adhering to specified frontmatter fields enables proper change tracking and ensures documents meet the hygiene standards.

When should I archive draft design documents in a repository?

Draft design documents should be archived when a feature is completed and the code changes are merged. Archiving superseded content at this stage keeps active documentation current and relevant.

What are the limitations of automating documentation structure enforcement?

Structure enforcement relies on adherence to specified frontmatter metadata and directory rules. Limitations arise when existing documents lack the required metadata or fail to follow the standard layout conventions.