principle-boundary-discipline
From the author
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.
Install
npx skills add backnotprop/pstack --skill principle-boundary-discipline -a claude-code
Installs to .claude/skills/principle-boundary-discipline/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 90
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- principle-type-system-disciplinebacknotprop/pstackApply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, exhaust variants, derive from authoritative schemas.Writing★ 3K
- ml-decision-boundary-assessmentzero-lab-ai/skillsEvaluates classifiers and scoring models used as security gates for adversarial robustness, preprocessing differences, thresholds, abstention, and fallback behavior. Use when an authorized assessment must measure whether bounded input changes alter a security decision.Security★ 283
- code-standardstamdogood/builder-essential-skillsApply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).Engineering★ 225
- fork-disciplinejezweb/claude-skillsAudit and enforce the core/client boundary in multi-client projects. Detects where shared platform code is tangled with client-specific code, finds hardcoded client checks, config files that replace instead of merge, scattered client code, migration conflicts, and missing extension points. Produces a boundary map, violation report, and refactoring plan. Optionally generates FORK.md documentation and restructuring scripts. Triggers: 'fork discipline', 'check the boundary', 'is this core or client', 'platform audit', 'client separation', 'fork test', 'refactor for multi-client', 'clean up the fork'.Testing★ 1.1K
- infinitysickn33/agentic-awesome-skillsEnforces a strict input boundary protocol (detect, classify, filter, verify) to ensure untrusted data never reaches business logic raw.Other★ 48.7K
- source-command-plan-network-boundarieslegioncodeinc/vibe-coding-toolsChoose network firewall, WAF and application rate-limit layers from actual trust boundaries, protocols and operating constraints.Planning★ 94
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in