Kiket docsTemplates
Start from a GitHub template or copy `.kiket/` from the in-repo flagship definition packs.
A template is a complete .kiket/ directory — workflows, boards, case types, intake forms, dashboards, automations — curated for a specific kind of work. When you start a workspace from a template, Kiket creates a repo pre-populated with all of it.
Prefer depth over catalog size: for vendor onboarding, contract review, privacy/DSAR, and security incident stories, start from Definition packs (in-repo, evidence + findings + simulations). For everything else, use your own GitHub template repository or fork an existing .kiket/ repo.
Flagship packs (recommended)
Using a template
Pick it at project creation
In the New project wizard, click Copy from Template and browse the gallery. Each card shows a preview of the states, case types, and integrations the template uses.
Review the included workflows
Every template lists the workflows it ships. Most include one primary workflow (e.g. contract_review) plus one or two supporting ones (e.g. amendment).
Create the project
Kiket creates a workspace repo from the template (via GitHub's template-repo API or a simple copy), connects it, and syncs. You land ready to create your first case.
Customize in place
The template is a starting point. Edit the YAML in your IDE or the canvas in the app — both write to your repo. You're never locked to the upstream template.
Add evidence sources and packs after onboarding
Install integrations from Settings → Evidence sources (the legacy /marketplace URL redirects there). To add more .kiket/ workflows, copy from Definition packs or your own template repo into the workspace under .kiket/.
Forking vs. copying
Two ways to start from a template:
| Mode | Result | Use when |
|---|---|---|
| Copy (default) | Independent repo, no upstream link | You want full autonomy; the template is a starting point. |
| Fork | Repo forked from the upstream template | You want to pull upstream updates later. Requires the template repo to be a GitHub template. |
Copy is the right choice ~95% of the time.
Authoring your own template
Any .kiket/-containing repo can be a template. To publish:
- Mark the GitHub repo as a template repository (Settings → Template).
- Add
metadata.yamlat the repo root listing preview details (states, integrations, category). - Share the repo URL; anyone can use it via From GitHub → Template URL.