Skip to main content
Give your coding agent this instruction:

​
Context

Inspect the repository, its package manager, agent client, and existing Polymorfa configuration. Use the documentation index to find the guide for the selected feature. A recommendation does not grant feature access. Read code and configuration before asking questions. Infer facts such as the language, hosting model, existing provider and webhook implementation from the project. Ask only about unresolved decisions that change the recommendation. Distinguish existing behavior, migration plans and starting defaults; explain conflicts instead of treating a default as your decision.

​
Task

  1. Install the skills from polymorfa/agent-kit through the client’s plugin or skill installer. Follow the repository’s installation instructions for the agent in use.
  2. Connect the public documentation MCP at https://docs.polymorfa.com/mcp. Reuse a valid existing connection instead of adding a duplicate. Verify it can search a Polymorfa guide.
  3. If the project needs the CLI, follow the CLI guide. The published development prerelease requires Node.js 22 or later. Check the installed version before changing it.
  4. If the task needs customer data, configure the hosted API MCP with a scoped Polymorfa credential supplied through the client’s secret mechanism. Documentation MCP, hosted API MCP, and CLI local MCP are separate connections.
  5. Inspect the selected project’s numbers, credentials and webhooks. Use its setup checklist to identify missing configuration and the feature guides to plan the next step.
Existing API credentials authorize hosted MCP. Do not invent an OAuth login or assume that installing a plugin grants access to a team or project.

​
Constraints

When building an interface, use visible filled or outlined buttons, readable labels, clear selection and keyboard focus, and usable touch targets. Reuse saved answers. Check the rendered task in light and dark themes on desktop and mobile. Preserve existing configuration and unrelated files. Merge only the entries needed for Polymorfa. Do not overwrite another MCP connection or enable automatic approval of all tools. Keep credentials out of source files, logs, URLs, chat, and copied prompts. Ask the user to complete sign-in or secret entry when the client requires it. Wait before continuing work that depends on that step. Follow the user’s authorized scope. Get approval before sending a message, creating or deleting remote resources, or incurring charges unless those effects were already authorized. Do not retry a write whose outcome is uncertain. Start in Development. Check number capabilities, feature access, and opt-in requirements before configuring calls, catalogs, message history, or production sending. Saving a template, campaign, Flow, or webhook does not prove successful delivery.

​
Verification

Confirm the CLI version if installed, discover the MCP tools, and perform one permitted read if a credential is available. Do not send a test message automatically. Report these results separately: local installation, documentation search, authenticated project access, saved configuration, and any live delivery explicitly tested. Name the blocked step when a credential, permission, enrollment, or configured integration is missing.

​
Plan your project integration

Choose Set up with your AI agent during Console onboarding. The Recommended option shows Works for with coding-agent icons. Ask your coding agent contains the prompt, Copy prompt button and the input for its JSON answer block. The input shows a JSON example until you paste your output. Paste the JSON output here appears above it; an import or save error replaces that helper without moving the field. Ask the agent to inspect your integration, explain its recommendations and ask about choices it cannot infer from code. When available, the agent uses request_user_input or AskUserQuestion to ask you. Decisions neither of you answers can stay undecided for you to complete in the Console later. Your own business includes serving your buyers or diners. A product for other businesses connects numbers those businesses own. Voice calls are separate from audio messages and text-to-speech. Existing provider code describes where you start; it does not determine which connection you want after migration. The prompt supplies the answer format, allowed values and their meanings. Ask the agent to return every required field and put its evidence and unresolved choices outside the JSON block. The first turn asks what you want to change and how it should work. The agent waits for your reply, then starts the agreed work. You can add one feature or move part of an integration; a full migration is optional. Connecting numbers, sending messages and paid actions need your authorization. The questions reuse answers you already gave. Your current platform and intended connection lead to relevant migration questions. Business outcomes determine which features enter the checklist. Workflow control, conversation storage and hosting lead to further questions only when they apply. Own-business users can choose the basics; anyone can skip straight to their project. Paste the answer block under Import agent answers. Complete answers can be saved with Finish. If the agent leaves decisions unanswered, Continue opens only the relevant remaining questions. You can also choose Finish to save what you have and leave those decisions explicitly unknown. The Console derives the checklist from confirmed answers. Importing answers does not grant feature access, change retention, move templates or run a session migration. The import accepts only listed choices; keep credentials and session snapshots out. For later changes, open Edit setup plan on your project’s checklist, then Ask your coding agent. Each manual question includes Ask your agent instead. Deferred questions become a follow-up prompt at the end, carrying the answers you already gave. The agent fills unresolved choices; an import that changes a confirmed answer is rejected. You can switch back to ordinary questions for anything it misses. See Project setup for completion requirements. The agent can include your existing library package or provider name and public website in its answers. These details are saved for later setup prompts. In manual setup, Another provider opens Specify which solution you are using instead, a textbox for your description. You do not need a package name or URL. If the agent can read the complete connected-number inventory, it reports the observed count and when it checked. If you have an existing setup but the agent cannot read its inventory, it asks for a range. Starting fresh leaves both count fields empty. Manual setup asks for a range only if you already have WhatsApp users. That question comes before the separate existing-solution step; a range is never converted into an exact count. Selecting 101–500 or 501+ connected numbers shows the Builders Program offer. Which solution are you already using? shows Enhanced support for your existing solution. Each offer includes its benefits and eligibility note. Dismiss the offer or swipe it away on mobile to continue setup. Select an answer to enable Continue. To leave the questions or agent import without saving a feature selection, use Skip in the bottom action bar.