Menú
Use when the user wants to switch, list, save, edit, delete, or compare formae configuration profiles in ~/.config/formae/
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when the user wants to add support for a new resource type to an existing formae plugin
Use when the user wants to check for infrastructure drift, see what changed out-of-band, or absorb/overwrite out-of-band changes into their IaC codebase
Use when the user wants to bring unmanaged/discovered resources under formae management, import resources into their IaC codebase, or absorb cloud resources into existing forma files
Use when the user wants to rename a managed resource, relabel a resource, change a resource's label, or give a discovery-named resource a readable name — a rename on its own never destroys or recreates the cloud object
Use when the user wants to deploy infrastructure, apply a forma file, reconcile a stack, update a stack, or make planned infrastructure changes
Use when the user wants to start authoring formae infrastructure or deploy something NEW with formae — e.g. 'I want to deploy X with formae', 'build a k8s app with formae', 'set up infrastructure for Y', 'create a new forma file for my service', 'write formae IaC for Z'. The front door that triages where the work happens, sets up plugin schema deps, and dispatches to focused authoring skills. NOT for applying an existing forma file (use formae-apply) or operating existing infra.
| name | formae-config |
| description | Use when the user wants to switch, list, save, edit, delete, or compare formae configuration profiles in ~/.config/formae/ |
fcfg is a small CLI that manages named profiles for ~/.config/formae/. The active config is a symlink at ~/.config/formae/formae.conf.pkl pointing into ~/.config/formae/profiles/. fcfg only moves files; it does not restart the formae agent. After fcfg use <name> the user must restart the agent themselves if it is running.
fcfg init [--name <name>] [--yes] — convert an existing formae.conf.pkl into a profile and replace it with a symlink. Always pass --yes from agent contexts.fcfg list [--json] — list profiles, marking the active one with * in plain output. Use --json when you need to parse.fcfg current — print the active profile name on a single line.fcfg use <name> — atomically switch the active profile.fcfg save <name> [--force] — snapshot the active profile under a new name. Does not switch. --force overwrites an existing profile.fcfg edit [<name>] — open $EDITOR on a profile (or the active one). Skip from agent contexts; edit the file directly instead.fcfg delete <name> — delete a profile. Refuses if it is the active one — switch first.fcfg diff <a> [<b>] — diff -u between two profiles, or <a> vs the active profile. Exit code 1 from this command means "files differ" (not an error); only codes >1 are errors.| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | User error (missing profile, invalid name, overwrite without --force, etc.) |
| 2 | Filesystem / permission error |
| 3 | Not initialized — run fcfg init --yes first |
Only fcfg list --json produces JSON:
{"active": "local-dev", "profiles": ["default", "load-test", "local-dev", "prod"]}
active is null if the user has not run fcfg init yet.
User: "switch my formae to load-test"
fcfg use load-test.fcfg init --yes first.fcfg list to see what's available).