Gud Boi
69a6edd6f8
Canonicalize legacy socket pairs and tagged tuples before storing or comparing `Registry.addrs`, keeping existing config readable when tractor emits protocol-tagged forms. Also, - broaden registry/runtime addr annotations for both wire shapes - compare service fixture addrs through tractor's address codec - use tractor's shared `--ll` pytest option instead of registering it twice - cover mixed legacy/tagged registry state and `pikerd` startup Prompt-IO: ai/prompt-io/opencode/20260820T163519Z_5f631e19_prompt_io.md (this patch was generated in some part by `opencode` using `gpt-5.6-sol` (`openai`)) |
||
|---|---|---|
| .. | ||
| claude-code | ||
| prompt-io | ||
| README.md | ||
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:
- A
README.mdcovering setup, available skills/commands, and usage examples - Any tool-specific config or prompt files
ai/
├── README.md # <- you are here
├── claude-code/
│ └── README.md
├── opencode/ # future
│ └── README.md
└── <your-tool>/
└── README.mdConventions
- Skill/command names use hyphen-case (
commit-msg, notcommit_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