Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Requirements Specification: Holochain Agent Skill

Discovery session: 2026-03-12 Status: v1 scope confirmed


Problem Statement

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.


Target Users

PersonaContextPrimary Need
Junior Holochain developerLearning the framework, first hAppGuided workflows, explanations, scaffold commands
Experienced Holochain developerActive project, knows the patternsFast pattern lookup, CRUD generation, debugging help
Full-stack developer new to HolochainKnows Rust/TypeScript, learning DHT conceptsArchitecture explanation, data model design, TypeScript client integration

Functional Requirements

IDRequirementPriorityAcceptance Criteria
FR-01Skill must cover Architecture domainMustArchitecture.md loads on request; covers coordinator/integrity split, DNA structure, Nix, progenitor, multi-DNA, private entries
FR-02Skill must cover Design domainMustWorkflows/DesignDataModel.md guides entry/link type design with output artifacts
FR-03Skill must cover Scaffold domainMustScaffold.md + Workflows/Scaffold.md cover: Holonix setup, Nix flake, hc CLI, hc scaffold commands, new project workflow, add-domain-to-existing workflow
FR-04Scaffold workflow follows official Holochain documentationMustCommands and patterns reference developer.holochain.org; version pins current (hdk=0.6.1, hdi=0.7.1)
FR-05Skill must cover Implementation domainMustPatterns.md covers entry types, link types, CRUD, cross-zome calls, signals, validation, HDK 0.6 API
FR-06Skill must cover Testing domainMustTesting.md covers Tryorama setup, two-agent scenarios, dhtSync, update/delete patterns
FR-07Skill must cover Deployment domainMustDeployment.md + Workflows/PackageAndDeploy.md cover Kangaroo-Electron packaging, CI/CD, versioning
FR-08Skill must be PAI-independentMustNo voice notification curl, no SKILLCUSTOMIZATIONS hook, no PROJECTS.md references, no Algorithm routing; works in vanilla Claude Code
FR-09Skill must include installation documentationMustREADME.md with 3 installation options (global, project-local, symlink), quick start examples
FR-10Domain correspondence with PAI versionShouldSame sections, same knowledge depth, same workflow structure — different wrappers
FR-11Skill routing covers all 5 workflowsMustSKILL.md routing table maps natural language triggers to correct workflows
FR-12Context files load on demandMustSKILL.md specifies which context file to load for each topic; not all pre-loaded

Non-Functional Requirements

IDCategoryRequirementTarget
NFR-01PortabilityWorks with zero PAI infrastructureVerified by install in fresh Claude Code with no ~/.claude/PAI/
NFR-02CurrencyVersion pins match current stable Holochainhdk=0.6.1, hdi=0.7.1, holonix ref=main-0.6 at release
NFR-03CompletenessAll 6 domains have contentNo stub files in v1 release
NFR-04AccuracyCode examples compile and run correctlyExamples tested against real hAppenings/Nondominium codebase

Constraints

  • v1 conforms to Agent Skills Open Standard — compatible with Claude Code, GitHub Copilot, Cursor, Augment, and Codex
  • Ecosystem expansion deferred to v2 — hREA, unyt, holochain-open-dev, ADAM, Wind Tunnel not in scope
  • 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

Open Questions

  • Public repo location: Personal GitHub or a community org (Holochain Foundation, holochain-open-dev)?
  • Community discovery: How to publicize the skill to the Holochain developer community?
  • PAI merge trigger: Time-based (3 months) or milestone-based (X workflows proven stable)?
  • Contribution model: Solo-maintained or open contributions from day one?

Deferred (v2+)

FeatureTarget VersionDescription
hREA / ValueFlows sub-skillv2Scaffold and implement ValueFlows-compatible zomes
holochain-open-dev patternsv2Profiles, links to other happs, linked devices
ADAM (coasys) integrationv2AD4M perspectives and expression languages
Wind Tunnel testingv2Performance testing for Holochain apps
unyt integrationv2Unit-aware numeric types for resource tracking
Holo hosting / edge nodesv2HTTP gateway, HolOS, Holo Node ISO setup
Cross-LLM portabilityv2Adapt for GLM 5, other AI clients with skill support
Skill graph / ecosystem orchestratorv2Parent skill routing to domain sub-skills
GUI / visual programmingv3+No-code interface with DHT model explorer
Diagram generationv3+Visual architecture and data flow diagrams
Progressive disclosure UIv3+Junior/senior mode switching