claude

design-pack

Design-handoff pack: /design-implement takes an exported design and re-expresses it in the project's stack pixel-accurately — computed-style token inventory, reuse-vs-create recon, an approval gate, and a measured pixel diff as the completion criterion. Opt-in; requires core.

8 on GitHubby atretyakv0.5.0Apache-2.0updated 9 days ago
/

Plugin design-pack from marketplace swarmery in atretyak1985/swarmery. Commands read from the repo's manifest — 9 days ago.

What it installs

Skills (3)

  • design-acquire

    Resolve a design handoff into something measurable: parse a handoff prompt, unpack an exported HTML/zip, pull tokens from a design-system source, or record an honest degraded mode for screenshots-only input. NOT for the implementation workflow itself (that's design-build) and NOT for measuring a dif

  • design-build

    Use when a finished visual design has to be re-expressed in this project's stack pixel-accurately — the user says \"implement this design\", \"here's a design handoff\", \"make this screen match the mockup\", \"design-implement\", pastes a design-tool handoff prompt, or attaches an exported design H

  • design-verify

    Measure an implemented screen against its design export with a headless pixel diff and report the regions, the number and the side-by-side image. NOT for choosing what to build (that's design-build), NOT for resolving the design input (that's design-acquire), and NOT for behavioural UI checks withou

Slash commands (1)

  • /design-pack:design-implement

    Thin entry point for `/design-implement <export-path|url> [--route <path>] [--viewport WxH] [--from-screenshots] [--dry-run]` — parses and validates the argument shape only, then hands control to the `design-build` skill. No run logic lives here.

Subagents (1)

  • design-implementer

    Execute the approved implementation of a design handoff — re-express the design in the project's own stack, then measure the result against the design with a pixel diff and iterate within the approved file set. Invoked only after the operator approved a Phase 4 plan; stops and returns the decision o

View source on GitHub atretyak1985.github.io

More from atretyak1985/swarmery

All 16 plugins →

core

claude

Vendor-neutral agent-development core: generic agents, skills, commands, hooks, and the project-aware agent-work CLI.

37 skills · 8 commands · 13 agents · hooks

8

Infrastructure & delivery domain pack: Kubernetes/Helm, GitOps promotion, IaC, GitLab CI, cloud CI auth (GCP + AWS), Keycloak. Opt-in; requires core.

11 skills · 1 command · 3 agents

8

jira-pack

claude

Issue-tracker pack: /jira-fix drives any Jira ticket end-to-end — access preflight, defect-or-change triage, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition. Opt-in; requires core and an Atlassian MCP provider enabled on the machine.

7 skills · 1 command · 1 agent

8

uav-pack

claude

UAV/drone domain pack: MAVLink-style telemetry, mission planning, embedded/edge runtime.

3 skills · 4 agents

8

Claude-engineering pack: skills for building/auditing Claude agent systems — agent architecture, tool/MCP design, prompt engineering, Claude Code config, context reliability. Opt-in; requires core.

5 skills

8

web-pack

claude

Web/marketing domain pack: SEO, i18n, landing-page CRO, Figma-to-code styling.

1 command · 3 agents

8

Maintain design-pack?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins16 plugins