Kittl
Create typography-heavy graphics, labels, posters, and merchandise-ready exports
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Kittl, create typography-heavy graphics, labels, posters, and merchandise-ready exports. The hard boundary is specialized templates, fonts, vector effects, asset library, and mockups, plus editor polish, assets, collaboration, and distribution.
Build verification: not recorded. How we judge buildability
What you give up
- specialized templates, fonts, vector effects, asset library, and mockups
- huge template and asset libraries
- real-time multiplayer
- brand governance
- professional print workflows
Why people still pay
People still pay for Kittl because people pay for a vast ready-made design system and a collaboration surface that behaves predictably under deadline. The recurring cost buys canvas correctness, fonts, exports, templates, asset rights, multiplayer state, and accessibility, not just the visible interface.
Your build guide
The stack, security requirements, and agent rules for a focused replacement.
Before you start
- A supported Node release for development and a modern browser. Ship a static bundle that can work locally without an account.
- Implementation components: Vite, React, TypeScript and Fabric.js for editable vector/text composition. IndexedDB project snapshots, licensed local font assets and SVG/PDF export with explicit physical dimensions.
- Scope boundary: Universal print-shop compatibility and merchandise fulfillment are excluded.
Use these project rules and optional skill references alongside the prompt. Review each skill before adding it to your agent; the AGENTS.md export includes the same guidance.
Optional external skill: vercel-composition-patterns — Design reusable React components with composition, context and explicit component variants. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Optional external skill: web-design-guidelines — Review web interfaces for accessibility, keyboard focus, forms, navigation and interaction quality. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Optional external skill: pdf — Process PDFs through extraction, generation, page operations, form filling and OCR workflows. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission.
Project rule — data model: vector layers, text runs, font references, ornament assets, print dimensions and export profiles
Project rule — preserve this invariant: A raster placed inside SVG is still raster; output must disclose missing fonts and cannot claim print readiness from DPI metadata alone.
Project rule — acceptance evidence: Export a 200 mm label and confirm its dimensions and text bounds; reopening editable JSON preserves layer order and licensed font references.
Implementation plan
Phase 1
Scope and fixtures. Implement this bounded workflow: Design a typography-led poster or label with editable text, curves, ornaments and reusable layouts. Show font licensing/source information and export SVG plus a reviewed PDF at explicit physical dimensions. Record prerequisites, select representative user-owned fixtures and document the unsupported features: Universal print-shop compatibility and merchandise fulfillment are excluded.
Phase 2
Durable model. Model vector layers, text runs, font references, ornament assets, print dimensions and export profiles Add migrations or a versioned document format, explicit validation, stable IDs and a visible import-error report. Preserve this rule: A raster placed inside SVG is still raster; output must disclose missing fonts and cannot claim print readiness from DPI metadata alone.
Phase 3
Complete the first useful path. Implement the workflow's input, review and output interface, with clear controls and explicit empty/error states. Represent edits as reversible commands, debounce autosave, and persist a complete project snapshot before destructive structural changes.
Phase 4
Permissions and integration failure. Sanitize imported SVG, reject external scripts and oversized assets, and require user selection before reading local files. Keep document contents out of telemetry. Request integration credentials and permissions only for the enabled feature; show a disconnected state instead of mock results.
Phase 5
Portable handoff. Export editable JSON with assets and an SVG or PNG rendering. Reopen the editable export to retain layers, relationships and IDs; image exports alone are not backups. Include setup, operating limits, fixture walkthrough and shutdown/restart instructions in the README.
Phase 6
Acceptance scenarios. Export a 200 mm label and confirm its dimensions and text bounds; reopening editable JSON preserves layer order and licensed font references. Repeat the workflow after restart and with a denied permission or unavailable dependency; show recoverable failure rather than a success placeholder.
WORKING SLICE Design a typography-led poster or label with editable text, curves, ornaments and reusable layouts. Show font licensing/source information and export SVG plus a reviewed PDF at explicit physical dimensions. Build this scoped Kittl-inspired workflow with a documented data model and visible failure states. Architecture - Vite, React, TypeScript and Fabric.js for editable vector/text composition. - IndexedDB project snapshots, licensed local font assets and SVG/PDF export with explicit physical dimensions. Prerequisites and limits A supported Node release for development and a modern browser. Ship a static bundle that can work locally without an account. Outside this release: Universal print-shop compatibility and merchandise fulfillment are excluded. Data model and correctness vector layers, text runs, font references, ornament assets, print dimensions and export profiles Invariant: A raster placed inside SVG is still raster; output must disclose missing fonts and cannot claim print readiness from DPI metadata alone. Represent edits as reversible commands, debounce autosave, and persist a complete project snapshot before destructive structural changes. Security and privacy Sanitize imported SVG, reject external scripts and oversized assets, and require user selection before reading local files. Keep document contents out of telemetry. Recovery and export Export editable JSON with assets and an SVG or PNG rendering. Reopen the editable export to retain layers, relationships and IDs; image exports alone are not backups. Implementation order 1. Phase 1 — Scope and fixtures. Implement this bounded workflow: Design a typography-led poster or label with editable text, curves, ornaments and reusable layouts. Show font licensing/source information and export SVG plus a reviewed PDF at explicit physical dimensions. Record prerequisites, select representative user-owned fixtures and document the unsupported features: Universal print-shop compatibility and merchandise fulfillment are excluded. 2. Phase 2 — Durable model. Model vector layers, text runs, font references, ornament assets, print dimensions and export profiles Add migrations or a versioned document format, explicit validation, stable IDs and a visible import-error report. Preserve this rule: A raster placed inside SVG is still raster; output must disclose missing fonts and cannot claim print readiness from DPI metadata alone. 3. Phase 3 — Complete the first useful path. Implement the workflow's input, review and output interface, with clear controls and explicit empty/error states. Represent edits as reversible commands, debounce autosave, and persist a complete project snapshot before destructive structural changes. 4. Phase 4 — Permissions and integration failure. Sanitize imported SVG, reject external scripts and oversized assets, and require user selection before reading local files. Keep document contents out of telemetry. Request integration credentials and permissions only for the enabled feature; show a disconnected state instead of mock results. 5. Phase 5 — Portable handoff. Export editable JSON with assets and an SVG or PNG rendering. Reopen the editable export to retain layers, relationships and IDs; image exports alone are not backups. Include setup, operating limits, fixture walkthrough and shutdown/restart instructions in the README. 6. Phase 6 — Acceptance scenarios. Export a 200 mm label and confirm its dimensions and text bounds; reopening editable JSON preserves layer order and licensed font references. Repeat the workflow after restart and with a denied permission or unavailable dependency; show recoverable failure rather than a success placeholder. Acceptance Export a 200 mm label and confirm its dimensions and text bounds; reopening editable JSON preserves layer order and licensed font references. Use real source data or clearly labeled fixtures. Explain unsupported input and provider failures; do not fabricate analytics, delivery receipts, accuracy claims or security guarantees. Optional agent guidance Optional external skill: [vercel-composition-patterns](https://github.com/vercel-labs/agent-skills/blob/main/skills/composition-patterns/SKILL.md) — Design reusable React components with composition, context and explicit component variants. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission. Optional external skill: [web-design-guidelines](https://github.com/vercel-labs/agent-skills/blob/main/skills/web-design-guidelines/SKILL.md) — Review web interfaces for accessibility, keyboard focus, forms, navigation and interaction quality. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission. Optional external skill: [pdf](https://github.com/anthropics/skills/blob/main/skills/pdf/SKILL.md) — Process PDFs through extraction, generation, page operations, form filling and OCR workflows. Review its instructions and compatibility before use; it does not grant deployment, data-access or publication permission. Project rule — data model: vector layers, text runs, font references, ornament assets, print dimensions and export profiles Project rule — preserve this invariant: A raster placed inside SVG is still raster; output must disclose missing fonts and cannot claim print readiness from DPI metadata alone. Project rule — acceptance evidence: Export a 200 mm label and confirm its dimensions and text bounds; reopening editable JSON preserves layer order and licensed font references.
$ open in your agent (prompt prefilled, you press enter), copy the prompt or copy or download AGENTS.md
prompt copied. want to know what dies next week?
new verdicts + top votes, weekly. free. one-click out.
Alternatives to building your own
no votes, no pay-to-list · just what's real
Kittl pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/user | $0/user | 5 projects and 200 one-time AI tokens; personal use only. |
| pro | $19/user | $14/user | Unlimited projects; 2,000 AI tokens/month; 10 GB storage; commercial licence up to 500,000 copies. |
| expert | $45/user | $34/user | 6,000 AI tokens/month plus 200 daily tokens; 100 GB storage; commercial licence up to 500,000 copies. |
| max | — | — | 600 daily AI tokens plus a monthly balance; public plan card price and exact monthly balance were not exposed.Top-ups are available on Expert and Max. |
| business | — | — | Enhanced commercial licence beyond 500,000 copies and team collaboration; public price is not listed.Additional editors are charged. |
free tier5 projects and 200 one-time AI tokens; personal use only.
billingmonthly + annual
hidden costsMonthly AI tokens expire at the end of each cycle; daily tokens reset every 24 hours. Extra editors are charged, and commercial reproduction above 500,000 copies requires Business.
pricing sources checked 2026-08-14 · pricing source ↗
Questions about Kittl
Can you build your own Kittl with AI?
Partly. The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Kittl, create typography-heavy graphics, labels, posters, and merchandise-ready exports. The hard boundary is specialized templates, fonts, vector effects, asset library, and mockups, plus editor polish, assets, collaboration, and distribution.
What does the Kittl build prompt cover?
The prompt starts with this scope: Design a typography-led poster or label with editable text, curves, ornaments and reusable layouts. Show font licensing/source information and export SVG plus a reviewed PDF at explicit physical dimensions. Full-product capabilities excluded from the comparison include: specialized templates, fonts, vector effects, asset library, and mockups; huge template and asset libraries; real-time multiplayer. Follow the implementation plan and its prerequisites before expanding the build.
How do I use the prompt, AGENTS.md and agent skills?
Start with the Kittl prerequisites and stack, then copy the prompt into your coding agent. Save the project rules as AGENTS.md in the project root. Linked skills are optional packages or source instructions for specific tasks; review their current contents and install only those matching the chosen stack. A skill does not supply API credentials or verify the finished app.
How long will this Kittl project take?
The catalogue estimate is multi-day for the limited scope. Setup, integration approvals, debugging, deployment and ongoing maintenance can add time. This is an estimate, not a delivery guarantee.
What would I give up by replacing Kittl?
specialized templates, fonts, vector effects, asset library, and mockups; huge template and asset libraries; real-time multiplayer; brand governance; professional print workflows. People still pay for Kittl because people pay for a vast ready-made design system and a collaboration surface that behaves predictably under deadline. The recurring cost buys canvas correctness, fonts, exports, templates, asset rights, multiplayer state, and accessibility, not just the visible interface.
What price is this guide comparing against?
The recorded Pro plan is $19/mo per seat (monthly per user), checked 2026-08-14. Check the linked pricing source before buying. Building your own also has hosting, API and maintenance costs; the recorded amount is not a guaranteed saving.
What can I use instead of building Kittl?
Inkscape: Serious vector lettering, paths, labels, posters, and print-ready SVG/PDF export; stock mockups and one-click effects are your problem. Affinity: A fully featured vector, raster, and layout suite now free forever; bring your own templates and taste. Check each option's license, hosting needs and feature limits.