Aligns gokit modules with the sibling rskit Rust toolkit by capability.
npx skills add https://github.com/kbukum/gokit --skill parity-kbukum
Please help me install this Agent Skill. Skill: parity Source: https://github.com/kbukum/gokit/tree/main/.github/skills/parity Command: npx skills add https://github.com/kbukum/gokit --skill parity-kbukum
any in public APIs instead of transliterating Rust. - Parity tracking workflow: Records mirroring levels and deliberate divergences in rskit tracking issues referenced by full URL, and validates changes with toven tests. - Use Case: When porting a resilience or config module from rskit to gokit, use this Skill to study the stronger implementation, decide the mirroring level, implement it idiomatically, and log the parity decision. ## Quick Start Ask the assistant to align the gokit config module with its rskit counterpart and record the parity decision in an rskit tracking issue.High-intent search queries and answers about installing and using this skill.
Locate the counterpart crate in the rskit repository, study its public API, invariants, and error model, then decide which kit has the stronger implementation. Implement the capability idiomatically in Go rather than transliterating Rust, and record the decision in an rskit tracking issue.
Parity means matching capabilities and behavior so users transfer intuition between kits, not copying symbols or directory layouts. Each scope is judged individually, and the kit with the better implementation sets the shape the other mirrors.
No. Capabilities are classified as fully mirrored, light versions, or intentionally kit-only. Heavy media transcoding stays rskit-only, while framework-specific items like rskit's Axum http layer are folded into gokit server and recorded as deliberate exclusions.
Idiomatic, up-to-date Go practices always win over parity, and project-wide consistency outranks both. Parity only strictly binds wire and contract compatibility such as serialized shapes and protocol semantics, not internal representations.
Decisions are recorded in tracking issues in the rskit repository, noting the capability, mirroring level, and any intentional divergence. Cross-repo references must use full URLs because bare issue numbers resolve to the current repository.
devs6186Search npm, PyPI, GitHub, and internal references before coding.
kortix-aiStructure sections, extract claims, verify facts, and annotate PDF, DOCX, PPTX, and XLSX documents.
y-miyazakiGuide manual Go code reviews across correctness, security, performance, and idioms.
kimmyxpowGenerate craft-driven interface designs from intent and domain exploration.