principle-boundary-discipline SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

principle-boundary-discipline from j-star-films-studios/vibecode-protocol-suite is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add j-star-films-studios/vibecode-protocol-suite/principle-boundary-discipline@git:20260821.1b830a3

Pins git:20260821.1b830a3 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

j-star-films-studios/vibecode-protocol-suite

Path

assets/.agent/skills/engineering-principles/boundary-discipline/SKILL.md

Versions recorded

1

Latest version

git:20260821.1b830a3, committed Aug 21, 2026

Size

1,919 bytes

Repository stars

26

License

ISC

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Boundary Discipline

Place validation, type narrowing, and error handling at system boundaries. Trust internal code unconditionally. Business logic lives in pure functions; the shell is thin and mechanical.

**Why:** Scattered validation is noisy, redundant, and gives a false sense of safety. Validate data once at the boundary. Keep logic out of framework wiring so it can be tested without the framework.

**The pattern:**
- **At boundaries** (CLI args, config files, external APIs, network protocols): validate, return errors, handle defensively.
- **Inside the system:** typed data, error propagation, no re-validation. Trust the types.
- **Across the boundary.** Expose domain concepts, not the boundary's private representation. Keep general-purpose mechanism inside and special-purpose policy at the edge.

**Applications:**

Validation and error handling:
- Validate config at parse time (the boundary), not inside business logic
- Parse raw data into domain types at the boundary
- Do not re-export transport, storage, framework, or wire types through the public surface
- No redundant nil checks deep in call chains if the boundary already validated

Code organization:
…

Read the whole file at its exact version.

How to install

mdr add j-star-films-studios/vibecode-protocol-suite/principle-boundary-discipline@sha256:ab3c690ce361542c

[![mdr](https://markdownregistry.com/badge/art_guxumnymhngferwo.svg)](https://markdownregistry.com/a/art_guxumnymhngferwo)

Versions

The registry has recorded 1 version of this file, committed on Aug 21, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_guxumnymhngferwo
GET https://markdownregistry.com/api/v1/resolve?ref=j-star-films-studios/vibecode-protocol-suite/principle-boundary-discipline
GET https://markdownregistry.com/api/v1/blob/ab3c690ce361542ca00446b8406f5afd47776f544b8ce06a9ef2eaa2338bde6d

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from j-star-films-studios/vibecode-protocol-suite

Every file in j-star-films-studios/vibecode-protocol-suite

Other files named principle-boundary-discipline

Browse by kind, by grade A, or by owner.