Remove verbose YAML examples, bash pseudo-code, tutorial prose, and motivational content from configuration/integration skills while preserving all operational protocols, reference tables, and rules. Skills trimmed: domains, colette-bridge, multi-project, cost-tracking, git-integration, custom-archetypes, workflow-design, templates, autonomous-mode, progress, presence.
2.8 KiB
2.8 KiB
name, description
| name | description |
|---|---|
| templates | Template gallery for sharing workflows, team presets, archetypes, domain configs, and complete setup bundles across ArcheFlow projects. Supports init-from-template, save-as-template, and clone-from-project operations. <example>User: "archeflow init writing-short-story"</example> <example>User: "archeflow template save my-backend-setup"</example> <example>User: "archeflow template list"</example> |
Template Gallery -- Shareable ArcheFlow Configurations
Makes ArcheFlow setups portable and reusable across projects.
Template Storage
| Location | Scope | Precedence |
|---|---|---|
.archeflow/templates/ |
Project-local | Higher (checked first) |
~/.archeflow/templates/ |
Global (user-wide) | Lower (fallback) |
Subdirectories: workflows/, teams/, archetypes/, domains/, bundles/.
Bundles
A bundle is a complete setup (team + workflow + archetypes + domain) in one directory.
Manifest (manifest.yaml):
name: writing-short-story
description: "Complete setup for short fiction writing"
domain: writing
includes:
team: story-development.yaml
workflow: kurzgeschichte.yaml
archetypes: [story-explorer.md, story-sage.md]
domain: writing.yaml
requires: [colette.yaml]
variables:
target_words: 6000
max_cycles: 2
| Field | Required | Description |
|---|---|---|
name |
Yes | Bundle identifier for archeflow init <name> |
description |
Yes | Human-readable description |
includes |
Yes | File types to filenames within bundle |
requires |
No | Files that must exist in target project |
variables |
No | Key-value defaults, overridable at init |
Operations
archeflow init <bundle-name>
- Find bundle (project-local, then global)
- Check
requiresfiles exist - Warn before overwriting existing
.archeflow/config - Copy files to
.archeflow/(teams/, workflows/, archetypes/, domains/) - Generate
.archeflow/config.yamlwith variables
archeflow init --from <project-path>
- Copy teams/, workflows/, archetypes/, domains/, config.yaml, hooks.yaml
- Skip run-specific data: events/, artifacts/, context/, templates/
archeflow template save <name>
- Package current
.archeflow/into~/.archeflow/templates/bundles/<name>/ - Auto-generate manifest.yaml
archeflow template list
- Show all bundles and individual templates (global + project-local)
Variable Substitution
Variables in manifests are stored in .archeflow/config.yaml after init. Substitution happens at run time, not template time.
Override at init: archeflow init writing-short-story --set target_words=8000
Individual Templates
Single files can be copied directly without a bundle:
~/.archeflow/templates/workflows/<name>.yaml~/.archeflow/templates/archetypes/<name>.md~/.archeflow/templates/teams/<name>.yaml