Agent skill
folder-structure-guidelines
Explain folder structure strategy and rules to respect all over any realization.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/folder-structure-guidelines
SKILL.md
Lexique :
- project folder : Current folder of user, referece too the root of the project folder.
- documentation files : all files containing text explanations, like : spécifications, README, LICENSE, Backlog and all non file writing for human readibility. It could concern media file too, like : image, video, sound, etc...
When create or read file, always respect thoses rules :
- All documentation files must be into the folder /docs of project folder
- All specifications files must be into the folder /docs/specs of project folder
- All design specifications files must be into the folder /docs/specs/design of project folder
- All technical and architectural specifications files must be into the folder /docs/specs/architecture of project folder
- All functional and product specification files must be into the folder /docs/specs/product of project folder
- All testing specification files must be into the folder /docs/specs/testing of project folder
- All tests must be into the folder "/tests" of project folder
Keep project folder structure clear and compliant to thoses rules conversational.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?