bakaphp

Add `@search` to a GraphQL list query — pick `DatabaseSearchableTrait` vs `DynamicSearchableTrait`, implement `searchableAs()`/`toSearchableArray()`/`shouldBeSearchable()`, and (critical) override `search()` to scope by `apps_id` + `companies_id` so search doesn't leak across tenants. Load when adding `search: String @search` to a query, adding a searchable trait to a model, or auditing/fixing multi-tenant search scoping.

Build a new external-service integration under `src/Domains/Connectors/{ConnectorName}/` — Handler + Client + DTO + Enums + Webhook job + Workflow activity + GraphQL setup mutation + `integrations` row. Load when adding/editing a connector (Shopify, Stripe, WaSender, Microsoft, OpenClaw, Hermes, etc.) or its associated `app/GraphQL/Connector/` / `graphql/schemas/Connector/` files. **NOTE**: `AgentRuntime` is a primary domain at `src/Domains/Intelligence/AgentRuntime/`, NOT a connector — see the "AgentRuntime is a primary domain" section before touching it.

Canonical pattern for building a new domain CRUD in Kanvas (DTO + Create/Update Actions + GraphQL Mutation + schema + tests). Load when scaffolding a new entity under `src/Domains/{Domain}/{Entity}/` or its GraphQL surface in `app/GraphQL/{Domain}/Mutations/{Entity}/` and `graphql/schemas/{Domain}/`. Skip for connectors (use kanvas-connector) or when only editing existing CRUD code.

Use when interacting with the Kanvas CRM to manage leads, pipelines, send template emails, create follow-ups, upload files, and log sales activity.

How an agent finds work assigned to it, plans the work as a checklist, executes it task by task, asks humans for approval when required, and leaves comments to communicate. Use this skill any time the agent is asked to "do" something for a user or company — the work belongs in a Plan, the steps belong in Tasks, and the conversation belongs in the Activities channel. Triggers on phrases like "find my work", "what do I have to do", "I need to plan this", "can you do X", "block until human approves", "leave a note for the user", "I'm stuck and need help".

Expert guidance for working with the @kanvas/core TypeScript SDK — the official client for the Kanvas Niche ecosystem. Use this skill whenever the user mentions @kanvas/core, KanvasCore, Kanvas SDK, or asks about integrating with a Kanvas backend. Triggers for any task involving Kanvas client setup, authentication, file uploads, commerce (cart/orders), locations, settings, or building custom Kanvas modules. Also triggers when migrating from the legacy KanvasCore class to the new modular API, or when debugging GraphQL/network errors from a Kanvas-backed app. Apply this skill even if the user just says "kanvas" in a development context — they almost certainly need SDK help.

Use this skill whenever the user needs to write, debug, or understand GraphQL queries or mutations for the Kanvas API ecosystem. Trigger when the user asks about Kanvas entities, mutations, queries, types, enums, or inputs — even if they don't explicitly say "GraphQL". Also trigger for questions like "how do I create a X in Kanvas", "what fields does Y have", "which input do I use for Z", or any task that requires reading the Kanvas API schema before writing code. Always use this skill before writing any Kanvas GraphQL — never guess types, arguments, or enum values from memory.

Safe GraphQL runtime interaction skill for Kanvas Ecosystem API and Sales Assist environments.