// Add a new endpoint or endpoints to Ghost's Admin API at `ghost/api/admin/**`.
| name | Add Admin API Endpoint |
| description | Add a new endpoint or endpoints to Ghost's Admin API at `ghost/api/admin/**`. |
ghost/core/core/server/api/endpoints/. Otherwise, locate the existing endpoint file in the same directory.docName and a single endpoint definition, i.e. browse.ghost/core/core/server/web/api/endpoints/admin/routes.js.e2e-api tests for the endpoint in ghost/core/test/e2e-api/admin to ensure the new endpoints function as expected.cd ghost/core && pnpm test:single test/e2e-api/admin/{test-file-name}.For a detailed reference on Ghost's API framework and how to create API controllers, see reference.md.
Use when adding a new private (developer experiments) feature flag to Ghost, including the backend registration and settings UI toggle.
Create a database migration to add a table, add columns to an existing table, add a setting, or otherwise change the schema of Ghost's MySQL database. Use this skill whenever the task involves modifying Ghost's database schema — including adding, removing, or renaming columns or tables, adding new settings, creating indexes, updating data, or any change that requires a migration file in ghost/core. Also use when the user references schema.js, knex-migrator, the migrations directory, or asks to "add a field" or "add a column" to any Ghost model/table. Even if the user frames it as a feature or Linear issue, if the implementation requires a schema change, this skill applies.
Commit message formatting and guidelines
