When To Use

Pick this skill when the user wants to change what an existing Twenty app does, its data model, UI, logic, or workflows. Representative triggers:

• "add a new object to my Twenty app"
• "create a logic function that runs on record create"
• "add a custom field to the company object"
• "build a front component for the deal page"
• "modify an existing entity / object / field"
• "add a workflow with a manual trigger"
• "add roles and permissions to my app"
• "create a standalone page in my app"

Do not use this skill to scaffold a brand-new app (use create-app), to sync/deploy/troubleshoot (use manage-app), to prepare marketplace assets (use publish-app), or to query workspace records (use use-twenty-mcp).

Boundaries

For background on how Twenty apps work, the SDK packages, remotes, sync lifecycle, and rendering model, read ../../references/concepts/how-apps-work.md. Cross-skill operating rules that apply to every Twenty app task are in ../../references/concepts/operating-rules.md; they are authoritative and not restated per skill.

Do not scaffold a new app here. Use create-app first when the app does not exist.

Workflow

First, confirm the setup is sane before changing entities. The current directory should be the root of an existing Twenty app:

test -f package.json
test -f src/application-config.ts

If either file is missing, do not edit blindly. Inspect nearby folders to find the app root, or use create-app when the app does not exist.

If setup, dependencies, remotes, authentication, sync, build, deploy, logs, or CI/CD are failing, switch to manage-app before continuing with entity work.

For app shape and entity file structure, read ../../references/develop-app/app-structure.md.

Plan Before Editing