No user-submitted related servers found.
Scored across 36 tools
The set is organized into clear families (knowledge retrieval, generators, audits) and descriptions cross-reference each other heavily, which helps an agent pick between them. The main confusable pair is audit_design_system vs audit_project, which both report color/shadow/spacing sprawl, and get_design_doc vs get_design_language overlap slightly as document fetchers.
The vast majority follow a predictable verb_noun pattern across list_/search_/get_, generate_, audit_, suggest_, create_, compare_, measure_, and import_ families. A few outliers—design_review_checklist, seo_geo_guide, knowledge_freshness, and design_lint—break the pattern but are still readable.
36 tools is far above the 25+ threshold and creates a heavy selection burden for an agent, even though the scope is broad. Several audit_* and generate_* tools could plausibly be consolidated, with audit_project largely subsuming design_lint plus audit_design_system's consistency counting.
The surface covers the full design workflow: knowledge discovery and planning, component guidance and recipes, deterministic design-token/color/type/motion generation, import of existing systems, screenshot measurement, and a wide matrix of audits across accessibility, copy, ethical design, security, SEO, performance, Apple, and Android. There are no obvious dead ends or missing lifecycle stages for the stated purpose.
