# forge-app-builder

Adopt this skill: https://proskills.md/skills/other/atlassian-forge-skills-skills-forge-app-builder

Page: https://proskills.md/skills/other/atlassian-forge-skills-skills-forge-app-builder
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: skills/forge-app-builder/SKILL.md
size: 8000
upstream: https://github.com/atlassian/forge-skills/blob/main/skills/forge-app-builder/SKILL.md

```text
---
name: forge-app-builder
description: Plan, build, scaffold, or safely extend Atlassian Forge apps using current official documentation. Use for fresh Forge apps, existing-app feature work, module and manifest changes, UI Kit or Custom UI implementation, backend functions and events, Atlassian or external APIs, storage, permissions, environment configuration, distribution-affecting implementation, validation, and explicitly authorized deployment or installation; route standalone debugging and specialist reviews to their dedicated skills.
license: Apache-2.0
metadata:
  labels: "confluence,jira,bitbucket,atlassian,forge"
  maintainer: amoore
  namespace: cloud
---

# 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:

| Intent                                                              | Route                                                                          |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Architecture, feasibility, or implementation plan only              | Read [references/plan-only.md](references/plan-only.md); stop before mutations |
| Create a deployable app                                             | Read [references/create-new-app.md](references/create-new-app.md)              |
| Add or change behavior in an existing app                           | Read [references/extend-existing-app.md](references/extend-existing-app.md)    |
| Known error, failed command, blank UI, logs, or unexpected behavior | Route to `forge-debugger`                                                      |
| Broad pre-deploy or release-readiness review                        | Route to `forge-app-review`                                                    |
| Deep security review or static analysis                             | Route to `forge-security-review`                                               |
| Cost or platform-consumption optimization                           | Route to `forge-cost-optimizer`                                                |
| Teamwork Graph connector                                            | Route to `forge-connector`                                                     |

Continue here when diagnosis or review is incidental to active build work. If the route is unclear, inspect the workspace before asking the user.

## Ground the selected route

Read [references/documentation-routing.md](references/documentation-routing.md) when current platform detail is needed. Use Forge MCP as the first preference whenever it is available. Discover its current capabilities by purpose rather than assuming permanent tool names, and call the narrowest relevant capability before relying on web documentation or remembered platform knowledge. Use focused official Atlassian documentation when MCP is unavailable, fails, or lacks the exact coverage needed, and for critical verification.

Call the general Forge development guide when broad orientation is useful. Do not call it merely to satisfy a ritual when the task needs only one known leaf reference. Retrieve the exact module, manifest property, endpoint, scope, or CLI page before relying on it.

## Activate capability gates conditionally

Load only the references implicated by the requested outcome and observed code:

| Trigger                                                                                                                  | Read                                                                                         |
| ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------- |
| Select or add an extension point or module                                                                               | [references/module-selection.md](references/module-selection.md)                             |
| Implement or change UI Kit                                                                                               | [references/ui-kit.md](references/ui-kit.md)                                                 |
| Implement or change Custom UI or `Frame`                                                                                 | [references/custom-ui.md](references/custom-ui.md)                                           |
| Add resolvers, functions, events, schedules, queues, web triggers, app REST APIs, realtime, or runtime services          | [references/backend-and-events.md](references/backend-and-events.md)                         |
| Call or expose Atlassian, Forge app, or external APIs; use providers or remotes; change scopes, authorization, or egress | [references/apis-permissions-and-egress.md](references/apis-permissions-and-egress.md)       |
| Persist data or affect tenancy, lifecycle, migration, or residency                                                       | [references/storage-and-residency.md](references/storage-and-residency.md)                   |
| Configure environments, runtime variables, secrets, or manifest interpolation                                            | [references/environments-and-configuration.md](references/environments-and-configuration.md) |
| Change cross-product compatibility, unlicensed access, licensing, sharing, or distribution behavior                      | [references/distribution-and-access.md](references/distribution-and-access.md)               |
| Validate, deploy, install, upgrade, or hand off                                                                          | [references/validation-and-release.md](references/validation-and-release.md)                 |

Do not load UI guidance for a headless app, storage guidance for a stateless feature, Custom UI guidance for a UI Kit-only change, or release guidance until validation or an authorized release becomes relevant.

## Implement and validate iteratively

Before non-trivial edits, establish the requested outcome, affected Forge surfaces, consequential design choices, and a proportionate validation approach. Resolve decisions that affect authorization, data handling, compatibility, lifecycle status, cost, or live state before implementation.

Work in coherent increments. After each meaningful change, use the most relevant available evidence to assess it, such as focused tests, type checks, frontend builds, handler or resource inspection, or `forge lint`. Choose the increment size and validation frequency according to risk, feedback cost, and the existing codebase; combine related
```

## File: README.md
upstream: https://github.com/atlassian/forge-skills/blob/main/README.md

````text
# Forge App Builder Skill

Guides creation, deployment, and installation of Atlassian Forge apps (Jira widgets, Confluence macros, issue panels, dashboard gadgets, etc.). Use when building any Forge app. Provides automated `forge create` workflow, module selection, CLI commands, and deployment scripts.

## Installation

This skill ships inside the **[Forge Skills](https://github.com/atlassian/forge-skills)** plugin bundle (`skills/forge-app-builder/`). Prefer installing that repo as a plugin in your editor or CLI so you get the skill plus Forge and ADS MCP configuration. See the [forge-skills README](https://github.com/atlassian/forge-skills/blob/main/README.md) for Cursor, Claude Code, Gemini, Codex, and Copilot CLI.

### Using only this skill folder (advanced)

If your host can load a skill from an arbitrary path, point it at `skills/forge-app-builder` inside a checkout of [forge-skills](https://github.com/atlassian/forge-skills). For example, clone the repo and symlink into a global skills directory:

```bash
git clone https://github.com/atlassian/forge-skills.git ~/dev/forge-skills
ln -s ~/dev/forge-skills/skills/forge-app-builder ~/.cursor/skills/forge-app-builder
```

Adjust the target path for your tool (`.claude/skills/`, `.agents/skills/`, etc.). You will not get `.mcp.json` from the symlink alone; install the full plugin or add MCP servers yourself if you want them.

---

## What This Skill Provides

- **Automated workflow** — Discovers dev spaces, creates apps with `forge create`, deploys and installs
- **Module selection** — Guidance for Jira panels, Confluence macros, dashboard gadgets, Rovo agents, and more
- **Helper scripts** — Python scripts for dev spaces, templates, and deployment
- **Reference docs** — CLI workflow, module selector, project setup

See [SKILL.md](SKILL.md) for the full skill content.
````
