Gud Boi
f084e89991
Commit the AI-authored design doc driving this branch's 7-commit `brokerd` -> (`datad` + `brokerd`) split; all prior commits' `Prompt-IO:` entries reference its stages so this makes those refs resolvable in-repo for PR review. Also, - add the doc's own prompt-io entry pair (scope: docs) incl. a 4-item implementation-deviation log vs. the plan as written. (this patch was generated in some part by [`claude-code`][claude-code-gh]) [claude-code-gh]: https://github.com/anthropics/claude-code Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Prompt-IO: ai/prompt-io/claude/20260610T173309Z_f15f8178_prompt_io.md |
||
|---|---|---|
| .. | ||
| claude-code | ||
| prompt-io/claude | ||
| 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