Web experience orchestrator
Open-source interaction-design intelligence for AI coding agents - securely discover, select, adapt and validate UI motion, effects and interaction patterns.
npx -y skills add Suraj787/motif --skill web-experience-orchestratorAssembled 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.
What its author says it does
Copied from the file, not written here
Use as a convenience entry point for web experience and interaction-design requests; it immediately defers to the motif root orchestrator.
SKILL.md
0.9 KB, 186 tokens by cl100k_base, as published. Nobody here has run it
Web Experience Orchestrator (alias)
Responsibility: Thin alias / entry point. It holds no logic of its own; it routes to
the root motif skill.
When to invoke
- When a request arrives phrased as "web experience", "interaction design", or "motion/effect" work and you want a familiar entry point.
What it does
- Defers to the root
motiforchestrator. - Runs the same 16-step workflow and Hard rules.
- Loads the same specialist skills and
python -m motifCLI.
How it connects
- Adds nothing to
registry/orintelligence/; it only forwards.
Notes
Do not duplicate orchestration logic here. If behaviour needs to change, change the root skill. This file exists only so multiple natural entry phrases reach the same governance.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most agent orchestration skills give in 186 tokens
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-07
- Reference existing artifacts by path or URLin 53 of 742, across 25 files
- Run the full test suite after integrating changesin 51 of 742, across 19 files
- Dispatch one agent per independent problem domainin 50 of 742, across 17 files
- Verify fixes do not conflictin 45 of 742, across 13 files
- Include a suggested skills section in the documentin 45 of 742, across 17 files
- Redact sensitive informationin 41 of 742, across 11 files
- Save to the temporary directory of the operating systemin 39 of 742, across 10 files
- Tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
- Spot check agent changes for systematic errorsin 34 of 742, across 7 files
- Write a handoff document summarising the current conversationin 31 of 742, across 6 files
- Assign each agent a specific scopein 23 of 742, across 8 files
- Provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- defer to the root orchestrator
- run the same 16-step workflow
- load the same specialist skills
- change the root skill if behavior needs changing
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.