Guides safe changes to zicato source code, tests, contracts, and workflows.
npx skills add https://github.com/pedapudi/zicato --skill zicato-dev-guide
Please help me install this Agent Skill. Skill: zicato-dev-guide Source: https://github.com/pedapudi/zicato/tree/main/skills/zicato-dev-guide Command: npx skills add https://github.com/pedapudi/zicato --skill zicato-dev-guide
This Skill helps developers modify zicato safely without overlooking its architecture, contracts, testing requirements, or hard-won engineering invariants.
Use the zicato development guide to safely review and implement the requested source or test change.
High-intent search queries and answers about installing and using this skill.
To safely modify software architecture and preserve invariants, consult a code-grounded development guide that outlines Golden Rules, visibility constraints, and worker-boundary rules before changing source code. This ensures architectural integrity and invariant protection throughout your development workflow.
Required pre-commit verification steps for testing and formatting include running a validation ladder covering tests, formatting checks, typing, import contracts, parity gates, JavaScript checks, oracle tests, and vendor scanning. These steps ensure source code changes meet all engineering invariants before committing.
You need to check development guide chapters when changing tournament or scoring code to identify governing invariants, read relevant development recipes, and run required validation steps. This surface routing directs changes to the correct chapter across 14 development guide sections.
Yes, this code-grounded guidance covers orchestrator, runtime, and storage development workflows, applying also to proposer, tournament, selection, scoring, supervisor, dashboard, builder, CLI, and harness-adapter work. It ensures safe changes across all listed architectural components.
The Golden Rules and shipped-bug warnings are invariant protection mechanisms that define visibility constraints, epoch requirements, and worker-boundary rules you must follow when modifying contracts. They prevent regressions and preserve hard-won engineering invariants during code modification.
ThorstensenDetect LLM reward hacking in .NET code changes with SW001–SW006 rules.
sayali-ingle-pdlConfigure Husky pre-commit hooks to run linting, tests, and formatting.
cosmixGenerate and validate Kubernetes manifests for deployments, services, and RBAC.
PlamenTSVAnalyze monetary parameter configurations in Sui Move protocols for boundary violations and invariant breaches.
