GitHub collection
agentsorg/design-engineering
Imported from GitHub — is this yours?
1 skill imported from this repository.
- Stars
- 40
- Forks
- 2
- License
- MIT
Skills (1)
design-engineering
Load when reviewing UI code, designing a component or page layout, picking an easing curve or transition pattern, deciding whether something should animate at all, choosing an avatar/typography/color system, building an OKLCH palette or fixing contrast, writing UI copy or error m
Claude
Skill
design-engineering
Commands (15)
-
source
/cmd-a11y— **Posture: judge.** A finding needs evidence: a WCAG criterion it fails, or a behaviour you can reproduce. Anything else is a preference, and is labelled as one. -
source
/cmd-break— Aliases: `worst-case`, `break-ui`. **Posture: adversary, then judge.** Build the worst-case data and the toggle, report, and stop. Never fix the component until the user names which breaks to fix. -
source
/cmd-film— The second word picks the job. Without one, a video file or URL means `review`; anything else means `plan`. -
source
/cmd-mobile— Alias: `native-feel`. **Posture: fixer.** Apply the fixes, keep each to the declaration that does the job, and never claim a fix is verified when only a device could verify it. -
source
/cmd-motion— **Posture: decide first, then judge (code in hand) or build (greenfield).** The modes below change the posture; bare `motion` is judge or build. -
source
/cmd-polish— **Posture: build.** Edit the code, then show what changed. -
source
/cmd-review— **Posture: judge.** Read and report. Never edit code unless the user asks after the table. -
source
/cmd-ship— Aliases: `prep`, `prod`, `launch`. **Posture: fix.** Edit the code, then report. With `audit`, judge only: every row's status is Open. Run it last, on a screen whose design is settled; it fixes defects, not taste ([[ship-check]]). -
source
/cmd-small— Each of these hands off to one owner node. Open it, follow it, and stop where the owner says to stop. -
source
/cmd-sound— **Posture: decide, then build.** If the user only asked *whether* something should make a sound, answer from [[sound-decision-framework]] in one line and stop. -
source
/cmd-stage— Build posture, except `review`, which judges and does not edit. The second word picks the job; without one, a brief that says "animated", "loop", "cursor" or "demo" is `demo`, a grid of features is `bento`, anything else is `still`. -
source
/cmd-svg— The second word picks the job. Without one, `create` applies to a new or messy file and `animate` to a clean file the user wants moving. -
source
/cmd-tells— Aliases: `unslop`, `slop`. **Posture: judge.** The output is a list of things to delete, not a new visual direction. -
source
/cmd-tokens— Aliases: `contract`, `apply-design-md`. **Posture: build.** -
source
/MOC-commands— The skill has one entry point. `/design-engineering` reads its first argument, and if that is a verb, it opens the matching file here. The dispatch table at the top of SKILL.md is the canonical index of verbs and aliases. This MOC exists so the graph view shows the cluster.