File Placementv1.0.0

During a two-week hackathon-like sprint, multiple developers create markdown notes, test scripts, and API docs simultaneously. The File Placement skill enforces folder conventions so all documentation lands in docs/ and all scripts in scripts/ from the first commit. This eliminates merge conflicts and keeps the repository navigable when the team reviews progress at sprint end.

A fintech company must maintain audit trails for every bug fix, test result, and deployment runbook. The skill ensures issue reports go to docs/issues/ and deployment guides to docs/deployment/, creating a consistent, traceable structure. Auditors can quickly locate required documents without scanning root folders.

An AI agent swarm platform generates many workflow and stage documents as agents collaborate. The skill routes all AGENT_SWARM_* and WORKFLOW_* files to docs/agent-swarm/, preventing root clutter. New engineers can immediately find relevant process documentation and contribute without guessing file locations.

A web project with separate frontend and backend teams often mixes documentation in both roots. The skill separates backend docs into core/docs/ and frontend docs into AINative-website/docs/, with clear subfolders for features, testing, and issues. This reduces cross-team confusion and speeds up knowledge sharing.

A DevOps team wants to prevent accidental root-level script commits before they reach CI. The skill provides a simple, deterministic rule set that can be turned into a pre-commit hook. It ensures every test, migration, and monitoring script lives in scripts/, keeping pipelines clean and predictable.

The File Placement rules are published as an open-source CLI or linter plugin. A paid support tier offers custom rule configurations, priority bug fixes, and integration assistance for enterprise codebases. Revenue comes from annual support contracts.

A cloud service that connects to GitHub or GitLab and continuously enforces file placement policies across all repositories. It provides dashboards, violation alerts, and automated fix suggestions. Teams pay per repository or per active developer.

Organizations hire consultants to implement strict documentation and script placement policies aligned with internal audit requirements. The offering includes policy templates, developer workshops, and a one-time audit of existing repositories. Revenue is project-based or retainer-based.