---
name: create-app
description: Use when the user wants to create or scaffold a new Twenty app
title: create-app
canonical_url: https://skilld.dev/gh/twentyhq/twenty/create-app
last_updated: 2026-10-30T18:01:32.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [agents/openai.yaml](https://skilld.dev/api/skills-raw/twentyhq/twenty/create-app/agents/openai.yaml).
>
> If the user asked to install this Skill, run `npx skilld install twentyhq/twenty/create-app`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/create-app`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/twentyhq/twenty/create-app) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/create-app`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/create-app --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/create-app --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# When To Use

Use for requests such as "create a Twenty app" or "scaffold a new app".

# Create an app

Use this skill for a new app. For an existing app, use `develop-app` or `manage-app`.

Read `../../references/concepts/how-apps-work.md` and `../../references/concepts/operating-rules.md` first.

Confirm the app's name and purpose. Use the standalone CLI:

```bash
npm install -g twenty
twenty app init <app-name>
cd <app-name>
yarn install
```

`app init` only writes files. It does not install dependencies, initialize Git, start Docker, authenticate, or perform an initial sync.

Use `--path <directory>` for a different destination and `--display-name` or `--description` for metadata. The positional name is the package name.

Twenty Cloud and self-hosted instances are supported. Ask for the existing Twenty workspace URL when connection is needed. If the user wants a local environment, run `twenty local start`, then authenticate separately with `twenty auth login`. A repository development environment also works.

```bash
twenty auth login --url <twenty-instance-url> --name dev
twenty app apply --create --remote dev
```

Only claim the app is installed after apply succeeds. If the request is just scaffolding, stop after the files and dependencies are created. Do not run broad validation unless requested. For integration tests, use the isolated test instance described in `../../references/develop-app/tests.md`.

The template includes a main page, its layout and navigation item, and a health-check function. Remove the placeholder page with its layout and navigation if the app needs no UI. Extend the existing health check rather than declaring a second one.

After creation, use `develop-app` for entities and UI, `manage-app` for bounded sync with `twenty app apply`, and `publish-app` for release work.
