Skill
The instructions for your agent: memory, briefing, research with 12 to 20 real references, moodboard, three directions as real HTML pages, decision, design system, roll-out to web, slides, social and app, checks, filing.
MIT, free
Four parts, one process.
Kiekkist works like a small studio inside your AI agent. The skill runs the process, the tool measures, the gallery supplies finished systems, and the launch package gets the site online.
Tool
MCP server and command line: capture references, build boards, file themes, check, export to HTML, Astro, React, WordPress (block theme, first version) and Elementor (design layer).
AGPL-3.0, free
Gallery
Finished, checked design systems with the full page set, social and slides, a check report and a licence for client work. Your agent searches and fetches them through the connector.
Design or All-Access
Launch package
Checklist and checks for going live: domain, hosting, legal page templates, forms, analytics without cookies, accessibility statement, performance budget.
included in the tool
One project from start to finish
Memory
The agent reads your taste profile, earlier themes and the client’s brand rules before it thinks about colours.
Briefing
Questions in short rounds: offer, audience, promise, proof, tone, and what it must not turn into.
Research and moodboard
Real sites from the industry and neighbouring fields, sorted by mechanism, with a scene: who looks at this page, and when?
Three directions
Safe, middle, bold. Three real HTML pages with the client’s real content, different on at least three of five axes.
Decision
You decide, or your client does through a link without a login. The reason is recorded word for word.
System and roll-out
The direction becomes DESIGN.md and tokens, then pages, slides, social graphics and app screens.
Checks
Kiekkist measures first, then a second agent that has not seen the build writes its critique. Two rounds of fixes at most.
How it gets into your agent
Ordered by effort. Take the first one that fits your setup.
-
Remote MCP URL
For any MCP client: your AI assistant in the browser, the terminal or the editor. Gallery search and free designs without an account, paid designs with a licence key.
- In the assistant: settings, connectors or MCP servers, add a custom server, paste the URL.
- Terminal clients: add the server as an HTTP MCP server with this URL, usually with the client’s add command.
https://kiekkist.de/mcp-gallery -
Skill as a ZIP
For assistants that accept skills as an upload, if you want to work without a connector. The process keeps everything in your project.
- Settings, Skills, upload the ZIP.
- In the chat: “Use kiekkist-agency for a new website for …”
kiekkist-agency.zip -
Skill folder in your repo
For cloud sessions that check out a repository. No server needed.
- Copy the kiekkist-agency folder into your assistant’s skills folder in the repo and commit it.
- The next session finds the skill on its own.
skills/kiekkist-agency/ -
npx for local work
The whole tool on your machine, with checker and export. Needs Node 22.
- npx kiekkist mcp starts the local MCP server (stdio).
- npx kiekkist check ./dist/index.html checks a finished page.
npx kiekkist mcp
The repository and the npm package go public at launch.
What you need
An AI assistant that can write and run code and connects MCP servers or skills. Or someone who knows Astro, HTML, WordPress, React or Elementor.
What happens to your data
Everything is rendered on your side. Your text, images and client data stay in your project. There are no accounts. The Kiekkist server only knows your order, your licence and the names of registered projects.
Updates
Bug and security fixes go to everyone, for good. Your agent asks for new versions and shows you the changelog before anything is applied.
What a design package contains
DESIGN.mdtokens.css, tokens.jsonpages/ (every page)slides/social/app/ (when included)assets/fonts/ with licence textsLICENSE.md with licence IDreport/ (check report)
