base44-platform-entities — Claude Code skill: features and install
The base44-platform-entities Claude Code skill covers Base44 entities, data queries, and user access rules. It activates when stored data or per-user permissions change in a Base44 app.
MIT 3,100 installs ★ 94 updated 2026-10-22
npx skills add base44/skills --skill base44-platform-entities -a claude-codeWhat base44-platform-entities does
The skill guides changes to Base44 data models written as JSON schemas, use of the entity SDK, and configuration of row-level security (RLS). Model files live in base44/entities/. Base44 applies each entity’s RLS rules to every app-user request.
It first identifies the app profile with GET /api/apps/{app_id}/agent-profile, then selects reference material for a web or Expo mobile app. The profile request uses the execute_api tool in Base44 MCP or a Base44 CLI token. If the profile cannot be fetched, project files can identify the app type: app/_layout.* signals Expo, while src/routes/__root.* and src/routeTree.gen.ts indicate TanStack Start.
What it helps with
- define a data model as a JSON schema
- change entity queries through the SDK
- set per-user access rules for stored rows
- select references for a web or Expo app
Example prompts for the agent
- Add an order entity under
base44/entities/and configure its RLS rules. - Change the entity queries in this Base44 app.
- Identify the app profile and choose the right references for Expo.
How to install base44-platform-entities
1Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-entities -a claude-code2Manually: put the files in place
~/.claude/skills/base44-platform-entities/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/base44-platform-entities/
1Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-entities -a codex2Manually: put the files in place
.agents/skills/base44-platform-entities/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-entities -a cursor2Manually: put the files in place
.cursor/skills/base44-platform-entities/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install base44/skills skills/base44-platform-entities2Manually: put the files in place
.github/skills/base44-platform-entities/SKILL.md1Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-entities -a gemini-cli2Platform CLI
gemini skills install https://github.com/base44/skills --path skills/base44-platform-entitiesManually: put the files in place
.devin/skills/base44-platform-entities/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add base44/skills --skill base44-platform-entities -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about base44-platform-entities
How do I install base44-platform-entities in Claude Code?
Run npx skills add base44/skills --skill base44-platform-entities -a claude-code. The skill file is at ~/.claude/skills/base44-platform-entities/SKILL.md.
What does base44-platform-entities do?
It guides work on Base44 entity schemas, the entity SDK, and RLS rules. It also selects reference files based on the app profile.
What does base44-platform-entities need to work?
Fetching the app profile requires Base44 MCP with its execute_api tool or a Base44 CLI token. If the profile is unavailable, the skill identifies the app type from project files.
Source text
SKILL.md · MIT
---
name: base44-platform-entities
description: "Base44 entities: the JSON-schema data models under base44/entities/, the entity SDK, and row-level security (RLS) rules. Use when adding or changing stored data, queries, or per-user access rules in a Base44 app."
---
<!-- GENERATED FILE. DO NOT EDIT. Compiled from the Base44 builder's prompt sources; the
source commit is in /SOURCE_COMMIT at the repository root. Edits here are overwritten by
the next sync; change the source instead. -->
# Base44 entities
Entities are JSON-schema objects stored as `base44/entities/<Name>.jsonc`; writing the file is what defines the data model. The platform applies each entity's `rls` rules on every app-user request.
## Pick the reference for this app
Determine the app profile first. Call `GET /api/apps/{app_id}/agent-profile` (over the Base44 MCP `execute_api`
tool, or with your Base44 CLI token); it returns the framework, app type, runtime,
entitlements and the exact reference files to read. Without it, detect from the project files:
`src/routes/__root.*` and `src/routeTree.gen.ts` mean TanStack Start; `app/_layout.*` means a
native mobile (Expo) app; otherwise it is a Vite SPA.
## For every app
- [Row-level security (RLS)](references/rls.md)
| Profile | Read |
|---|---|
| Web app, Vite SPA (the default web template) | [Entities and the entity SDK (web apps)](references/web.md) |
| Web app, TanStack Start | [Entities and the entity SDK (web apps)](references/web.md) |
| Native mobile app (Expo, React Native) | [Entities and the entity SDK (mobile apps)](references/mobile.md) |
© base44 · MIT · base44/skills