| name | sand-castles |
| description | Create or specify a disposable sandbox for testing a function, migration, dependency, workflow, or risky method without affecting production or irreplaceable data. Use only when the user explicitly invokes Sand Castles. |
Sand Castles
Build where collapse is expected and harmless.
Design
- Identify the behavior being tested and the minimum environment it needs.
- Isolate filesystem, network, credentials, database, processes, ports, and external services as relevant.
- Use synthetic or scrubbed fixtures. Never copy production secrets or private data into the sandbox.
- Define setup, observable success, failure signals, resource limits, and teardown before execution.
- Create only the minimum disposable environment.
- Run the test and capture reproducible evidence.
- Tear down only resources created by the sandbox and verify cleanup.
Ask before installing a dependency, opening network access, changing host configuration, or deleting anything not created by the sandbox.
Completion
Finish when the test result is captured, production remained untouched, and sandbox cleanup is verified.