file-placement
Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces.
Best use case
file-placement is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces.
Teams using file-placement should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/file-placement/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How file-placement Compares
| Feature / Agent | file-placement | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# File Placement Skill Apply correct file placement rules for all output files. ## Why This Matters File placement is **enforced by hooks** - violations will be blocked. This skill ensures you understand the rules so your work isn't rejected. ## File Placement Rules | File Type | Required Directory | Examples | |-----------|-------------------|----------| | Summaries | `summaries/` | execution-summary.md, review-summary.md | | Reports | `summaries/` | analysis-report.md, audit-report.md | | Stories | `stories/` | STORY-001-feature.md | | Bugs | `bugs/` | BUG-001-issue.md | | Memory (exports) | `memory/exports/` | memory/exports/patterns/oauth2.md | | Documentation | `docs/` | api-docs.md, architecture.md | ## Forbidden Placements **NEVER place these in the wrong location:** - Summaries in `docs/` or project root - Reports in `docs/` or project root - Memory entries outside `memory/exports/` - Output files in source directories ## Filename Rules ### ALL-CAPS Restrictions Only these filenames may be ALL-CAPS: - README.md, LICENSE, LICENSE.md - CLAUDE.md, SKILL.md, AGENTS.md - CHANGELOG.md, CONTRIBUTING.md - AUTHORS, NOTICE, PATENTS, VERSION - MAKEFILE, DOCKERFILE, COPYING, COPYRIGHT **All other files**: Use lowercase-kebab-case - `execution-summary.md` (correct) - `EXECUTION-SUMMARY.md` (blocked) ## Hook Enforcement The `summary-file-enforcement.js` hook will: 1. **Block** files with ALL-CAPS names (except allowlist) 2. **Block** summary/report files outside `summaries/` 3. **Suggest** correct filename/location ## Before Creating Files Ask yourself: 1. Is this a summary or report? → Put in `summaries/` 2. Is this a memory entry? → Put in `memory/exports/<category>/` (category: architecture, implementation, issues, patterns) 3. Is my filename lowercase-kebab? → If not, fix it 4. Am I using ALL-CAPS? → Only if in allowlist ## Integration with Hooks This skill provides **guidance** - you understand the rules. The hook provides **enforcement** - violations are blocked. Together they ensure consistent file organization even when: - Context is lost - Rules are forgotten - New team members join
Related Skills
add-mouse-profile
Create a new mouse profile for a mouse model not yet supported
production-dockerfile
Generate production-ready Dockerfiles with multi-stage builds, security best practices, and optimization. Use when containerizing Python applications for production deployment.
jenkinsfile-generator
Comprehensive toolkit for generating best practice Jenkinsfiles for both Declarative and Scripted pipeline syntaxes. Use this skill when creating new Jenkins pipelines, implementing CI/CD workflows.
file-uploads
Expert at handling file uploads and cloud storage. Covers S3, Cloudflare R2, presigned URLs, multipart uploads, and image optimization. Knows how to handle large files without blocking. Use when: f...
dockerfile-optimization
Optimize Dockerfiles for smaller images, faster builds, better caching, and security. Use this skill when writing, reviewing, or debugging Dockerfiles.
azure-storage-file-share-py
Azure Storage File Share SDK for Python. Use for SMB file shares, directories, and file operations in the cloud.
agentuity-cli-cloud-sandbox-files
List files in a sandbox directory. Requires authentication. Use for Agentuity cloud platform operations
writing-claude-md-files
Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness dates
write-coding-standards-from-file
Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.
tool-call-file-parameter-formatting
Formats file and URL parameters for tool calls. You must analyze the target tool's parameter names and descriptions to choose the correct format (base64, text, or URL ref).
planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
organizing-files
Organizes macOS files across Desktop, Documents, Downloads, and iCloud Drive into a consistent structure. Use when the user asks to organize files, clean up folders, sort downloads, declutter desktop, tidy up documents, or structure their filesystem. Triggers on "organize", "clean up", "sort files", "declutter", "file mess", "tidy", or any request about file/folder structure on macOS.