WEBFLOW AI STARTER PACK — START HERE
Kvalifik workshop companion · Updated 21 October 2026

CONNECT WEBFLOW TO YOUR AI CLIENT
These prompts need an AI client connected to your Webflow project. You can use the regular Webflow connector or MCP Router, the app we demonstrated in the workshop.

MCP Router lets you connect multiple Webflow workspaces and manage which projects and actions are available through the connection—for example, allowing edits while disabling publishing. It is optional; the prompts support both connection paths.

Read about MCP Router and follow the setup guide:
https://github.com/Kvalifik/mcp-router#readme

Download the app from GitHub Releases:
https://github.com/Kvalifik/mcp-router/releases

Once your project is connected, start with the foundation audit below.

START WITH ONE PROMPT
1. Open your agent-capable AI client with Webflow connected. Have the intended project’s name or URL ready.
2. Open 01-audit-your-webflow-foundations.txt. Paste only the text between BEGIN PROMPT and END PROMPT into the chat. Add your project name/URL, or let the agent ask.
3. Answer its focused questions. It should inspect the site first, then ask about intent, approved examples, team workflow, and decisions the website cannot reveal. “I don’t know—recommend an approach” is a useful answer.
4. Review the recommended pilot and paste the matching improvement prompt into the same chat. In a new chat, provide the audit and confirmed decisions too.
5. Authorize a clear scope. Improve one example, verify it, then expand within the agreed rollout. Publishing remains separate.
6. At the end of each audit or improvement, review the proposed Webflow instruction updates and authorize saving them if not already covered by your scope. Use Prompt 6 to consolidate the growing setup and test a small task in a fresh chat.

CHOOSE YOUR NEXT PROMPT
01 — Audit your Webflow foundations: get the overview and recommended starting point.
02 — Organize and apply variables: review which styles will survive, then improve variable organization and bind those styles.
03 — Standardize and clean up styles: complete naming, consolidation, and verified orphan cleanup using the agreed variable system.
04 — Improve components and slots: build a documented catalog of everything the AI should be able to assemble on the established styles and variables.
05 — Clarify and improve your CMS: improve editorial clarity and separate simple fixes from migrations.
06 — Build and test project rules and skills: interview the team, reconcile guidance, bind real resources, and test workflows.

Default order: audit and style triage → variables → style cleanup → components → CMS → instruction consolidation. First classify styles to keep, merge, retire, or investigate; avoid rebinding classes already verified for retirement. Complete any essential scoped consolidation before variable migration when it prevents duplicate work. You do not need to run every prompt; adjust for actual dependencies. For example, settle a CMS model before building components that depend on it. A well-structured site may go straight to Prompt 6. Existing instructions must be loaded from the beginning in every case.

USEFUL REPLIES
“Implement the proposed pilot on [scope]. Verify it and show me the result before expanding.”
“If the pilot’s stated checks pass, continue through [specific scope] in verified batches. Stop for regressions or a material change of approach.”
“Keep appearance and behavior unchanged.”
“Pause after the current batch and save a checkpoint.”

COMPONENT PRINCIPLE
Everything the AI should independently select, assemble, or reuse belongs in the component catalog—even if it currently appears only once. Keep minor variations in properties, variants, and slots rather than creating near-identical components.

WHAT TO EXPECT
Specific findings, targeted questions, a concrete pilot, visual/functional checks, and a record of completed and remaining work. Creating components or variables is not the same as migrating their consumers. Drafted instructions are not necessarily installed, enabled, or tested.

ACCESS AND FILES
Automatic approvals do not replace permission scoping or verification. Router restrictions apply to routed calls, not automatically to browser actions. Some writes affect live content without publishing.

Each numbered file is standalone. all-six-prompts.txt contains the same prompts together; paste one at a time. The ZIP includes both forms and this guide. This is a reviewed workflow pack, not preinstalled instructions or a migration tested against your site. The prompts require live capability discovery before execution.
