file-organizer
Triggers on cluttered folders, file chaos, storage cleanup, or directory restructuring needs. TRIGGER WHEN: organizing messy folders (Downloads, Desktop, Documents), finding duplicate files, cleaning up old files, restructuring project directories, separating work from personal files, or automating file cleanup tasks DO NOT TRIGGER WHEN: the task is outside the specific scope of this component.
What this skill does
# File Organizer
## Instructions
### 1. Understand Scope
Ask clarifying questions before starting:
- Which directory needs organization?
- Main problem? (can't find things, duplicates, no structure, general mess)
- Files or folders to avoid? (active projects, sensitive data)
- How aggressive? (conservative vs comprehensive cleanup)
For broad reorganization, briefly propose a philosophy from the reference guide (PARA, Johnny Decimal, GTD, 7-Folder). Let user choose - never force one. Skip for scoped tasks like cleaning Downloads.
### 2. Analyze Current State
```bash
ls -la [target_directory]
find [target_directory] -type f -exec file {} \; | head -20
du -sh [target_directory]/* | sort -rh | head -20
find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn
```
Summarize: total files/folders, type breakdown, size distribution, date ranges, obvious issues.
**Anti-patterns to flag:**
- Desktop used as permanent archive (goal: zero permanent files on Desktop)
- Unnamed folders (`New Folder`, `New Folder (3)`)
- Broken versioning (`document_FINAL_v2_DEFINITIVE_copy.docx`)
- Downloads folder never cleaned (thousands of unsorted files)
- Same file duplicated across locations (use shortcuts instead)
### 3. Identify Organization Patterns
**By type:**
- Documents (PDF, DOCX, TXT), Images (JPG, PNG, SVG), Videos (MP4, MOV)
- Archives (ZIP, TAR, DMG), Code/Projects, Spreadsheets (XLSX, CSV), Presentations (PPTX, KEY)
**By purpose:**
- Work vs Personal, Active vs Archive, Project-specific, Reference, Temporary/scratch
**By date:**
- Current year/month, Previous years, Very old (archive candidates)
**Context-specific structures:**
- Photos/Video: `Year/YYYY-MM_event-location/` with RAW, Edited, Export subfolders
- Music: `Artist/[Year] Album/NN - Track.ext`
- Work projects: numbered prefixes (`01_Brief/`, `02_Research/`, `03_Assets/`, `04_Deliverables/`) with WIP/FINAL_APPROVED separation
- Finance/personal docs: include expiry dates in filenames (`passport_exp_2030.pdf`), organize by year then type
- Code: map local paths to remote URLs (`github.com/username/repo/`)
See `references/organization-guide.md` for detailed templates.
### 4. Find Duplicates
When requested:
```bash
find [directory] -type f -exec md5 {} \; | sort | uniq -d
find [directory] -type f -printf '%f\n' | sort | uniq -d
```
For each duplicate set: show paths, sizes, dates, recommend which to keep. ALWAYS confirm before deleting. Suggest shortcuts/aliases instead of keeping copies.
### 5. Propose Organization Plan
Present plan before making changes. Include:
- Current state summary (file count, size, type breakdown, problems found)
- Anti-patterns detected
- Proposed folder tree structure
- Changes to make: new folders, file moves, renames, deletions
- Files needing user decision (ambiguous placement)
- Ask for explicit approval before proceeding
### 6. Execute Organization
After approval, organize systematically.
**Rules:**
- Always confirm before deleting anything
- Log all moves for potential undo
- Preserve original modification dates
- Handle filename conflicts gracefully
- Stop and ask on unexpected situations
**File renaming conventions** (only when user agrees - never auto-rename):
- ISO dates: `YYYY-MM-DD` for correct alphabetical sort
- Formula: `[Date]_[Context]_[Description]_[Version].ext`
- Zero-padded versions: `v01`, `v02` (minor: `v01.1`)
- Separators: `kebab-case` or `snake_case` (never spaces)
- All lowercase, filenames under 25-30 chars, let folder context provide the rest
- Zero-pad sequences: `001`, `002` (prevents `1, 10, 11, 2` sort)
- Status prefixes when useful: `WIP_`, `DRAFT_`, `REVIEW_`, `APPROVED_`
- Avoid: `< > : " / \ | ? *`, accents, emoji, leading dots, Windows reserved names (`CON`, `PRN`, `AUX`, `NUL`)
- Watch full path length approaching Windows 260-character limit
### 7. Provide Summary
After organizing, report:
- Folders created, files organized, space freed, anti-patterns fixed
- New folder tree structure
- Maintenance schedule (below)
- Custom bash commands for ongoing cleanup
**Maintenance Schedule:**
| Frequency | Time | Tasks |
|-----------|------|-------|
| Weekly | 15 min | Empty Downloads, process Inbox to zero, verify recent files are in place |
| Monthly | 45 min | Scan for duplicates, verify backups, archive completed projects |
| Quarterly | 2 hrs | Disk space audit, archive projects inactive 3+ months, test backup restore |
| Yearly | Half day | Disaster recovery test, retention policy review, structure update |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.