Menu
Use when adding a new API endpoint, route, or HTTP handler. ALWAYS use for new Fastify controller endpoints.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation inline (CONTEXT.md per bounded context, ADRs, feature docs). Also runs mandatory feature-overlap detection before any new feature and maintains the .agents/features/ registry. Use when stress-testing a plan, defining domain terms, hardening terminology, or proposing/adding a new feature.
Debug a failed Activepieces flow run end-to-end: given a flow run id (or BullMQ job id), find why it failed, cross-referencing the live BullMQ job + Postgres rows (SSH script on the DevOps box), the centralized ClickHouse logs (ClickStack MCP), and the code in this repo, then categorize the failed-job backlog on request.
Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.
Builds Activepieces pieces (integrations) with actions and triggers. Use when the user asks to create a new piece, add actions to a piece, add triggers to a piece, or build an integration for a third-party app. Also use when the user mentions Activepieces pieces, connectors, or integration development.
Use when the user asks to add a feature, implement functionality, or build something spanning database, API, and frontend. ALWAYS use for multi-layer feature work.
Analyze application logs from the .evlog/logs/ directory. Use when debugging errors, investigating slow requests, understanding request patterns, or answering questions about application behavior. Reads structured NDJSON wide events written by evlog's file system drain.
| name | add-endpoint |
| description | Use when adding a new API endpoint, route, or HTTP handler. ALWAYS use for new Fastify controller endpoints. |
Create endpoint for $ARGUMENTS.
Read the pattern: Open packages/server/api/src/app/tables/table/table.controller.ts as reference.
Create or update controller using FastifyPluginAsyncZod:
export const myController: FastifyPluginAsyncZod = async (fastify) => {
fastify.post('/', CreateRequest, async (request) => {
return myService(request.log).create({
projectId: request.projectId,
request: request.body,
})
})
}
Define route config AFTER the controller (not inline):
const CreateRequest = {
config: {
security: securityAccess.project(
[PrincipalType.USER, PrincipalType.ENGINE, PrincipalType.SERVICE],
Permission.WRITE_MY_FEATURE,
{ type: ProjectResourceType.BODY },
),
},
schema: {
tags: ['my-feature'],
body: CreateMyFeatureRequest, // Zod schema from @activepieces/shared
response: { [StatusCodes.CREATED]: MyFeature },
},
}
Security access (pick one):
securityAccess.project(principals, permission, { type: ProjectResourceType.X }) — project-scopedsecurityAccess.platformAdminOnly(principals) — admin onlysecurityAccess.publicPlatform(principals) — any platform membersecurityAccess.public() — no authCreate module and register in app.ts:
export const myModule: FastifyPluginAsyncZod = async (app) => {
app.addHook('preSerialization', entitiesMustBeOwnedByCurrentProject)
await app.register(myController, { prefix: '/v1/my-features' })
}
Add Permission if new: add to Permission enum in @activepieces/shared.
Verify: npm run lint-dev