codeflash-agent/.claude/rules/optimization-projects.md
Kevin Turcios cc29a27289
Migrate .codeflash/ to {teammember}/{org}/{project}/ format (#15)
Add team member dimension to case study paths so multiple contributors
can track optimization data independently. Derives member from
git config user.name in session-start hooks.

- Move all case studies under .codeflash/krrt7/
- Rename pypa/pip → python/pip (org grouping)
- Update session-start hooks, docs, scripts, and references
2026-04-14 23:04:34 -05:00

911 B

Optimization Project Workflow

Location

Active optimization data lives in .codeflash/{teammember}/{org}/{project}/ on main. Summaries are built into case-studies/{org}/{project}/.

Status tracking

Every optimization project has a status.md at its root. Update it after every session:

  • What was completed this session
  • What's next
  • Current branches in the target repo
  • VM state (running/deallocated)
  • Any blockers

This file persists across sessions -- it's the source of truth for resuming work, not session memory.

Recording results

After every VM benchmark run:

  1. Append to data/results.tsv with the commit, target, before/after numbers
  2. Update README.md results table if the optimization is kept
  3. Update status.md with current state

Committing

Commit optimization data changes to main alongside other work. This data is part of the repo, not isolated on branches.