Workflow style contract
Skill bcorfman/gui-workflow-guardrails/skills/workflow-style-contract
Extract existing UI style patterns (layout + interaction conventions) and enforce them for new/updated GUI features.From its SKILL.md
npx -y skills add bcorfman/gui-workflow-guardrails --skill workflow-style-contractAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 345 tokens by cl100k_base, as published. Nobody here has run it
When to use
Use this skill when:
- Adding a new panel/inspector section/tool
- Adding new canvas objects or interaction affordances
- You want to prevent “style drift” (new UI breaks established patterns)
Process
1) Extract current style patterns
Scan the existing GUI for “style contracts”:
- Layout patterns (e.g., paired controls side-by-side, consistent spacing, foldout patterns)
- Interaction conventions (e.g., where object actions live; near-cursor vs inspector)
- Terminology conventions (verbs and labels)
- Discoverability patterns (hints/tooltips, menu placement)
Write them as general rules, not one-off examples.
2) Enforce style by default
When designing a new feature:
- Match the existing pattern first.
- Only deviate if it improves intuition or efficiency (fewer steps / shorter pointer travel).
3) Style vs workflow tradeoff gate
If a deviation could improve workflow but violates style:
- Stop and ask the user which to prioritize.
- Provide 1–2 alternatives that preserve style.
4) Regression checks
Before finishing:
- Ensure newly introduced UI does not reintroduce banned patterns (e.g., splitting conceptual pairs across lines).
- Ensure comparable objects get comparable affordances (menus, shortcuts, hover/cursor).
Output format
- Style contracts (generalized): bullet list
- Where each contract applies: file/module/surface
- Planned deviations: none / list with rationale + confirmation status
Exit criteria
- New UI matches existing style contracts (or approved deviations are documented).
- No “style drift” is introduced inadvertently.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.