Template guide
Amistio open-source template
Start with a portable project brain in your repository before adopting the hosted Amistio app. The template path is intentionally transparent: use it today, and import later if the product becomes useful for your workflow.
What the template gives you
The template creates the same control-plane shape Amistio uses: architecture notes, context, decisions, feature specs, memory, plans, prompts, and workflows. It is a repo-native starting point for teams that want durable project knowledge without starting in a SaaS product.
Portable brain folders
Keep important project knowledge in Markdown files under `docs/`, close to source code and code review.
Model-agnostic prompts
Write implementation prompts as work units that a capable coding agent can execute without vendor-specific assumptions.
Decision trail
Capture architectural and product decisions as ADRs so later contributors can understand why the project moved a certain way.
Import-ready structure
If you later choose Amistio, the accepted brain files already map to the product's expected repository mirror.
When to use the template first
- You want the project-brain method but are not ready to use a hosted workspace.
- You need to test the control-plane folder structure in a private repository first.
- You are starting a client or side project and want a clean process from day one.
- You want a transparent fallback before asking a team to adopt the Amistio app.
Import later
Changing your mind should not punish you. Keep working in the template, commit the useful Markdown files, then import the existing checkout into Amistio when you want the hosted workspace, review flow, local-runner queue, and synced project state.
In Amistio, create or select a project, generate an import code, then run `amistio import <code>` from the existing checkout. The CLI pairs the repo, creates or reuses the repository link, and uploads accepted brain records for review.