repository-organization

Name: repository-organization
Availability: InStock
Author: darkmatter

Organize repository guidance, docs, scripts, and ADRs into canonical locations.

1|Updated Apr 27, 2026

Search Tags:#documentation #adr #skills #readme #repository organization #agent context

Ready to run

npx skills add https://github.com/darkmatter/skills --skill repository-organization-darkmatter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repository-organization
Source: https://github.com/darkmatter/skills/tree/main/skills/repository-organization
Command: npx skills add https://github.com/darkmatter/skills --skill repository-organization-darkmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams decide where repository guidance, policies, reusable instructions, scripts, docs, and architectural decisions should live so they stay easy to find and hard to duplicate.

Core Features & Use Cases

Placement Decisions: Chooses the right home for durable content such as AGENTS files, .agent context, policies, workflows, skills, docs, scripts, presets, and ADRs.
Repository Cleanup: Helps reorganize scattered Markdown, duplicated instructions, and ad hoc decision notes into canonical locations.
Use Case: A new project needs a convention for where to store agent instructions, project facts, and shared skills, and this Skill maps each item to the correct folder or file type.

Quick Start

Ask this skill where a new repository rule, doc, workflow, script, skill, or ADR should live and have it recommend the canonical location.

Frequently Asked Questions about repository-organization

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

FAQPage Schema

Where should I put repository guidance like agent instructions and project policies?▼

Architectural decisions belong in ADRs (Architecture Decision Records), which follow a specific lifecycle discipline. Separating ADRs from standard docs and scripts ensures historical context is preserved while keeping actionable guidance easily discoverable.

How do I organize scattered Markdown files and duplicated instructions during a repository cleanup?▼

Skills are reusable instructions mapped to a designated skills directory, while standard documentation goes into the docs folder. Categorizing reusable logic separately from static project facts ensures agents and developers can find the right context efficiently.

What is the best way to structure a new project for agent context and shared workflows?▼

The best way to structure a new project is to establish conventions upfront for storing agent context, workflows, and shared skills in their correct durable locations. This bootstrapping approach applies canonical placement rules from the start.

Do I need standard-readme compliance when organizing repository documentation?▼

Yes, standard-readme compliance is required when organizing repository documentation. Enforcing standard-readme compliance alongside link hygiene and canonical placement rules ensures that repository guidance remains consistent and easy to navigate.