workspace-standardslisted

# Workspace Management Standards ## Cross-Project Documentation Each project must maintain: 1. **README.md** at root: purpose, quick start, usage examples, cost implications 2. **Directory structure docs** for complex projects 3. **Change logs** for significant modifications ## Git Workflow - **Branching**: `main` for production. Prefixes: `feature/`, `bugfix/`, `hotfix/`, `release/`, `chore/`. - **Commits**: Follow Conventional Commits (`feat:`, `fix:`, `docs:`, etc.). - **Worktrees**: All development in dedicated worktrees (see `/git-workflow-standards`). ## Security - Use `.env` locally (never committed) and secure parameter stores for cloud. - Principle of least privilege for all resources and services. ## Cost Management | Environment | Lifecycle | | --- | --- | | Development | Automated shutdown | | Testing | Manual cleanup | | Production | Scheduled backups | Define and monitor monthly budgets per environment. ## Project Lifecycle - **Create**: Initialize with standard templates (README, .gitignore, LICENSE). - **Maintain**: Review dependencies, update docs, optimize costs. - **Retire**: Document, archive, clean up. ## Related Skills - **agentsmd-authoring** (project-standards) — Use when editing agentsmd files, creating skills/agents/rules, or working in ai-assistant-instructions - **skills-registry** (project-standards) — Use when looking up available tools, skills, commands, agents, or plugins