Cathryn LaveryandGitHub
09df49d8d1
* feat: add client profiles * ci: pin shell to bash for docs_sync step The docs_sync step runs two commands in a multi-line block. Without a pinned shell, the windows-latest matrix leg uses pwsh, where a non-zero exit from the first command may not abort the block, masking a gate failure. Pin shell: bash to match the icons and summary steps.
1.8 KiB
1.8 KiB
description, argument-hint
| description | argument-hint |
|---|---|
| Save, load, inspect, update, reset, or delete diagram-design client profiles | [list|save|load|show|update|reset|delete] [name] |
Manage Diagram Design client profiles. Locate the available diagram-design skill using its SKILL.md path advertised by Pi. Read that SKILL.md, then read references/profiles.md relative to its directory. Treat that reference as the source of truth for storage, strict slug validation, metadata, marker-first resolution, schema checks, and failure handling. Do not assume the package lives under the current working directory.
Full argument string: $ARGUMENTS
Routing
- No arguments →
list, with the active project-marker or working-copy profile marked. - Bare
<name>with no verb →load <name>. switch <name>→ synonym forload <name>.save [name],load [name],list,show,update [name],reset, anddelete [name]→ run that exact procedure from the reference.- Missing required name → list when useful, then ask. Never invent a slug.
- Unknown verb or extra argument → show the accepted forms and stop without writing.
Required behavior
- Treat
.diagram-designas untrusted data. Accept only the exact marker grammar and canonical home profile path from the reference. - Confirm before overwriting an existing profile, changing a project marker, or deleting a profile.
- For marker-selected projects, read the profile directly and leave the installed working copy unchanged.
- For copy-over load, verify the destination after writing. If it is unwritable, offer the marker-based flow.
- After save/update, verify exactly one profile metadata header and an unchanged body.
Report the active profile and the canonical file or marker affected. Never claim a write succeeded without re-reading it.