piker/ai
Gud Boi cb5e81d443 Pin qualified `tractor` and require `trio>=0.34.0`
Advance the `piker_pin` lock from `b64c89f0` to the published
`8fe574c1`, retaining the evaluated Trio 0.34.0 release. Require
Trio >=0.34.0 for the updated cancellation APIs. Restore the Git
source used before local editable evaluation; no environment sync
is included.

Record the human's overlapping charts, Gateway data reset and
close/reopen qualification. Keep the full Gateway restart string
error and Tractor teardown callback assertion explicit as separate
recovery limits. Offline lock validation resolves 126 packages;
this is not a fresh-install qualification claim.

Prompt-IO: ai/prompt-io/20261106T201746Z_495c0915_612dfc_prompt_io.md

(this patch was generated in some part by `codex` (`openai`))
2026-11-06 15:21:33 -05:00
..
claude-code Add `ai/` integration docs w/ `/commit-msg` usage 2026-03-05 15:30:34 -05:00
prompt-io Pin qualified `tractor` and require `trio>=0.34.0` 2026-11-06 15:21:33 -05:00
README.md Add `ai/` integration docs w/ `/commit-msg` usage 2026-03-05 15:30:34 -05:00
ib-recovery-candidate.md Document bounded IB recovery and downstream replay 2026-10-23 11:36:29 -04:00
ib-recovery-qualification-20261106.md Pin qualified `tractor` and require `trio>=0.34.0` 2026-11-06 15:21:33 -05:00

README.md

AI Tooling Integrations

Documentation and usage guides for AI-assisted development tools integrated with this repo.

Each subdirectory corresponds to a specific AI tool or frontend and contains usage docs for the custom skills/prompts/workflows configured for it.

Originally introduced in PR #69; track new integration ideas and proposals in issue #79.

Integrations

Tool Directory Status
Claude Code claude-code/ active

Adding a New Integration

Create a subdirectory named after the tool (use lowercase + hyphens), then add:

  1. A README.md covering setup, available skills/commands, and usage examples
  2. Any tool-specific config or prompt files
ai/
├── README.md                  # <- you are here
├── claude-code/
│   └── README.md
├── opencode/                  # future
│   └── README.md
└── <your-tool>/
    └── README.md

Conventions

  • Skill/command names use hyphen-case (commit-msg, not commit_msg)
  • Each integration doc should describe what the skill does, how to invoke it, and any output artifacts it produces
  • Keep docs concise; link to the actual skill source files (under .claude/skills/, etc.) rather than duplicating content