# Toolbox Template SEED

This SEED file defines the high-level objectives for all toolboxes created from this template.

## 🎯 Goals

- **Extensibility**: Each toolbox should extend from `toolbox-base` to inherit core tooling
- **Consistency**: All toolboxes should follow the same patterns and conventions
- **Reproducibility**: Toolbox builds should be deterministic and cache-efficient
- **Security**: Toolboxes should run as non-root users with minimal privileges
- **Portability**: Toolboxes should work identically across different host environments

## 🧰 Requirements

- **Base Image**: Extend from `tsysdevstack-toolboxstack-toolbox-base:release-current`
- **User Model**: Run as non-root `toolbox` user (UID/GID mapped to host)
- **Workspace**: Mount current directory to `/workspace` (read/write)
- **Runtime**: Inherit all base tooling plus toolbox-specific additions
- **Configuration**: Preserve user configs/mise toolchains via volume mounts

## 🛠️ Implementation

- **Dockerfile**: Extend from base with toolbox-specific tooling
- **docker-compose.yml**: Configure service with inherited + custom settings
- **build.sh**: Wrapper around `docker build` with UID/GID mapping
- **run.sh**: Helper to bring service up/down
- **devcontainer.json**: VS Code remote container definition
- **SEED**: Define toolbox-specific objectives (this file)
- **PROMPT**: LLM onboarding prompt for future contributors

## ✅ Verification

- Toolboxes should build without errors
- Toolboxes should start and run indefinitely
- Toolboxes should be accessible via `docker exec`
- Toolboxes should inherit all base tooling
- Toolboxes should support toolbox-specific additions
- Toolboxes should preserve user configurations across restarts