Module boundaries is handled by this skill in a buyer-readable, reusable workflow.
Tradeoffs recorded is handled by this skill in a buyer-readable, reusable workflow.
SB_architecture_governor@SB_architecture_governorAgent SetupLevel 2 Guided Skill15 minutes
What is this?
A paid architecture skill that turns accepted product needs into safer module boundaries, tradeoffs, and technical decisions before coding hardens the wrong shape. Decide the system shape, responsibilities, integrations, scale assumptions, and handoffs before implementation spreads. Use it when you need help with Use it when your product is no longer a simple page and now has workflows, data, APIs, payments, admin areas, reports, or multiple user roles and Use it when the app still works, but you are worried that every new feature is being attached to the wrong place. Without it, teams usually keep suffering through Clearer system shape and Fewer late rebuilds. The buyer can use it to produce Architecture decision notes and Module boundaries with a clearer next step and less prompt guesswork. It is especially useful for Best when a product idea is real enough to build, but the team needs to avoid locking fragile architecture into the repo and Buyers who want reusable AI-agent guidance instead of one-off prompts.
When this helps
What you get
- Architecture decision notes
- Module boundaries
- Tradeoff record
- Governor handoffs
Use it when
- Use it when your product is no longer a simple page and now has workflows, data, APIs, payments, admin areas, reports, or multiple user roles.
- Use it when the app still works, but you are worried that every new feature is being attached to the wrong place.
- Use it when you need clear system boundaries before AI keeps building on top of a fragile structure.
Not the right fit when
- It is not necessary for tiny throwaway pages. It is valuable when the app has workflows, data, integrations, or future growth risk.
What this prepares next
Clearer system shape -> Fewer late rebuilds -> Better implementation discipline
Why this is stronger than asking AI once: A normal prompt can produce a useful answer once. This skill gives the buyer a repeatable workflow with checks, boundaries, and handoff evidence.
Who this is for
- Best when a product idea is real enough to build, but the team needs to avoid locking fragile architecture into the repo.
- Buyers who want reusable AI-agent guidance instead of one-off prompts.
What this helps you improve
- Clearer system shape
- Fewer late rebuilds
- Better implementation discipline
Included interface patterns
Scale-Aware Architecture Intake
Questions product stage, users, document/transaction volume, devices, connectivity, security, and deployment before decisions.
Scale and risk profile with facts, assumptions, and unknowns.Architecture Decision Package
Maps components, data, integrations, deployment, offline behavior, and tradeoffs to requirements and constraints.
Decision table, rejected alternatives, risks, and accept/clarify/reject status.Linked Skill Handoffs
Prepares file registration, standalone packaging configuration, and security assessment scope.
@SB_file_governor, @SB_standalone_webapp_packager, and @SB_security_assessment handoff blocks. Workflow fit
Where this skill fits in the workflow.
This product belongs to the Architecture and data stage in the Vibe app builder roadmap. Use the roadmap to decide what to clarify first, which check should come next, and whether a connected workflow fits your current AI project problem better than a single skill.
Connected offer
Clarify My App Idea Bundle
Turn a vague app idea into clear scope, acceptance criteria, and architecture direction before build starts.
If two bundles include the same skill, the cart keeps it once and removes the duplicate from the estimate.