Windsurf rules

1---
2name: organize-workspace
3model: haiku
4description: "Scans the active workspace for disposable artifacts—logs, caches, stale build output, and stray draft markdown—and proposes consolidation of scattered assets. Produces a reviewable list, asks for explicit confirmation before any delete or move, and optionally revises .gitignore. Use when the user says \"clean my room\", \"organize workspace\", \"workspace cleanup\", \"remove temp files\", \"organize assets\", \"gitignore\", or wants a safe tidy pass."
5---
6 
7# Organize Workspace
8> **HARD GATE** — **HARD GATE** — Workspace structure must reflect domain structure. If the codebase feels disorganized, flag it. Disorganization != 'just a style thing;' it is a signal of domain misalignment.
9 
10 
11## Principles
12 
13- **Read-only first**: inventory and size (`du`, `ls -la`) before any change.
14- **Never delete or move** without a numbered list and **explicit user approval** (item-level or "approve all").
15- **Prefer `fd` / `ripgrep` / `find`** in that order; avoid blind `rm -rf` on vague globs.
16- **Do not** touch `.git/`, `node_modules/`, `venv/`, `.env*`, or SSH keys; flag them only if the user asked about them.
17- Confirm prompts in the **user's language** if they are not writing in English.
18 
19## 1. Establish scope
20 
21- Default: **current project root** (where the user is working) or the path they name.
22- Record OS (macOS vs Linux) for ignore patterns (e.g. `.DS_Store`).
23 
24## 2. Classify candidates (scan)
25 
26Group findings under these **buckets**:
27 
28| Bucket | Examples | Typical action |
29|--------|----------|----------------|
30| **Logs & temp** | `*.log`, `logs/`, `tmp/`, `temp/`, `*.pid` | Delete after confirm |
31| **Build / cache** | `dist/`, `build/`, `.next/`, `coverage/`, `.turbo/` | Delete if rebuildable |
32| **Package caches** | root `.cache/`, `__pycache__/` | Offer delete |
33| **Stray drafts** | root-level `*.md` named `draft`, `scratch`, `temp` | User picks: delete, move to `specs/`, or keep |
34| **Duplicate / dump dirs** | `old/`, `backup/`, `copy/`, `*_backup` | List + ask |
35 
36Use quick size hints: `du -sh` per top-level dir; sort large items first.
37 
38## 3. Assets & data (organize, not only delete)
39 
40If the user wants **organization**:
41 
421. Propose a **single convention**, e.g.:
43   - `assets/` — images, fonts, static media
44   - `data/` — JSON, CSV, fixtures, samples
45   - `specs/` — all planning and domain documents
462. For each cluster of loose files, suggest **one target path** and a short rationale.
473. Use **git-aware moves** when in a repo: `git mv` if tracked; otherwise `mv` and report.
484. Never move secrets or production DB dumps into `docs/` or public `assets/`.
49 
50## 4. Present the plan
51 
52Output a table or numbered list:
53 
54- Path
55- Kind (log / build / draft / asset / other)
56- Approx size
57- Proposed action: **delete** | **move to …** | **keep**
58 
59Ask: *"Delete items 1–3? Move 4–5? Skip 6?"*
60 
61## 5. Execute after approval
62 
63- Deletes: on macOS, prefer a Trash-capable tool (e.g. `trash` from Homebrew) if installed; else `rm` with paths echoed back.
64- Moves: create dirs with `mkdir -p` first; one batch at a time.
65- **Verify**: re-run listing on affected parents; if anything failed, report stderr.
66 
67## 6. Post-cleanup and `.gitignore` revision
68 
69Do this when the repo is under Git and the cleanup surfaced **untracked** noise:
70 
711. **Inventory ignore sources**: root `.gitignore`, `.git/info/exclude`, any subpackage `.gitignore` files.
722. **Map findings to rules**: for each deleted or recurring artifact class, check whether a pattern already exists; note gaps.
733. **Propose a patch**: list only **concrete** changes — `+` add / `-` remove / `~` reword — with one-line why.
744. **User must approve** the exact diff before editing the file.
755. **Verify**: run `git check-ignore -v <path>` on 2–3 representative paths.
76 
77See [REFERENCE.md](REFERENCE.md) for shell patterns, `.gitignore` mechanics, and safety checks.
78 
79 
80 
81<!-- story: e04s03 -->
82 
83---
84 
85# clean-my-room — reference patterns
86 
87Optional commands for the agent. Adapt paths; **dry-run** before bulk delete.
88 
89## Discover large top-level entries
90 
91```sh
92du -sh ./* .[!.]* 2&gt;/dev/null | sort -hr | head -30
93```
94 
95## Find common logs (respect `.gitignore` when using fd)
96 
97```sh
98fd -t f '\.log$' . 2&gt;/dev/null
99fd 'npm-debug' . 2&gt;/dev/null
100```
101 
102## Find build-like dirs (review list before `rm -rf`)
103 
104```sh
105fd -t d '^(dist|build|out|target|\.next|coverage)$' . --max-depth 3 2&gt;/dev/null
106```
107 
108## Stray markdown at repo root (heuristic)
109 
110```sh
111ls -1 ./*.md 2&gt;/dev/null
112fd -t f '^(draft|scratch|untitled|TODO|notes)' . --max-depth 1 2&gt;/dev/null
113```
114 
115## Git-safe moves
116 
117```sh
118git status -sb
119git check-ignore -v &lt;path&gt;   # was ignored?
120# Tracked: git mv old new
121# Untracked: mkdir -p … && mv old new
122```
123 
124## `.gitignore` revision (after cleanup)
125 
126**Goal:** stop regenerated junk from polluting `git status`, without hiding real source.
127 
1281. **Read** root `.gitignore` and, in monorepos, `apps/*/.gitignore` / `packages/*/.gitignore` as needed. Check **`.git/info/exclude`** for machine-only rules that should *not* be committed (keep personal noise there; don’t copy into shared `.gitignore` unless the team agrees).
1292. **Per-path checks** (last match wins; shows which file defined the rule):
130 
131```sh
132   git check-ignore -v path/to/artifact
133   git status -u --ignored    # optional: see ignored names (noisy)
134```
135 
1363. **Pattern style**
137   - Leading `/` = relative to the `.gitignore`’s directory (e.g. `/dist/` = only that folder at that level, not all nested `dist` unless intended).
138   - `**` for deep trees, e.g. `**/*.log`, when noise appears at many depths.
139   - **Negation** (`!`) is tricky: later rules, parent dirs, and `git add -f` interact—prefer narrow positive ignores over `!` unless you already use negation in that file.
1404. **Do not** add rules that would ignore: application source, small JSON/YAML config the repo tracks, or `!important` assets. When unsure, run `git check-ignore -v` on a *known good* file that must stay tracked.
1415. **Tracked but should be ignored** (user already committed `build/` once): this skill does not silently fix history; flag `git rm -r --cached <path>` + `.gitignore` as a **separate** explicit step the user must approve.
1426. **Global excludes** (optional heads-up for “why is this still ignored?”):
143 
144```sh
145   git config --get core.excludesfile
146```
147 
148## Safety: never pass through these in automated deletes
149 
150- `.git/`, `.svn/`, `.hg/`
151- `node_modules/`, `vendor/`, `venv/`, `.venv/`, `__pypackages__/`
152- Files matching `.env`, `.env.*` (except `.env.example` if intentional)
153- `~/.ssh`, `id_rsa*`, `*.pem` inside project trees
154 
155## Post-deploy / server-ish extras (name buckets to stack)
156 
157- Docker: dangling images/volumes (only if user asked for Docker cleanup; requires `docker` context).
158- CI: `*.log` under `build/`, artifact dirs from previous runs.
159- K8s: local `*.kube`, tmp kubeconfigs—list only; do not delete without confirmation.
160 
161## Inspiration
162 
163- Same **inventory → plan → confirm → act** flow as [post-deploy environment cleanup](https://mcpmarket.com/tools/skills/post-deploy-environment-cleanup) style workflows.
164- [Agent template public](https://github.com/matsuni-kk/agent_template_public): honor **Flow** (draft) vs **Stock** (stable); do not “clean” user drafts from Flow without explicit approval.
165