⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v1.0.0

authoring-motion-diagrams

2389-research@2389-research⭐ 102 stars· last commit 4d ago· 1 open issues

Use when adding a plugin to the marketplace, or when authoring, editing, or re-rendering a scene under scripts/animations/scenes/ — including when a scene fails the render contract, the contrast gate, or the grid baseline.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐ 102 on GitHubGitHub ↗

Popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

2389 Research Claude Code Plugin Marketplace

28 plugins and MCP servers for Claude Code — parallel exploration, iterative refinement, binary reverse engineering, structured decision-making, and more.

Built by the team at 2389. These are the tools we use every day.

Browse the marketplace: https://skills.2389.ai

Quick Start

Install any plugin in any agent (Claude Code, Cursor, Codex, …) with vercel-labs/skills:

npx skills add 2389-research/simmer

Or natively in Claude Code:

# Add the marketplace, then install any plugin
/plugin marketplace add 2389-research/claude-plugins
/plugin install simmer@2389-research

The 4 MCP servers (journal, socialmedia, slack-mcp, agent-drugs) install via Claude Code only — they ship no skills for npx.

Available Plugins

Meta Plugins

PluginDescription
botboard-bizSocial media and journaling capabilities for AI agents
better-devCSS, Firebase, code quality, testing, parallel exploration, docs verification, codegen
sysadminStructured Linux maintenance and diagnostics

Development

PluginDescription
css-developmentCSS workflows with Tailwind, semantic naming, dark mode by default
firebase-developmentFirebase project workflows: setup, features, debugging, validation
landing-page-designHigh-converting landing pages with anti-AI-slop principles
xtoolXcode-free iOS development with xtool via SwiftPM
building-multiagent-systemsArchitecture patterns for multi-agent systems
speed-runToken-efficient code generation with hosted LLM (Cerebras)
thriftyTiered-delegation execution: Sonnet plans a spec into sprints, cheap Haiku executes + self-verifies; ~64% cheaper than Opus
binary-reAgentic binary reverse engineering for ELF binaries

Testing and Quality

PluginDescription
test-kitchenParallel exploration of implementation approaches
simmerIterative artifact refinement with investigation-first judges
scenario-testingEnd-to-end testing with real dependencies, no mocks
fresh-eyes-reviewFinal sanity check before commits/PRs
documentation-auditVerify documentation against codebase reality
review-squadDispatch panels of specialized subagents for project review
prbuddyPR health assistant: CI monitoring, review triage, fixes
git-repo-prepPrepare codebases for public/open-source release

Business and Strategy

PluginDescription
ceo-personal-osPersonal operating system for executives
worldview-synthesisSystematic worldview articulation
deliberationDecision-making through deliberation and discernment
summarize-meetingsBatch-process meeting transcripts into structured summaries

Utilities

PluginDescription
terminal-titleAuto-update terminal title with emoji + project + topic
remote-system-maintenanceLinux system diagnostics and maintenance via SSH/tmux

MCP Servers

ServerDescription
agent-drugsDigital drugs that modify AI behavior through prompt injection
socialmediaSocial media functionality for AI agents
journalPrivate journaling capability for Claude
slack-mcpSlack workspace integration MCP server

Adding a Plugin

  1. Create a GitHub repo under 2389-research/ with standard plugin structure
  2. Add an entry to .claude-plugin/marketplace.json
  3. Run npm run generate to update the marketplace site
  4. Commit and push

See CLAUDE.md for the full marketplace.json format and detailed instructions.

Like this?

If these plugins save you time, a ⭐ helps us know what's landing. We build what people use.

Contact

Email: [email protected] — we'd love to hear what you're building with these.

License

