gistfile1.txt

# AI Sandbox Repository

This repository is an **open sandbox exclusively for AI tools** (like Claude Code, Cursor, etc.) to use for experiments, prototypes, and research projects.

## Purpose

This space is for AI-assisted work that doesn't belong in other repositories. Use it freely to:
- Test ideas and prototypes
- Build small utilities or tools
- Conduct research or experiments
- Create proof-of-concepts
- Try out new technologies

## Repository Structure

Follow the structure used by [Simon Willison's research repository](https://github.com/simonw/research):

```
ai-sandbox/
├── README.md
├── CLAUDE.md (this file)
├── project-name-1/
│   ├── README.md
│   ├── notes.md
│   └── [project files]
├── project-name-2/
│   ├── README.md
│   ├── notes.md
│   └── [project files]
└── ...
```

### Project Organization

Each new project should:

1. **Live in its own directory** with a descriptive kebab-case name
2. **Keep working notes and thoughts in a notes.md file**
3. **Include a README.md** with full report of the project
4. **Update the repo’s root README.md** to list the new project

## Updating the Root README

**IMPORTANT**: Every time you finish a project, you MUST update `/Users/chase/Repositories/ai-sandbox/README.md` to include the new project.

The README should:
1. List all projects in **reverse chronological order** (newest first)
2. Include the date the project was created
3. Link to the project directory
4. Include an executive summary and key features of the project

### README Format

```markdown
# AI Sandbox

Research projects and experiments conducted by AI tools.

## Projects

### [project-name](./project-name/) - YYYY-MM-DD

Executive summary goes here.

**Key Features/Findings**:
- Feature 1
- Feature 2
- Feature 3

---

### [older-project](./older-project/) - YYYY-MM-DD

...
```

## Workflow

When creating a new project:

1. Create a new directory with a descriptive name
2. Create a notes.md file in that folder and append notes to it as you work, tracking what you tried and anything you learned along the way.
3. Build a README.md report at the end of the investigation.
4. Your final commit should include just that folder and selected items from its contents:
  	- The notes.md and README.md files
  	- Any code you wrote along the way
  	- If you checked out and modified an existing repo, the output of "git diff" against that modified repo saved as a file.
5. Update the root README.md by adding the new project at the TOP of the projects list
7. Commit with a clear message describing what was built