Skip to main content
The StackKits finder captures intent before it generates technical configuration. The first output is not a final deployment file. It is a structured draft that makes the decision points visible. This guide explains the bridge between a human situation and a StackKits spec. The goal is not to guess every technical setting. The goal is to preserve the decisions that would otherwise be lost in a generic template choice.

​
What this guide helps you decide

  • which answers belong in the first spec draft
  • which technical details should wait
  • how to keep recommendation confidence honest
  • how the finder can hand off to future configuration flows

​
What intent means

Intent is the user’s answer to questions such as:
  • What are you trying to build?
  • Where should it run?
  • How technical should the workflow be?
  • How many servers are involved?
  • Do you want ongoing management?
  • Which use cases matter?
Good intent captures the user’s moment, constraints, and proof needs. It should explain why a kit fits, not only name the kit.

​
What the first spec should contain

A first StackKits spec should capture: 
stackkit: base-kit
meta:
  name: my-kombify-stack
  goal: home-server
  environment: local
  management: cloud-managed
  experience: Guide me
  servers:
    count: 1
    already_available: true
use_cases:
  - app-hosting
  - monitoring

​
What should not be over-decided

The first draft should avoid pretending to know details the user has not provided:
  • exact DNS provider
  • final service list
  • backup target credentials
  • production availability guarantees
  • low-level CUE overrides
Those can be resolved later by the installer, CLI, or kombify Cloud workflow. The finder should stay useful even when the user is early. It can say “Base Kit first” while still preserving a future Modern Homelab or High Availability direction.

​
Recommendation confidence

The recommendation can be confident when the answers are consistent. It should stay conservative when the answers conflict. Examples:
  • one server + first homelab + guided setup: strong Base Kit signal
  • hybrid + many use cases: Modern Homelab direction
  • startup + public services + three nodes: High Availability direction, with readiness review

​
What happens next

After the intent profile is captured, kombify can:
  • show the likely StackKit
  • explain why it was chosen
  • produce a draft stack-spec.yaml
  • link to the relevant docs
  • hand the profile to a future guided configuration flow