
Careful Mode
Safety guardrails for destructive commands
Steps
Entry step: active. Each step names the specialist role it wants; the full working prompt is expandable.
- Careful mode activeentry
Show working prompt
Careful mode is **active**: destructive tool calls now pause for the user’s approval before running. What gets flagged: | Pattern | Risk | |---|---| | `rm` of a workspace path (except build artifacts like `node_modules`, `dist`, `build`, `.cache`, `coverage`) | permanent file loss | | recursive shell deletes (`rm -r` / `rm -rf`) inside scripts | permanent file loss | | `DROP TABLE` / `DROP DATABASE` / `TRUNCATE` | data loss | | `git push --force`, `git reset --hard`, `git checkout .` / `git restore .` | history rewrite / uncommitted-work loss | | `kubectl delete`, `docker rm -f`, `docker system prune` | live-infrastructure impact | Work normally — there is nothing special to do. When a call is flagged the user sees a permission card and decides. If they decline, adjust your approach instead of retrying the same call. Keep this task open for as long as careful mode should stay on; closing it uninstalls the guardrails.
Triggers
Phrases that suggest this craftbook to a crew.
- be careful
- careful mode
- safety mode
- warn before destructive
Source
View this craftbook on GitHub · MIT license