AI Developer Documentation
Instructions for AI coding assistants (Claude, Copilot, etc.) working on devcontainer-toolbox.
Documents​
| Document | Purpose |
|---|---|
| WORKFLOW.md | End-to-end flow from idea to implemented feature (start here) |
| PLANS.md | Plan structure, templates, and how to write plans |
| CREATING-SCRIPTS.md | How to create new install/service/config scripts |
| CI/CD | GitHub Actions, versioning, and pre-merge checklist |
Plans Folder​
Implementation plans are stored in plans/:
plans/
├── active/ # Currently being worked on (max 1-2 at a time)
├── backlog/ # Approved plans waiting for implementation
└── completed/ # Done - kept for reference
File Types​
| Type | When to use |
|---|---|
PLAN-*.md | Solution is clear, ready to implement |
INVESTIGATE-*.md | Needs research first, approach unclear |
Quick Reference​
When user says "I want to add X" or "Fix Y":​
- Create
PLAN-*.mdinplans/backlog/ - Ask user to review the plan
- Wait for approval before implementing
When user approves a plan:​
- Ask: "Do you want to work on a feature branch? (recommended)"
- Create branch if yes
- Move plan to
plans/active/ - Implement phase by phase
- Ask user to confirm after each phase
When implementation is complete:​
- Move plan to
plans/completed/ - Create Pull Request if on feature branch
When creating new tools or services:​
- Read CREATING-SCRIPTS.md for patterns and templates
- Follow the metadata requirements exactly
- Tests must pass - Run before committing:
.devcontainer/additions/tests/run-all-tests.sh static <script> - CI will reject PRs with failing tests
Related Documentation​
- Contributor docs - Technical documentation for human developers
- CLAUDE.md - Project-specific Claude Code instructions (in repo root)