file-placement

Place output files into designated directories with ALL-CAPS naming rules.

35|3|Updated Jun 24, 2025
One-click install
npx skills add https://github.com/intelligentcode-ai/intelligent-claude-code --skill file-placement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-placement
Source: https://github.com/intelligentcode-ai/intelligent-claude-code/tree/main/src/skills/file-placement
Command: npx skills add https://github.com/intelligentcode-ai/intelligent-claude-code --skill file-placement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a clear protocol for placing each output file in its designated directory, preventing misfiling and aligning with organizational hooks.

Core Features & Use Cases

  • Enforces correct destinations for file types: summaries and reports in summaries/, memory entries in memory/, stories/ for narratives, and bugs/ for issues.
  • Acts as a guidance layer that mirrors the summary-file-enforcement hook, reducing human error during file creation.
  • Use Case: After generating a new analysis, place the outcome in summaries/ with an appropriately named file to ensure quick retrieval and audit.

Quick Start

Place a newly created file into its designated folder according to its type (e.g., summaries/execution-summary.md for a summary, memory/diary.md for a memory entry). Ensure filenames use lowercase-kebab-case unless the ALL-CAPS exceptions apply.

Frequently Asked Questions about file-placement

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

FAQPage Schema
How do I automatically place output files in the correct project directories?

To place output files in the correct directories, this skill enforces directory rules that route summaries, reports, memory entries, stories, and bugs into their respective folders to prevent misfiling and ensure quick retrieval.

What is the correct file naming convention for directory organization?

For directory organization, the correct file naming convention requires filenames to use lowercase-kebab-case unless an ALL-CAPS exception applies, ensuring outputs align with organizational hooks and directory rules.

How do I save summaries and reports to prevent misfiling?

To prevent misfiling summaries and reports, save them directly into the summaries/ directory using an appropriately named lowercase-kebab-case file to ensure quick retrieval and audit.

Can I use directory organization rules for memory entries and bugs?

Yes, you can use directory organization rules for memory entries and bugs by placing memory entries in memory/ and issues in bugs/, which enforces correct destinations and reduces human error during file creation.

When should I not use lowercase-kebab-case for file placement?

You should not use lowercase-kebab-case for file placement when ALL-CAPS restrictions apply, as this skill guides naming to comply with specific exceptions to prevent misfiling.