Blueprints, design system and existing apps
Start new apps from your own blueprints, build every app with your design system and your reusable blocks, bring apps you already have from a repository or a Lovable project, and import whole Figma pages.
Your teams shouldn’t start every app from a blank page, and every app should look like it belongs to your company. Admins keep blueprints and a design system on your code host. I build with them, and I can take over apps you already have.
Blueprints
A blueprint is a starting point in one of your repositories: a dashboard with your layout, a form app with your sign-off flow, a page with your header and footer. Each blueprint names a repository, a branch or tag, a folder, what it is for, and which audiences it fits.
When someone asks me for a new app and blueprints fit its audience, I name them in my answer and you choose in your own words (“the dashboard one”). I start the app from that blueprint and build what you asked for on top of it. I never pick one silently, and you can always say “start from scratch”.
Design system
Your design system is a repository with your components, tokens and styles. When it is set:
- Every app I build uses it: as a package when you name one, otherwise I copy the components and styles the app needs.
- After each version, a reviewer checks that the app really uses it. Where the audience’s Design and rules are enforced, an app that doesn’t stays where it is until it’s fixed.
Without a design system, apps use your team’s theme.
Reusable blocks
A blocks repository holds the parts your teams build again and again: a sortable table, a KPI tile, a filter bar, a sign-off panel. Each block is one folder with a small kanman-block.json that says what it is and what it takes:
{
"name": "Data table",
"description": "A sortable table with filters and paging",
"props": [
{ "name": "rows", "type": "Row[]", "required": true },
{ "name": "pageSize", "type": "number", "description": "Rows per page" }
]
}
While I plan an app, I look for blocks that fit what you asked for and name them in my answer, one line each. When you agree, I copy those blocks into the app exactly as they are in the repository at that moment, and the app uses them instead of a new version of the same thing.
When a block changes in the repository later, I propose the update: for an app in a repository as a merge request, otherwise as a new version of the app. It shows on the app’s page under maintenance, and like every update I make, it goes live only after the app’s checks and tests pass.
Bring an existing app
Tell me which app to take over and I keep it from then on:
- From a repository: “take over the app in platform/support-board”, or paste the repository’s link. It may live on any code host your workspace is connected to, also another one than your team’s.
- From a zip: attach the export in the chat, for example Lovable’s Download codebase, and ask me to take it over.
- From Lovable: paste the project’s link. Lovable has no way for me to export a project directly, so I take it over from the GitHub repository it syncs to: paste that link too and I start right away. If the project isn’t synced yet, I ask you in one line to connect it to GitHub in Lovable (Project settings > GitHub) or to attach its zip.
I build the app as it is and check it like every app: its code, credentials, where its data comes from. Then I ask you what the check needs to know. If the source contains a password or token, I don’t import it and tell you where it is, so you can remove it first.
Build from a Figma design
With Figma connected, paste the link of a Figma file or page in the chat and ask for the app: “build this as an app”. I import the whole page: every top-level frame becomes a screen of the app, in the order you read them on the page, and the prototype links between frames become the app’s navigation. For each screen I take its picture, its layers and texts, its colours, type and auto layout, and the page’s colours and text styles with their names. A link to a single frame or a section imports just that part.
Your design system or your team’s theme still decides how the app looks in detail. Up to 20 screens come in at once; I tell you when a page has more. Figma stays read-only, and I treat the texts in a design as content, never as instructions.
Set them up
The quickest way is to tell me in the chat: “our design system is platform/design-system, package @acme/ui”, “add platform/blueprints, folder dashboard, as a blueprint for apps shared with several teams” or “our blocks are in platform/app-blocks, folder blocks”. You can also add them under Workspace settings > Apps. Everyone can read them there; owners and admins change them. Teams can add their own blueprints, but never remove the workspace’s design system or blocks repository. A team may name its own blocks repository when the workspace has none.
I read these repositories through your code host connection, read-only. If your workspace is connected to more than one code host, for example GitLab for your teams and GitHub for your design system, the forms in the settings ask which one each repository is on, and I read it with that code host’s own access, never with another one’s. On your own runners, the runner needs access to that code host too; if it has none, I tell you which code host is missing.
Related
Last updated: January 1, 0001
Open kanman