AGENT SKILL

principle-boundary-discipline

Boundary discipline. Apply when reviewing or writing validation, error handling or framework adapters.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 2
Forks
0

01 前言 Front Matter

name
principle-boundary-discipline
license
MIT
metadata
{ "source": "pstack principle-boundary-discipline, MIT, Copyright (c) 2026 Lauren Tan, github.com/cursor/plugins, adapted; checked against pstack 0.15.36 at commit 0bb6f37" }
description
Boundary discipline. Apply when reviewing or writing validation, error handling or framework adapters.

03 SKILL.md 正文

<!-- Generated by scripts/build.mjs from the sources; edit the source, then run npm run build. -->

Boundary discipline

Put validation, type narrowing and error handling at the system's boundaries. Trust internal code. Keep business logic in pure functions; keep the shell thin and mechanical.

Why. Scattered validation is noisy, redundant, and gives a false sense of safety. Logic kept out of framework wiring can be tested without the framework.

What to do.

  • At a boundary (command-line arguments, configuration files, external APIs, network input, files): validate, return errors, handle defensively.
  • Inside: typed data, errors propagated, no re-validation. Trust the types.
  • Across the boundary: expose domain concepts, not the boundary's private representation. Keep general mechanism inside and special-purpose policy at the edge.

In practice. Parse raw data into domain types at the boundary. Do not re-export transport, storage or framework types through the public surface. No redundant nil checks deep in call chains when the boundary already validated. Prompt construction, parsing and scoring are pure transforms.

Two tests. "Is this data crossing a boundary right now?" If not, validation is redundant. "Can this be a pure function the shell calls?" If yes, extract it.

As a reviewer, report input that reaches logic unvalidated.

04 同仓库更多 Skills

erickb336
erickb336/sage-stack

writing-standard

Write at 80% of Simplified Technical English. Apply to any text an agent writes for a person: messages, reports, specs, findings, reviews, plans.

★ 2
erickb336
erickb336/sage-stack

sage

The state tool of sage mode: records tasks, routes, agent runs, findings, verdicts by head SHA and the user's gates in ~/.claude/sage/<project>/. Use in sage mode for every change of a task's state, and before any merge. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

sage-help

Help with sage: how to set it up, switch sage mode and autopilot, read the board, answer the chief's questions, pick a skill or a principle, fix a run that went wrong, and find where sage keeps its files. The user types /sage:sage-help (or /sage-help) with a question. Load it only when the user types it; do not load it on your own. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

report

The report that every sage agent ends with: STATUS, RESULT, EVIDENCE, FINDINGS, QUESTIONS, NOT VERIFIED, BRANCH. Use at the end of any task that the sage chief of staff gave you. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

remote-control

Set up Remote Control, so that the user can follow, steer and start Claude Code sessions from the Claude app on a phone. It turns Remote Control on for every new session, and it can run a server in a folder (such as ~/workspace) that starts at each login. Use when the user asks to reach sessions or start new ones from a phone, or to set up, check or undo Remote Control. Claude Code only.

★ 2
erickb336
erickb336/sage-stack

readme-guide

Write a project README. Apply when you write, change or review a README of any project, in any language.

★ 2