Menu
When files are accidentally created in the wrong directory, remove them immediately before proceeding to the correct location.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Before adding new UI elements to an existing site, read the stylesheet to extract design tokens (colors, radii, font, button classes) so new elements look native.
Before implementing new features, run existing tests to confirm green baseline: this ensures any failures after changes are attributable to new code, not pre-existing issues.
Review skills that the skill-extractor mined from your Claude Code traces โ inspect each candidate's definition and confidence/utility scores, edit it, then install it as a real skill or reject it with a comment. Use when the user runs /review-skills, asks to "review discovered/mined skills", or a session-start banner reports pending skills.
| name | clean-up-wrong-path-immediately |
| description | When files are accidentally created in the wrong directory, remove them immediately before proceeding to the correct location. |
When to use: When you realize you've written files to the wrong project directory or path.
rm -f <file> and rmdir <dir> to clean up.Why: Stray files in wrong repos cause confusion, potential git commits of garbage, and clutter. The longer they exist, the more likely they'll be forgotten.
Prevention: Before writing files, confirm the correct project root by checking for existing project markers (package.json, README, .git, existing index.html).
Mined by skill-extractor from a local repo (confidence 0.7, utility 0.629, trace outcome success). Review & edit as needed.