New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Type Centric Rust API

by 0xMiden in 0xMiden/protocol

A skill your agent uses when adding a public Rust function, or adding a new case or check to an existing flow (a new note type, enum variant, validation rule) - put the behavior on the type that…

MITAuto-check passedDevelopment

Install Type Centric Rust API

skills CLI
$ npx skills add 0xMiden/protocol --skill type-centric-rust-api -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 0xMiden/protocol type-centric-rust-api --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/0xMiden/protocol.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/type-centric-rust-api .claude/skills/type-centric-rust-api && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
type-centric-rust-api
GitHub stars
133
Token cost
~1.5k tokens
SKILL.md length
564 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when adding a public Rust function, or adding a new case or check to an existing flow (a new note type, enum variant, validation rule) - put the behavior on the type that…

  • Works in 5 steps: Find the home type. The home type of a… → Find the existing decision point. This… → Hold shared context in a type. When… → …
  • Adding a public Rust function
  • SKILL.md covers Rule, Why and Examples
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Type Centric Rust API is an agent skill from 0xMiden/protocol. Use when adding a public Rust function, or adding a new case or check to an existing flow (a new note type, enum variant, validation rule) - put the behavior on the type that owns it and reshape the flow, instead of adding a free function or one more special case.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Rust. The repository describes itself as: Core components of the Miden protocol. The licence is MIT.

When your agent uses it

  • Adding a public Rust function
  • Adding a new case
  • Check to an existing flow (a new note type
  • Validation rule) - put the behavior on the type that owns it and reshape the flow

Example prompts

  • “/type-centric-rust-api”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Find the home type. The home type of a rule is the type whose data the rule reads. Put the rule in the crate that defines that type, next…
  2. Find the existing decision point. This is the match or loop that already classifies the input, for example the match on the StandardNote…
  3. Hold shared context in a type. When three or more functions take the same parameters (account_id, block_ref, fee_asset_id), make a struct…
  4. Put each operation on the type it operates on. A method on T operates on one T value. A function that builds a collection of T (for…
  5. Delete what the new structure replaces: the follow-up pass, the special-case block, the second parse, and each expect that relies on a…

What it can do on your machine

Read from SKILL.md and the folder at commit 474c88e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are rust).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Type Centric Rust API loads about 1.5k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 0xMiden/protocol at commit 474c88e, republished under its MIT licence (© 0xMiden). 564 words, ~1,465 tokens.

