xmr-method

Modify xmris library methods while preserving domain contracts and exports.

5|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/andrewendlinger/xmris --skill xmr-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xmr-method
Source: https://github.com/andrewendlinger/xmris/tree/main/.claude/skills/xmr-method
Command: npx skills add https://github.com/andrewendlinger/xmris --skill xmr-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you add or modify xmris library methods correctly, keeping free functions, accessor methods, domain contracts, and exports in sync.

Core Features & Use Cases

  • Method Changes: Update existing .xmr methods safely when signatures, defaults, or mathematical behavior change.
  • New Method Wiring: Add transforms, vendor loaders, or fitting functions and connect them to the correct accessor location.
  • Contract Compliance: Apply the right decorator stack, preserve attributes, respect dimensional rules, and update the required test lists.
  • Documentation and Verification: Keep exports, notebooks, and architecture checks aligned so changes remain discoverable and testable.

Quick Start

Use this Skill to update an xmris method, wire it into the accessor, and tell me which tests, exports, and docs need to change.

Frequently Asked Questions about xmr-method

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Python API methods without breaking domain contracts?

To update Python API methods without breaking domain contracts, modify free functions and accessor delegators simultaneously while preserving attributes and verifying decorator stacks. This ensures signature changes, dimension defaults, and mathematical behavior stay aligned across module exports.

What's the best way to wire new transform functions into an accessor?

The best way to wire new transform functions into an accessor is connecting the free function to the correct accessor location while applying the appropriate decorator stack. You must preserve attributes, enforce dimension defaults, and explicitly update module exports and test lists.

Why do my fitting function updates fail tests after changing method signatures?

Fitting function updates fail tests after signature changes because free functions, accessor delegators, and test lists fall out of sync. Resolving this requires explicitly updating test lists, verifying decorator choices, and preserving attributes across the entire method chain.

Do I need to update module exports when adding vendor loaders?

Yes, you need to explicitly update module exports when adding vendor loaders to keep changes discoverable and testable. You must also update architecture checks, notebooks, and test lists to maintain alignment across free functions and accessor delegators.

How does accessor delegator alignment work for fitting functions?

Accessor delegator alignment for fitting functions works by keeping the delegator methods synchronized with their underlying free functions. This requires applying the correct decorator stack, preserving original attributes, respecting dimensional rules, and updating required test lists.

Can I change dimension defaults on existing transforms without breaking exports?

You can change dimension defaults on existing transforms without breaking exports by applying the correct decorator stack and preserving method attributes. You must simultaneously update accessor delegators, module exports, and architecture checks to maintain domain contract compliance.