craft-standard

Enforces code quality standards for ownership, typed boundaries, and root-cause fixes.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill craft-standard-harivansh-afk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: craft-standard
Source: https://github.com/harivansh-afk/loom-index-e2e/tree/main/skills/craft-standard
Command: npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill craft-standard-harivansh-afk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases degrade when changes ship with unclear ownership, silent fallbacks, copy-pasted orchestration, and fixes that patch symptoms instead of root causes. This Skill gives an AI agent a binding craft bar so every change lands with clear ownership, typed boundaries, checked defaults, and a durable test. ## Core Features & Use Cases - Design discipline: Enforces small named helpers, typed boundaries, DRY domain facts, and thin logic-free bindings (Python, Wasm, FFI) over Rust-owned domain logic. - No silent fallbacks: Requires missing owners, routes, configs, schemas, or transports to return typed, observable errors instead of guessed defaults or silent retries. - Root-cause fixing with tests: Mandates that every fix lands code plus the nearest durable test, and that causal claims are tested by breaking the cause and watching the effect disappear. - Use Case: When an agent is about to add a compatibility shim or a silent retry to make a failing change pass, this Skill redirects it to fix the invariant at the boundary that owns it and delete the obsoleted code in the same change. ## Quick Start Apply the craft standard to review this diff and reject any silent fallbacks or untested causal claims before it lands.

Frequently Asked Questions about craft-standard

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

FAQPage Schema
How do I enforce code quality standards on AI-generated patches?▼

Apply a craft standard that makes lint failures and repo rules binding, requires typed boundaries and clear ownership, and rejects silent fallbacks. Each change must land code plus the nearest durable test, so diagnosis alone counts as unfinished work.

What is a silent fallback in code and why avoid it?▼

A silent fallback is a guessed default, sentinel value, or silent retry used when an owner, route, config, schema, or transport is missing. The standard rejects these because they hide failures; instead the code must return a typed, observable error.

How should domain logic be split between Rust and Python bindings?▼

Own domain logic once in Rust and keep bindings in Python, Wasm, or FFI thin and logic-free. This prevents duplicated orchestration and ensures invariants live at the boundary that owns them.

How do I test a causal claim in a code review?▼

Test a causal claim by breaking the cause and watching the effect disappear, not by confirming the premises hold. Pin load-bearing claims with a test named for the property rather than the mechanism, so refactors cannot silently break it.

When is it acceptable to bypass a lint rule?▼

Bypass a lint rule only with local evidence, kept small, with the reason written next to the line. Lint failures and repo rules are otherwise binding on every change.