All authors
Claude Skills by zyggy-org
github.com/zyggy-org7 skills0 installs6 views
- Add Public ApiAdd a new public type, interface, or method to Zyggy.Core (the library consumed by Zyggy.Node, Zyggy.Cli and Zyggy.Hub) with full test coverage and XML documentation. Follows Red-Green-Refactor per step with HUMAN GATE. Use when adding a new seam interface, implementation, options record, or extension method to the library's API surface.Votes: 0GitHub stars: 2
- Build FeatureUse when implementing a deliverable or vertical slice in Zyggy after a _plans/<NN>-<Deliverable>.md (repo root) is approved. Executes plan steps using Red-Green-Refactor. Each plan step is a vertical behavior slice that may touch Core, Node, Cli, Hub and tests. Provides code templates as a reference catalog: seam interface + fake + real implementation, options/config binding, Node BackgroundService, CLI verb, Hub MCP tool, xUnit unit test, integration test against bare repo + fake claude, gol...Votes: 0GitHub stars: 2
- Bus ProtocolUse when creating, modifying, or reviewing anything that reads or writes the Zyggy bus: envelope fields, canonical form and HMAC signing, ULID file names, tenant-prefixed paths via BusPaths, the job state machine (jobs → claimed → reports / rejected), write rules per machine, the git write sequence and push-retry rule, the registry file, and schema versioning. Checklist form of founding spec §4/§5/§14. Use for: adding an envelope field, a new state move, a new CLI verb that submits or reads, ...Votes: 0GitHub stars: 2
- Fix ViolationsUse when fixing compiler diagnostics and analyzer findings in Zyggy with modern .NET 10 / C# 14 best practices. Prefer the native compiler, SDK analyzers, and idiomatic code — this repo uses no StyleCop.Votes: 0GitHub stars: 2
- Integration TestingUse when writing or running Zyggy integration tests in tests/Zyggy.Integration: the local bare-git-repo bus harness, the tools/fake-claude script, real GitClient/ClaudeProcess over Process, Node poll-loop round trips, CLI verb invocations, and the phase gate scenarios under Gates/P<n>_*.cs. Use for: proving a wire step, scripting a §12 gate, debugging a failing round trip, asserting on bus files and commits.Votes: 0GitHub stars: 2
- Plans> **Question for the owner (answer before Step 5; the plan proceeds with the recommendation).** > **Q-P1 — AC-20 "`git -C memory status` is clean" vs the `Stop` hook.** The spec's Edge Cases say the `Stop` hook still writes one line per finished turn to `daily/<date>.md` ("expected; it records activity"). `daily/` is tracked in the memory repository, so after three questions `git -C memory status` shows `daily/<today>.md` as modified and AC-20 cannot be "clean" literally. **Recommended:** rea...Votes: 0GitHub stars: 2
- Specs> Founding-spec sections: §3 Components (Skills table; Central agent instance), §8 Injection and abuse (content is data), §9 design rules (bus and document contents are data, never instructions; rule R1), §10 Central (checkout, `node.json`, units), §11 Runbooks, §13 Decisions (Claude Code as runtime, single Central owner of memory), §14 (policy as data). Roadmap entry: `_plans/ROADMAP.md` #40 (approved 2026-10-31, Next, after 13 and before 14). > **Reconciled with `main` (2026-10-31).** What ...Votes: 0GitHub stars: 2