What is the Minimal Root philosophy?

It is an organizational standard where the root directory contains only essential architectural pillars (like src/ and README.md), while configuration and implementation details are moved to subdirectories.

Which community files does it manage?

It ensures the presence of critical governance and community health files such as LICENSE, CONTRIBUTING.md, CODEOWNERS, and SECURITY.md within the .github/ or root directories.

How does the skill move configuration files without breaking tools?

The skill provides 'Glue Code,' which includes specific package.json script overrides or VS Code settings to point tools like ESLint or Prettier to their new locations in the .config/ folder.

What documentation standards does this skill follow?

It follows a 'World-Class README' anatomy, including a hero section with badges, automated navigation, dark-mode adaptive images, and Mermaid.js diagrams for architecture.

Can this skill help with repository accessibility?

Yes, it performs accessibility checks on documentation, ensuring meaningful alt text for images and using HTML tags for dark/light mode compatibility.

GitHub Repository Architect

Name: GitHub Repository Architect
Author: organvm-iv-taxis

byorganvm-iv-taxis

•

Developer Tools

Enforces the Minimal Root philosophy and implements world-class README standards to eliminate repository clutter and improve documentation.

The GitHub Repository Standards skill transforms disorganized codebases into professionally structured repositories by enforcing the 'Minimal Root' philosophy and 'Progressive Disclosure' principles. It systematically relocates configuration clutter (like ESLint, Prettier, and Docker files) into a dedicated .config/ directory, generates high-conversion documentation with automated tables of contents and Mermaid.js diagrams, and ensures community health compliance. This skill is ideal for developers looking to signal architectural maturity and improve user onboarding through standardized, accessible, and visually appealing repository structures.

Key Features

01Performs Root Hygiene Audits to identify and relocate architectural 'entropy'.

022 GitHub stars

03Enforces 'Minimal Root' philosophy to move configuration clutter into subdirectories.

04Provides glue-code for package.json and VS Code to maintain tool functionality after relocation.

05Automates 'World-Class README' generation with high-conversion hero sections and diagrams.

06Standardizes community health files including SECURITY.md, SUPPORT.md, and CITATION.cff.

Use Cases

01Refactoring a cluttered legacy repository to improve developer onboarding and maintainability.

02Standardizing repository structures across a multi-repo organization to ensure architectural consistency.

03Preparing a private project for public open-source release with professional-grade documentation.

Key Features

01Performs Root Hygiene Audits to identify and relocate architectural 'entropy'.

022 GitHub stars

03Enforces 'Minimal Root' philosophy to move configuration clutter into subdirectories.

04Provides glue-code for package.json and VS Code to maintain tool functionality after relocation.

05Automates 'World-Class README' generation with high-conversion hero sections and diagrams.

06Standardizes community health files including SECURITY.md, SUPPORT.md, and CITATION.cff.

Use Cases

01Refactoring a cluttered legacy repository to improve developer onboarding and maintainability.

02Standardizing repository structures across a multi-repo organization to ensure architectural consistency.

03Preparing a private project for public open-source release with professional-grade documentation.