Builder Kit
Use this skill as a thin router. Do not load every reference.
Start
- Read profiles and resolve the communication and delivery profiles.
- Read task classification.
- Inspect repository instructions, neighboring code, tests, build files, documentation, branch, and uncommitted changes.
- Explain the classification and proposed lens set in language appropriate to the communication profile. Let the user override optional lenses and classification.
- Apply the authority order in authority and legacy guidance.
For a tiny fix, make the smallest coherent change when implementation is requested, then use verification. For planned work, read and follow the develop-from-spec instructions and stop at its approval gate.
Conditional routing
| Trigger |
Read or invoke |
| Select expert concerns |
lens routing, then only selected lens files |
| Data, APIs, search, lists, caches |
data boundaries |
| Auth, integrations, external services |
integration boundaries |
| Secrets, permissions, sensitive data |
security and privacy |
| Frontend styling or components |
frontend composition |
| Mutations, concurrency, migrations |
reliability and evolution |
| Java, frontend, Python, C++, Jenkins |
Only the matching file under ../../references/standards/ |
| Specialized platform or service work |
external capability routing, then invoke an available owning skill |
| Prototype project |
prototype delivery |
| New application |
start-new-app instructions |
| Challenge assumptions or readiness |
adversarial-review instructions |
| Standard code/design review |
standard review |
| Repeated review of current changes |
PR review loop instructions |
| Maintaining or releasing Builder Kit |
release and update policy |
Mandatory safety, security/privacy, accessibility, data-sustainability, authorization, and trust-boundary guidance applies when triggered even if the user declines optional lenses.
Boundaries
- Do not impose Builder Kit when it was not invoked.
- Do not replace local conventions with generic preferences.
- Do not use persona language as a substitute for objective, constraints, success criteria, and verification.
- Do not implement non-trivial work before explicit approval.
- Do not discard, overwrite, stage, or absorb unrelated user work.
1---2name: builder-kit-23description: Explicitly invoked development harness for safely planning, building, or changing software with an agent. Use only when the user invokes Builder Kit or asks to use the Builder Kit workflow. Classify tiny fixes versus planned work, load only relevant standards and expert lenses, protect unrelated changes, require approval for non-trivial implementation, and verify the result.4---56# Builder Kit78Use this skill as a thin router. Do not load every reference.910## Start11121. Read [profiles](../../references/workflow/profiles.md) and resolve the communication and delivery profiles.132. Read [task classification](../../references/workflow/task-classification.md).143. Inspect repository instructions, neighboring code, tests, build files, documentation, branch, and uncommitted changes.154. Explain the classification and proposed lens set in language appropriate to the communication profile. Let the user override optional lenses and classification.165. Apply the authority order in [authority and legacy guidance](../../references/workflow/authority-and-legacy.md).1718For a tiny fix, make the smallest coherent change when implementation is requested, then use [verification](../../references/workflow/verification.md). For planned work, read and follow [the develop-from-spec instructions](../develop-from-spec/SKILL.md) and stop at its approval gate.1920## Conditional routing2122| Trigger | Read or invoke |23| ------------------------------------- | --------------------------------------------------------------------------------------------------- |24| Select expert concerns | [lens routing](../../references/lenses/lens-routing.md), then only selected lens files |25| Data, APIs, search, lists, caches | [data boundaries](../../references/architecture/data-boundaries.md) |26| Auth, integrations, external services | [integration boundaries](../../references/architecture/integration-boundaries.md) |27| Secrets, permissions, sensitive data | [security and privacy](../../references/architecture/security-and-privacy.md) |28| Frontend styling or components | [frontend composition](../../references/architecture/frontend-composition.md) |29| Mutations, concurrency, migrations | [reliability and evolution](../../references/architecture/reliability-and-evolution.md) |30| Java, frontend, Python, C++, Jenkins | Only the matching file under `../../references/standards/` |31| Specialized platform or service work | [external capability routing](../../references/workflow/external-capabilities.md), then invoke an available owning skill |32| Prototype project | [prototype delivery](../../references/workflow/prototype-delivery.md) |33| New application | [start-new-app instructions](../start-new-app/SKILL.md) |34| Challenge assumptions or readiness | [adversarial-review instructions](../adversarial-review/SKILL.md) |35| Standard code/design review | [standard review](../../references/lenses/standard-review.md) |36| Repeated review of current changes | [PR review loop instructions](../pr-review-loop/SKILL.md) |37| Maintaining or releasing Builder Kit | [release and update policy](../../references/workflow/release-and-updates.md) |3839Mandatory safety, security/privacy, accessibility, data-sustainability, authorization, and trust-boundary guidance applies when triggered even if the user declines optional lenses.4041## Boundaries4243- Do not impose Builder Kit when it was not invoked.44- Do not replace local conventions with generic preferences.45- Do not use persona language as a substitute for objective, constraints, success criteria, and verification.46- Do not implement non-trivial work before explicit approval.47- Do not discard, overwrite, stage, or absorb unrelated user work.
gabonio