How do I install the Project Structure skill?

Run npx skillmds@latest add maskar/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?

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

Project Structure by maskar — Agent Skill

Name: Project Structure
Author: maskar

Project Structure

This skill should be used when the user is scaffolding a new project, reorganizing file structure, or discussing directory layout conventions. It provides language-specific best practices for Python, Node/TypeScript, Go, and general projects. Enforces the ./tmp/ intermediary workflow and .claude/CLAUDE.md convention. Triggers on: project init, directory layout, file organization, scaffolding, repo structure, creating new projects, setting up a Python/Node/Go project, or organizing code. Also available as /sawkit:project-structure.

maskar e95d9ed 8 files · 13.8 KB Updated Sep 17, 2026

File contents

Project Structure Expert

Follow these conventions when scaffolding or organizing any project.

Intermediary Workflow

All intermediary scripts, debug files, and work-in-progress files go in ./tmp/ at the project root. This directory is always gitignored.

Rules:

Create ./tmp/ at project root for all temporary work
Write analysis scripts, test data, debug output to ./tmp/
Only move files to their final project location after user approval
Never commit ./tmp/ contents
Add tmp/ to .gitignore in every project

Example workflow:

# Write intermediary script
mkdir -p ./tmp
cat > ./tmp/analyze.py << 'EOF'
# analysis script...
EOF
python ./tmp/analyze.py

# After approval, move to final location
mv ./tmp/analyze.py scripts/analyze.py

CLAUDE.md Location

Place CLAUDE.md at .claude/CLAUDE.md, not at project root.

mkdir -p .claude
# Write CLAUDE.md to .claude/CLAUDE.md

Use the template at ${CLAUDE_PLUGIN_ROOT}/skills/project-structure/templates/claude-md-template.md as a starter.

Universal Files

Every project should include:

File	Purpose
`.gitignore`	Git ignore patterns
`README.md`	Project overview and usage
`.claude/CLAUDE.md`	Claude Code project context

Project Detection

Before suggesting structure, detect the project type from existing files:

File Present	Project Type
`pyproject.toml`	Python
`setup.py`	Python (legacy)
`.python-version`	Python
`package.json`	Node/TypeScript
`tsconfig.json`	TypeScript
`go.mod`	Go
`Cargo.toml`	Rust
`justfile`	Any (task runner)
`Makefile`	Any (build)

If no files exist, ask the user what they are building.

Language-Specific Layouts

For detailed layouts per language, read the reference files:

Python: ${CLAUDE_PLUGIN_ROOT}/skills/project-structure/references/python-layout.md
Node/TypeScript: ${CLAUDE_PLUGIN_ROOT}/skills/project-structure/references/node-layout.md
Go: ${CLAUDE_PLUGIN_ROOT}/skills/project-structure/references/go-layout.md
General: ${CLAUDE_PLUGIN_ROOT}/skills/project-structure/references/general-conventions.md

General Principles

Flat for small projects — do not create deep nesting for projects with < 10 files
Group by feature, not by type — auth/models.py + auth/routes.py over models/auth.py + routes/auth.py
Config at root — pyproject.toml, package.json, go.mod stay at project root
Docs in docs/ — separate documentation from source code
Scripts in scripts/ — operational scripts separate from source
Tests mirror source — src/auth/login.py → tests/auth/test_login.py

---name: project-structuredescription: This skill should be used when the user is scaffolding a new project, reorganizing file structure, or discussing directory layout conventions. It provides language-specific best practices for Python, Node/TypeScript, Go, and general projects. Enforces the ./tmp/ intermediary workflow and .claude/CLAUDE.md convention. Triggers on: project init, directory layout, file organization, scaffolding, repo structure, creating new projects, setting up a Python/Node/Go project, or organizing code. Also available as /sawkit:project-structure.---# Project Structure ExpertFollow these conventions when scaffolding or organizing any project.## Intermediary WorkflowAll intermediary scripts, debug files, and work-in-progress files go in `./tmp/` at the project root. This directory is always gitignored.**Rules:**- Create `./tmp/` at project root for all temporary work- Write analysis scripts, test data, debug output to `./tmp/`- Only move files to their final project location after user approval- Never commit `./tmp/` contents- Add `tmp/` to `.gitignore` in every project**Example workflow:**```bash# Write intermediary scriptmkdir -p ./tmpcat > ./tmp/analyze.py << 'EOF'# analysis script...EOFpython ./tmp/analyze.py# After approval, move to final locationmv ./tmp/analyze.py scripts/analyze.py```## CLAUDE.md LocationPlace `CLAUDE.md` at `.claude/CLAUDE.md`, not at project root.```bashmkdir -p .claude# Write CLAUDE.md to .claude/CLAUDE.md```Use the template at `${CLAUDE_PLUGIN_ROOT}/skills/project-structure/templates/claude-md-template.md` as a starter.## Universal FilesEvery project should include:| File | Purpose ||-----------------------|--------------------------------|| `.gitignore` | Git ignore patterns || `README.md` | Project overview and usage || `.claude/CLAUDE.md` | Claude Code project context |## Project DetectionBefore suggesting structure, detect the project type from existing files:| File Present | Project Type ||----------------------|-----------------|| `pyproject.toml` | Python || `setup.py` | Python (legacy) || `.python-version` | Python || `package.json` | Node/TypeScript || `tsconfig.json` | TypeScript || `go.mod` | Go || `Cargo.toml` | Rust || `justfile` | Any (task runner)|| `Makefile` | Any (build) |If no files exist, ask the user what they are building.## Language-Specific LayoutsFor detailed layouts per language, read the reference files:- Python: `${CLAUDE_PLUGIN_ROOT}/skills/project-structure/references/python-layout.md`- Node/TypeScript: `${CLAUDE_PLUGIN_ROOT}/skills/project-structure/references/node-layout.md`- Go: `${CLAUDE_PLUGIN_ROOT}/skills/project-structure/references/go-layout.md`- General: `${CLAUDE_PLUGIN_ROOT}/skills/project-structure/references/general-conventions.md`## General Principles1. **Flat for small projects** — do not create deep nesting for projects with < 10 files2. **Group by feature, not by type** — `auth/models.py` + `auth/routes.py` over `models/auth.py` + `routes/auth.py`3. **Config at root** — `pyproject.toml`, `package.json`, `go.mod` stay at project root4. **Docs in `docs/`** — separate documentation from source code5. **Scripts in `scripts/`** — operational scripts separate from source6. **Tests mirror source** — `src/auth/login.py` → `tests/auth/test_login.py`

Frequently asked questions