forge-app-builder
Forge App Builder
When building a Forge app, the agent MUST complete this workflow in order. Do not skip steps. Do not substitute manual instructions for running the scripts below.
Critical Rules
- Always use
forge createto scaffold apps — it registers the app and generates a valid app ID - Never manually scaffold — apps without valid app IDs cannot be deployed
- If
forge createfails, STOP — inform the user and provide the manual command - Never ask for API tokens in chat — direct users to run
forge loginin their terminal and enter credentials there - Always ask the user to choose when multiple options exist (developer spaces, sites) — never pick on their behalf
- Always ask the user for their Atlassian site URL during installation — never try to discover it from other apps, environment variables, or any other source
- Always run the deploy script for deploy and install — do not give the user only manual
forge deploy/forge installcommands as the primary outcome; runscripts.deploy_forge_app.pyyourself
MCP Server Prerequisites
This skill works best with the following MCP servers. The scripts and CLI workflow function without them, but the agent will lack access to up-to-date Forge documentation for template selection, module configuration, and code patterns.
More from atlassian/forge-skills
forge-debugger
Diagnoses and fixes issues in Atlassian Forge apps. Use this skill whenever a Forge app has errors, crashes, shows blank UI, fails to deploy, doesn't appear after installation, has permission issues, or produces unexpected output. Trigger on any mention of forge logs, forge deploy errors, resolver errors, blank panels, missing scopes, Custom UI not rendering, production vs dev discrepancies, or any Jira/Confluence app that "stopped working". Also trigger when the user asks to debug, troubleshoot, investigate, or fix a Forge app issue — even if they haven't used the word "Forge" but describe a Jira panel or Confluence macro acting up.
45forge-app-review
>
44forge-connector
>
3