How do I install the Project Structure skill?

Run npx skillmds@latest add enso-org/project-structure in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Structure safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Structure?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Structure free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Structure?

enso-org (@enso-org) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Structure by enso-org — Agent Skill

Name: Project Structure
Author: enso-org

Project Structure

Mandatory practices for reading, understanding, and maintaining project documentation (CLAUDE.md, ARCHITECTURE.md). This skill MUST be used for ALL coding tasks, ALL conversations, ALL projects, regardless of language or context. It defines non-negotiable rules for how to orient yourself in any codebase before doing any work. Trigger on every single interaction — any file edit, code review, bug fix, feature addition, refactoring, question about code, or any task that involves a project directory. There are no exceptions. Even if the user asks a simple question, these rules apply.

enso-org 7d15dd7 2.5 KB Updated Sep 17, 2026

File contents

Reading Project Documentation

Before doing ANY work in a project, read all CLAUDE.md files in the hierarchy — from the current working directory up through every parent directory to the project root. These files tell you where you are, what the project is, and how to work on the code. They contain critical guidance, conventions, and rules specific to that project and its modules.
NEVER skip reading these files. No matter what. No matter how small the task seems. No matter if you think you already know the answer. Read them every time.

ARCHITECTURE.md

If there is an ARCHITECTURE.md file next to the closest (most specific) CLAUDE.md, always read it too. It contains system design, module boundaries, data flows, and key decisions that you need to understand.
You don't need to read ARCHITECTURE.md files next to parent CLAUDE.md files unless you feel the task requires that broader architectural context.

Maintaining Project Documentation

Update CLAUDE.md IMMEDIATELY when you learn new things about the project. NEVER ask for permission — just do it. This includes things you learn from:
- Reading code and discovering patterns or conventions
- User corrections or preferences during conversation
- Build/test commands and workflows
- Module responsibilities and boundaries
- Gotchas, edge cases, or non-obvious behaviors
Apply common sense about where to put what:
- If the learning is specific to a library or crate, update or create the CLAUDE.md at that library/crate root.
- If the learning is generic and applies to the whole project, update the root CLAUDE.md.

Ensuring CLAUDE.md Coverage

Every Cargo.toml and package.json must have a sibling CLAUDE.md. If one doesn't exist, create it. It's fine to start with an empty file and fill it as you learn about that package. This applies to every crate and package in a workspace — the root and every member.

---name: project-structuredescription: Mandatory practices for reading, understanding, and maintaining project documentation (CLAUDE.md, ARCHITECTURE.md). This skill MUST be used for ALL coding tasks, ALL conversations, ALL projects, regardless of language or context. It defines non-negotiable rules for how to orient yourself in any codebase before doing any work. Trigger on every single interaction — any file edit, code review, bug fix, feature addition, refactoring, question about code, or any task that involves a project directory. There are no exceptions. Even if the user asks a simple question, these rules apply.---## Reading Project Documentation- Before doing ANY work in a project, read all CLAUDE.md files in the hierarchy — from the current working directory up through every parent directory to the project root. These files tell you where you are, what the project is, and how to work on the code. They contain critical guidance, conventions, and rules specific to that project and its modules.- NEVER skip reading these files. No matter what. No matter how small the task seems. No matter if you think you already know the answer. Read them every time.### ARCHITECTURE.md- If there is an ARCHITECTURE.md file next to the closest (most specific) CLAUDE.md, always read it too. It contains system design, module boundaries, data flows, and key decisions that you need to understand.- You don't need to read ARCHITECTURE.md files next to parent CLAUDE.md files unless you feel the task requires that broader architectural context.## Maintaining Project Documentation- Update CLAUDE.md IMMEDIATELY when you learn new things about the project. NEVER ask for permission — just do it. This includes things you learn from: - Reading code and discovering patterns or conventions - User corrections or preferences during conversation - Build/test commands and workflows - Module responsibilities and boundaries - Gotchas, edge cases, or non-obvious behaviors- Apply common sense about where to put what: - If the learning is specific to a library or crate, update or create the CLAUDE.md at that library/crate root. - If the learning is generic and applies to the whole project, update the root CLAUDE.md.### Ensuring CLAUDE.md Coverage- Every Cargo.toml and package.json must have a sibling CLAUDE.md. If one doesn't exist, create it. It's fine to start with an empty file and fill it as you learn about that package. This applies to every crate and package in a workspace — the root and every member.

Frequently asked questions