CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
## Project Overview
Amazon competitive intelligence and category selection analysis workspace using Sorftime
other detail that identifies whose system produced a payload must never appear in code, comments, test fixtures, commit messages, branch names, file names, PR titles, PR descriptions, PR comments
must be propagated: Browser → WebSocket → PTY → tmux
- Input/output is binary-safe (supports ANSI escape codes, Unicode, etc.)
When working with terminal components:
- xterm.js handles rendering only - it doesn't know
CLAUDE.md
This file provides guidance to Claude Code when working with code in this repository.
## Project Overview
Link CLI — lets agents get secure, one-time-use payment credentials from
task will clearly exceed these sizes, propose splitting it into
multiple independently reviewable PRs *before* writing code, and call out
the split in your plan.
- If a size warning fires
code already
says. Keep it short and specific. If a comment doesn't clearly earn its
place, omit it.
The goal is signal-dense PRs that are easy to review
Windows-first** desktop app that organizes, operates, and resumes multiple coding
agents (Claude Code, Codex, OpenCode) and shells in parallel, inside a persistent workspace with
real terminals (PTYs), layouts, themes
warns,
and then needs `JARVIS_ALLOWED_ORIGINS`.
## The Run Pipeline
Nothing spawns Claude Code outside `RunExecutor`. Two invariants govern it:
1. **A run always reaches a terminal state.** `succeeded`, `failed
spec written to
disk and approved by voice, then a real Claude Code session driven through
plan, review and execute.
- You watch every Claude Code session on the machine
stored in `~/.typeagent/`
- Tracing via the `debug` package — enable with `DEBUG=typeagent:*` env var
## CodeReview Guidelines
Use these criteria both when **writing** changes and when **reviewing** code (your
which `.context/INDEX.md` links.
Always use the `clean-code:typescript` skill when writing or reviewing TypeScript code in this
repo.
## First-time setup after clone
```bash
bun install
line)
- Use self-deprecating humor about AI when it fits ("I've reviewed 500 lines of code and my only complaint is that I can't drink coffee while doing
Before opening, run the [`closeout-review`](.agents/skills/closeout-review/SKILL.md)
skill on the working diff (a `PreToolUse` hook gates `gh pr create` on it).
Describe what the code does now — plain, factual language
command discovery. Invoke the selected skill with
`flow-next:flow-next- ` on Claude Code; follow its task-specific contract.
This is a repo-customized block. Keep maintainer additions outside
auditor`) skills |
### Generator vs Advisory vs Workflow Skills
- **Advisory skills** (ios/, macos/, release-review/): Reviewcode and provide recommendations
- **Generator skills** (generators/): Produce production-ready Swift code with templates
- **Workflow
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.