agentsclimarketplace

Design to code orchestrator

Skill newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/design-to-code-orchestrator

Shared library of AI agent skills — works across Claude Code, Cursor, Codex, Windsurf, OpenCode, and Google Antigravity via a single universal installer.

Install
npx -y skills add newmindsgroup/ai-agent-skills-library --skill design-to-code-orchestrator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 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 when the user wants to build a screen in Figma, implement from Figma, design this screen, build this page, match code to design, match design to code, or coordinate a hybrid workflow between design artifacts and implementation. Also use when the user asks for both design and code help and the path needs to be chosen explicitly instead of ad hoc.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 252 tokens by cl100k_base, as published. Nobody here has run it

Design To Code Orchestrator

Use this skill to choose and enforce the right workflow for hybrid design and implementation work.

Read First

  • /Users/newmindsgroup/.codex/knowledge/visual-core/component-composition-rules.md
  • /Users/newmindsgroup/.codex/knowledge/design-reviews/design-qa-checklist.md

Routing Rules

  • If Figma files, Figma URLs, or design artifacts are present or requested, prefer Figma-first:
    • figma-use
    • figma-generate-design
    • figma-implement-design
    • design-system rules where relevant
  • If the request starts in code or implementation, prefer code-first:
    • visual-style-bible
    • design-system
    • design-qa
  • If the user wants both, choose the primary owner first and document the sequence.

Workflow

  1. Detect artifacts and intent.
  2. Choose Figma-first or code-first explicitly.
  3. Route to the relevant skills.
  4. Ensure a review step exists before calling the work complete.

Guardrails

  • do not leave the workflow choice implicit
  • prefer reusable system rules over one-off screen decisions

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.