Design system for the Horizen protocol website (www.horizen.io). Use this skill whenever building UI, components, pages, or layouts for the Horizen protocol โ including when the user mentions Horizen, hz- tokens, horizen.io, or needs to create web3/blockchain UI following Horizen's yellow/black brand. Also use when the user references horizen-design-system.html or asks about Horizen design tokens, typography (Funnel Display, Proxima Nova), or component patterns.
Design system for the Horizen Labs company website (www.horizenlabs.io). Use this skill whenever building UI, components, pages, or layouts for Horizen Labs โ including when the user mentions Horizen Labs, hl- tokens, horizenlabs.io, or needs to create institutional/technical UI following Horizen Labs' navy/teal/magenta brand with sharp corners. Also use when the user references horizenlabs-design-system.html or asks about Horizen Labs design tokens, typography (Azeret Mono, Roboto), component patterns, or the sharp-corner design philosophy.
Design system for the zkVerify verification protocol website (www.zkverify.io). Use this skill whenever building UI, components, pages, or layouts for zkVerify โ including when the user mentions zkVerify, zk- tokens, zkverify.io, zero-knowledge proofs, or needs to create verification/ZK-proof UI following zkVerify's green(Pulse)/blue(Signal)/dark(Void) brand. Also use when the user references zk-verify-design-system.html or asks about zkVerify design tokens, typography (Monigue, Space Grotesk), or component patterns.
Horizen Labs Agent Marketplace integration on Base Sepolia โ full pipeline from ZK proof submission (Kurier) through attestation relay to on-chain validation recording. Covers agent registration (IdentityRegistry), validation recording (ValidationGateway), attestation polling, and marketplace discovery.
Kurier REST API for simplified proof verification. Use when you want the simplest integration path, don't need real-time events, or are building serverless/REST-based architectures. Covers API key setup, proof submission, status polling, and aggregation.
This skill should be used when the user asks to "analyze a crate for no_std", "assess no_std compatibility", "check if a crate supports no_std", "evaluate no_std support", "no_std assessment report", "can this crate compile with no_std", "no_std feasibility", "what std dependencies does this crate have", or mentions evaluating a Rust crate or library for `no_std` compilation support.
This skill should be used when the user asks to "assess a Rust crate for stable toolchain", "check if a crate needs nightly", "analyze nightly features in a Rust crate", "evaluate stable compatibility", "can this crate compile on stable", "assess stable migration feasibility", "check nightly dependencies", or mentions evaluating whether a Rust crate can drop the nightly toolchain requirement.
This skill should be used when the user asks to "assess a verifier crate", "assess verifier feasibility", "evaluate a ZK crate for zkVerify", "check if a crate can be a zkVerify verifier", "analyze unsafe in a verifier crate", "create a verifier assessment", "full verifier assessment", or mentions assessing whether a ZK proof verification crate can be integrated as a zkVerify verifier pallet. This is a comprehensive assessment that first checks no_std and stable toolchain compatibility, and only then proceeds to verifier-specific analysis.