Skill v1.5.0
currentLLM-judged scan90/100name: lpm-config version: 1.5.0 description: Create and edit lpm YAML configs for projects, duplicates, worktree metadata, services, actions, header and footer button zones and zone layers, terminals, profiles, SSH projects, and shared config layers. Use when the user explicitly asks to configure lpm, add an lpm service/action/button/zone/terminal, edit .lpm.yml, or manage lpm templates or global config. For creating or removing linked Git worktrees and operating running projects, use lpm-cli.
Configure lpm
Create and modify lpm config on macOS exclusively through lpm config get and lpm config apply. Never modify a live project, repo, global, or template config directly with an editor, filesystem tool, patch, redirection, or script. The CLI validates the candidate before the app atomically replaces the destination.
Load only the relevant reference
- Read references/core.md for project identity, services, dependencies, profiles, duplicates, linked Git worktrees, auto pull, and project creation.
- Read references/actions.md when adding or changing actions, buttons, terminals, inputs, ports, shortcuts, colors, dynamic labels, agent prompts, or nested menus.
- Read references/zones.md when creating, filling, rearranging, or removing button zones or zone layers.
- Read references/sharing.md for
.lpm.yml, global config, templates,extends, layering, and sparse overrides. - Read references/ssh.md for remote projects or
mode: sync. - Read references/validation.md before preparing a candidate and follow its transactional workflow.
Resolve the target
Honor an explicit project or layer from the user. Otherwise run:
lpm config resolve --cwd . --json
Interpret the result:
- One match: use the returned project name with
lpm config get; never edit the returnedpath. A match locates the file even when the app cannot load it; validation reports what to fix. - Multiple matches: ask which candidate to use.
- No match: offer to create a project for the current directory or configure one of the returned
availableprojects.
Use these explicit layer overrides:
- “globally” or “all my projects” →
~/.lpm/global.yml - “share with the team”, “check it in”, or “for everyone” →
<root>/.lpm.yml - “template” or “reuse across projects” →
~/.lpm/templates/<name>.yml
When lpm config resolve is unavailable, inspect the YAML project files read-only. Match the current directory against expanded root paths by path components; the deepest root wins. An SSH project never matches by root or ssh.dir (a path on the host); only its local sync mirror ~/.lpm/sync/<project> matches, where <project> is the project's file name (~/.lpm/projects/<project>.yml), not its name: field. Do not parse YAML with line-oriented tools and do not write a config without lpm config apply.
Choose the shape
| Intent | Config shape | |||
|---|---|---|---|---|
| Long-running process started with the project | services | |||
| One-shot command or button | actions | |||
| Persistent interactive shell | actions with type: terminal | |||
| Start prerequisites first | service dependsOn | |||
| Ask for parameters | action inputs | |||
| Default action plus alternatives | parent cmd plus nested actions | |||
| Split button whose main segment repeats the last used option | parent primary: last-used plus nested actions | |||
| Menu with no default | nested actions without parent cmd | |||
| Framed group of buttons in the header or footer | zones entry with rows, plus display: <zone> on each button | |||
| Several button sets in one zone, switched with dots | zone layers, plus layer: <key> on each button | |||
| Fold a zone into one button with a hover popup | collapsed: true on the zone's entry in its source file | |||
| Put a button declared elsewhere into a zone or layer | sparse override with display, layer, and position only | |||
| Colored button or terminal tab | action color | |||
| Label or emoji that shows the branch, the last tag and its age, the next version, or a command's output (on a button, input or option) | {{git.branch}}, {{git.tag}}, {{git.tagAge}}, {{git.nextPatch}} or $(command) in label or emoji | |||
| Agent terminal that starts with a task | type: terminal with an agent cmd plus prompt | |||
| Hidden command with completion notification | type: background | |||
| Send command into the focused terminal | type: command | |||
| Reused visible pane | type: terminal plus reuse: true | |||
| Team-shared config | <root>/.lpm.yml | |||
| Reusable action set | template plus extends | |||
| Remote execution | project ssh block | |||
| Scheduled task (automation) | not a config edit: lpm automations add from lpm-cli; keep any jobs section as it is | |||
| Let the app pull one project from origin by itself, or never | autoPull, set with `lpm auto-pull <project> --set on\ | off\ | default; see core.md` |
Ask only when the requested shape is genuinely ambiguous. For “button with options,” distinguish a split button, dropdown, and input prompt. For a terminal action, distinguish one reused pane from a fresh pane each run.
Apply the change
For a new project, inspect repo signals such as package.json, Makefile, docker-compose.yml, Procfile, and mise.toml. Detect long-running services separately from one-shot test, lint, build, migration, and deploy actions.
Read the selected layer and its revision:
lpm config get --layer project --project <name> --jsonlpm config get --layer repo --project <name> --jsonlpm config get --layer global --jsonlpm config get --layer template --template <name> --json
Use --create with both get and apply when intentionally creating a missing project or template. Build the candidate from the returned content in a temporary file, preserving unrelated fields and formatting where practical. Use shorthand only when an entry needs no options. Set confirm: true for destructive operations.
Apply the candidate using the exact returned revision:
lpm config apply --layer <layer> <target-args> \--if-revision <revision> --file <candidate-path> --json
The command must return applied: true before reporting success. Fix validation errors in the temporary candidate and retry. On a revision conflict, run get again and reapply the intended change to the new content instead of forcing an overwrite.
Confirm only before replacing an existing config during intentional creation. Do not confirm an unambiguous edit. Config deletion must go through the lpm app; never delete a config file directly.
If the app is not running or config get/apply is unavailable, tell the user to start or update lpm. Do not fall back to direct writes.