AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Boundary Review

skill-jukrap-ai-agent-playbook-boundary-review · by jukrap

Use when reviewing architecture boundaries, FSD layers, DDD modules, monorepo package ownership, dependency direction, or cross-module coupling.

↗ Website ↗ Repository
— No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-jukrap-ai-agent-playbook-boundary-review

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Boundary Review? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Boundary Review

Use this as the primary architecture skill for module and layer boundaries.

Workflow

  1. Identify the intended architecture boundary from code, docs, package layout, and imports.
  2. Check dependency direction, public APIs, shared utilities, feature ownership, and data flow.
  3. Prefer local conventions over forcing a new architecture.
  4. Recommend small boundary repairs before broad restructuring unless the user asks for redesign.

Reference

Read references/boundary-redesign-protocol.md when deciding whether to keep local conventions, apply FSD/DDD/layered rules, split packages, or propose a broader restructure.

Read references/fsd-ddd-fit-matrix.md when deciding between feature-sliced, layered, domain-driven, modular monolith, or legacy seam approaches.

Read references/modular-boundary-migration.md when a boundary repair needs staged moves, adapters, compatibility shims, or import/dependency checks.

Read references/deep-module-design-review.md when evaluating whether a module should become deeper, when comparing alternative interfaces, or when a shallow extraction may only move complexity around.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills