Forge App Builder

Route each request through only the branches and capability gates it needs. Keep platform facts live and keep local guidance focused on safe decisions.

Preserve these invariants

1. Retrieve current official Forge guidance before committing to platform syntax, modules, APIs, scopes, limits, runtimes, packages, lifecycle status, or CLI flags.
2. Register every new deployable app with forge create; never hand-build an app identity or replace a failed creation with an unregistered scaffold.
3. Inspect an existing app and its repository instructions before planning or editing it. Preserve unrelated user changes.
4. Never request or accept credentials in chat. Use the relevant interactive CLI or secure configuration flow.
5. Never accept Forge terms or billing consent, deploy, install, upgrade, promote, set a production variable, or change a live site without explicit authorization and a confirmed target.
6. Validate every manifest change against the exact current reference and with forge lint.
7. Use least privilege and avoid unnecessary egress, privileged backend operations, and migrations.
8. Prefix Forge CLI commands run for this skill with ATL_FORGE_ATTRIBUTION_SKILL_NAME=forge-app-builder; exclude user-run forge login and forge tunnel.

Route the primary intent

Choose one primary route before loading implementation guidance: