claude-sandbox

Document Claude sandbox architecture decisions and historical reversals for audits.

32|5|Updated Oct 6, 2024

Search Tags:#architecture #claude #sandbox #devcontainer #threat-model #decision-log #promote

Ready to run

npx skills add https://github.com/gilesknap/tpi-k3s-ansible --skill claude-sandbox

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-sandbox
Source: https://github.com/gilesknap/tpi-k3s-ansible/tree/main/.claude/skills/claude-sandbox
Command: npx skills add https://github.com/gilesknap/tpi-k3s-ansible --skill claude-sandbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill documents Claude sandbox architecture decisions, tradeoffs, and historical reversals to aid onboardings, audits, and future changes within the repo.

Core Features & Use Cases

Decision log: captures core architectural constraints, invariants, and the rationale behind changes to the Claude sandbox.
Walkthroughs & governance: outlines the three-layer model and the paths walked back, to guide maintainers and reviewers.
Surface guidance: lists files and artifacts to surface during development and CI updates (e.g., claude-shadow, install.sh, promote.sh, verify-sandbox.md).

Quick Start

Review the Claude sandbox guidelines and surface the recommended changes to the files listed in this skill.

Frequently Asked Questions about claude-sandbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I document architecture decisions and historical reversals for a devcontainer sandbox?▼

Document architecture decisions and historical reversals for a devcontainer sandbox by capturing invariants, design principles, and walkbacks, then linking directly to files and commands to aid audits and onboarding.

What files should I surface before making edits to Claude sandbox CI workflows?▼

Before editing Claude sandbox CI workflows, you should surface files like claude-shadow, install.sh, promote.sh, and verify-sandbox.md to maintain DevOps consistency and policy compliance.

Why does threat-modeling require a decision log for sandbox environments?▼

Threat-modeling requires a decision log for sandbox environments to capture architectural constraints and rationale behind policy changes, guiding reviewers through the three-layer model and walked-back paths.

Can I use a decision log to track policy walkbacks across devcontainers and CI workflows?▼

Yes, you can use a decision log to track policy walkbacks across devcontainers and CI workflows by recording design principles, historical reversals, and links to relevant installation and test references.

What is the best way to maintain DevOps consistency when updating a sandbox threat model?▼

Maintain DevOps consistency when updating a sandbox threat model by outlining invariants, surfacing recommended changes to listed files, and documenting the three-layer governance paths before edits.