Download SKILL.mdSave it as .claude/skills/type-centric-rust-api/SKILL.md (or your agent's skills folder).
name
type-centric-rust-api
description
Use when adding a public Rust function, or adding a new case or check to an existing flow (a new note type, enum variant, validation rule) - put the behavior on the type that owns it and reshape the flow, instead of adding a free function or one more special case.

Type-Centric Rust API

Rule

Behavior lives on the type whose data it reads. Public behavior is a method (with a self, &self or &mut self receiver) on that type. Use a free function only when no single type owns the behavior, for example a private helper or when a type would only be introduced to hold the function as a method.

When a new requirement arrives, reshape the existing structure so that it fits the requirement:

  1. Find the home type. The home type of a rule is the type whose data the rule reads. Put the rule in the crate that defines that type, next to the MASM that the rule mirrors (if there is one). The type owns the rule:
    • A rule about the type's own data is an invariant. The constructor enforces it (see validate-in-constructor) and every mutating method upholds it, so holding a value proves the rule.
    • A rule that also needs outside context (the consuming account, the current block) is a method that takes that context as parameters.
  2. Find the existing decision point. This is the match or loop that already classifies the input, for example the match on the StandardNote variants. Add the new case as an arm or branch of it, not as a new pass before or after it. Parse and classify each input only one time.
  3. Hold shared context in a type. When three or more functions take the same parameters (account_id, block_ref, fee_asset_id), make a struct that holds them and has the operations as methods.
  4. Put each operation on the type it operates on. A method on T operates on one T value. A function that builds a collection of T (for example a Vec<T> from a slice of inputs), does not belong on T. Put it on the type that holds that input or context, for example the context struct from step 3.
  5. Delete what the new structure replaces: the follow-up pass, the special-case block, the second parse, and each expect that relies on a shape that only the old pass guaranteed.
Show full SKILL.md (217 more words)Show less

Each caller maps the result of the shared method to its own output type (a status enum, a failure record). The rule itself stays in one place.

Signs that the structure needs reshaping:

  • A function classifies its input again after an earlier step already did (it parses every note again, or infers "head vs. bound note" from the position in a Vec).
  • A match returns None for a variant (often through _ => None), and a special-case block after the match handles the same variant.
  • A free function takes a type from another crate as its first parameter. The function belongs on that type, in that crate.
  • An associated function without a receiver does not construct Self, for example NoteBundle::group(&[Note]) -> Vec<NoteBundle>.
  • Three or more functions take the same parameter list.

Why

A rule with one home is one place to change and one place to review. Each special case added next to an existing structure repeats part of the decision that the structure already makes. The copies drift apart, and a reader must find all of them to know the real behavior. A method is found through its type (IDE completion, rustdoc). A free function is found only if you already know its name.

Examples

The note consumption checker had to reject FEE_SPONSORSHIP notes that the account cannot consume.

rust
// Bad: free functions and special cases next to the existing structure.

// miden-tx: a second pass parses every note again, after `NoteBundle::group` already did,
// and infers from the bundle layout what `group` already knew.
pub(super) fn reject_unconsumable_sponsorships(
    bundles: &[NoteBundle],
    native_account_id: AccountId,
    block_ref: BlockNumber,
    collected_fee_asset_id: Option<AssetId>,
) -> Vec<FailedNote> {
    for bundle in bundles {
        let (head, bound_notes) = bundle.notes().split_first().expect("...");
        // ...
    }
}

// miden-tx: the reclaim rule mirrors MASM in miden-standards, but lives in another crate.
fn reject_orphan_sponsorship(sponsorship: &FeeSponsorshipNote, /* ... */) -> Option<SponsorshipRejection>;

// can_consume: `StandardNote::is_consumable` returns `None` for FEE_SPONSORSHIP,
// then one more special case follows.
if let Some(status) = sponsorship_consumption_status(note, target_account_id, block_ref) {
    return Ok(status);
}
rust
// Good: the structure is reshaped.

// miden-standards: the reclaim rule is on the note type, next to the MASM it mirrors.
impl FeeSponsorshipNote {
    pub fn check_reclaim(&self, account_id: AccountId, block_ref: BlockNumber) -> Result<(), ReclaimError>;
}

// miden-standards: FEE_SPONSORSHIP is one more arm of the existing match.
StandardNote::FEE_SPONSORSHIP => {
    match FeeSponsorshipNote::try_from(note)?.check_reclaim(target_account_id, block_ref) {
        Ok(()) => Ok(Some(NoteConsumptionStatus::ConsumableWithAuthorization)),
        // ...
    }
},

// miden-tx: the context is a type. The loop that already classifies each note also rejects it.
// `NoteBundle::group` became `NoteBundler::bundle`, because it builds a `Vec<NoteBundle>`, not one bundle.
struct NoteBundler {
    native_account_id: AccountId,
    block_ref: BlockNumber,
    collected_fee_asset_id: Option<AssetId>,
}

impl NoteBundler {
    fn bundle(&self, notes: &[Note]) -> (Vec<NoteBundle>, Vec<FailedNote>) {
        // ...
        match (sponsorship, feature_idx) {
            (Some(sponsorship), None) => match sponsorship.check_reclaim(self.native_account_id, self.block_ref) {
                // ...
            },
            // ...
        }
    }
}

© 0xMiden, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/type-centric-rust-api of 0xMiden/protocol.

Open the folder on GitHubat commit 474c88e

Compare with similar skills

Type Centric Rust API next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Type Centric Rust API compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Type Centric Rust API this skill0xMiden/protocol133—~1.5kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi23k—~2.5kAutomated safety check: NotesApache-2.0
RTK Rust Design Patternsrtk-ai/rtk83k—~1.9kAutomated safety check: PassApache-2.0
Release Skillsnexmoe/eve4213 repos~3.3kAutomated safety check: PassNone

Similar skills

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Rust Best Practices

    farm-fe/farm

    Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

  • RTK Rust Design Patterns

    rtk-ai/rtk

    Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.

    83k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release Skills

    nexmoe/eve

    Universal release workflow. An agent skill from nexmoe/eve.

    421 GitHub starsUsed in 3 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Pnpm Engine

    teambit/bit

    Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from 0xMiden/protocol

All 35 skills in this repo

  • Advice Provider Hygiene

    0xMiden/protocol

    A skill your agent uses when writing kernel, account, or note MASM code that reads from or writes to the advice provider (advice stack / advice map) — validate advice data.

    133 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cheap Masm Equivalents

    0xMiden/protocol

    A skill your agent uses when writing or reviewing MASM hot paths or loops — prefer the cheaper equivalent: loop counters and pointers on the operand stack instead of procedure locals, neq.0 over…

    133 GitHub stars~804 tokensUpdated yesterday
    Auto-check passed

  • Concise Changelog Entries

    0xMiden/protocol

    Keep CHANGELOG.md entries to a single concise sentence. An agent skill from 0xMiden/protocol.

    133 GitHub stars~805 tokensUpdated yesterday
    Auto-check passed

  • Concise PR And Issue Descriptions

    0xMiden/protocol

    Keep PR and issue descriptions short and decision-focused. An agent skill from 0xMiden/protocol.

    133 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

  • Conversion Method Naming

    0xMiden/protocol

    A skill your agent uses when naming a conversion or accessor method in Rust — follow the Rust API naming conventions for the method's cost and ownership.

    133 GitHub stars~450 tokensUpdated yesterday
    Auto-check passed

  • Decouple Component From Storage

    0xMiden/protocol

    A skill your agent uses when writing a generic MASM utility that accesses a caller-selected account storage slot — receive the slot as a parameter so the utility is portable across storage layouts.

    133 GitHub stars~529 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Type Centric Rust API

What does Type Centric Rust API do?

A skill your agent uses when adding a public Rust function, or adding a new case or check to an existing flow (a new note type, enum variant, validation rule) - put the behavior on the type that…. Type Centric Rust API is an agent skill from 0xMiden/protocol. Use when adding a public Rust function, or adding a new case or check to an existing flow (a new note type, enum variant, validation rule) - put the behavior on the type that owns it and reshape the flow, instead of adding a free function or one more special case.

When should I use Type Centric Rust API?

Type Centric Rust API fits situations like: adding a public Rust function; adding a new case; check to an existing flow (a new note type; validation rule) - put the behavior on the type that owns it and reshape the flow.

How do I install Type Centric Rust API in Claude Code?

Run `npx skills add 0xMiden/protocol --skill type-centric-rust-api -a claude-code`. Or copy the skill folder (.claude/skills/type-centric-rust-api in 0xMiden/protocol) into .claude/skills/type-centric-rust-api in your project. Claude Code loads it when a task matches its description.

How do I install Type Centric Rust API in Codex?

Run `npx skills add 0xMiden/protocol --skill type-centric-rust-api -a codex`. Or copy the skill folder (.claude/skills/type-centric-rust-api in 0xMiden/protocol) into .agents/skills/type-centric-rust-api in your project. Codex loads it when a task matches its description.

Can I use Type Centric Rust API in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 0xMiden/protocol --skill type-centric-rust-api -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/type-centric-rust-api, .gemini/skills/type-centric-rust-api, .github/skills/type-centric-rust-api and .opencode/skills/type-centric-rust-api in your project.

What does Type Centric Rust API need to run?

SKILL.md names no scripts, command-line tools or credentials: Type Centric Rust API is instructions for the agent only.

Does Type Centric Rust API access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Type Centric Rust API safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Type Centric Rust API use?

Type Centric Rust API is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Type Centric Rust API use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Type Centric Rust API?

Skills that share tags, products or a category with Type Centric Rust API: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Rust Best Practices (farm-fe/farm, 5.6k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars) and RTK Rust Design Patterns (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Type Centric Rust API?

0xMiden (a GitHub organization) maintains it in 0xMiden/protocol, which has 133 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.

Source: 0xMiden/protocol on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.