plugins/dev/skills/design/designer-integration/SKILL.md
Detects the designer@magus plugin and delegates pixel-level design validation. Use when dev:frontend or dev:browser-debugging needs design comparison or AI semantic UI analysis.
npx skillsauth add madappgang/magus designer-integrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The designer plugin provides pixel-level design comparison and AI semantic analysis
for UI validation. When installed alongside dev, it enhances frontend workflows with
structured design fidelity checks.
This skill is optional — all dev plugin functionality works without designer installed.
Use this skill when:
Check if the designer plugin is available before delegating:
# Check designer plugin availability
designer_available=$(claude /plugin list 2>/dev/null | grep -c "designer" || echo "0")
if [ "$designer_available" -gt "0" ]; then
echo "designer plugin available — can delegate validation"
else
echo "designer plugin not installed — use manual comparison"
fi
When designer is available, delegate pixel-level validation from dev:frontend:
Task(
subagent_type: "designer:review",
prompt: "Compare reference design at {REFERENCE_PATH} against implementation at {IMPL_URL}. Viewport: 1440x900."
)
Or use the designer:review command directly:
# Pixel-diff comparison
/designer:review REFERENCE_SOURCE={path} IMPL_SOURCE={url}
| dev Component | Without designer | With designer |
|--------------|-----------------|---------------|
| dev:frontend agent | Manual Chrome MCP screenshots | Delegate to designer:review |
| dev:browser-debugging skill | Manual visual check | designer:review for diff report |
| Any UI implementation | Describe visual issues | Structured pixel-diff + semantic report |
When designer:review succeeds, it produces:
diff.json — Structured report with pixel diff + semantic analysissummary.md — Human-readable summary with severity (PASS/WARN/FAIL/CRITICAL)diff.png — 3-panel composite: reference | implementation | diff overlaySeverity thresholds:
If designer plugin is NOT installed and user needs design validation:
Design validation features are available with the designer plugin.
Install: /plugin marketplace add designer@magus
Without the designer plugin, you can still:
- Use Chrome MCP screenshot capture for manual visual comparison
- Use Gemini via claudish for AI-based visual analysis
- Compare screenshots manually side-by-side
testing
A test skill for validation testing. Use when testing skill parsing and validation logic.
tools
--- name: bad-skill description: This skill has invalid YAML in frontmatter allowed-tools: [invalid, array, syntax prerequisites: not-an-array --- # Bad Skill This skill has malformed frontmatter that should fail parsing. The YAML has: - Unclosed array bracket - Wrong type for prerequisites (should be array, not string)
development
Sync model aliases from the curated Firebase database. Fetches default model assignments, short aliases, team compositions, and known model metadata from the claudish API. Run this to get fresh model recommendations.
tools
Release one or more Magus plugins to the distribution repos (magus, magus-alpha, magus-marketing). Handles version inference from git history, marketplace.json updates, tagging, and force-push to lean dist repos. Use whenever the user says "release kanban", "release the dev plugin", "cut a new version of gtd", "bump kanban to 1.7", or hands you a batch like "release kanban and gtd". Also use for multi-plugin releases and for checking what a release would contain before committing.