file-operations

Enforces efficient file moves and proper frontend/backend project structure separation.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/dominionism/Noesis --skill file-operations-dominionism
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-operations
Source: https://github.com/dominionism/Noesis/tree/main/assets/skills/file-operations
Command: npx skills add https://github.com/dominionism/Noesis --skill file-operations-dominionism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers and AI agents often waste tokens and time recreating files just to relocate them, and projects frequently accumulate structural violations like React components in backend folders or business logic stuffed into controllers. This Skill enforces efficient file operations and flags architecture violations before they become technical debt. ## Core Features & Use Cases - Efficient File Relocation: Mandates using bash mv and cp commands instead of wasteful read-write-delete cycles when moving or duplicating files. - Project Structure Standards: Defines a canonical frontend/backend/shared/docs layout with clear ownership for components, services, models, routes, and types. - Violation Detection: Identifies eight red flags including frontend code in backend directories, API routes mixed with UI, scattered utilities, and god files lacking separation of concerns. - Use Case: When reorganizing a monorepo, the Skill ensures every file move uses mv with mkdir -p, and immediately flags a database query found inside a React component file, suggesting the correct backend service location. ## Quick Start Ask the AI to move the utils folder from frontend/src to shared/ and flag any files that violate the frontend/backend separation rules.

Frequently Asked Questions about file-operations

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

FAQPage Schema
How do I move files efficiently in a coding project?▼

Use the bash mv command to relocate files instead of reading, rewriting, and deleting them. Create parent directories first with mkdir -p, then run mv old/path/file new/path/file to preserve content without token-wasting recreation.

What is the best project structure for frontend and backend separation?▼

Use top-level frontend, backend, shared, and docs directories. Frontend holds components, hooks, and API clients; backend holds controllers, services, models, and routes; shared holds types and utilities used by both sides.

When should I use cp instead of mv for file operations?▼

Use cp when duplicating a file so the original stays in place, and mv when relocating or renaming. Never recreate a file through read and write operations just to move it, since that wastes tokens and risks content drift.

What project structure violations should I watch for?▼

Watch for React components in backend folders, database queries in frontend code, API routes mixed with UI files, business logic inside controllers, duplicated utilities, scattered type definitions, and god files handling multiple concerns.

Why should business logic stay out of controllers?▼

Controllers should remain thin request handlers that delegate to service layers. Placing business logic in controllers couples it to HTTP transport, making it harder to test, reuse, and maintain across the backend codebase.