develop-app

Adds and modifies objects, fields, logic functions, and front components in Twenty apps.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/masoodtalha/twenty --skill develop-app-masoodtalha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: develop-app
Source: https://github.com/masoodtalha/twenty/tree/main/packages/twenty-codex-plugin/skills/develop-app
Command: npx skills add https://github.com/masoodtalha/twenty --skill develop-app-masoodtalha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers extending an existing Twenty CRM app need to correctly create and modify entities like objects, fields, views, logic functions, and front components while following the SDK's file structure, naming conventions, and sync lifecycle. ## Core Features & Use Cases - Entity Creation via CLI: Uses yarn twenty dev:add to scaffold objects, fields, views, logic functions, and front components with correct UUIDs and boilerplate. - Code Organization Rules: Enforces kebab-case filenames, one export per file, and dedicated folders for utils, types, and service clients. - Verification Workflow: Runs typecheck, lint, and yarn twenty apply once after edits to sync entity definitions to the active remote. - Use Case: A developer asks to add a custom field to the company object and a logic function that runs on record create; the Skill plans the change, scaffolds the entities, and syncs the app. ## Quick Start Ask the assistant to add a new object or logic function to your existing Twenty app using the develop-app skill.

Frequently Asked Questions about develop-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new object or field to a Twenty app?▼

Run yarn twenty dev:add from the app root to scaffold objects, fields, views, logic functions, and front components. The CLI generates correct file structure, UUIDs, and SDK imports automatically, so manual file creation is only needed for unsupported entity types.

How do I sync Twenty app changes to a remote workspace?▼

After finishing all edits, run yarn twenty dev:typecheck, yarn lint, and yarn twenty apply once. The apply command syncs entity definitions to the active remote, while typecheck and lint validate generated app types and local rules.

When should I use develop-app instead of create-app?▼

Use develop-app only when an existing Twenty app root is present, verified by package.json and src/application-config.ts. If the app does not exist yet, scaffold it with create-app first; use manage-app for sync, deploy, or troubleshooting issues.

What file structure conventions does a Twenty app enforce?▼

Files use kebab-case names with one export per file. Helpers go in src/utils, shared types in src/types, external SDK wrappers in src/<service>-client folders, and every util needs a matching spec file in a sibling __tests__ folder.

Why should logic functions for front components be bulk-capable?▼

Front components often act on selected records, so the default payload shape is records: Array<{ id: string; ...fields }>. Bulk-capable functions handle multiple records in one call; single-record payloads are only kept when explicitly required for an existing API.