MIT

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • .claude/skills/authoring-motion-diagrams/SKILL.md3.8 KBupstream ↗
    ---
    name: authoring-motion-diagrams
    description: Use when adding a plugin to the marketplace, or when authoring, editing, or re-rendering a scene under scripts/animations/scenes/ — including when a scene fails the render contract, the contrast gate, or the grid baseline.
    ---
    
    # Authoring motion diagrams
    
    Every marketplace entry has one authored scene at `scripts/animations/scenes/<plugin>.svg`,
    shown on that plugin's detail page. `docs/plugins/<plugin>/anim.mp4` and `anim-poster.png`
    are derived from it. Never patch the video — change the scene and re-render.
    
    A scene must **say what the plugin does**: what moves, in what order, and what is different
    at the end. A scene where things merely move is decoration.
    
    ## Flow
    
    1. Read the plugin's category from `.claude-plugin/marketplace.json`, then take that
       category's `mark` and `ink` from `scripts/animations/palette.js`. One accent per scene.
    2. Copy `references/scene-template.svg` to `scripts/animations/scenes/<plugin>.svg`.
    3. Compose the beats. `references/binding.md` has the tokens, the beat pattern, and the
       scene mechanics already in use — reuse one rather than inventing a shape.
    4. `node scripts/animations/render.js --check` — validates the contract in about a second,
       no Chrome. Run it constantly, not once at the end.
    5. `node scripts/animations/preview.js <plugin>` — one frame, ~1s. `AT=0.3` for another
       moment. This catches what no checker can: a label sitting on a connector, a box crossing
       its frame, a path ending in mid-air.
    6. `node scripts/animations/render.js <plugin>` — mp4 + poster, ~75s.
    7. `npm run generate && npm test`.
    8. Commit the scene, the mp4 and the poster together. They drift the moment they don't.
    
    ## What `--check` enforces
    
    | Gate | Rule |
    |---|---|
    | Cycle | every `dur` is `8s`, `repeatCount="indefinite"`, events placed in `keyTimes` |
    | Counts | `keySplines` = n−1, `values` = n, `keyPoints` = n. A mismatch disables the animation *silently* |
    | Ground | a `#faf9f6` rect is the first element |
    | Type | every text fill is a legal ink token — 4.5:1 on paper, computed not judged |
    | Blocks | solid rects use a category `ink`, so white type on them clears 4.5:1 |
    | Grid | placement on 20px; existing scenes carry a frozen debt in `grid-baseline.json` and may only improve |
    
    `palette.js` re-derives its own contrast claims before any scene is checked, so a token
    edited below its floor fails the build rather than shipping quietly.
    
    ## What no gate can check
    
    - **Two beats per change.** Transit says something arrived; settlement says the thing is now
      different. One beat alone reads as decoration.
    - **The changed state holds** until 0.95 of the cycle. A transition with no hold shows motion
      and communicates no outcome.
    - **Routes avoid what they don't address.** A path to C that crosses B reads as having entered B.
    - **Position is pre-allocated.** Draw routes as faint dashed guides from frame one, so the
      layout never reflows as parts land — reflow reads as rewriting, not extending.
    - **The poster carries the whole diagram** for a reduced-motion reader. Check it, not just the video.
    
    ## Common mistakes
    
    | Mistake | What happens |
    |---|---|
    | Chaining with `begin="other.end"` | can't scrub to a frame; export breaks |
    | A lighter grey "because the label is secondary" | fails the floor; there is no legal grey above `muted` |
    | Recolouring a travelling dot to `ink` | dots are marks at the 3:1 floor — leave them `mark` |
    | Editing `anim.mp4` or shipping a scene without re-rendering | video and source drift, and nothing reports it |
    | Nudging geometry off-grid in an existing scene | ratchet fails the build; the baseline only goes down |
    
    ## References
    
    - `references/binding.md` — this marketplace's tokens, treatments, and scene mechanics
    - `references/mechanic.md` — the portable declarative-SVG-motion doc
    - `references/scene-template.svg` — a conforming skeleton
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/2389-research-claude-plugins-claude-skills-authoring-motion-diagrams.md

// REPO STATS

102 stars
1 open issues
Last commit: 4d ago