The Holochain developer ecosystem lacks a comprehensive AI coding assistant skill that covers the full development cycle in one place. Existing documentation is scattered across developer.holochain.org, GitHub repos, and community channels. New developers face steep learning curves; experienced developers lack a fast co-pilot for implementation patterns. This skill addresses both by providing a structured, context-aware assistant that works across the full spiral: architecture, design, scaffolding, implementation, testing, and deployment.
A secondary goal is enabling the wider Holochain community to benefit from AI-assisted development without requiring PAI (Personal AI Infrastructure) — the skill must work as a standalone agent skill with zero external dependencies.
v1 conforms to Agent Skills Open Standard — compatible with Claude Code, GitHub Copilot, Cursor, Augment, and Codex
Ecosystem expansion deferred to v2: hREA, unyt, ADAM, and deep holochain-open-dev component patterns are not in scope. Wind Tunnel ships in v1.0 (references/wind-tunnel.md), and SKILL.md carries a companion-library currency table so users are not steered at 0.6-era tooling
Two independent codebases for v1 — PAI version and vanilla version developed separately; integration/merge post-v1
No GUI in v1 — visual tooling, diagram generation, and no-code interfaces are v3+ vision
Official docs anchor — Scaffold workflow must follow developer.holochain.org, not invent conventions
Personal GitHub, Soushi888/holochain-agent-skills, Apache-2.0. Moving to a community org stays possible later and costs nothing now
The repo is already there; LICENSE is Apache-2.0
Contribution model
Open from day one
CONTRIBUTING.md, CODE_OF_CONDUCT.md (Contributor Covenant 2.1), issue forms including a dedicated stale-version report, and a PR template all ship in v1.0
Community discovery: how to publicize to the Holochain developer community. Candidates are the Holochain Discord, the developer forum, and the holochain-open-dev orbit. Not a code decision, so it does not gate v1.0.
PAI merge trigger: time-based or milestone-based. Out of scope for the public repo, which must stay PAI-independent by constraint.