BuilderBot Code Skill

Operate

1. Identify the stack — confirm provider package, database adapter, and flow entrypoints before writing code.
2. Type the callback signature correctly:
   • ctx: BotContext → { body, from, name, host, ...platform fields }
   • methods: BotMethods → { flowDynamic, gotoFlow, endFlow, fallBack, state, globalState, blacklist, provider, database, extensions }
3. Enforce flow-control semantics — these three MUST be returned:
   • return gotoFlow(flow) · return endFlow('msg') · return fallBack('msg')
   • These MUST be awaited: await flowDynamic(...) · await state.update(...) · await globalState.update(...)
4. Prefer small, composable flows — one responsibility per flow file.
5. Keep secrets in env vars — never hardcode tokens, keys, or credentials.
6. After writing any flow, run through the UX Review Checklist below — simulate the conversation as the end-user and verify every item before considering the flow done.
7. Always validate lint before finishing — run eslint . --no-ignore and fix every error before delivering code.

Critical Rules (common bugs)