Skip to content
Knorra
Build your kit

Product Developer

Help: setting up Product Developer

These are the same steps the setup wizard walks you through, on one page.

  1. 1. Business profile

    Tell Knorra about your business once. Every flow reads this first, and picks up a change on its next run.

    • Business name
    • What do you sell?
    • Who buys it?
    • Your main offer
    • Facts you can state
    • How should it sound?
    • Words or claims to avoid
    • Website
    • Where are you based?
    • Who must never be contacted?

  2. 2. Flow interview

    Questions for this flow only. Each one says where the answer is used.

    • Preferred stack What new products are built with.
    • Code host Where repositories live.
    • Hosting Where previews and releases are deployed.
    • Repository for the weekly checks What the weekly QA and monthly audit read.
    • Weekly QA time on Friday When the weekly QA task runs.
    • Code and hosting: which app do you use? The flow works in this app when your Claude can reach it, through its own connector, then Zapier, then files, and keeps it in Knorra otherwise.
    • Documents and notes: which app do you use? The flow works in this app when your Claude can reach it, through its own connector, then Zapier, then files, and keeps it in Knorra otherwise.

  3. 3. Requirements check

    Everything this flow needs, with what it costs you. Tick each one when you have it.

    • A Claude plan with Claude Code and scheduled tasks. Builds run in Claude Code on your own plan. Cost: Your existing Claude subscription. Claude Code needs a paid Claude plan.
    • A code host. For example GitHub. You stay signed in on your own machine. Cost: Free plans cover private repositories on the common hosts.
    • A hosting account. For example Vercel. Previews first; production only with your yes. Cost: Free plans exist. Paid plans depend on your traffic.

  4. 4. Connect Knorra to Claude

    One guided step adds the Knorra connector to your Claude and signs it in. There is no key to paste.

    • In Claude, open Settings, then Connectors.
    • Choose "Add custom connector".
    • Name it Knorra and paste this address: https://knorra.ai/api/mcp
    • Press Connect. A Knorra page opens: sign in with your Knorra email, choose this workspace and press Allow.
    • Come back to this page. It confirms by itself when the connector first calls home.

  5. 5. Install the starter skill

    One download, one upload into Claude. The file carries your licence ID and holds no method of its own.

    • Download the skill file below.
    • In Claude, open Settings, then Capabilities, and find Skills.
    • Choose "Upload skill" and pick the file you downloaded.
    • Make sure the skill is switched on.
    • This flow includes the Branding plugin. Install it the same way to create one brand kit that every flow writes from.

  6. 6. Permissions and connectors

    Allow these in order, so scheduled runs are not stopped by a permission prompt nobody is there to answer. For each one, choose the option that allows it for this skill without asking every time.

    • Knorra connector. Allow its tools for this skill, in Claude Code as well as the Claude app. Where: Claude, Settings, Connectors, Knorra.
    • Claude Code access to your project folder. Allow reading and editing files and running the project's own test commands. Where: Claude Code, the permission prompt when a run starts.

  7. 7. Create the schedule

    Copy this one short prompt and paste it into a new Claude chat. It creates the scheduled tasks for this flow. It is the only thing you paste in the whole setup.

    • Product build: When you ask. One stage of a product, with a gate for your approval.
    • Weekly QA: Fri 16:00. Type check, lint and tests on shipped products.
    • Monthly security audit: Day 1 of the month, 09:00. Findings by severity for shipped products.
    • Brand kit: When you ask. One brand kit every flow writes and designs from.
    • Create these scheduled tasks for my Knorra workspace "your workspace". Each one uses the knorra-product-developer skill and the Knorra connector. 1. Name: "Knorra: Weekly QA". When: every Friday at 16:00 (your time zone). Prompt: "Use the knorra-product-developer skill. Run task product-qa." Connectors: Knorra, Claude Code. 2. Name: "Knorra: Monthly security audit". When: on day 1 of every month at 09:00 (your time zone). Prompt: "Use the knorra-product-developer skill. Run task product-security." Connectors: Knorra, Claude Code. Confirm each task back to me with its next run time.

  8. 8. Test run

    Run the flow once by hand. This page waits for the first report and moves on by itself.

    • In a new Claude chat, say: "Run a Knorra test run for Product Developer"
    • Reads your repository and runs its checks if it has them. Changes nothing.

  9. 9. Live

    The first good report has arrived. This flow now has a card on your dashboard with real numbers.

    • This flow starts in approve first mode. Nothing outbound goes without your yes. After enough approved items, the dashboard offers autopilot.

Stuck on a step? Use the support button on any dashboard page. The message carries the workspace, the flow and the step, so you do not have to explain where you are.