AGENT SKILL

ams-file-organizer

暂无简介

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

03 SKILL.md 正文

File Organizer

Overview

File chaos has a cost: every search, every 'final_v2_REAL' confusion, every duplicated download burns time and trust.

A working system: consistent naming, shallow meaningful folders, an inbox for unsorted files, and regular archiving.

Goal: any file findable in 30 seconds via search or two folder clicks — months later, by future you.

When to use

  • Downloads folder with thousands of unsorted files
  • Setting up file organization on a new computer
  • 'final_v2_FINAL' version chaos in shared projects
  • Photo/document libraries growing unmanageable
  • Teams needing shared file conventions

Core concepts

  • Naming conventions. YYYY-MM-DD descriptive-name v03.ext. Dates sort chronologically; descriptive names are searchable; versions are explicit. Agree once, use always.
  • Shallow folders. 2-3 levels deep max. Deep trees hide files; search + good names beat elaborate hierarchies.
  • The inbox pattern. One 00 Inbox folder for all new/unsorted files. Process weekly: file, rename, or delete. Never browse the inbox as storage.
  • PARA or project structure. Top level by actionability (Projects/Areas/Resources/Archive) or by project. Pick one; apply everywhere.
  • Versioning discipline. Explicit versions (v01, v02) or version control (git) for documents. Never 'final', 'final2', 'final-FINAL'.
  • Deduplication. Periodic sweeps for duplicates (same file, three locations). Hash-based tools find them reliably; keep one canonical copy.
  • Archive vs. delete. Archive completed/old work (cheap storage); delete true junk (duplicates, installers, temp files). Archiving everything = hoarding.
  • Search-first retrieval. Good names + OS search/indexing. Train yourself to search rather than browse — it's faster once names are consistent.

Practical workflow

  1. Audit the mess. Survey: where are files now, what's duplicated, what's the inbox situation. Size the problem before solving.
  2. Define the convention. Write down: naming format, top-level folders, versioning rule. One page. Share with anyone who shares the files.
  3. Create the structure. Top-level folders + 00 Inbox. Don't over-build; start with 5-8 folders and grow as needed.
  4. Process the backlog. Sort existing files in passes: delete obvious junk first, then file by project, rename key files. Timebox it — perfection isn't required.
  5. Set up the inbox habit. All new files land in Inbox. Weekly 15-min processing: rename, file, or delete. The habit is the system.
  6. Deduplicate. Run a duplicate finder quarterly. One canonical copy; aliases/shortcuts where a file is needed in two places.
  7. Archive on completion. Finished projects move to Archive with a consistent structure. Active areas stay lean and truthful.
  8. Maintain. Monthly: inbox zero, downloads cleared. Quarterly: archive sweep, duplicate check, convention review.

Common pitfalls

  • Over-engineering folders. 15 levels of taxonomy built before any files exist. Start flat; let structure emerge from real contents.
  • 'Final' versioning. final_v2_REAL_FINAL.docx. Explicit version numbers or git — the word 'final' is a lie.
  • No inbox discipline. Files scattered across Desktop, Downloads, and Documents. One inbox, processed weekly, or chaos returns.
  • Archiving nothing. Active folders clogged with 5-year-old projects. Archive on completion; active stays current.
  • Inconsistent naming. Three date formats and random capitalization. The convention only works if everyone (including you) follows it always.
  • Duplicate sprawl. Same file in email, downloads, desktop, and project folder. Canonical copy + links; dedupe quarterly.
  • Organizing instead of deleting. Carefully filing files you'll never need. Delete first, organize second.
  • No shared convention. Team members each inventing their own scheme in shared drives. Agree once, document, enforce kindly.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

★ 0