Feature slice boundary
Skill jukrap/ai-agent-playbook/skills/architecture/feature-slice-boundary
Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.
npx -y skills add jukrap/ai-agent-playbook --skill feature-slice-boundaryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when changing or reviewing FSD, feature-sliced, vertical-slice, feature-first, route-level, module-level, or component-domain boundaries.
SKILL.md
1.0 KB, as published. Nobody here has run it
Feature Slice Boundary
Use this as the primary architecture skill for feature, slice, route, and module boundaries.
Workflow
- Identify the project architecture from code and docs before applying FSD, vertical slice, feature-first, or layered labels.
- Check allowed imports, public API files, shared/common usage, state ownership, UI/API boundaries, and test placement.
- Preserve local conventions unless the requested change explicitly includes migration or redesign.
- Record coupling risks, moved ownership, compatibility shims, and verification commands.
Reference
Read references/feature-slice-layering.md for feature, layer, slice, and dependency direction checks.
Read references/slice-public-api-checks.md for public API files, shared modules, and migration safety.