diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 78619f0..3340a07 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -1,13 +1,12 @@ { - "name": "claude-code-workflows", + "name": "libreuiux", "owner": { - "name": "Hermetic Ormus", - "email": "hermeticormus@proton.me", + "name": "Diego Bodart", "url": "https://github.com/HermeticOrmus" }, "metadata": { - "description": "Production-ready workflow orchestration with 64 focused plugins, 87 specialized agents, and 44 tools - optimized for granular installation and minimal token usage", - "version": "1.2.0" + "description": "LibreUIUX: 71 Claude Code plugins for UI/UX-centered development. 5 are original (design-mastery, archetypal-alchemy, mcp-integrations, vibe-coding, libreuiux-hooks) and 66 engineering plugins are derived from wshobson/agents (MIT, Seth Hobson).", + "version": "2.0.0" }, "plugins": [ { @@ -28,17 +27,7 @@ "technical-writing", "tutorials" ], - "category": "documentation", - "strict": false, - "commands": [ - "./commands/doc-generate.md", - "./commands/code-explain.md" - ], - "agents": [ - "./agents/docs-architect.md", - "./agents/tutorial-engineer.md", - "./agents/code-reviewer.md" - ] + "category": "documentation" }, { "name": "debugging-toolkit", @@ -58,15 +47,7 @@ "troubleshooting", "essential" ], - "category": "development", - "strict": false, - "commands": [ - "./commands/smart-debug.md" - ], - "agents": [ - "./agents/debugger.md", - "./agents/dx-optimizer.md" - ] + "category": "development" }, { "name": "git-pr-workflows", @@ -87,16 +68,7 @@ "onboarding", "essential" ], - "category": "workflows", - "strict": false, - "commands": [ - "./commands/pr-enhance.md", - "./commands/onboard.md", - "./commands/git-workflow.md" - ], - "agents": [ - "./agents/code-reviewer.md" - ] + "category": "workflows" }, { "name": "backend-development", @@ -120,24 +92,7 @@ "workflow-orchestration", "distributed-systems" ], - "category": "development", - "strict": false, - "commands": [ - "./commands/feature-development.md" - ], - "agents": [ - "./agents/backend-architect.md", - "./agents/graphql-architect.md", - "./agents/tdd-orchestrator.md", - "./agents/temporal-python-pro.md" - ], - "skills": [ - "./skills/api-design-principles", - "./skills/architecture-patterns", - "./skills/microservices-patterns", - "./skills/workflow-orchestration-patterns", - "./skills/temporal-python-testing" - ] + "category": "development" }, { "name": "frontend-mobile-development", @@ -158,15 +113,7 @@ "ui", "cross-platform" ], - "category": "development", - "strict": false, - "commands": [ - "./commands/component-scaffold.md" - ], - "agents": [ - "./agents/frontend-developer.md", - "./agents/mobile-developer.md" - ] + "category": "development" }, { "name": "full-stack-orchestration", @@ -187,17 +134,7 @@ "security", "testing" ], - "category": "workflows", - "strict": false, - "commands": [ - "./commands/full-stack-feature.md" - ], - "agents": [ - "./agents/test-automator.md", - "./agents/security-auditor.md", - "./agents/performance-engineer.md", - "./agents/deployment-engineer.md" - ] + "category": "workflows" }, { "name": "unit-testing", @@ -218,15 +155,7 @@ "javascript", "automation" ], - "category": "testing", - "strict": false, - "commands": [ - "./commands/test-generate.md" - ], - "agents": [ - "./agents/test-automator.md", - "./agents/debugger.md" - ] + "category": "testing" }, { "name": "tdd-workflows", @@ -246,18 +175,7 @@ "workflow", "red-green-refactor" ], - "category": "workflows", - "strict": false, - "commands": [ - "./commands/tdd-cycle.md", - "./commands/tdd-red.md", - "./commands/tdd-green.md", - "./commands/tdd-refactor.md" - ], - "agents": [ - "./agents/tdd-orchestrator.md", - "./agents/code-reviewer.md" - ] + "category": "workflows" }, { "name": "code-review-ai", @@ -277,14 +195,7 @@ "ai-analysis", "quality" ], - "category": "quality", - "strict": false, - "commands": [ - "./commands/ai-review.md" - ], - "agents": [ - "./agents/architect-review.md" - ] + "category": "quality" }, { "name": "code-refactoring", @@ -304,17 +215,7 @@ "technical-debt", "cleanup" ], - "category": "utilities", - "strict": false, - "commands": [ - "./commands/refactor-clean.md", - "./commands/tech-debt.md", - "./commands/context-restore.md" - ], - "agents": [ - "./agents/legacy-modernizer.md", - "./agents/code-reviewer.md" - ] + "category": "utilities" }, { "name": "dependency-management", @@ -335,14 +236,7 @@ "auditing", "upgrades" ], - "category": "utilities", - "strict": false, - "commands": [ - "./commands/deps-audit.md" - ], - "agents": [ - "./agents/legacy-modernizer.md" - ] + "category": "utilities" }, { "name": "error-debugging", @@ -362,17 +256,7 @@ "diagnostics", "troubleshooting" ], - "category": "utilities", - "strict": false, - "commands": [ - "./commands/error-analysis.md", - "./commands/error-trace.md", - "./commands/multi-agent-review.md" - ], - "agents": [ - "./agents/debugger.md", - "./agents/error-detective.md" - ] + "category": "utilities" }, { "name": "team-collaboration", @@ -392,15 +276,7 @@ "standup", "issue-management" ], - "category": "utilities", - "strict": false, - "commands": [ - "./commands/issue.md", - "./commands/standup-notes.md" - ], - "agents": [ - "./agents/dx-optimizer.md" - ] + "category": "utilities" }, { "name": "llm-application-dev", @@ -422,23 +298,7 @@ "gpt", "claude" ], - "category": "ai-ml", - "strict": false, - "commands": [ - "./commands/langchain-agent.md", - "./commands/ai-assistant.md", - "./commands/prompt-optimize.md" - ], - "agents": [ - "./agents/ai-engineer.md", - "./agents/prompt-engineer.md" - ], - "skills": [ - "./skills/langchain-architecture", - "./skills/llm-evaluation", - "./skills/prompt-engineering-patterns", - "./skills/rag-implementation" - ] + "category": "ai-ml" }, { "name": "agent-orchestration", @@ -458,15 +318,7 @@ "ai-agents", "optimization" ], - "category": "ai-ml", - "strict": false, - "commands": [ - "./commands/multi-agent-optimize.md", - "./commands/improve-agent.md" - ], - "agents": [ - "./agents/context-manager.md" - ] + "category": "ai-ml" }, { "name": "context-management", @@ -486,15 +338,7 @@ "conversation", "memory" ], - "category": "ai-ml", - "strict": false, - "commands": [ - "./commands/context-save.md", - "./commands/context-restore.md" - ], - "agents": [ - "./agents/context-manager.md" - ] + "category": "ai-ml" }, { "name": "machine-learning-ops", @@ -516,19 +360,7 @@ "pytorch", "mlflow" ], - "category": "ai-ml", - "strict": false, - "commands": [ - "./commands/ml-pipeline.md" - ], - "agents": [ - "./agents/data-scientist.md", - "./agents/ml-engineer.md", - "./agents/mlops-engineer.md" - ], - "skills": [ - "./skills/ml-pipeline-workflow" - ] + "category": "ai-ml" }, { "name": "data-engineering", @@ -549,16 +381,7 @@ "data-warehouse", "batch-processing" ], - "category": "data", - "strict": false, - "commands": [ - "./commands/data-driven-feature.md", - "./commands/data-pipeline.md" - ], - "agents": [ - "./agents/data-engineer.md", - "./agents/backend-architect.md" - ] + "category": "data" }, { "name": "incident-response", @@ -578,16 +401,7 @@ "sre", "troubleshooting" ], - "category": "operations", - "strict": false, - "commands": [ - "./commands/incident-response.md", - "./commands/smart-fix.md" - ], - "agents": [ - "./agents/incident-responder.md", - "./agents/devops-troubleshooter.md" - ] + "category": "operations" }, { "name": "error-diagnostics", @@ -607,17 +421,7 @@ "root-cause", "debugging" ], - "category": "operations", - "strict": false, - "commands": [ - "./commands/error-trace.md", - "./commands/error-analysis.md", - "./commands/smart-debug.md" - ], - "agents": [ - "./agents/debugger.md", - "./agents/error-detective.md" - ] + "category": "operations" }, { "name": "distributed-debugging", @@ -637,15 +441,7 @@ "debugging", "observability" ], - "category": "operations", - "strict": false, - "commands": [ - "./commands/debug-trace.md" - ], - "agents": [ - "./agents/error-detective.md", - "./agents/devops-troubleshooter.md" - ] + "category": "operations" }, { "name": "observability-monitoring", @@ -669,24 +465,7 @@ "prometheus", "grafana" ], - "category": "operations", - "strict": false, - "commands": [ - "./commands/monitor-setup.md", - "./commands/slo-implement.md" - ], - "agents": [ - "./agents/observability-engineer.md", - "./agents/performance-engineer.md", - "./agents/database-optimizer.md", - "./agents/network-engineer.md" - ], - "skills": [ - "./skills/distributed-tracing", - "./skills/grafana-dashboards", - "./skills/prometheus-configuration", - "./skills/slo-implementation" - ] + "category": "operations" }, { "name": "deployment-strategies", @@ -707,13 +486,7 @@ "canary", "blue-green" ], - "category": "infrastructure", - "strict": false, - "commands": [], - "agents": [ - "./agents/deployment-engineer.md", - "./agents/terraform-specialist.md" - ] + "category": "infrastructure" }, { "name": "deployment-validation", @@ -733,14 +506,7 @@ "configuration", "deployment-safety" ], - "category": "infrastructure", - "strict": false, - "commands": [ - "./commands/config-validate.md" - ], - "agents": [ - "./agents/cloud-architect.md" - ] + "category": "infrastructure" }, { "name": "kubernetes-operations", @@ -762,18 +528,7 @@ "argocd", "gitops" ], - "category": "infrastructure", - "strict": false, - "commands": [], - "agents": [ - "./agents/kubernetes-architect.md" - ], - "skills": [ - "./skills/gitops-workflow", - "./skills/helm-chart-scaffolding", - "./skills/k8s-manifest-generator", - "./skills/k8s-security-policies" - ] + "category": "infrastructure" }, { "name": "cloud-infrastructure", @@ -796,23 +551,7 @@ "terraform", "infrastructure" ], - "category": "infrastructure", - "strict": false, - "commands": [], - "agents": [ - "./agents/cloud-architect.md", - "./agents/kubernetes-architect.md", - "./agents/hybrid-cloud-architect.md", - "./agents/terraform-specialist.md", - "./agents/network-engineer.md", - "./agents/deployment-engineer.md" - ], - "skills": [ - "./skills/cost-optimization", - "./skills/hybrid-cloud-networking", - "./skills/multi-cloud-architecture", - "./skills/terraform-module-library" - ] + "category": "infrastructure" }, { "name": "cicd-automation", @@ -833,24 +572,7 @@ "github-actions", "gitlab-ci" ], - "category": "infrastructure", - "strict": false, - "commands": [ - "./commands/workflow-automate.md" - ], - "agents": [ - "./agents/deployment-engineer.md", - "./agents/devops-troubleshooter.md", - "./agents/kubernetes-architect.md", - "./agents/cloud-architect.md", - "./agents/terraform-specialist.md" - ], - "skills": [ - "./skills/deployment-pipeline-design", - "./skills/github-actions-templates", - "./skills/gitlab-ci-patterns", - "./skills/secrets-management" - ] + "category": "infrastructure" }, { "name": "application-performance", @@ -870,16 +592,7 @@ "optimization", "core-web-vitals" ], - "category": "performance", - "strict": false, - "commands": [ - "./commands/performance-optimization.md" - ], - "agents": [ - "./agents/performance-engineer.md", - "./agents/frontend-developer.md", - "./agents/observability-engineer.md" - ] + "category": "performance" }, { "name": "database-cloud-optimization", @@ -899,17 +612,7 @@ "query-tuning", "scalability" ], - "category": "performance", - "strict": false, - "commands": [ - "./commands/cost-optimize.md" - ], - "agents": [ - "./agents/database-optimizer.md", - "./agents/database-architect.md", - "./agents/backend-architect.md", - "./agents/cloud-architect.md" - ] + "category": "performance" }, { "name": "comprehensive-review", @@ -930,17 +633,7 @@ "security", "best-practices" ], - "category": "quality", - "strict": false, - "commands": [ - "./commands/full-review.md", - "./commands/pr-enhance.md" - ], - "agents": [ - "./agents/code-reviewer.md", - "./agents/architect-review.md", - "./agents/security-auditor.md" - ] + "category": "quality" }, { "name": "performance-testing-review", @@ -959,16 +652,7 @@ "test-coverage", "quality-analysis" ], - "category": "quality", - "strict": false, - "commands": [ - "./commands/ai-review.md", - "./commands/multi-agent-review.md" - ], - "agents": [ - "./agents/performance-engineer.md", - "./agents/test-automator.md" - ] + "category": "quality" }, { "name": "framework-migration", @@ -989,23 +673,7 @@ "angular", "react" ], - "category": "modernization", - "strict": false, - "commands": [ - "./commands/legacy-modernize.md", - "./commands/code-migrate.md", - "./commands/deps-upgrade.md" - ], - "agents": [ - "./agents/legacy-modernizer.md", - "./agents/architect-review.md" - ], - "skills": [ - "./skills/angular-migration", - "./skills/database-migration", - "./skills/dependency-upgrade", - "./skills/react-modernization" - ] + "category": "modernization" }, { "name": "codebase-cleanup", @@ -1025,17 +693,7 @@ "refactoring", "dependencies" ], - "category": "modernization", - "strict": false, - "commands": [ - "./commands/deps-audit.md", - "./commands/tech-debt.md", - "./commands/refactor-clean.md" - ], - "agents": [ - "./agents/test-automator.md", - "./agents/code-reviewer.md" - ] + "category": "modernization" }, { "name": "database-design", @@ -1055,16 +713,7 @@ "sql", "data-modeling" ], - "category": "database", - "strict": false, - "commands": [], - "agents": [ - "./agents/database-architect.md", - "./agents/sql-pro.md" - ], - "skills": [ - "./skills/postgresql" - ] + "category": "database" }, { "name": "database-migrations", @@ -1085,16 +734,7 @@ "mysql", "mongodb" ], - "category": "database", - "strict": false, - "commands": [ - "./commands/sql-migrations.md", - "./commands/migration-observability.md" - ], - "agents": [ - "./agents/database-optimizer.md", - "./agents/database-admin.md" - ] + "category": "database" }, { "name": "security-scanning", @@ -1115,19 +755,7 @@ "owasp", "devsecops" ], - "category": "security", - "strict": false, - "commands": [ - "./commands/security-hardening.md", - "./commands/security-sast.md", - "./commands/security-dependencies.md" - ], - "agents": [ - "./agents/security-auditor.md" - ], - "skills": [ - "./skills/sast-configuration" - ] + "category": "security" }, { "name": "security-compliance", @@ -1149,14 +777,7 @@ "secrets", "regulatory" ], - "category": "security", - "strict": false, - "commands": [ - "./commands/compliance-check.md" - ], - "agents": [ - "./agents/security-auditor.md" - ] + "category": "security" }, { "name": "backend-api-security", @@ -1177,13 +798,7 @@ "jwt", "oauth" ], - "category": "security", - "strict": false, - "commands": [], - "agents": [ - "./agents/backend-security-coder.md", - "./agents/backend-architect.md" - ] + "category": "security" }, { "name": "frontend-mobile-security", @@ -1204,16 +819,7 @@ "csrf", "csp" ], - "category": "security", - "strict": false, - "commands": [ - "./commands/xss-scan.md" - ], - "agents": [ - "./agents/frontend-security-coder.md", - "./agents/mobile-security-coder.md", - "./agents/frontend-developer.md" - ] + "category": "security" }, { "name": "data-validation-suite", @@ -1234,12 +840,7 @@ "pydantic", "jsonschema" ], - "category": "data", - "strict": false, - "commands": [], - "agents": [ - "./agents/backend-security-coder.md" - ] + "category": "data" }, { "name": "api-scaffolding", @@ -1261,18 +862,7 @@ "django", "express" ], - "category": "api", - "strict": false, - "commands": [], - "agents": [ - "./agents/backend-architect.md", - "./agents/graphql-architect.md", - "./agents/fastapi-pro.md", - "./agents/django-pro.md" - ], - "skills": [ - "./skills/fastapi-templates" - ] + "category": "api" }, { "name": "api-testing-observability", @@ -1293,14 +883,7 @@ "swagger", "observability" ], - "category": "api", - "strict": false, - "commands": [ - "./commands/api-mock.md" - ], - "agents": [ - "./agents/api-documenter.md" - ] + "category": "api" }, { "name": "seo-content-creation", @@ -1320,14 +903,7 @@ "content-planning", "content-audit" ], - "category": "marketing", - "strict": false, - "commands": [], - "agents": [ - "./agents/seo-content-writer.md", - "./agents/seo-content-planner.md", - "./agents/seo-content-auditor.md" - ] + "category": "marketing" }, { "name": "seo-technical-optimization", @@ -1348,15 +924,7 @@ "schema-markup", "snippets" ], - "category": "marketing", - "strict": false, - "commands": [], - "agents": [ - "./agents/seo-meta-optimizer.md", - "./agents/seo-keyword-strategist.md", - "./agents/seo-structure-architect.md", - "./agents/seo-snippet-hunter.md" - ] + "category": "marketing" }, { "name": "seo-analysis-monitoring", @@ -1377,14 +945,7 @@ "authority", "monitoring" ], - "category": "marketing", - "strict": false, - "commands": [], - "agents": [ - "./agents/seo-content-refresher.md", - "./agents/seo-cannibalization-detector.md", - "./agents/seo-authority-builder.md" - ] + "category": "marketing" }, { "name": "documentation-generation", @@ -1406,18 +967,7 @@ "swagger", "mermaid" ], - "category": "documentation", - "strict": false, - "commands": [ - "./commands/doc-generate.md" - ], - "agents": [ - "./agents/docs-architect.md", - "./agents/api-documenter.md", - "./agents/mermaid-expert.md", - "./agents/tutorial-engineer.md", - "./agents/reference-builder.md" - ] + "category": "documentation" }, { "name": "multi-platform-apps", @@ -1439,19 +989,7 @@ "react-native", "flutter" ], - "category": "development", - "strict": false, - "commands": [ - "./commands/multi-platform.md" - ], - "agents": [ - "./agents/mobile-developer.md", - "./agents/flutter-expert.md", - "./agents/ios-developer.md", - "./agents/frontend-developer.md", - "./agents/backend-architect.md", - "./agents/ui-ux-designer.md" - ] + "category": "development" }, { "name": "business-analytics", @@ -1473,12 +1011,7 @@ "reporting", "bi" ], - "category": "business", - "strict": false, - "commands": [], - "agents": [ - "./agents/business-analyst.md" - ] + "category": "business" }, { "name": "hr-legal-compliance", @@ -1501,13 +1034,7 @@ "hipaa", "policies" ], - "category": "business", - "strict": false, - "commands": [], - "agents": [ - "./agents/hr-pro.md", - "./agents/legal-advisor.md" - ] + "category": "business" }, { "name": "customer-sales-automation", @@ -1528,13 +1055,7 @@ "email-campaigns", "automation" ], - "category": "business", - "strict": false, - "commands": [], - "agents": [ - "./agents/customer-support.md", - "./agents/sales-automator.md" - ] + "category": "business" }, { "name": "content-marketing", @@ -1554,13 +1075,7 @@ "marketing-strategy", "social-media" ], - "category": "marketing", - "strict": false, - "commands": [], - "agents": [ - "./agents/content-marketer.md", - "./agents/search-specialist.md" - ] + "category": "marketing" }, { "name": "blockchain-web3", @@ -1583,18 +1098,7 @@ "nft", "smart-contracts" ], - "category": "blockchain", - "strict": false, - "commands": [], - "agents": [ - "./agents/blockchain-developer.md" - ], - "skills": [ - "./skills/defi-protocol-templates", - "./skills/nft-standards", - "./skills/solidity-security", - "./skills/web3-testing" - ] + "category": "blockchain" }, { "name": "quantitative-trading", @@ -1615,13 +1119,7 @@ "algorithmic-trading", "risk-management" ], - "category": "finance", - "strict": false, - "commands": [], - "agents": [ - "./agents/quant-analyst.md", - "./agents/risk-manager.md" - ] + "category": "finance" }, { "name": "payment-processing", @@ -1644,18 +1142,7 @@ "subscriptions", "pci" ], - "category": "payments", - "strict": false, - "commands": [], - "agents": [ - "./agents/payment-integration.md" - ], - "skills": [ - "./skills/billing-automation", - "./skills/paypal-integration", - "./skills/pci-compliance", - "./skills/stripe-integration" - ] + "category": "payments" }, { "name": "game-development", @@ -1677,13 +1164,7 @@ "bukkit", "spigot" ], - "category": "gaming", - "strict": false, - "commands": [], - "agents": [ - "./agents/unity-developer.md", - "./agents/minecraft-bukkit-pro.md" - ] + "category": "gaming" }, { "name": "accessibility-compliance", @@ -1704,14 +1185,7 @@ "compliance", "inclusive-design" ], - "category": "accessibility", - "strict": false, - "commands": [ - "./commands/accessibility-audit.md" - ], - "agents": [ - "./agents/ui-visual-validator.md" - ] + "category": "accessibility" }, { "name": "python-development", @@ -1732,23 +1206,7 @@ "async", "backend" ], - "category": "languages", - "strict": false, - "commands": [ - "./commands/python-scaffold.md" - ], - "agents": [ - "./agents/python-pro.md", - "./agents/django-pro.md", - "./agents/fastapi-pro.md" - ], - "skills": [ - "./skills/async-python-patterns", - "./skills/python-testing-patterns", - "./skills/python-packaging", - "./skills/python-performance-optimization", - "./skills/uv-package-manager" - ] + "category": "languages" }, { "name": "javascript-typescript", @@ -1769,21 +1227,7 @@ "nodejs", "react" ], - "category": "languages", - "strict": false, - "commands": [ - "./commands/typescript-scaffold.md" - ], - "agents": [ - "./agents/javascript-pro.md", - "./agents/typescript-pro.md" - ], - "skills": [ - "./skills/typescript-advanced-types", - "./skills/nodejs-backend-patterns", - "./skills/javascript-testing-patterns", - "./skills/modern-javascript-patterns" - ] + "category": "languages" }, { "name": "systems-programming", @@ -1805,17 +1249,7 @@ "systems-programming", "performance" ], - "category": "languages", - "strict": false, - "commands": [ - "./commands/rust-project.md" - ], - "agents": [ - "./agents/rust-pro.md", - "./agents/golang-pro.md", - "./agents/c-pro.md", - "./agents/cpp-pro.md" - ] + "category": "languages" }, { "name": "jvm-languages", @@ -1837,14 +1271,7 @@ "enterprise", "dotnet" ], - "category": "languages", - "strict": false, - "commands": [], - "agents": [ - "./agents/java-pro.md", - "./agents/scala-pro.md", - "./agents/csharp-pro.md" - ] + "category": "languages" }, { "name": "web-scripting", @@ -1865,13 +1292,7 @@ "wordpress", "web-scripting" ], - "category": "languages", - "strict": false, - "commands": [], - "agents": [ - "./agents/php-pro.md", - "./agents/ruby-pro.md" - ] + "category": "languages" }, { "name": "functional-programming", @@ -1892,12 +1313,7 @@ "otp", "distributed" ], - "category": "languages", - "strict": false, - "commands": [], - "agents": [ - "./agents/elixir-pro.md" - ] + "category": "languages" }, { "name": "julia-development", @@ -1919,13 +1335,7 @@ "data-science", "multiple-dispatch" ], - "category": "languages", - "strict": false, - "commands": [], - "agents": [ - "./agents/julia-pro.md" - ], - "skills": [] + "category": "languages" }, { "name": "arm-cortex-microcontrollers", @@ -1948,12 +1358,7 @@ "teensy", "stm32" ], - "category": "languages", - "strict": false, - "commands": [], - "agents": [ - "./agents/arm-cortex-expert.md" - ] + "category": "languages" }, { "name": "shell-scripting", @@ -1976,18 +1381,7 @@ "shellcheck", "testing" ], - "category": "languages", - "strict": false, - "commands": [], - "agents": [ - "./agents/bash-pro.md", - "./agents/posix-shell-pro.md" - ], - "skills": [ - "./skills/bash-defensive-patterns/SKILL.md", - "./skills/shellcheck-configuration/SKILL.md", - "./skills/bats-testing-patterns/SKILL.md" - ] + "category": "languages" }, { "name": "developer-essentials", @@ -2011,28 +1405,15 @@ "monorepo", "essential" ], - "category": "development", - "strict": false, - "commands": [], - "agents": [], - "skills": [ - "./skills/git-advanced-workflows", - "./skills/sql-optimization-patterns", - "./skills/error-handling-patterns", - "./skills/code-review-excellence", - "./skills/e2e-testing-patterns", - "./skills/auth-implementation-patterns", - "./skills/debugging-strategies", - "./skills/monorepo-management" - ] + "category": "development" }, { "name": "design-mastery", "source": "./plugins/design-mastery", - "description": "Comprehensive design knowledge from timeless principles to legendary masters. Features brand identity commands, design auditing, and deep expertise in visual hierarchy, typography, color theory, Gestalt psychology, and historical design movements. Draws from Saul Bass, Massimo Vignelli, Dieter Rams, Paula Scher, and other design legends.", - "version": "1.0.0", + "description": "Design principles, legendary designers, and historical movements applied to UI work, with agents and workflows for brand identity, design audits, style guides, and premium landing pages.", + "version": "1.1.0", "author": { - "name": "Hermetic Ormus", + "name": "Diego Bodart", "url": "https://github.com/HermeticOrmus" }, "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", @@ -2048,28 +1429,104 @@ "visual-design", "design-principles", "saul-bass", + "massimo-vignelli", "dieter-rams", "bauhaus", - "swiss-design" - ], - "category": "design", - "strict": false, - "commands": [ - "./commands/brand-identity.md", - "./commands/design-audit.md", - "./commands/style-guide.md" - ], - "agents": [ - "./agents/design-master.md", - "./agents/brand-architect.md", - "./agents/visual-historian.md" - ], - "skills": [ - "./skills/design-principles", - "./skills/design-masters", - "./skills/design-movements", - "./skills/brand-systems" - ] + "swiss-design", + "gestalt", + "paula-scher", + "paul-rand", + "design-audit", + "landing-page" + ], + "category": "design" + }, + { + "name": "archetypal-alchemy", + "source": "./plugins/archetypal-alchemy", + "description": "Jungian archetypes and Major Arcana symbolism turned into UI structure and color systems, with commands that generate archetype-driven components and Tailwind palettes.", + "version": "1.0.0", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "archetypes", + "jung", + "tarot", + "color-palettes", + "design-systems", + "tailwind", + "ui-ux" + ], + "category": "design" + }, + { + "name": "mcp-integrations", + "source": "./plugins/mcp-integrations", + "description": "Browser DevTools through MCP for live UI inspection, screenshot-to-code, design token extraction, and visual debugging of running interfaces.", + "version": "1.0.0", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "mcp", + "chrome-devtools", + "browser-automation", + "screenshot-to-code", + "visual-debugging", + "design-tokens" + ], + "category": "design" + }, + { + "name": "vibe-coding", + "source": "./plugins/vibe-coding", + "description": "Rapid, disposable UI prototyping: when to explore fast and when to refine, variant exploration, and how to carry a validated prototype toward production.", + "version": "1.0.0", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "prototyping", + "vibe-coding", + "ui-exploration", + "rapid-iteration", + "ai-assisted-development" + ], + "category": "design" + }, + { + "name": "libreuiux-hooks", + "source": "./plugins/libreuiux-hooks", + "description": "Optional hooks for UI projects: one line of stack context at session start, a confirmation prompt before editing secrets files, and accessibility and design-system hints after UI file edits.", + "version": "1.0.0", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "hooks", + "accessibility", + "design-systems", + "ui-ux", + "wcag" + ], + "category": "design" } ] } diff --git a/.github/ISSUE_TEMPLATE/feedback.yml b/.github/ISSUE_TEMPLATE/feedback.yml new file mode 100644 index 0000000..fb3e083 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feedback.yml @@ -0,0 +1,41 @@ +name: Feedback +description: Tell us what worked, what is missing, and what to build next. +title: "[Feedback] " +labels: ["feedback"] +body: + - type: markdown + attributes: + value: | + Thanks for trying this. Every piece of feedback gets read and answered. When feedback turns into a change, the release notes say so, and credit you if you tick the box at the bottom. + - type: input + id: using-for + attributes: + label: What are you using it for? + placeholder: "redesigning a dashboard, building a component library" + validations: + required: true + - type: input + id: plugins + attributes: + label: Which plugins, agents, or skills did you use? + placeholder: "Names as they appear in /plugin, or 'just browsing'" + - type: textarea + id: worked + attributes: + label: What worked well? + - type: textarea + id: missing + attributes: + label: What is missing, wrong, or got in your way? + validations: + required: true + - type: textarea + id: next + attributes: + label: If you could add one thing next, what would it be? + - type: checkboxes + id: credit + attributes: + label: Credit + options: + - label: If this feedback leads to a change, you may credit my GitHub handle in the changelog and release notes. diff --git a/.github/workflows/validate.yml b/.github/workflows/validate.yml new file mode 100644 index 0000000..f909d79 --- /dev/null +++ b/.github/workflows/validate.yml @@ -0,0 +1,37 @@ +name: validate + +on: + push: + branches: [main] + pull_request: + +jobs: + plugins: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v7 + - uses: actions/setup-node@v7 + with: + node-version: 22 + - name: Install the Claude Code CLI + run: npm install -g @anthropic-ai/claude-code + - name: Validate the marketplace manifest + run: claude plugin validate . + - name: Validate every plugin + run: | + set -euo pipefail + for p in $(jq -r '.plugins[].source | strings' .claude-plugin/marketplace.json); do + echo "::group::$p" + claude plugin validate --strict "$p" + echo "::endgroup::" + done + - name: Install every plugin into a clean config + run: | + set -euo pipefail + export CLAUDE_CONFIG_DIR="$RUNNER_TEMP/claude-config" + claude plugin marketplace add "$GITHUB_WORKSPACE" + mk=$(jq -r '.name' .claude-plugin/marketplace.json) + for p in $(jq -r '.plugins[].name' .claude-plugin/marketplace.json); do + claude plugin install "$p@$mk" + done + claude plugin list diff --git a/.gitignore b/.gitignore index 99fefbd..ceb07d0 100644 --- a/.gitignore +++ b/.gitignore @@ -46,3 +46,7 @@ coverage/ .cache/ .temp/ .tmp/ + +# Eval results (claude plugin eval) +plugins/*/evals/results/ +evals/results/ diff --git a/CHANGELOG.md b/CHANGELOG.md index 424ead4..72eac9c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,7 +6,40 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). ## [Unreleased] +## [2.0.0] - 2026-09-30 + +A major release because the marketplace name changes. Every plugin keeps its name, and nothing is removed. See "Migrating from 1.x" in the README. + +### Changed (breaking) + +- The marketplace is now named `libreuiux` (it was `claude-code-workflows`). The old name is also the name of [wshobson/agents](https://github.com/wshobson/agents), so anyone who had that marketplace installed could not add this one. Install plugins as `@libreuiux`. If `/plugin marketplace list` shows `claude-code-workflows` pointing to this repository, remove it and add this repository again; if it points to wshobson/agents, leave it. +- `setup.sh` now installs the plugins through the Claude Code CLI (`--list`, `--only`, `--scope`, `--uninstall`). The old interactive project bootstrap is unchanged and moved to `bootstrap.sh`. + +### Added + +- `.claude-plugin/plugin.json` for all 71 plugins, so `claude plugin validate plugins/` passes for each (with `--strict`, no warnings). +- Three original plugins that were on disk but not installable are now in the marketplace: `archetypal-alchemy`, `mcp-integrations`, `vibe-coding`. +- `libreuiux-hooks`, an optional plugin that registers the UI/UX hooks: one line of stack context at session start in UI projects, a confirmation prompt before editing `.env`, key, certificate, or credentials files, and accessibility and design-system hints after UI file edits. The scripts read Claude Code's JSON hook input with `jq`, use the documented output format, and write no files. The original scripts stay in `hooks/`. +- design-mastery 1.1.0, synced with [design-mastery-claude-code](https://github.com/HermeticOrmus/design-mastery-claude-code) v1.1.0: 24 new reference files (masters, movements, principles, brand systems; 27 in total), factual corrections, routing descriptions, and an eval suite for `claude plugin eval plugins/design-mastery`. +- `NOTICE.md`, which lists the 66 plugins derived from wshobson/agents and reproduces the upstream MIT license. +- A GitHub Actions workflow that validates the marketplace and every plugin, then installs every plugin into a clean config. +- A feedback issue form, and a Feedback section in the README that links it and GitHub Discussions. + +### Changed + +- The marketplace owner is Diego Bodart, and its description states what the repository actually contains (71 plugins: 5 original, 66 derived from wshobson/agents). The old description was upstream's ("64 focused plugins, 87 specialized agents, and 44 tools"). +- Marketplace entries drop `strict: false` and their component lists; each plugin's plugin.json is the manifest and Claude Code discovers `agents/`, `commands/`, and `skills/` itself. +- Every command in the derived plugins that had no frontmatter (67 files) now has a `description` and, where it takes input, an `argument-hint`, so it shows up with a description in `/help`. The command text is unchanged. +- The original plugins (design-mastery, archetypal-alchemy, mcp-integrations, vibe-coding) and the three UI skills inside derived plugins (`ui-agent-patterns`, `design-system-context`, `prompt-engineering-ui`) have routing descriptions ("Use this agent when", "Use when"). Their agents use `model: inherit`. +- README: counts match the manifests (71 plugins, 152 agent definitions of which 93 are distinct, 76 command files of which 65 are distinct, 74 skills, 3 hooks), install instructions for Claude Code, the terminal, and `./setup.sh`, a "Migrating from 1.x" note, a repository tree that matches the files, and an Acknowledgments section. + ### Fixed + +- Credit for the upstream work: LICENSE now carries `Copyright (c) 2024 Seth Hobson` for the derived plugins next to the existing notice, NOTICE.md lists them, and the README credits Seth Hobson and wshobson/agents. + +### Also in this release (previously listed as Unreleased) + +#### Fixed - Corrected plugin/agent/command/skill counts in README (70 plugins, 152 agents, 76 commands, 74 skills) - Fixed broken internal links (beginner/examples/, modern-component-template.md) - Restored execute permissions on hook scripts @@ -14,7 +47,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). - Fixed git clone URL to point to actual repository - Corrected FUNDING.yml GitHub username -### Added +#### Added - `.gitignore` for standard project hygiene - Pull request template (`.github/PULL_REQUEST_TEMPLATE.md`) - This CHANGELOG diff --git a/LICENSE b/LICENSE index cc17fc7..dd32dc5 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,7 @@ MIT License Copyright (c) 2025-2026 Hermetic Ormus +Copyright (c) 2024 Seth Hobson (the plugins derived from wshobson/agents, listed in NOTICE.md) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/NOTICE.md b/NOTICE.md new file mode 100644 index 0000000..32742a6 --- /dev/null +++ b/NOTICE.md @@ -0,0 +1,118 @@ +# Notice + +LibreUIUX for Claude Code combines original work by Diego Bodart (Hermetic Ormus) with plugins derived from [wshobson/agents](https://github.com/wshobson/agents) by Seth Hobson and its contributors, used under the MIT License. + +## Plugins derived from wshobson/agents + +The 66 plugins below come from wshobson/agents, forked in late 2025 (their files match upstream commit `ddbd034`). The author column is the author recorded in that repository's marketplace manifest; plugins by Ryan Snodgrass and the community were contributed to wshobson/agents and are distributed under its license. + +| Plugin | Author in wshobson/agents | +|--------|---------------------------| +| `accessibility-compliance` | Seth Hobson | +| `agent-orchestration` | Seth Hobson | +| `api-scaffolding` | Seth Hobson | +| `api-testing-observability` | Seth Hobson | +| `application-performance` | Seth Hobson | +| `arm-cortex-microcontrollers` | Ryan Snodgrass | +| `backend-api-security` | Seth Hobson | +| `backend-development` | Seth Hobson | +| `blockchain-web3` | Seth Hobson | +| `business-analytics` | Seth Hobson | +| `cicd-automation` | Seth Hobson | +| `cloud-infrastructure` | Seth Hobson | +| `code-documentation` | Seth Hobson | +| `code-refactoring` | Seth Hobson | +| `code-review-ai` | Seth Hobson | +| `codebase-cleanup` | Seth Hobson | +| `comprehensive-review` | Seth Hobson | +| `content-marketing` | Seth Hobson | +| `context-management` | Seth Hobson | +| `customer-sales-automation` | Seth Hobson | +| `data-engineering` | Seth Hobson | +| `data-validation-suite` | Seth Hobson | +| `database-cloud-optimization` | Seth Hobson | +| `database-design` | Seth Hobson | +| `database-migrations` | Seth Hobson | +| `debugging-toolkit` | Seth Hobson | +| `dependency-management` | Seth Hobson | +| `deployment-strategies` | Seth Hobson | +| `deployment-validation` | Seth Hobson | +| `developer-essentials` | Seth Hobson | +| `distributed-debugging` | Seth Hobson | +| `documentation-generation` | Seth Hobson | +| `error-debugging` | Seth Hobson | +| `error-diagnostics` | Seth Hobson | +| `framework-migration` | Seth Hobson | +| `frontend-mobile-development` | Seth Hobson | +| `frontend-mobile-security` | Seth Hobson | +| `full-stack-orchestration` | Seth Hobson | +| `functional-programming` | Seth Hobson | +| `game-development` | Seth Hobson | +| `git-pr-workflows` | Seth Hobson | +| `hr-legal-compliance` | Seth Hobson | +| `incident-response` | Seth Hobson | +| `javascript-typescript` | Seth Hobson | +| `julia-development` | Community Contribution | +| `jvm-languages` | Seth Hobson | +| `kubernetes-operations` | Seth Hobson | +| `llm-application-dev` | Seth Hobson | +| `machine-learning-ops` | Seth Hobson | +| `multi-platform-apps` | Seth Hobson | +| `observability-monitoring` | Seth Hobson | +| `payment-processing` | Seth Hobson | +| `performance-testing-review` | Seth Hobson | +| `python-development` | Seth Hobson | +| `quantitative-trading` | Seth Hobson | +| `security-compliance` | Seth Hobson | +| `security-scanning` | Seth Hobson | +| `seo-analysis-monitoring` | Seth Hobson | +| `seo-content-creation` | Seth Hobson | +| `seo-technical-optimization` | Seth Hobson | +| `shell-scripting` | Ryan Snodgrass | +| `systems-programming` | Seth Hobson | +| `tdd-workflows` | Seth Hobson | +| `team-collaboration` | Seth Hobson | +| `unit-testing` | Seth Hobson | +| `web-scripting` | Seth Hobson | + +Changes made in this repository to those plugins: + +- A README.md for each plugin. +- A `.claude-plugin/plugin.json` for each plugin, with the values from the marketplace entry. +- YAML frontmatter (`description`, and `argument-hint` where the command takes input) on commands that had none, so Claude Code can list and route them. The command text itself is unchanged. +- Small edits to twenty agent and command files: year references moved forward by one year (for example 2024/2025 to 2025/2026), and the Python and Julia version floors raised (3.13+, 1.11+). +- Three original skills added inside derived plugins, which are Diego Bodart's work, not Seth Hobson's: `agent-orchestration/skills/ui-agent-patterns`, `context-management/skills/design-system-context`, and `llm-application-dev/skills/prompt-engineering-ui`. + +## Original plugins + +`design-mastery`, `archetypal-alchemy`, `mcp-integrations`, `vibe-coding`, and `libreuiux-hooks` are original to this repository, as are the learning paths (`beginner/`, `intermediate/`, `advanced/`), `templates/`, `resources/`, `hooks/`, and the root `.claude/` commands and agent. + +## Upstream license + +The derived plugins are covered by the upstream MIT License, reproduced here as required by its terms: + +``` +MIT License + +Copyright (c) 2024 Seth Hobson + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. +``` + +The repository as a whole is licensed under the MIT License in [LICENSE](LICENSE), which carries both copyright notices. diff --git a/README.md b/README.md index f968657..15f020d 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@

LibreUIUX Claude Code

- Complete UI/UX system for Claude Code -- 152 agents, 70 plugins, 76 commands, 74 skills + Complete UI/UX system for Claude Code -- 71 plugins, 152 agents, 76 commands, 74 skills, 3 hooks

@@ -40,9 +40,10 @@ He described Claude Code as *"the first convincing demonstration of what an LLM | New Stack Component | LibreUIUX Provides | |---------------------|-------------------| | **Skills** | 74 specialized skills (accessibility, animation, design systems, etc.) | -| **Agents** | 152 task-specific agents (UI validator, design critic, responsive checker, etc.) | -| **Commands** | 76 slash commands for common UI/UX workflows | -| **Plugins** | 70 domain plugins (frontend, accessibility, design mastery, etc.) | +| **Agents** | 152 agent definitions across the plugins (93 distinct agents; shared ones such as `code-reviewer` ship in several plugins) | +| **Commands** | 76 slash commands across the plugins (65 distinct) | +| **Plugins** | 71 installable plugins (frontend, accessibility, design mastery, etc.) | +| **Hooks** | 3 optional hooks in `libreuiux-hooks` (stack context, secrets-file confirmation, accessibility hints) | | **Workflows** | Beginner to advanced learning paths | This isn't just a prompt library. It's infrastructure for the new way we build software with AI. @@ -53,10 +54,11 @@ This isn't just a prompt library. It's infrastructure for the new way we build s ``` LibreUIUX-Claude-Code/ -├── 70 Plugins # Domain-specific collections -├── 152 Agents # Task-specialized AI personas -├── 76 Commands # Slash commands for Claude Code +├── 71 Plugins # Installable from the libreuiux marketplace +├── 152 Agents # Task-specialized AI personas (93 distinct) +├── 76 Commands # Slash commands for Claude Code (65 distinct) ├── 74 Skills # Reusable capability modules +├── 3 Hooks # Optional, in the libreuiux-hooks plugin ├── 3 Skill Levels # Beginner → Intermediate → Advanced └── Templates # Ready-to-use configurations ``` @@ -83,6 +85,32 @@ LibreUIUX-Claude-Code/ ## Quick Start +### Install from Claude Code + +``` +/plugin marketplace add HermeticOrmus/LibreUIUX-Claude-Code +/plugin install design-mastery@libreuiux +``` + +Install any other plugin the same way (`/plugin install accessibility-compliance@libreuiux`), or browse them all with `/plugin`. The same thing from a terminal: + +```bash +claude plugin marketplace add HermeticOrmus/LibreUIUX-Claude-Code +claude plugin install design-mastery@libreuiux +``` + +From a clone, `./setup.sh` installs every plugin through the Claude Code CLI (`./setup.sh --list` to see them, `--only design-mastery,accessibility-compliance` for a subset, `--scope project` for one project, `--uninstall` to remove them). The optional hooks are one more plugin: `/plugin install libreuiux-hooks@libreuiux`. Restart Claude Code after installing. + +To drop a LibreUIUX `CLAUDE.md` template and config into a project instead, run `./bootstrap.sh` from inside that project (this was `setup.sh` before 2.0.0). + +### Migrating from 1.x + +Version 2.0.0 renames the marketplace from `claude-code-workflows` to `libreuiux`. The old name is also the name of [wshobson/agents](https://github.com/wshobson/agents), so anyone with that marketplace installed could not add this one. The plugins keep their names. + +1. Run `/plugin marketplace list` (or `claude plugin marketplace list` in a terminal) and check which repository `claude-code-workflows` points to. +2. Only if it points to `HermeticOrmus/LibreUIUX-Claude-Code`, remove it: `/plugin marketplace remove claude-code-workflows`. If it points to `wshobson/agents`, leave it alone. +3. Add this repository again: `/plugin marketplace add HermeticOrmus/LibreUIUX-Claude-Code`, then reinstall what you use as `@libreuiux`. + Prefer the dedicated walkthrough: **[QUICK_START.md](./QUICK_START.md)** (about 5 minutes). ### Installation Paths @@ -209,7 +237,7 @@ This repository provides solutions for **all skill levels**: LibreUIUX-Claude-Code/ ├── README.md # You are here │ -├── plugins/ # 68 domain-specific plugin collections +├── plugins/ # 71 installable plugins │ ├── design-mastery/ # UI/UX design expertise │ │ ├── agents/ # Specialized AI agents │ │ ├── commands/ # Slash commands @@ -218,48 +246,53 @@ LibreUIUX-Claude-Code/ │ ├── frontend-mobile-development/ # React, Vue, React Native, etc. │ ├── backend-development/ # APIs, databases, architecture │ ├── cicd-automation/ # Deployment, pipelines, DevOps +│ ├── libreuiux-hooks/ # Optional hooks (session context, secrets, a11y hints) │ └── ... (65 more plugins) # See full list below │ ├── beginner/ # Start here if new │ ├── README.md # Beginner guide overview │ ├── design-vocabulary.md # Learn the language of modern UI -│ ├── prompts/ # Ready-to-use prompt templates +│ ├── prompts/ # Ready-to-use prompt templates (button, card, form, nav) │ └── checklist.md # Pre-request checklist │ ├── intermediate/ # Build systematic workflows │ ├── README.md # Intermediate guide overview -│ ├── design-systems/ # Complete design system templates -│ ├── claude-md-templates/ # CLAUDE.md file templates -│ ├── component-libraries/ # Integration guides (Shadcn, Aceternity) -│ ├── workflows/ # Step-by-step workflows -│ └── examples/ # Real project examples +│ ├── design-systems/ # Design system template (modern web app) +│ └── workflows/ # Iteration workflow │ ├── advanced/ # Pro-level automation -│ ├── README.md # Advanced guide overview -│ ├── mcp-servers/ # MCP server configurations -│ ├── slash-commands/ # Custom Claude Code commands -│ ├── automation/ # Automated workflows -│ └── examples/ # Production-level examples +│ └── README.md # Advanced guide overview │ ├── resources/ # Curated resources │ ├── component-libraries.md # Library comparisons & links -│ ├── inspiration/ # Design inspiration sources │ ├── tools.md # Recommended tools │ └── github-repos.md # Curated GitHub repositories │ -├── templates/ # Copy-paste templates +├── templates/ # Copy-paste CLAUDE.md templates │ ├── CLAUDE.md # Template for project root -│ ├── design-brief.md # Design brief template -│ └── component-spec.md # Component specification template +│ ├── CLAUDE.minimal.md +│ ├── CLAUDE.mobile-first.md +│ ├── CLAUDE.modern-webapp.md +│ └── CLAUDE.saas-platform.md +│ +├── hooks/ # Original hook scripts (use the libreuiux-hooks plugin) +├── demo/ # Demo page and checklist +├── setup.sh # Install the plugins through the Claude Code CLI +├── bootstrap.sh # Add a CLAUDE.md template and config to a project +├── NOTICE.md # Credit and license for the wshobson/agents plugins │ -└── .claude/ # Claude Code configuration - └── commands/ # Global slash commands +└── .claude/ # Claude Code configuration for this repo + ├── agents/ + │ └── synthesis-master.md + └── commands/ # Slash commands (copy to ~/.claude/commands to use elsewhere) ├── ui-modern.md ├── ui-critique.md - └── ui-responsive.md + ├── ui-responsive.md + ├── ui-review.md + └── ui-synth.md ``` -### All 70 Plugins +### All 71 Plugins

Click to expand full plugin list @@ -271,7 +304,7 @@ LibreUIUX-Claude-Code/ | api-scaffolding | REST/GraphQL API design | | api-testing-observability | API testing & monitoring | | application-performance | Frontend/backend optimization | -| archetypal-alchemy | Design psychology patterns | +| archetypal-alchemy \* | Design psychology patterns | | arm-cortex-microcontrollers | Embedded systems | | backend-api-security | Auth, validation, security | | backend-development | Server architecture | @@ -296,7 +329,7 @@ LibreUIUX-Claude-Code/ | dependency-management | Package management | | deployment-strategies | Blue-green, canary | | deployment-validation | Deploy verification | -| design-mastery | UI/UX excellence | +| design-mastery \* | UI/UX excellence | | developer-essentials | Core dev workflows | | distributed-debugging | Microservice debugging | | documentation-generation | Auto-docs | @@ -315,9 +348,10 @@ LibreUIUX-Claude-Code/ | julia-development | Julia lang | | jvm-languages | Java, Kotlin, Scala | | kubernetes-operations | K8s management | +| libreuiux-hooks \* | Optional hooks: stack context, secrets-file confirmation, accessibility hints | | llm-application-dev | AI/LLM apps | | machine-learning-ops | MLOps | -| mcp-integrations | MCP server tools & browser DevTools | +| mcp-integrations \* | MCP server tools & browser DevTools | | multi-platform-apps | Cross-platform | | observability-monitoring | Logging, metrics | | payment-processing | Stripe, payments | @@ -334,9 +368,11 @@ LibreUIUX-Claude-Code/ | tdd-workflows | Test-driven dev | | team-collaboration | Team processes | | unit-testing | Testing strategies | -| vibe-coding | Rapid AI-assisted prototyping | +| vibe-coding \* | Rapid AI-assisted prototyping | | web-scripting | Scraping, automation | +\* Original to LibreUIUX. The other 66 plugins derive from [wshobson/agents](https://github.com/wshobson/agents) by Seth Hobson (MIT); see [NOTICE.md](./NOTICE.md). +
--- @@ -439,6 +475,12 @@ The craft grows when knowledge flows. --- +## Feedback + +Starred this? Tell us what worked and what is missing: [open a feedback issue](https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/issues/new?template=feedback.yml). Every piece of feedback gets an answer, and changes that come from it are credited in the release notes. For questions and open-ended ideas, use [GitHub Discussions](https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/discussions). + +--- + ## 🤝 Contributing This is a **knowledge commons**, not just a repository. Every contribution raises our collective understanding of UI/UX development with AI. @@ -539,6 +581,8 @@ The craft grows when knowledge flows. [MIT License](./LICENSE) — free to use in your projects, commercial or otherwise. See [CONTRIBUTING.md](./CONTRIBUTING.md) if you want to improve the commons. +The plugins derived from wshobson/agents keep their original MIT copyright (Copyright (c) 2024 Seth Hobson). [NOTICE.md](./NOTICE.md) lists them and reproduces the upstream license. + --- ## ⭐ Star This Repo @@ -547,6 +591,12 @@ If this helps you build better UIs with Claude Code, give us a star! It helps ot --- +## Acknowledgments + +66 of the 71 plugins here derive from **[wshobson/agents](https://github.com/wshobson/agents)** by **[Seth Hobson](https://github.com/wshobson)**, the Claude Code plugin marketplace this repository was forked from, released under the MIT License. The engineering plugins (backend, testing, DevOps, security, languages, and more), their agents, commands, and skills are his work and that of the wshobson/agents contributors, including Ryan Snodgrass. LibreUIUX adds the UI/UX layer on top: design-mastery, archetypal-alchemy, mcp-integrations, vibe-coding, libreuiux-hooks, the learning paths, and the templates. [NOTICE.md](./NOTICE.md) has the full list and the upstream license. + +--- + ## Attribution & Inspiration The framing of this repository was inspired by [Andrej Karpathy's](https://karpathy.ai/) observations about the transformation of programming in the AI era: diff --git a/bootstrap.sh b/bootstrap.sh new file mode 100644 index 0000000..93f3854 --- /dev/null +++ b/bootstrap.sh @@ -0,0 +1,199 @@ +#!/bin/bash + +# LibreUIUX Setup Script +# Bootstraps a project with LibreUIUX design system configuration + +set -e + +# Colors for output +RED='\033[0;31m' +GREEN='\033[0;32m' +YELLOW='\033[1;33m' +BLUE='\033[0;34m' +NC='\033[0m' # No Color + +# Configuration +LIBREUI_VERSION="1.0.0" +REPO_URL="https://raw.githubusercontent.com/HermeticOrmus/LibreUIUX-Claude-Code/main" + +echo "" +echo -e "${BLUE}╔══════════════════════════════════════╗${NC}" +echo -e "${BLUE}║ LibreUIUX Setup - v${LIBREUI_VERSION} ║${NC}" +echo -e "${BLUE}╚══════════════════════════════════════╝${NC}" +echo "" + +# Check if we're in a project directory +if [ ! -f "package.json" ] && [ ! -f "index.html" ] && [ ! -f "README.md" ]; then + echo -e "${YELLOW}Warning: This doesn't look like a project directory.${NC}" + read -p "Continue anyway? (y/n) " -n 1 -r + echo + if [[ ! $REPLY =~ ^[Yy]$ ]]; then + exit 1 + fi +fi + +# Function to download file +download_file() { + local url=$1 + local dest=$2 + + if command -v curl &> /dev/null; then + curl -fsSL "$url" -o "$dest" 2>/dev/null + elif command -v wget &> /dev/null; then + wget -q "$url" -O "$dest" 2>/dev/null + else + echo -e "${RED}Error: curl or wget required${NC}" + exit 1 + fi +} + +# Step 1: Choose design system +echo -e "${GREEN}Step 1: Choose your design system${NC}" +echo "" +echo " 1) Modern Web App (Shadcn, Tailwind, animations)" +echo " 2) SaaS Platform (Dashboard-focused, data-dense)" +echo " 3) Mobile First (Responsive, touch-friendly)" +echo " 4) Minimal (Clean, content-focused)" +echo "" +read -p "Choose (1-4): " choice + +case $choice in + 1) TEMPLATE="modern-webapp" ;; + 2) TEMPLATE="saas-platform" ;; + 3) TEMPLATE="mobile-first" ;; + 4) TEMPLATE="minimal" ;; + *) TEMPLATE="modern-webapp" ;; +esac + +echo -e "${BLUE}Selected: ${TEMPLATE}${NC}" +echo "" + +# Step 2: Download CLAUDE.md +echo -e "${GREEN}Step 2: Setting up CLAUDE.md${NC}" + +if [ -f "CLAUDE.md" ]; then + echo -e "${YELLOW}CLAUDE.md already exists.${NC}" + read -p "Overwrite? (y/n) " -n 1 -r + echo + if [[ ! $REPLY =~ ^[Yy]$ ]]; then + echo "Keeping existing CLAUDE.md" + else + download_file "${REPO_URL}/templates/CLAUDE.${TEMPLATE}.md" "CLAUDE.md" + echo -e "${GREEN}✓ CLAUDE.md updated${NC}" + fi +else + download_file "${REPO_URL}/templates/CLAUDE.${TEMPLATE}.md" "CLAUDE.md" + echo -e "${GREEN}✓ CLAUDE.md created${NC}" +fi + +# Step 3: Create .libreui-config.yaml +echo "" +echo -e "${GREEN}Step 3: Creating configuration${NC}" + +if [ ! -f ".libreui-config.yaml" ]; then + cat > .libreui-config.yaml << 'EOF' +# LibreUIUX Configuration +# Customize your design system preferences + +version: "1.0.0" + +# Learning level affects prompt suggestions and documentation links +level: beginner # beginner | intermediate | advanced + +# Design system configuration +design_system: + style: modern # modern | minimal | bold | playful + + # Component libraries to reference + libraries: + primary: shadcn-ui # shadcn-ui | radix | headless-ui | mui | chakra + animation: motion-primitives # motion-primitives | framer-motion | react-spring + icons: lucide # lucide | heroicons | phosphor | feather + + # Tailwind preset (if using Tailwind) + tailwind: + enabled: true + preset: default # default | typography | forms + +# Accessibility standards +accessibility: + level: AA # A | AA | AAA + screen_reader: true + keyboard_nav: true + color_contrast: true + +# Component defaults +components: + # Default border radius + radius: md # none | sm | md | lg | xl | full + + # Default animation style + animation: subtle # none | subtle | playful | dramatic + + # Default spacing scale base (in pixels) + spacing_base: 4 + +# Personal preferences (for personalized analogies - optional) +profile: + interests: [] # e.g., ["gaming", "cooking", "music"] + experience: "" # e.g., "2 years frontend development" + +# Enabled modules +modules: + design_vocabulary: true + component_templates: true + accessibility_checker: true + responsive_validator: true + animation_suggestions: true + +# Output preferences +output: + framework: react # react | vue | svelte | html + styling: tailwind # tailwind | css-modules | styled-components | css + typescript: true +EOF + echo -e "${GREEN}✓ .libreui-config.yaml created${NC}" +else + echo -e "${YELLOW}✓ .libreui-config.yaml already exists${NC}" +fi + +# Step 4: Create .claude directory structure (optional) +echo "" +echo -e "${GREEN}Step 4: Setting up commands (optional)${NC}" +read -p "Install custom slash commands? (y/n) " -n 1 -r +echo + +if [[ $REPLY =~ ^[Yy]$ ]]; then + mkdir -p .claude/commands + + # Download commands + download_file "${REPO_URL}/.claude/commands/ui-modern.md" ".claude/commands/ui-modern.md" + download_file "${REPO_URL}/.claude/commands/ui-critique.md" ".claude/commands/ui-critique.md" + download_file "${REPO_URL}/.claude/commands/ui-responsive.md" ".claude/commands/ui-responsive.md" + + echo -e "${GREEN}✓ Commands installed:${NC}" + echo " /ui-modern - Generate modern components" + echo " /ui-critique - Review design quality" + echo " /ui-responsive - Check responsive design" +fi + +# Step 5: Summary +echo "" +echo -e "${GREEN}╔══════════════════════════════════════╗${NC}" +echo -e "${GREEN}║ Setup Complete! ║${NC}" +echo -e "${GREEN}╚══════════════════════════════════════╝${NC}" +echo "" +echo "Files created:" +echo " • CLAUDE.md (${TEMPLATE} design system)" +echo " • .libreui-config.yaml (configuration)" +if [ -d ".claude/commands" ]; then + echo " • .claude/commands/ (custom commands)" +fi +echo "" +echo -e "${BLUE}Next steps:${NC}" +echo " 1. Run 'claude' to start Claude Code" +echo " 2. Try: 'Create a modern button with hover effects'" +echo " 3. Read QUICK_START.md for more commands" +echo "" +echo -e "${YELLOW}Tip: Edit .libreui-config.yaml to customize your design system${NC}" +echo "" diff --git a/hooks/README.md b/hooks/README.md index efd50c7..1b4eb32 100644 --- a/hooks/README.md +++ b/hooks/README.md @@ -2,6 +2,15 @@ > Automated UI/UX quality checks for Claude Code sessions +> **Install these as a plugin instead.** The `libreuiux-hooks` plugin (`plugins/libreuiux-hooks/`) registers the same three hooks for you, reads Claude Code's JSON hook input with `jq`, answers in the documented hook output format, and writes no log files: +> +> ``` +> /plugin marketplace add HermeticOrmus/LibreUIUX-Claude-Code +> /plugin install libreuiux-hooks@libreuiux +> ``` +> +> The scripts in this directory are kept as the original reference implementation. Note that Claude Code reads hook `timeout` values in seconds, so the `5000` and `2000` timeouts in `settings.json` mean that many seconds, not milliseconds. + ## Overview This hooks system provides automated assistance for UI/UX development workflows. It detects design systems, validates accessibility, checks color contrast, and provides contextual guidance when editing UI-related files. diff --git a/plugins/accessibility-compliance/.claude-plugin/plugin.json b/plugins/accessibility-compliance/.claude-plugin/plugin.json new file mode 100644 index 0000000..11252eb --- /dev/null +++ b/plugins/accessibility-compliance/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "accessibility-compliance", + "version": "1.2.0", + "description": "WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "accessibility", + "wcag", + "a11y", + "compliance", + "inclusive-design" + ] +} diff --git a/plugins/accessibility-compliance/commands/accessibility-audit.md b/plugins/accessibility-compliance/commands/accessibility-audit.md index 3b4602b..42e208a 100644 --- a/plugins/accessibility-compliance/commands/accessibility-audit.md +++ b/plugins/accessibility-compliance/commands/accessibility-audit.md @@ -1,3 +1,8 @@ +--- +description: "Audit a UI for WCAG compliance with automated and manual checks, then give remediation steps" +argument-hint: "[URL, component, or path]" +--- + # Accessibility Audit and Testing You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users. diff --git a/plugins/agent-orchestration/.claude-plugin/plugin.json b/plugins/agent-orchestration/.claude-plugin/plugin.json new file mode 100644 index 0000000..9385aa9 --- /dev/null +++ b/plugins/agent-orchestration/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "agent-orchestration", + "version": "1.2.0", + "description": "Multi-agent system optimization, agent improvement workflows, and context management", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "multi-agent", + "orchestration", + "ai-agents", + "optimization" + ] +} diff --git a/plugins/agent-orchestration/commands/improve-agent.md b/plugins/agent-orchestration/commands/improve-agent.md index d5d0164..b829c09 100644 --- a/plugins/agent-orchestration/commands/improve-agent.md +++ b/plugins/agent-orchestration/commands/improve-agent.md @@ -1,3 +1,8 @@ +--- +description: "Improve an existing agent through baseline metrics, prompt changes, and evaluation" +argument-hint: "[agent name or path]" +--- + # Agent Performance Optimization Workflow Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration. diff --git a/plugins/agent-orchestration/commands/multi-agent-optimize.md b/plugins/agent-orchestration/commands/multi-agent-optimize.md index 1ee1b24..e2b9016 100644 --- a/plugins/agent-orchestration/commands/multi-agent-optimize.md +++ b/plugins/agent-orchestration/commands/multi-agent-optimize.md @@ -1,3 +1,8 @@ +--- +description: "Profile a multi-agent system and optimize its coordination, cost, and performance" +argument-hint: "[system or workflow to optimize]" +--- + # Multi-Agent Optimization Toolkit ## Role: AI-Powered Multi-Agent Performance Engineering Specialist diff --git a/plugins/agent-orchestration/skills/ui-agent-patterns/SKILL.md b/plugins/agent-orchestration/skills/ui-agent-patterns/SKILL.md index b941b89..c0b1447 100644 --- a/plugins/agent-orchestration/skills/ui-agent-patterns/SKILL.md +++ b/plugins/agent-orchestration/skills/ui-agent-patterns/SKILL.md @@ -1,6 +1,6 @@ --- name: ui-agent-patterns -description: Patterns for delegating UI work to specialized agents. Covers synthesis-master vs specialized agents, multi-agent UI generation workflows, and orchestration strategies for complex UI tasks. +description: "Patterns for delegating UI work to agents: one synthesis agent versus specialized agents, multi-agent pipelines for research, design, implementation, and review, and clean handoffs between them. Use when a UI task is too large for one pass or you are designing an agent workflow for components or design systems." --- # UI Agent Patterns diff --git a/plugins/api-scaffolding/.claude-plugin/plugin.json b/plugins/api-scaffolding/.claude-plugin/plugin.json new file mode 100644 index 0000000..e67b60c --- /dev/null +++ b/plugins/api-scaffolding/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "api-scaffolding", + "version": "1.2.1", + "description": "REST and GraphQL API scaffolding, framework selection, backend architecture, and API generation", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "api", + "rest", + "graphql", + "fastapi", + "django", + "express" + ] +} diff --git a/plugins/api-testing-observability/.claude-plugin/plugin.json b/plugins/api-testing-observability/.claude-plugin/plugin.json new file mode 100644 index 0000000..3dbebaf --- /dev/null +++ b/plugins/api-testing-observability/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "api-testing-observability", + "version": "1.2.0", + "description": "API testing automation, request mocking, OpenAPI documentation generation, observability setup, and monitoring", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "api-testing", + "mocking", + "openapi", + "swagger", + "observability" + ] +} diff --git a/plugins/api-testing-observability/commands/api-mock.md b/plugins/api-testing-observability/commands/api-mock.md index 98b3949..6add0c4 100644 --- a/plugins/api-testing-observability/commands/api-mock.md +++ b/plugins/api-testing-observability/commands/api-mock.md @@ -1,3 +1,8 @@ +--- +description: "Build realistic mock APIs for development, testing, or demos" +argument-hint: "[API spec or endpoints]" +--- + # API Mocking Framework You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing. diff --git a/plugins/application-performance/.claude-plugin/plugin.json b/plugins/application-performance/.claude-plugin/plugin.json new file mode 100644 index 0000000..8ebf477 --- /dev/null +++ b/plugins/application-performance/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "application-performance", + "version": "1.2.1", + "description": "Application profiling, performance optimization, and observability for frontend and backend systems", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "performance", + "profiling", + "optimization", + "core-web-vitals" + ] +} diff --git a/plugins/application-performance/commands/performance-optimization.md b/plugins/application-performance/commands/performance-optimization.md index 341d3c8..90d04b2 100644 --- a/plugins/application-performance/commands/performance-optimization.md +++ b/plugins/application-performance/commands/performance-optimization.md @@ -1,3 +1,8 @@ +--- +description: "Profile an application end to end and run a coordinated performance optimization" +argument-hint: "[application or area to optimize]" +--- + Optimize application performance end-to-end using specialized performance and optimization agents: [Extended thinking: This workflow orchestrates a comprehensive performance optimization process across the entire application stack. Starting with deep profiling and baseline establishment, the workflow progresses through targeted optimizations in each system layer, validates improvements through load testing, and establishes continuous monitoring for sustained performance. Each phase builds on insights from previous phases, creating a data-driven optimization strategy that addresses real bottlenecks rather than theoretical improvements. The workflow emphasizes modern observability practices, user-centric performance metrics, and cost-effective optimization strategies.] diff --git a/plugins/archetypal-alchemy/.claude-plugin/plugin.json b/plugins/archetypal-alchemy/.claude-plugin/plugin.json new file mode 100644 index 0000000..4877a78 --- /dev/null +++ b/plugins/archetypal-alchemy/.claude-plugin/plugin.json @@ -0,0 +1,21 @@ +{ + "name": "archetypal-alchemy", + "version": "1.0.0", + "description": "Jungian archetypes and Major Arcana symbolism turned into UI structure and color systems, with commands that generate archetype-driven components and Tailwind palettes.", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "archetypes", + "jung", + "tarot", + "color-palettes", + "design-systems", + "tailwind", + "ui-ux" + ] +} diff --git a/plugins/archetypal-alchemy/agents/archetypal-alchemist.md b/plugins/archetypal-alchemy/agents/archetypal-alchemist.md index 212a913..fe4fb49 100644 --- a/plugins/archetypal-alchemy/agents/archetypal-alchemist.md +++ b/plugins/archetypal-alchemy/agents/archetypal-alchemist.md @@ -1,7 +1,7 @@ --- name: archetypal-alchemist -description: Master of Jungian archetypes + Tarot symbolism for UI/UX design. Synthesizes psychological patterns with symbolic color to create meaningful, coherent design systems. Use PROACTIVELY for any UI work involving archetypal themes, symbolic meaning, or when the user wants design with psychological depth. -model: sonnet +description: "Use this agent proactively when UI work calls for archetypal or symbolic meaning: a brand described as a hero, rebel, or sage, a mystical or lunar mood, or a request to design with psychological depth. It maps a Jungian archetype to structure and interaction and a Major Arcana card to color and mood, then produces Tailwind components and palettes that stay consistent with that pairing." +model: inherit --- You are an **Archetypal Alchemist** - a specialist in translating depth psychology and symbolic wisdom into practical UI/UX design. diff --git a/plugins/archetypal-alchemy/commands/archetypal-colors.md b/plugins/archetypal-alchemy/commands/archetypal-colors.md index 7938792..eaf8357 100644 --- a/plugins/archetypal-alchemy/commands/archetypal-colors.md +++ b/plugins/archetypal-alchemy/commands/archetypal-colors.md @@ -1,6 +1,7 @@ --- name: archetypal-colors -description: Generate complete color palettes and Tailwind configs from Major Arcana cards. Transform symbolic Tarot energy into actionable design tokens. +description: Generate a color palette and Tailwind config from a Major Arcana card +argument-hint: "[Major Arcana card], e.g. Sun" --- # Archetypal Color Palette Generation diff --git a/plugins/archetypal-alchemy/commands/archetypal-ui.md b/plugins/archetypal-alchemy/commands/archetypal-ui.md index 744c49c..d5c3f01 100644 --- a/plugins/archetypal-alchemy/commands/archetypal-ui.md +++ b/plugins/archetypal-alchemy/commands/archetypal-ui.md @@ -1,6 +1,7 @@ --- name: archetypal-ui -description: Generate UI components using Jungian archetypes + Major Arcana color alchemy (e.g., Hero+Sun, Magician+Moon). Combines behavioral patterns with symbolic color palettes for meaningful design. +description: Generate a UI component from a Jungian archetype paired with a Major Arcana card +argument-hint: "[Archetype]+[Card] for [component], e.g. Hero+Sun for pricing cards" --- # Archetypal UI Generation diff --git a/plugins/archetypal-alchemy/skills/archetypal-combinations/SKILL.md b/plugins/archetypal-alchemy/skills/archetypal-combinations/SKILL.md index fa90903..5782f1d 100644 --- a/plugins/archetypal-alchemy/skills/archetypal-combinations/SKILL.md +++ b/plugins/archetypal-alchemy/skills/archetypal-combinations/SKILL.md @@ -1,3 +1,8 @@ +--- +name: archetypal-combinations +description: "Rules and worked examples for combining an archetype (structure and behavior) with a Major Arcana card (color and mood) into one coherent design system. Use when pairing an archetype with a card, resolving conflicts between them, or generating a full system from a combination such as Hero+Sun." +--- + # Archetypal Combinations: Alchemy Engine ## Overview diff --git a/plugins/archetypal-alchemy/skills/jungian-archetypes/SKILL.md b/plugins/archetypal-alchemy/skills/jungian-archetypes/SKILL.md index 09e7019..ea72110 100644 --- a/plugins/archetypal-alchemy/skills/jungian-archetypes/SKILL.md +++ b/plugins/archetypal-alchemy/skills/jungian-archetypes/SKILL.md @@ -1,3 +1,8 @@ +--- +name: jungian-archetypes +description: "The twelve Jungian brand archetypes mapped to UI structure: layout, typography, motion, and interaction patterns for each. Use when a brand or product is framed as an archetype (Hero, Sage, Rebel, Caregiver, and so on) and the interface should behave like it." +--- + # Jungian Archetypes → UI/UX Aesthetics ## Overview diff --git a/plugins/archetypal-alchemy/skills/major-arcana/SKILL.md b/plugins/archetypal-alchemy/skills/major-arcana/SKILL.md index 5462302..b76aba7 100644 --- a/plugins/archetypal-alchemy/skills/major-arcana/SKILL.md +++ b/plugins/archetypal-alchemy/skills/major-arcana/SKILL.md @@ -1,3 +1,8 @@ +--- +name: major-arcana +description: "The 22 Major Arcana cards mapped to color palettes, lighting, gradients, and moods for UI. Use when a design needs a symbolic color system or atmosphere, or when a user names a card such as the Sun, the Moon, or the Hermit." +--- + # Major Arcana → Color Palettes & Moods ## Overview diff --git a/plugins/arm-cortex-microcontrollers/.claude-plugin/plugin.json b/plugins/arm-cortex-microcontrollers/.claude-plugin/plugin.json new file mode 100644 index 0000000..420ab3b --- /dev/null +++ b/plugins/arm-cortex-microcontrollers/.claude-plugin/plugin.json @@ -0,0 +1,21 @@ +{ + "name": "arm-cortex-microcontrollers", + "version": "1.2.0", + "description": "ARM Cortex-M firmware development for Teensy, STM32, nRF52, and SAMD with peripheral drivers and memory safety patterns", + "author": { + "name": "Ryan Snodgrass", + "url": "https://github.com/rsnodgrass" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "embedded", + "arm", + "cortex-m", + "firmware", + "microcontroller", + "teensy", + "stm32" + ] +} diff --git a/plugins/backend-api-security/.claude-plugin/plugin.json b/plugins/backend-api-security/.claude-plugin/plugin.json new file mode 100644 index 0000000..f1d5056 --- /dev/null +++ b/plugins/backend-api-security/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "backend-api-security", + "version": "1.2.0", + "description": "API security hardening, authentication implementation, authorization patterns, rate limiting, and input validation", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "api-security", + "authentication", + "authorization", + "jwt", + "oauth" + ] +} diff --git a/plugins/backend-development/.claude-plugin/plugin.json b/plugins/backend-development/.claude-plugin/plugin.json new file mode 100644 index 0000000..295f8db --- /dev/null +++ b/plugins/backend-development/.claude-plugin/plugin.json @@ -0,0 +1,22 @@ +{ + "name": "backend-development", + "version": "1.2.3", + "description": "Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "backend", + "api-design", + "graphql", + "tdd", + "architecture", + "temporal", + "workflow-orchestration", + "distributed-systems" + ] +} diff --git a/plugins/backend-development/commands/feature-development.md b/plugins/backend-development/commands/feature-development.md index 816c9cb..108f819 100644 --- a/plugins/backend-development/commands/feature-development.md +++ b/plugins/backend-development/commands/feature-development.md @@ -1,3 +1,8 @@ +--- +description: "Orchestrate a feature from requirements through implementation, tests, and deployment" +argument-hint: "[feature description]" +--- + Orchestrate end-to-end feature development from requirements to production deployment: [Extended thinking: This workflow orchestrates specialized agents through comprehensive feature development phases - from discovery and planning through implementation, testing, and deployment. Each phase builds on previous outputs, ensuring coherent feature delivery. The workflow supports multiple development methodologies (traditional, TDD/BDD, DDD), feature complexity levels, and modern deployment strategies including feature flags, gradual rollouts, and observability-first development. Agents receive detailed context from previous phases to maintain consistency and quality throughout the development lifecycle.] diff --git a/plugins/blockchain-web3/.claude-plugin/plugin.json b/plugins/blockchain-web3/.claude-plugin/plugin.json new file mode 100644 index 0000000..c7e0af3 --- /dev/null +++ b/plugins/blockchain-web3/.claude-plugin/plugin.json @@ -0,0 +1,21 @@ +{ + "name": "blockchain-web3", + "version": "1.2.1", + "description": "Smart contract development with Solidity, DeFi protocol implementation, NFT platforms, and Web3 application architecture", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "blockchain", + "web3", + "solidity", + "ethereum", + "defi", + "nft", + "smart-contracts" + ] +} diff --git a/plugins/business-analytics/.claude-plugin/plugin.json b/plugins/business-analytics/.claude-plugin/plugin.json new file mode 100644 index 0000000..4882664 --- /dev/null +++ b/plugins/business-analytics/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "business-analytics", + "version": "1.2.0", + "description": "Business metrics analysis, KPI tracking, financial reporting, and data-driven decision making", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "business", + "analytics", + "metrics", + "kpi", + "reporting", + "bi" + ] +} diff --git a/plugins/cicd-automation/.claude-plugin/plugin.json b/plugins/cicd-automation/.claude-plugin/plugin.json new file mode 100644 index 0000000..c1f5d65 --- /dev/null +++ b/plugins/cicd-automation/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "cicd-automation", + "version": "1.2.1", + "description": "CI/CD pipeline configuration, GitHub Actions/GitLab CI workflow setup, and automated deployment pipeline orchestration", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "ci-cd", + "automation", + "pipeline", + "github-actions", + "gitlab-ci" + ] +} diff --git a/plugins/cicd-automation/commands/workflow-automate.md b/plugins/cicd-automation/commands/workflow-automate.md index 75e6a29..233d791 100644 --- a/plugins/cicd-automation/commands/workflow-automate.md +++ b/plugins/cicd-automation/commands/workflow-automate.md @@ -1,3 +1,8 @@ +--- +description: "Design and automate CI/CD pipelines and development workflows, such as GitHub Actions" +argument-hint: "[workflow to automate]" +--- + # Workflow Automation You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design and implement automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security. diff --git a/plugins/cloud-infrastructure/.claude-plugin/plugin.json b/plugins/cloud-infrastructure/.claude-plugin/plugin.json new file mode 100644 index 0000000..f6ce28e --- /dev/null +++ b/plugins/cloud-infrastructure/.claude-plugin/plugin.json @@ -0,0 +1,21 @@ +{ + "name": "cloud-infrastructure", + "version": "1.2.1", + "description": "Cloud architecture design for AWS/Azure/GCP, Kubernetes cluster configuration, Terraform infrastructure-as-code, hybrid cloud networking, and multi-cloud cost optimization", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "cloud", + "aws", + "azure", + "gcp", + "kubernetes", + "terraform", + "infrastructure" + ] +} diff --git a/plugins/code-documentation/.claude-plugin/plugin.json b/plugins/code-documentation/.claude-plugin/plugin.json new file mode 100644 index 0000000..1aa54c3 --- /dev/null +++ b/plugins/code-documentation/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "code-documentation", + "version": "1.2.0", + "description": "Documentation generation, code explanation, and technical writing with automated doc generation and tutorial creation", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "documentation", + "code-explanation", + "technical-writing", + "tutorials" + ] +} diff --git a/plugins/code-documentation/commands/code-explain.md b/plugins/code-documentation/commands/code-explain.md index 14380ac..11ef68e 100644 --- a/plugins/code-documentation/commands/code-explain.md +++ b/plugins/code-documentation/commands/code-explain.md @@ -1,3 +1,8 @@ +--- +description: "Explain complex code with narrative, diagrams, and step-by-step breakdowns" +argument-hint: "[file, function, or code]" +--- + # Code Explanation and Analysis You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable explanations for developers at all levels. diff --git a/plugins/code-documentation/commands/doc-generate.md b/plugins/code-documentation/commands/doc-generate.md index 7b25151..1899e58 100644 --- a/plugins/code-documentation/commands/doc-generate.md +++ b/plugins/code-documentation/commands/doc-generate.md @@ -1,3 +1,8 @@ +--- +description: "Generate API docs, architecture diagrams, and guides from the codebase" +argument-hint: "[project or module]" +--- + # Automated Documentation Generation You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices. diff --git a/plugins/code-refactoring/.claude-plugin/plugin.json b/plugins/code-refactoring/.claude-plugin/plugin.json new file mode 100644 index 0000000..8920e6f --- /dev/null +++ b/plugins/code-refactoring/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "code-refactoring", + "version": "1.2.0", + "description": "Code cleanup, refactoring automation, and technical debt management with context restoration", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "refactoring", + "code-quality", + "technical-debt", + "cleanup" + ] +} diff --git a/plugins/code-refactoring/commands/context-restore.md b/plugins/code-refactoring/commands/context-restore.md index 63ed425..45a9acb 100644 --- a/plugins/code-refactoring/commands/context-restore.md +++ b/plugins/code-refactoring/commands/context-restore.md @@ -1,3 +1,7 @@ +--- +description: "Restore saved project context for a multi-agent or long-running session" +--- + # Context Restoration: Advanced Semantic Memory Rehydration ## Role Statement diff --git a/plugins/code-refactoring/commands/refactor-clean.md b/plugins/code-refactoring/commands/refactor-clean.md index 6140e2f..b90bf4e 100644 --- a/plugins/code-refactoring/commands/refactor-clean.md +++ b/plugins/code-refactoring/commands/refactor-clean.md @@ -1,3 +1,8 @@ +--- +description: "Refactor code for readability and maintainability using clean code and SOLID principles" +argument-hint: "[file, module, or code]" +--- + # Refactor and Clean Code You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance. diff --git a/plugins/code-refactoring/commands/tech-debt.md b/plugins/code-refactoring/commands/tech-debt.md index 167ea40..f7b636b 100644 --- a/plugins/code-refactoring/commands/tech-debt.md +++ b/plugins/code-refactoring/commands/tech-debt.md @@ -1,3 +1,8 @@ +--- +description: "Find, quantify, and prioritize technical debt, with a remediation plan" +argument-hint: "[project or area]" +--- + # Technical Debt Analysis and Remediation You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans. diff --git a/plugins/code-review-ai/.claude-plugin/plugin.json b/plugins/code-review-ai/.claude-plugin/plugin.json new file mode 100644 index 0000000..673d262 --- /dev/null +++ b/plugins/code-review-ai/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "code-review-ai", + "version": "1.2.0", + "description": "AI-powered architectural review and code quality analysis", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "code-review", + "architecture", + "ai-analysis", + "quality" + ] +} diff --git a/plugins/code-review-ai/commands/ai-review.md b/plugins/code-review-ai/commands/ai-review.md index 51571bf..8123f1f 100644 --- a/plugins/code-review-ai/commands/ai-review.md +++ b/plugins/code-review-ai/commands/ai-review.md @@ -1,3 +1,8 @@ +--- +description: "Run an AI-assisted code review combining static analysis with review feedback" +argument-hint: "[PR, diff, or path]" +--- + # AI-Powered Code Review Specialist You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, Claude 4.5 Sonnet) with battle-tested platforms (SonarQube, CodeQL, Semgrep) to identify bugs, vulnerabilities, and performance issues. diff --git a/plugins/codebase-cleanup/.claude-plugin/plugin.json b/plugins/codebase-cleanup/.claude-plugin/plugin.json new file mode 100644 index 0000000..4daf3f1 --- /dev/null +++ b/plugins/codebase-cleanup/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "codebase-cleanup", + "version": "1.2.0", + "description": "Technical debt reduction, dependency updates, and code refactoring automation", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "technical-debt", + "cleanup", + "refactoring", + "dependencies" + ] +} diff --git a/plugins/codebase-cleanup/commands/deps-audit.md b/plugins/codebase-cleanup/commands/deps-audit.md index 4cfdc8c..d857c32 100644 --- a/plugins/codebase-cleanup/commands/deps-audit.md +++ b/plugins/codebase-cleanup/commands/deps-audit.md @@ -1,3 +1,8 @@ +--- +description: "Audit project dependencies for vulnerabilities, license issues, and outdated packages" +argument-hint: "[project path]" +--- + # Dependency Audit and Security Analysis You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies. diff --git a/plugins/codebase-cleanup/commands/refactor-clean.md b/plugins/codebase-cleanup/commands/refactor-clean.md index 6140e2f..b90bf4e 100644 --- a/plugins/codebase-cleanup/commands/refactor-clean.md +++ b/plugins/codebase-cleanup/commands/refactor-clean.md @@ -1,3 +1,8 @@ +--- +description: "Refactor code for readability and maintainability using clean code and SOLID principles" +argument-hint: "[file, module, or code]" +--- + # Refactor and Clean Code You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance. diff --git a/plugins/codebase-cleanup/commands/tech-debt.md b/plugins/codebase-cleanup/commands/tech-debt.md index 167ea40..f7b636b 100644 --- a/plugins/codebase-cleanup/commands/tech-debt.md +++ b/plugins/codebase-cleanup/commands/tech-debt.md @@ -1,3 +1,8 @@ +--- +description: "Find, quantify, and prioritize technical debt, with a remediation plan" +argument-hint: "[project or area]" +--- + # Technical Debt Analysis and Remediation You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans. diff --git a/plugins/comprehensive-review/.claude-plugin/plugin.json b/plugins/comprehensive-review/.claude-plugin/plugin.json new file mode 100644 index 0000000..5525501 --- /dev/null +++ b/plugins/comprehensive-review/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "comprehensive-review", + "version": "1.2.1", + "description": "Multi-perspective code analysis covering architecture, security, and best practices", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "code-review", + "quality", + "architecture", + "security", + "best-practices" + ] +} diff --git a/plugins/comprehensive-review/commands/full-review.md b/plugins/comprehensive-review/commands/full-review.md index 1fc4b4c..e9da619 100644 --- a/plugins/comprehensive-review/commands/full-review.md +++ b/plugins/comprehensive-review/commands/full-review.md @@ -1,3 +1,8 @@ +--- +description: "Run a multi-agent code review across quality, security, performance, and architecture" +argument-hint: "[path or PR] [--security-focus] [--performance-critical]" +--- + Orchestrate comprehensive multi-dimensional code review using specialized review agents [Extended thinking: This workflow performs an exhaustive code review by orchestrating multiple specialized agents in sequential phases. Each phase builds upon previous findings to create a comprehensive review that covers code quality, security, performance, testing, documentation, and best practices. The workflow integrates modern AI-assisted review tools, static analysis, security scanning, and automated quality metrics. Results are consolidated into actionable feedback with clear prioritization and remediation guidance. The phased approach ensures thorough coverage while maintaining efficiency through parallel agent execution where appropriate.] diff --git a/plugins/comprehensive-review/commands/pr-enhance.md b/plugins/comprehensive-review/commands/pr-enhance.md index 9f0ac22..0521e8c 100644 --- a/plugins/comprehensive-review/commands/pr-enhance.md +++ b/plugins/comprehensive-review/commands/pr-enhance.md @@ -1,3 +1,8 @@ +--- +description: "Write or improve a pull request description, checklist, and review aids" +argument-hint: "[PR or branch]" +--- + # Pull Request Enhancement You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability. diff --git a/plugins/content-marketing/.claude-plugin/plugin.json b/plugins/content-marketing/.claude-plugin/plugin.json new file mode 100644 index 0000000..db87bd6 --- /dev/null +++ b/plugins/content-marketing/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "content-marketing", + "version": "1.2.0", + "description": "Content marketing strategy, web research, and information synthesis for marketing operations", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "content-marketing", + "research", + "marketing-strategy", + "social-media" + ] +} diff --git a/plugins/context-management/.claude-plugin/plugin.json b/plugins/context-management/.claude-plugin/plugin.json new file mode 100644 index 0000000..05c4328 --- /dev/null +++ b/plugins/context-management/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "context-management", + "version": "1.2.0", + "description": "Context persistence, restoration, and long-running conversation management", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "context", + "persistence", + "conversation", + "memory" + ] +} diff --git a/plugins/context-management/commands/context-restore.md b/plugins/context-management/commands/context-restore.md index 63ed425..45a9acb 100644 --- a/plugins/context-management/commands/context-restore.md +++ b/plugins/context-management/commands/context-restore.md @@ -1,3 +1,7 @@ +--- +description: "Restore saved project context for a multi-agent or long-running session" +--- + # Context Restoration: Advanced Semantic Memory Rehydration ## Role Statement diff --git a/plugins/context-management/commands/context-save.md b/plugins/context-management/commands/context-save.md index 6858ae7..49ba641 100644 --- a/plugins/context-management/commands/context-save.md +++ b/plugins/context-management/commands/context-save.md @@ -1,3 +1,7 @@ +--- +description: "Save the current project context so a later session can restore it" +--- + # Context Save Tool: Intelligent Context Management Specialist ## Role and Purpose diff --git a/plugins/context-management/skills/design-system-context/SKILL.md b/plugins/context-management/skills/design-system-context/SKILL.md index 162d7a2..5b70918 100644 --- a/plugins/context-management/skills/design-system-context/SKILL.md +++ b/plugins/context-management/skills/design-system-context/SKILL.md @@ -1,6 +1,6 @@ --- name: design-system-context -description: Managing design tokens and system context for LLM-driven UI development. Covers loading, persisting, and optimizing design decisions within context windows. +description: "Keeping a design system in an LLM's context: loading tokens compactly, persisting design decisions across sessions, handling multiple variants, and budgeting the context window. Use when generated UI drifts from the design system, or when setting up tokens and decisions so every session and agent uses the same ones." --- # Design System Context Management diff --git a/plugins/customer-sales-automation/.claude-plugin/plugin.json b/plugins/customer-sales-automation/.claude-plugin/plugin.json new file mode 100644 index 0000000..daaed85 --- /dev/null +++ b/plugins/customer-sales-automation/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "customer-sales-automation", + "version": "1.2.0", + "description": "Customer support workflow automation, sales pipeline management, email campaigns, and CRM integration", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "customer-support", + "sales", + "crm", + "email-campaigns", + "automation" + ] +} diff --git a/plugins/data-engineering/.claude-plugin/plugin.json b/plugins/data-engineering/.claude-plugin/plugin.json new file mode 100644 index 0000000..b2cf92f --- /dev/null +++ b/plugins/data-engineering/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "data-engineering", + "version": "1.2.1", + "description": "ETL pipeline construction, data warehouse design, batch processing workflows, and data-driven feature development", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "data-engineering", + "etl", + "data-pipeline", + "data-warehouse", + "batch-processing" + ] +} diff --git a/plugins/data-engineering/commands/data-driven-feature.md b/plugins/data-engineering/commands/data-driven-feature.md index 253a25b..5a31f6c 100644 --- a/plugins/data-engineering/commands/data-driven-feature.md +++ b/plugins/data-engineering/commands/data-driven-feature.md @@ -1,3 +1,8 @@ +--- +description: "Build a feature guided by data analysis, A/B testing, and measurement" +argument-hint: "[feature or hypothesis]" +--- + # Data-Driven Feature Development Build features guided by data insights, A/B testing, and continuous measurement using specialized agents for analysis, implementation, and experimentation. diff --git a/plugins/data-engineering/commands/data-pipeline.md b/plugins/data-engineering/commands/data-pipeline.md index 724e849..02fd11d 100644 --- a/plugins/data-engineering/commands/data-pipeline.md +++ b/plugins/data-engineering/commands/data-pipeline.md @@ -1,3 +1,8 @@ +--- +description: "Design a batch or streaming data pipeline architecture" +argument-hint: "[pipeline requirements]" +--- + # Data Pipeline Architecture You are a data pipeline architecture expert specializing in scalable, reliable, and cost-effective data pipelines for batch and streaming data processing. diff --git a/plugins/data-validation-suite/.claude-plugin/plugin.json b/plugins/data-validation-suite/.claude-plugin/plugin.json new file mode 100644 index 0000000..2ee521b --- /dev/null +++ b/plugins/data-validation-suite/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "data-validation-suite", + "version": "1.2.0", + "description": "Schema validation, data quality monitoring, streaming validation pipelines, and input validation for backend APIs", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "validation", + "schema", + "data-quality", + "pydantic", + "jsonschema" + ] +} diff --git a/plugins/database-cloud-optimization/.claude-plugin/plugin.json b/plugins/database-cloud-optimization/.claude-plugin/plugin.json new file mode 100644 index 0000000..866a90c --- /dev/null +++ b/plugins/database-cloud-optimization/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "database-cloud-optimization", + "version": "1.2.0", + "description": "Database query optimization, cloud cost optimization, and scalability improvements", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "database-optimization", + "cloud-cost", + "query-tuning", + "scalability" + ] +} diff --git a/plugins/database-cloud-optimization/commands/cost-optimize.md b/plugins/database-cloud-optimization/commands/cost-optimize.md index 8af4b1a..49a2e17 100644 --- a/plugins/database-cloud-optimization/commands/cost-optimize.md +++ b/plugins/database-cloud-optimization/commands/cost-optimize.md @@ -1,3 +1,8 @@ +--- +description: "Analyze cloud spend and recommend cost savings that keep performance and reliability" +argument-hint: "[cloud account, service, or scope]" +--- + # Cloud Cost Optimization You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP. diff --git a/plugins/database-design/.claude-plugin/plugin.json b/plugins/database-design/.claude-plugin/plugin.json new file mode 100644 index 0000000..872b631 --- /dev/null +++ b/plugins/database-design/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "database-design", + "version": "1.2.0", + "description": "Database architecture, schema design, and SQL optimization for production systems", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "database-design", + "schema", + "sql", + "data-modeling" + ] +} diff --git a/plugins/database-migrations/.claude-plugin/plugin.json b/plugins/database-migrations/.claude-plugin/plugin.json new file mode 100644 index 0000000..1a74033 --- /dev/null +++ b/plugins/database-migrations/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "database-migrations", + "version": "1.2.0", + "description": "Database migration automation, observability, and cross-database migration strategies", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "migrations", + "database-operations", + "postgres", + "mysql", + "mongodb" + ] +} diff --git a/plugins/debugging-toolkit/.claude-plugin/plugin.json b/plugins/debugging-toolkit/.claude-plugin/plugin.json new file mode 100644 index 0000000..a08a2b3 --- /dev/null +++ b/plugins/debugging-toolkit/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "debugging-toolkit", + "version": "1.2.0", + "description": "Interactive debugging, developer experience optimization, and smart debugging workflows", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "debugging", + "developer-experience", + "troubleshooting", + "essential" + ] +} diff --git a/plugins/debugging-toolkit/commands/smart-debug.md b/plugins/debugging-toolkit/commands/smart-debug.md index 600a582..df498ce 100644 --- a/plugins/debugging-toolkit/commands/smart-debug.md +++ b/plugins/debugging-toolkit/commands/smart-debug.md @@ -1,3 +1,8 @@ +--- +description: "Debug an issue from its error, stack trace, or symptoms with root cause analysis" +argument-hint: "[error, stack trace, or issue]" +--- + You are an expert AI-assisted debugging specialist with deep knowledge of modern debugging tools, observability platforms, and automated root cause analysis. ## Context diff --git a/plugins/dependency-management/.claude-plugin/plugin.json b/plugins/dependency-management/.claude-plugin/plugin.json new file mode 100644 index 0000000..39cfddb --- /dev/null +++ b/plugins/dependency-management/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "dependency-management", + "version": "1.2.0", + "description": "Dependency auditing, version management, and security vulnerability scanning", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "dependencies", + "npm", + "security", + "auditing", + "upgrades" + ] +} diff --git a/plugins/dependency-management/commands/deps-audit.md b/plugins/dependency-management/commands/deps-audit.md index 4cfdc8c..d857c32 100644 --- a/plugins/dependency-management/commands/deps-audit.md +++ b/plugins/dependency-management/commands/deps-audit.md @@ -1,3 +1,8 @@ +--- +description: "Audit project dependencies for vulnerabilities, license issues, and outdated packages" +argument-hint: "[project path]" +--- + # Dependency Audit and Security Analysis You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies. diff --git a/plugins/deployment-strategies/.claude-plugin/plugin.json b/plugins/deployment-strategies/.claude-plugin/plugin.json new file mode 100644 index 0000000..7f0ec45 --- /dev/null +++ b/plugins/deployment-strategies/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "deployment-strategies", + "version": "1.2.0", + "description": "Deployment patterns, rollback automation, and infrastructure templates", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "deployment", + "rollout", + "rollback", + "canary", + "blue-green" + ] +} diff --git a/plugins/deployment-validation/.claude-plugin/plugin.json b/plugins/deployment-validation/.claude-plugin/plugin.json new file mode 100644 index 0000000..0e72e55 --- /dev/null +++ b/plugins/deployment-validation/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "deployment-validation", + "version": "1.2.0", + "description": "Pre-deployment checks, configuration validation, and deployment readiness assessment", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "validation", + "pre-flight", + "configuration", + "deployment-safety" + ] +} diff --git a/plugins/deployment-validation/commands/config-validate.md b/plugins/deployment-validation/commands/config-validate.md index 090a17d..5f60fc7 100644 --- a/plugins/deployment-validation/commands/config-validate.md +++ b/plugins/deployment-validation/commands/config-validate.md @@ -1,3 +1,8 @@ +--- +description: "Validate application configuration with schemas, tests, and environment consistency checks" +argument-hint: "[config files or environment]" +--- + # Configuration Validation You are a configuration management expert specializing in validating, testing, and ensuring the correctness of application configurations. Create comprehensive validation schemas, implement configuration testing strategies, and ensure configurations are secure, consistent, and error-free across all environments. diff --git a/plugins/design-mastery/.claude-plugin/plugin.json b/plugins/design-mastery/.claude-plugin/plugin.json new file mode 100644 index 0000000..f2d545a --- /dev/null +++ b/plugins/design-mastery/.claude-plugin/plugin.json @@ -0,0 +1,32 @@ +{ + "name": "design-mastery", + "version": "1.1.0", + "description": "Design principles, legendary designers, and historical movements applied to UI work, with agents and workflows for brand identity, design audits, style guides, and premium landing pages.", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "design", + "ui-ux", + "brand-identity", + "design-systems", + "typography", + "color-theory", + "visual-design", + "design-principles", + "saul-bass", + "massimo-vignelli", + "dieter-rams", + "bauhaus", + "swiss-design", + "gestalt", + "paula-scher", + "paul-rand", + "design-audit", + "landing-page" + ] +} diff --git a/plugins/design-mastery/README.md b/plugins/design-mastery/README.md index 7172b9c..f6bd9da 100644 --- a/plugins/design-mastery/README.md +++ b/plugins/design-mastery/README.md @@ -184,7 +184,7 @@ Body: font-sans text-base leading-relaxed **Core Lesson**: Constraints liberate creativity **Apply His Wisdom**: -- Limited typefaces (he used 5 total) - restraint breeds excellence +- A few basic typefaces (his exhibition "A Few Basic Typefaces" used only four) - restraint breeds excellence - Strict grids create freedom within structure - Clarity over geographic accuracy (prioritize communication) @@ -197,6 +197,8 @@ Body: font-sans text-base leading-relaxed /* That's it. No more fonts. */ ``` +**Full profile**: [`skills/design-masters/references/massimo-vignelli.md`](skills/design-masters/references/massimo-vignelli.md) + --- ### Dieter Rams (1932-) @@ -226,6 +228,8 @@ Body: font-sans text-base leading-relaxed ``` +**Full profile**: [`skills/design-masters/references/dieter-rams.md`](skills/design-masters/references/dieter-rams.md) + --- ### Paula Scher (1948-) @@ -247,12 +251,14 @@ Body: font-sans text-base leading-relaxed ``` +**Full profile**: [`skills/design-masters/references/paula-scher.md`](skills/design-masters/references/paula-scher.md) + --- ### Josef Müller-Brockmann (1914-1996) > "The grid system is an aid, not a guarantee." -**Legacy**: Father of Swiss International Style, mathematical precision +**Legacy**: A leading figure of the Swiss International Style, mathematical precision **Core Lesson**: Grids create order, but knowing when to break them creates art **Apply His Wisdom**: @@ -271,8 +277,12 @@ Body: font-sans text-base leading-relaxed ``` +**Full profile**: [`skills/design-masters/references/josef-muller-brockmann.md`](skills/design-masters/references/josef-muller-brockmann.md) + --- +More masters (David Carson, Paul Rand) and every movement, principle, and brand topic have their own reference files in `skills/*/references/`; the skills load them when a task needs depth. + ## The 5 Design Movements ### Bauhaus (1919-1933) @@ -359,35 +369,40 @@ Body: font-sans text-base leading-relaxed ``` design-mastery/ ├── README.md # This file +├── .claude-plugin/plugin.json │ ├── skills/ # Knowledge base │ ├── design-principles/ │ │ ├── SKILL.md # 5 toolkits │ │ ├── assets/ │ │ │ └── principles-checklist.md -│ │ └── references/ -│ │ ├── color-theory.md -│ │ └── typography-fundamentals.md +│ │ └── references/ # gestalt, hierarchy, composition, color, typography │ ├── design-masters/ -│ │ ├── SKILL.md # 5 legendary designers -│ │ └── references/ -│ │ └── saul-bass.md +│ │ ├── SKILL.md # legendary designers +│ │ └── references/ # Bass, Vignelli, Rams, Scher, Müller-Brockmann, Carson, Rand │ ├── design-movements/ -│ │ └── SKILL.md # 5 historic movements -│ └── brand-systems/ -│ ├── SKILL.md # Brand strategy & systems -│ └── assets/ -│ └── brand-canvas-template.md +│ │ ├── SKILL.md # historic movements +│ │ └── references/ # one file per movement, Arts and Crafts to flat design +│ ├── brand-systems/ +│ │ ├── SKILL.md # Brand strategy & systems +│ │ ├── assets/ +│ │ │ └── brand-canvas-template.md +│ │ └── references/ # logo, palettes, type pairing, voice +│ └── premium-saas-design/ +│ └── SKILL.md # Define, Build, Review, Refine loop │ ├── commands/ # Slash commands │ ├── style-guide.md # Generate style guides │ ├── design-audit.md # Audit existing designs -│ └── brand-identity.md # Create brand systems +│ ├── brand-identity.md # Create brand systems +│ └── premium-landing.md # Premium SaaS landing pages +│ +├── agents/ # Specialist agents +│ ├── design-master.md # Timeless principles expert +│ ├── visual-historian.md # Movement & history expert +│ └── brand-architect.md # Brand strategy expert │ -└── agents/ # Specialist agents - ├── design-master.md # Timeless principles expert - ├── visual-historian.md # Movement & history expert - └── brand-architect.md # Brand strategy expert +└── evals/ # cases for `claude plugin eval plugins/design-mastery` ``` --- diff --git a/plugins/design-mastery/agents/brand-architect.md b/plugins/design-mastery/agents/brand-architect.md index 4a6736a..30183b8 100644 --- a/plugins/design-mastery/agents/brand-architect.md +++ b/plugins/design-mastery/agents/brand-architect.md @@ -1,7 +1,7 @@ --- name: brand-architect -description: Expert in building comprehensive brand identity systems from strategy through visual execution. Guides the complete brand development journey from positioning and values through logo, typography, color palette, voice, and brand guidelines. Use for brand creation, rebranding, or brand system development. -model: sonnet +description: "Use this agent when someone is creating a new brand, rebranding, or turning scattered brand assets into a system. It starts with discovery and positioning questions (audience, competitors, promise, personality) before proposing any logo, color, type, or voice direction, then documents the result as brand guidelines and design tokens." +model: inherit --- You are a brand architect who understands that great brands are built, not decorated. @@ -242,7 +242,7 @@ Hex: #0066CC RGB: 0, 102, 204 Tailwind: blue-600 Usage: Primary actions, links, trust signals -Accessibility: Passes WCAG AA on white (contrast 4.5:1) +Accessibility: Passes WCAG AA on white (contrast 5.57:1) Psychology: Conveys reliability, professionalism ``` diff --git a/plugins/design-mastery/agents/design-master.md b/plugins/design-mastery/agents/design-master.md index 2751e6a..570087d 100644 --- a/plugins/design-mastery/agents/design-master.md +++ b/plugins/design-mastery/agents/design-master.md @@ -1,7 +1,7 @@ --- name: design-master -description: Comprehensive design guide drawing from timeless principles, legendary designers, and historical movements. Masters visual hierarchy, color theory, typography, composition, and translates classical design wisdom into modern implementation. Use PROACTIVELY for any UI/UX design, component creation, or visual decision-making. -model: sonnet +description: "Use this agent proactively when a UI needs design judgment: a layout feels cluttered or flat, the hierarchy is unclear, type or color choices need a rationale, or a new component should follow proven principles. It diagnoses the problem against design principles, the masters, and historical movements, then proposes concrete Tailwind or CSS changes with the reasoning behind each." +model: inherit --- You are a design master who has studied under the greats and synthesized centuries of visual wisdom into actionable guidance. @@ -67,7 +67,7 @@ Bass revolutionized film title sequences and corporate identity. His work for AT ### Massimo Vignelli (1931-2014) > "If you can design one thing, you can design everything." -The Vignelli Canon: limited typefaces (he used 5), strict grids, and restraint. His NYC Subway map prioritizes clarity over geographic accuracy. **Apply his lesson**: Constraints liberate creativity; a smaller toolkit forces smarter solutions. +The Vignelli Canon: a few basic typefaces (one exhibition of his work used only four), strict grids, and restraint. His NYC Subway map prioritizes clarity over geographic accuracy. **Apply his lesson**: Constraints liberate creativity; a smaller toolkit forces smarter solutions. ### Dieter Rams (1932-) > "Good design is as little design as possible." @@ -77,12 +77,12 @@ His 10 Principles of Good Design remain the gold standard. Braun products influe ### Paula Scher (1948-) > "It's through mistakes that you actually can grow." -Bold typography, expressive lettering, and fearless experimentation. Her identity work transformed public spaces. **Apply his lesson**: Break rules intentionally, knowing what you're breaking and why. +Bold typography, expressive lettering, and fearless experimentation. Her identity work transformed public spaces. **Apply her lesson**: Break rules intentionally, knowing what you're breaking and why. ### Josef Müller-Brockmann (1914-1996) > "The grid system is an aid, not a guarantee." -Father of the Swiss International Style. Mathematical precision serving communication. **Apply his lesson**: Grids create order, but knowing when to break them creates art. +A leading figure of the Swiss International Style, alongside Max Bill, Armin Hofmann, and Emil Ruder. Mathematical precision serving communication. **Apply his lesson**: Grids create order, but knowing when to break them creates art. ## Design Movements Reference diff --git a/plugins/design-mastery/agents/visual-historian.md b/plugins/design-mastery/agents/visual-historian.md index b9b31ef..af5cd84 100644 --- a/plugins/design-mastery/agents/visual-historian.md +++ b/plugins/design-mastery/agents/visual-historian.md @@ -1,7 +1,7 @@ --- name: visual-historian -description: Expert in design history, movements, and the evolution of visual culture. Connects contemporary design decisions to their historical roots. Use when exploring design movements, studying legendary designers, or understanding why certain aesthetics feel the way they do. -model: sonnet +description: "Use this agent when the question is where a style comes from or what it signals: why something reads as retro or premium, which movement or designer to reference for a brand, or how a period shaped a pattern still used in interfaces. It traces the lineage through movements and masters and turns that history into deliberate design choices." +model: inherit --- You are a visual historian who traces the lineage of every design decision back through history. @@ -17,7 +17,7 @@ Nothing in design is truly new—it's all evolution, rebellion, or revival. Unde Every "new" trend is an old idea recontextualized: - Flat design = Swiss modernism + digital constraints - Brutalist web = punk + reaction to sterile UI -- Glassmorphism = Mac OS X frosted glass + neural transparency +- Glassmorphism = Mac OS X Aqua and Windows Aero translucency + the iOS 7 background blur - Neumorphism = skeuomorphism + minimalism's children rebelling Knowing history means knowing context. Context means intentionality. @@ -86,7 +86,7 @@ Knowing history means knowing context. Context means intentionality. - Minimal ornamentation - Grid-based layouts -**Legacy**: Father of graphic design as we know it. Directly influenced Swiss style, Apple, Google Material Design. +**Legacy**: A foundation of modern design education. Through émigré teachers and schools (the New Bauhaus in Chicago, Black Mountain College, HfG Ulm) it fed the functional modernism of Swiss style and corporate design. --- @@ -141,7 +141,7 @@ Knowing history means knowing context. Context means intentionality. --- -### 1981-1987: Memphis Group +### 1980-1987: Memphis Group **Reaction to**: Good taste and minimalist seriousness **Champions**: Ettore Sottsass, Michele De Lucchi **Core Idea**: Anti-design; pleasure over function @@ -154,7 +154,7 @@ Knowing history means knowing context. Context means intentionality. - Playful, childlike elements - Terrazzo patterns -**Legacy**: Bowie's "Tonight" album cover. 80s excess. Modern revival in Gen Z design. +**Legacy**: David Bowie collected Memphis furniture (his collection sold at Sotheby's in 2016). 80s excess. Modern revival in Gen Z design. --- @@ -205,7 +205,7 @@ Knowing history means knowing context. Context means intentionality. - Bold colors - No shadows or depth -**Legacy**: Enabled responsive design. Swiss style's digital grandchild. +**Legacy**: Grew up alongside responsive design. Swiss style's digital grandchild. --- @@ -254,13 +254,13 @@ Knowing history means knowing context. Context means intentionality. 3. Pragmatics: context 4. Discipline: constraint 5. Appropriateness: fit -6. Ambiguity: (avoid it) +6. Ambiguity: a plurality of meanings (not vagueness) 7. Design is One: universal principles 8. Visual Power: strength 9. Intellectual Elegance: clever solutions 10. Timelessness: longevity -11. Responsibility: ethics -12. Equity: quality for all +11. Responsibility: to the work, the client, and the public +12. Equity: respect the recognition an established mark has earned --- @@ -301,7 +301,7 @@ Knowing history means knowing context. Context means intentionality. ### Paula Scher (1948-) **Known For**: Typography, identity, environmental graphics -**Major Works**: The Public Theater, Citibank, Windows 8 +**Major Works**: The Public Theater, Citi, the Windows 8 logo **Philosophy**: "It's through mistakes that you actually can grow" **Approach**: @@ -357,12 +357,12 @@ Knowing history means knowing context. Context means intentionality. ### Pattern: Cyclical Revival -Movements return on ~30-year cycles: +Movements often return about a generation later (an observation, not a measured cycle): - 1990s → 2020s (Y2K aesthetic revival) - 1980s → 2010s (Memphis in hipster design) - 1970s → 2000s (disco in Web 2.0 gradients) -**Prediction**: Expect grunge/deconstructivist revival in late 2020s. +**Speculation**: a grunge/deconstructivist revival would fit the pattern; treat it as a hypothesis. --- diff --git a/plugins/design-mastery/commands/brand-identity.md b/plugins/design-mastery/commands/brand-identity.md index a138fb5..1c35900 100644 --- a/plugins/design-mastery/commands/brand-identity.md +++ b/plugins/design-mastery/commands/brand-identity.md @@ -1,6 +1,7 @@ --- name: brand-identity -description: Guided workflow for creating comprehensive brand identity systems. Walks through discovery, strategy, visual identity, and guidelines creation. +description: Guide a brand identity build from discovery and strategy through visual identity to guidelines +argument-hint: "[company, product, or project]" --- # Brand Identity Builder diff --git a/plugins/design-mastery/commands/design-audit.md b/plugins/design-mastery/commands/design-audit.md index 58c7ddd..df67d80 100644 --- a/plugins/design-mastery/commands/design-audit.md +++ b/plugins/design-mastery/commands/design-audit.md @@ -1,6 +1,7 @@ --- name: design-audit -description: Systematic evaluation of existing designs against fundamental principles. Provides actionable feedback rooted in design theory and best practices. +description: Audit a UI against eight design dimensions and return scored findings with fixes +argument-hint: "[screenshot path, URL, code, or description]" --- # Design Audit Command @@ -85,7 +86,7 @@ Check: Check: - [ ] Color contrast - 4.5:1 for text, 3:1 for large text - [ ] Focus indicators - keyboard navigation visible -- [ ] Touch targets - 44x44px minimum +- [ ] Touch targets - at least 24x24px (WCAG 2.2 AA), 44x44px recommended (AAA, Apple HIG) - [ ] Alt text - images have descriptions - [ ] Motion consideration - reduced motion options diff --git a/plugins/design-mastery/commands/premium-landing.md b/plugins/design-mastery/commands/premium-landing.md index 36a4322..9a63a60 100644 --- a/plugins/design-mastery/commands/premium-landing.md +++ b/plugins/design-mastery/commands/premium-landing.md @@ -1,3 +1,8 @@ +--- +description: Plan, build, review, and refine a premium SaaS landing page one section at a time +argument-hint: "[define|setup|build|review|refine] [section]" +--- + # Premium Landing Page Generator Generate premium $5k+ quality SaaS landing pages using the Define → Build → Review → Refine framework. diff --git a/plugins/design-mastery/commands/style-guide.md b/plugins/design-mastery/commands/style-guide.md index 505655a..23ad42b 100644 --- a/plugins/design-mastery/commands/style-guide.md +++ b/plugins/design-mastery/commands/style-guide.md @@ -1,6 +1,7 @@ --- name: style-guide -description: Generate comprehensive design system documentation including colors, typography, spacing, components, and usage guidelines. Outputs production-ready Tailwind/CSS configuration. +description: Generate a style guide with design tokens, type scale, spacing, components, and Tailwind or CSS config +argument-hint: "[brand, product, or scope]" --- # Style Guide Generator diff --git a/plugins/design-mastery/evals/brand-architect-bakery/graders/brand-component-fired.md b/plugins/design-mastery/evals/brand-architect-bakery/graders/brand-component-fired.md new file mode 100644 index 0000000..c2e55ce --- /dev/null +++ b/plugins/design-mastery/evals/brand-architect-bakery/graders/brand-component-fired.md @@ -0,0 +1,6 @@ +--- +type: tool_used +tool: Skill +input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(brand-identity|brand-systems)"' +min: 1 +--- diff --git a/plugins/design-mastery/evals/brand-architect-bakery/graders/strategy-before-visuals.md b/plugins/design-mastery/evals/brand-architect-bakery/graders/strategy-before-visuals.md new file mode 100644 index 0000000..5c24ec5 --- /dev/null +++ b/plugins/design-mastery/evals/brand-architect-bakery/graders/strategy-before-visuals.md @@ -0,0 +1,10 @@ +--- +type: llm +weight: 3 +--- + +The user asked for a logo and color palette but gave almost no information about the business. + +PASS if, before committing to a final logo or palette, the response asks discovery or positioning questions about the bakery (for example: who the customers are, what makes it different from other bakeries nearby, its personality or values, its name, price point, or the feeling it should give) or clearly explains that these answers are needed first. Offering a few clearly provisional directions alongside the questions is acceptable. + +FAIL if the response delivers a finished logo concept and a specific hex palette as the answer without asking any positioning or audience questions. diff --git a/plugins/design-mastery/evals/brand-architect-bakery/prompt.md b/plugins/design-mastery/evals/brand-architect-bakery/prompt.md new file mode 100644 index 0000000..0dec3b6 --- /dev/null +++ b/plugins/design-mastery/evals/brand-architect-bakery/prompt.md @@ -0,0 +1,10 @@ +--- +name: brand-architect-bakery +description: Asked for a logo and palette with no context, the plugin starts with positioning questions instead of jumping to visuals. +tags: [brand] +plugins: ["../.."] +max_turns: 8 +allowed_tools: [Read, Glob, Grep, Skill, Agent] +--- + +I'm opening a small neighborhood bakery. Can you design a logo and a color palette for it? diff --git a/plugins/design-mastery/evals/design-audit-dashboard/graders/audit-skill-fired.md b/plugins/design-mastery/evals/design-audit-dashboard/graders/audit-skill-fired.md new file mode 100644 index 0000000..99ab623 --- /dev/null +++ b/plugins/design-mastery/evals/design-audit-dashboard/graders/audit-skill-fired.md @@ -0,0 +1,6 @@ +--- +type: tool_used +tool: Skill +input_match: '"skill"\s*:\s*"(?:[\w-]+:)?(design-audit|design-principles)"' +min: 1 +--- diff --git a/plugins/design-mastery/evals/design-audit-dashboard/graders/finds-core-issues.md b/plugins/design-mastery/evals/design-audit-dashboard/graders/finds-core-issues.md new file mode 100644 index 0000000..6a89d64 --- /dev/null +++ b/plugins/design-mastery/evals/design-audit-dashboard/graders/finds-core-issues.md @@ -0,0 +1,11 @@ +--- +type: llm +weight: 3 +--- + +PASS if the response identifies all three of these problems and gives a concrete fix for each: +1. Hierarchy: the title, card titles, and table header share one size and weight, and the five equal buttons give "Upgrade plan" no priority. A fix differentiates sizes or weights and makes "Upgrade plan" the single primary action. +2. Contrast: #9CA3AF text on white fails WCAG AA for normal text (it is about 2.5:1, below 4.5:1). A fix names a darker text color or a ratio target. +3. Typography: four typefaces is too many and 12px body text is small. A fix reduces the families (for example to one or two) and raises body size. + +FAIL if any of the three is missing, or if the response only gives vague advice ("make it pop", "improve contrast") without specific values or changes. diff --git a/plugins/design-mastery/evals/design-audit-dashboard/graders/flags-color-only-status.md b/plugins/design-mastery/evals/design-audit-dashboard/graders/flags-color-only-status.md new file mode 100644 index 0000000..767045a --- /dev/null +++ b/plugins/design-mastery/evals/design-audit-dashboard/graders/flags-color-only-status.md @@ -0,0 +1,6 @@ +--- +type: llm +weight: 1 +--- + +PASS if the response points out that status shown only by colored dots relies on color alone (a problem for color-blind users) and suggests adding text, icons, or shapes. FAIL otherwise. diff --git a/plugins/design-mastery/evals/design-audit-dashboard/prompt.md b/plugins/design-mastery/evals/design-audit-dashboard/prompt.md new file mode 100644 index 0000000..1a4e82f --- /dev/null +++ b/plugins/design-mastery/evals/design-audit-dashboard/prompt.md @@ -0,0 +1,17 @@ +--- +name: design-audit-dashboard +description: A design audit of a described SaaS dashboard finds the hierarchy, contrast, and typography problems and gives concrete fixes. +tags: [audit, principles] +plugins: ["../.."] +max_turns: 8 +allowed_tools: [Read, Glob, Grep, Skill, Agent] +--- + +Audit this SaaS analytics dashboard design and tell me what to fix first. Here is the design: + +- Page background is white (#FFFFFF). Body text and table text are #9CA3AF at 12px. +- The page uses four typefaces: Montserrat for the page title, Lato for card titles, Georgia for table headers, and Roboto for everything else. +- The page title, the four card titles, and the table header are all 18px, weight 600. +- The top bar has five buttons of the same size and color: "Export", "Share", "Filter", "Settings", and "Upgrade plan". "Upgrade plan" is the action we most want people to take. +- Every gap on the page is 16px: between a label and its value, between cards, and between sections. +- Status in the table is shown only by a small colored dot (green, amber, red) with no text. diff --git a/plugins/design-mastery/evals/design-masters-rams/graders/rams-applied.md b/plugins/design-mastery/evals/design-masters-rams/graders/rams-applied.md new file mode 100644 index 0000000..d2b093c --- /dev/null +++ b/plugins/design-mastery/evals/design-masters-rams/graders/rams-applied.md @@ -0,0 +1,8 @@ +--- +type: llm +weight: 2 +--- + +PASS if the response uses Dieter Rams' principles accurately (for example "as little design as possible", "less, but better", understandable, unobtrusive, honest, thorough) and turns them into concrete changes for this screen: grouping or progressive disclosure for the toggles, removing or reducing the decorative header, a single consistent save action, moving "Advanced" out of the top position, and trimming tooltips to where they add meaning. + +FAIL if it misattributes principles to Rams, invents principles he did not state, or gives generic minimalism advice without specific changes. diff --git a/plugins/design-mastery/evals/design-masters-rams/prompt.md b/plugins/design-mastery/evals/design-masters-rams/prompt.md new file mode 100644 index 0000000..1392851 --- /dev/null +++ b/plugins/design-mastery/evals/design-masters-rams/prompt.md @@ -0,0 +1,10 @@ +--- +name: design-masters-rams +description: Applying Dieter Rams to a cluttered settings screen produces correct principles and concrete removals, not generic minimalism. +tags: [masters] +plugins: ["../.."] +max_turns: 8 +allowed_tools: [Read, Glob, Grep, Skill, Agent] +--- + +Use Dieter Rams' design principles to simplify our app's settings screen. Right now it has: 42 toggles on one long page with no grouping, a decorative gradient header with an illustration, three different "Save" buttons in different places, tooltips on every label, and an "Advanced" section that most users never open but that sits at the top. diff --git a/plugins/design-mastery/evals/visual-historian-retro/graders/context-and-application.md b/plugins/design-mastery/evals/visual-historian-retro/graders/context-and-application.md new file mode 100644 index 0000000..494a85d --- /dev/null +++ b/plugins/design-mastery/evals/visual-historian-retro/graders/context-and-application.md @@ -0,0 +1,8 @@ +--- +type: llm +weight: 2 +--- + +PASS if the response identifies the look as Art Deco, places it correctly in the 1920s and 1930s (mentioning the 1925 Paris exposition or the machine-age glamour context is a plus), connects at least three of the listed markers (sunburst, stepped forms, chevrons, gold and black, geometric all-caps sans) to that movement, and gives concrete advice for using the style deliberately in a modern UI (for example restraint, limiting ornament to a few moments, keeping body text readable). + +FAIL if it names the wrong movement as the main source, gets the period wrong, or gives no practical guidance. diff --git a/plugins/design-mastery/evals/visual-historian-retro/graders/names-art-deco.md b/plugins/design-mastery/evals/visual-historian-retro/graders/names-art-deco.md new file mode 100644 index 0000000..1eaee85 --- /dev/null +++ b/plugins/design-mastery/evals/visual-historian-retro/graders/names-art-deco.md @@ -0,0 +1,7 @@ +--- +type: regex +pattern: "art\\s+deco" +flags: i +match: contains +target: last_message +--- diff --git a/plugins/design-mastery/evals/visual-historian-retro/prompt.md b/plugins/design-mastery/evals/visual-historian-retro/prompt.md new file mode 100644 index 0000000..874854c --- /dev/null +++ b/plugins/design-mastery/evals/visual-historian-retro/prompt.md @@ -0,0 +1,10 @@ +--- +name: visual-historian-retro +description: Given the visual markers of a retro landing page, the plugin names the movement correctly and explains how to use it on purpose. +tags: [history, movements] +plugins: ["../.."] +max_turns: 8 +allowed_tools: [Read, Glob, Grep, Skill, Agent] +--- + +Our landing page mockup feels "retro" and I can't say why. It has a black background, gold (#C9A227) accents, a sunburst of thin radiating lines behind the headline, stepped borders on the cards, chevron dividers, and a tall geometric sans-serif set in all caps. Where does this look come from, and how do we keep it from feeling like a costume? diff --git a/plugins/design-mastery/skills/brand-systems/SKILL.md b/plugins/design-mastery/skills/brand-systems/SKILL.md index a5e93a9..cc9d0ae 100644 --- a/plugins/design-mastery/skills/brand-systems/SKILL.md +++ b/plugins/design-mastery/skills/brand-systems/SKILL.md @@ -1,6 +1,6 @@ --- name: brand-systems -description: Building comprehensive brand identity systems from strategy to implementation. Covers logo design, color palettes, typography pairing, voice guidelines, and system documentation. Use when creating new brands, rebranding, or systematizing existing identities. +description: "Brand identity building blocks: positioning, personality, archetypes, logo systems, color palettes, type pairing, voice, and guidelines documentation. Use when creating a brand, rebranding, or turning an existing identity into tokens and rules others can follow." --- # Brand Systems @@ -118,7 +118,7 @@ Primary: Tailwind: blue-600 Usage: CTAs, links, primary actions - Accessible on: white (4.5:1), gray-50 (4.2:1) + Accessible on: white (5.17:1), gray-50 (4.95:1) ``` **Extended Palette**: @@ -368,6 +368,8 @@ Style: [Visual approach in 2-3 words] ## Resources +Read the matching file when a brand task needs more depth than the summary above. + - **assets/brand-canvas-template.md**: Fillable brand canvas - **references/logo-design.md**: Logo creation principles - **references/color-palettes.md**: Color theory for branding diff --git a/plugins/design-mastery/skills/brand-systems/references/brand-voice.md b/plugins/design-mastery/skills/brand-systems/references/brand-voice.md new file mode 100644 index 0000000..a991dfa --- /dev/null +++ b/plugins/design-mastery/skills/brand-systems/references/brand-voice.md @@ -0,0 +1,125 @@ +# Brand voice + +Voice is the brand's personality in words. It is part of the identity system in the same way color and type are, and in product UI it is often the part users meet most: button labels, error messages, empty states, and onboarding are all writing. + +## Voice vs. tone + +**Voice stays the same; tone adapts to the situation.** Mailchimp's public Content Style Guide puts it this way: "You have the same voice all the time, but your tone changes." A person keeps the same personality at a celebration and at a hospital bedside, but speaks differently in each. + +| | Voice | Tone | +|---|-------|------| +| Changes? | No, it is constant | Yes, per context and reader state | +| Defined by | 3 to 4 personality attributes | A tone map per situation | +| Example | "Plainspoken, warm, precise" | Warmer in onboarding, calmer in errors, drier in legal | + +Mailchimp describes its own voice as plainspoken, genuine, translators (explaining complex things simply), and dry humor. It is a useful public model of attributes that are specific enough to write with. + +## Defining voice attributes + +Pick three or four attributes. For each, write what it means, what it does not mean, and a do/don't pair. "Friendly" alone is too vague to guide anyone. + +| Attribute | We are | We are not | Do | Don't | +|-----------|--------|------------|----|-------| +| **Plainspoken** | Direct, short sentences, common words | Blunt or cold | "Your card was declined." | "A payment authorization failure has occurred." | +| **Warm** | Human, considerate | Gushing or cute | "Welcome back, Ana." | "Yay!!! You're back, superstar!" | +| **Confident** | Clear recommendations | Arrogant or pushy | "We recommend the annual plan for teams." | "Only an amateur would pick monthly." | +| **Precise** | Specific numbers, names, next steps | Jargon-heavy | "Upload files up to 25 MB." | "Upload reasonably sized files." | + +## The four dimensions of tone + +Nielsen Norman Group (Kate Moran, "The Four Dimensions of Tone of Voice", 2016) describes tone along four spectrums. Copy can sit anywhere on each line: + +| Dimension | One end | Other end | +|-----------|---------|-----------| +| Humor | Funny | Serious | +| Formality | Formal | Casual | +| Respect | Respectful | Irreverent | +| Enthusiasm | Enthusiastic | Matter-of-fact | + +Place the brand's default on each spectrum, then define how far each situation may move from that default. + +## Tone map by situation + +| Situation | Reader state | Tone shift | Example | +|-----------|--------------|-----------|---------| +| **Onboarding** | Curious, uncertain | Warmer, encouraging, step by step | "Let's set up your first project. It takes three steps." | +| **Success** | Satisfied | Brief, lightly positive | "Invoice sent." | +| **Empty state** | Unsure what to do | Helpful, points to the first action | "No projects yet. Create one to start tracking work." | +| **Error** | Frustrated, blocked | Calm, serious, no jokes, clear fix | "We couldn't save your changes. Check your connection and try again." | +| **Destructive confirm** | Cautious | Serious, explicit about consequences | "Delete 12 files? This can't be undone." | +| **Marketing** | Evaluating | Most expressive the voice allows | "Close the books without the spreadsheet marathon." | +| **Legal and billing** | Careful | Formal, plain, complete | "Your card will be charged $20 for each billing period until you cancel." | + +Humor belongs in low-stakes moments. It never belongs in errors, payment failures, security messages, or anything involving loss. + +## Microcopy patterns + +### Buttons +- Use a verb that names the outcome: "Create invoice", not "Submit" +- Match the button to the question: a dialog titled "Delete project?" gets "Delete project" and "Cancel", not "Yes" and "No" +- Keep labels consistent across the product: if it is "Save" in one place, it is not "Apply" elsewhere for the same action + +### Error messages +A useful error says **what happened**, **why** (when known and useful), and **what to do next**, placed next to the problem. + +```text +Bad: Error 422 +Bad: Invalid input +Good: Enter a date after today. +Good: That email is already registered. Sign in instead? +``` + +Do not blame the user ("You entered an invalid value"); describe the fix. + +### Empty states +State why it is empty, what will appear, and the first action. One sentence plus one button is usually enough. + +### Form labels and help text +- Labels are nouns ("Company name"); help text explains format or purpose +- Do not use placeholder text as the label; it disappears when typing starts +- Mark optional fields rather than every required one when most are required + +### Notifications +Lead with the change, then the detail: "Payment received: $1,200 from Acme Co." + +## How voice maps onto UI components + +| Component | Voice guidance to document | +|-----------|----------------------------| +| Buttons | Verb style, casing (sentence case or title case), length limit | +| Headings | Sentence case or title case, question headings allowed or not | +| Errors | Structure (what, why, next step), banned words | +| Toasts | Maximum length, past tense for completed actions | +| Empty states | Template: explanation + first action | +| Tooltips | When allowed, maximum length, no essential information hidden in them | +| Emails | Greeting and sign-off conventions, subject line style | + +Pair this table with the design system so each component's documentation shows its copy rules next to its visual rules. + +## Writing guidelines to specify + +- **Person**: "we" and "you", or impersonal +- **Casing**: sentence case for UI is easier to scan and translate; pick one and apply it everywhere +- **Contractions**: allowed or not (contractions read as more conversational) +- **Numbers and dates**: numerals in UI, one date format per locale +- **Punctuation**: periods in single-sentence UI strings or not; no exclamation marks in errors +- **Word list**: preferred terms, banned terms, and product nouns with exact capitalization +- **Inclusive, plain language**: avoid idioms that do not translate; write for a broad reading level +- **Localization**: leave room for text expansion (many languages run longer than English), avoid text baked into images + +## Voice checklist + +- [ ] Three or four voice attributes, each with "we are / we are not" and a do/don't example +- [ ] Default position on each of the four tone dimensions +- [ ] Tone map for onboarding, success, empty, error, destructive, marketing, and legal contexts +- [ ] Button, error, empty state, and notification patterns documented +- [ ] Casing, person, punctuation, and number rules chosen +- [ ] Word list maintained with product terms +- [ ] Copy rules shown alongside component specs in the design system +- [ ] Sample screens rewritten in the voice and reviewed by someone outside the team + +## Related references + +- [../assets/brand-canvas-template.md](../assets/brand-canvas-template.md): personality and archetype inputs +- [typography-pairing.md](typography-pairing.md): making type personality agree with verbal voice +- [color-palettes.md](color-palettes.md): the visual counterpart of tone shifts (semantic colors for errors and success) diff --git a/plugins/design-mastery/skills/brand-systems/references/color-palettes.md b/plugins/design-mastery/skills/brand-systems/references/color-palettes.md new file mode 100644 index 0000000..5775450 --- /dev/null +++ b/plugins/design-mastery/skills/brand-systems/references/color-palettes.md @@ -0,0 +1,169 @@ +# Brand color palettes + +A brand palette is a system, not a swatch. It has to cover identity (the colors people remember), interface (text, surfaces, borders, states), and accessibility (every pairing that carries meaning must be readable). This reference builds on [color-theory.md](../../design-principles/references/color-theory.md), which covers harmony types and the 60-30-10 proportion rule. + +## Palette structure + +| Layer | Contents | Typical size | +|-------|----------|--------------| +| **Primary** | The signature brand color, with a full tonal scale | 1 hue, 11 steps | +| **Neutrals** | Grays for text, surfaces, borders (often tinted toward the primary hue) | 1 hue, 11 steps | +| **Accent** | A contrasting color for highlights and marketing moments | 1 to 2 hues | +| **Semantic** | Success, warning, danger, info | 4 hues, each with text, fill, and subtle-background steps | +| **Data** | Categorical colors for charts, distinguishable from each other and from semantic colors | 6 to 8 hues | + +Resist adding brand colors. Each extra hue multiplies the pairings you must test and dilutes recognition. + +## Tonal scales (50 to 950) + +The convention popularized by Tailwind CSS is an 11-step scale: 50, 100, 200 ... 900, 950. Lower numbers are lighter. + +| Step | Typical role (light theme) | +|------|-----------------------------| +| 50 to 100 | Subtle backgrounds, selected rows, tinted panels | +| 200 to 300 | Borders on tinted surfaces, disabled fills, decorative | +| 400 to 500 | Icons, large graphics, fills where text is not placed on them | +| 600 to 700 | Primary buttons, links, text in the brand color | +| 800 to 950 | Headings in brand color, dark surfaces | + +### Building a scale in a perceptual color space + +HSL lightness is not perceptual: a yellow and a blue at the same HSL lightness look very different in brightness. OKLCH (from Bjorn Ottosson's Oklab, 2020, and part of CSS Color Module Level 4) keeps perceived lightness consistent across hues, which makes scales predictable. Tailwind CSS v4 defines its default palette in OKLCH. + +```css +:root { + /* oklch(lightness chroma hue) */ + --brand-50: oklch(0.97 0.02 262); + --brand-100: oklch(0.93 0.04 262); + --brand-300: oklch(0.80 0.10 262); + --brand-500: oklch(0.62 0.19 262); + --brand-600: oklch(0.55 0.21 262); + --brand-700: oklch(0.48 0.19 262); + --brand-900: oklch(0.33 0.12 262); + --brand-950: oklch(0.25 0.08 262); +} +``` + +Method: +1. Fix the hue of your brand color +2. Step lightness evenly from about 0.97 down to about 0.25 +3. Reduce chroma toward both ends (very light and very dark colors cannot hold high chroma, and the browser will clip out-of-gamut values) +4. Check the actual contrast of the steps you plan to pair; the numbers above are illustrative, not measured + +## WCAG contrast + +WCAG 2.x contrast ratio = (L1 + 0.05) / (L2 + 0.05), where L1 and L2 are the relative luminances of the lighter and darker colors. Ratios range from 1:1 to 21:1. + +| Success criterion | Level | Requirement | +|-------------------|-------|-------------| +| 1.4.3 Contrast (Minimum) | AA | 4.5:1 for normal text; 3:1 for large text | +| 1.4.6 Contrast (Enhanced) | AAA | 7:1 for normal text; 4.5:1 for large text | +| 1.4.11 Non-text Contrast | AA | 3:1 for UI component boundaries, states, and meaningful graphics against adjacent colors | +| 1.4.1 Use of Color | A | Color must not be the only way information is conveyed | + +**Large text** in WCAG means at least 18 point (24 CSS px) regular, or at least 14 point (about 18.66 CSS px) bold. A 18px regular body size is not large text. + +### Measured pairs (Tailwind v3 hex values) + +| Pair | Ratio | Normal text AA | Large text / UI 3:1 | +|------|-------|----------------|---------------------| +| slate-900 on white | 17.85 | Pass | Pass | +| slate-600 on white | 7.58 | Pass | Pass | +| slate-500 on white | 4.76 | Pass | Pass | +| slate-400 on white | 2.56 | Fail | Fail | +| white on blue-600 | 5.17 | Pass | Pass | +| white on blue-500 | 3.68 | Fail | Pass | +| red-600 on white | 4.83 | Pass | Pass | +| red-500 on white | 3.76 | Fail | Pass | +| green-700 on white | 5.02 | Pass | Pass | +| green-600 on white | 3.30 | Fail | Pass | +| amber-700 on white | 5.02 | Pass | Pass | +| amber-500 on white | 2.15 | Fail | Fail | +| slate-300 border on white | 1.48 | n/a | Fail | + +Practical consequences: +- Semantic text on white usually needs the 600 or 700 step, not 500 +- Input borders need about the 500 step to meet 1.4.11 when the border is the only thing that shows the field +- Yellow and amber rarely work as text on white; use them as fills with dark text + +**APCA** (Accessible Perceptual Contrast Algorithm) is a newer method developed during WCAG 3 drafting. It models perceived contrast better, especially for dark themes, but it is not a WCAG 2.x conformance requirement. Use WCAG 2.x ratios for compliance; APCA can inform choices. + +## Color vision deficiency + +Red-green color vision deficiency affects about 8% of males and 0.5% of females of Northern European ancestry (MedlinePlus, US National Library of Medicine); rates are lower in most other populations. + +- Never encode status by red versus green alone: add an icon, a label, or a pattern +- Prefer blue/orange over red/green for binary data encodings +- Vary lightness, not only hue, between chart series +- Simulate: Chrome DevTools, Rendering panel, "Emulate vision deficiencies" + +```html + + Paid + + + Overdue + +``` + +## Associations are cultural, not universal + +Color meaning depends on culture, category, and context. White is associated with weddings in much of the West and with mourning in parts of East Asia; red can signal danger, luck, or a sale. Treat any "blue means trust" rule as a category convention (many banks use blue, so blue reads as "bank"), not a law of psychology. Choose colors that separate you from competitors and fit your audience, then test with that audience. + +## Dark mode palettes + +Dark mode is a second palette, not an inversion. + +| Concern | Light theme | Dark theme | +|---------|-------------|------------| +| Page background | white or 50 | 900 to 950, or a dark gray such as `#121212` (Material Design's dark theme baseline) | +| Elevation | Shadows | Lighter surfaces for raised layers | +| Body text | 900 | 100 to 200 (slightly off-white reduces glare) | +| Brand color | 600 | 400 to 500 (lighter, sometimes less saturated) | +| Borders | 200 to 300 | 700 to 800 | + +Re-measure contrast in dark mode: blue-600 on slate-900 is only 3.45:1, while blue-400 on slate-900 is 7.02:1. + +```css +:root { + --surface: #ffffff; + --text: #0f172a; + --action: #2563eb; +} +@media (prefers-color-scheme: dark) { + :root { + --surface: #0f172a; + --text: #f1f5f9; + --action: #60a5fa; + } +} +``` + +## Token naming + +Use three tiers so a rebrand or a dark theme changes one layer, not every component. + +| Tier | Example | Purpose | +|------|---------|---------| +| **Primitive** | `blue-600`, `slate-100` | The raw scale; never referenced by components directly | +| **Semantic** | `color-action-primary`, `color-text-muted`, `color-border-strong`, `color-status-danger` | Meaning; remapped per theme | +| **Component** | `button-primary-bg`, `input-border` | Optional; for components with special needs | + +Name semantic tokens by role, not appearance: `color-text-muted`, not `color-gray-light`. The W3C Design Tokens Community Group publishes a JSON format for exchanging tokens between tools. + +## Palette checklist + +- [ ] One primary brand hue with a full tonal scale +- [ ] Neutral scale that suits the primary (tinted or true gray, chosen deliberately) +- [ ] Semantic colors with text-safe steps (usually 600 or 700 on white) +- [ ] Every text pairing measured against WCAG 1.4.3 +- [ ] Component boundaries and focus indicators meet 3:1 (1.4.11) +- [ ] No information conveyed by color alone +- [ ] Dark theme defined and measured separately +- [ ] Tokens named by role, with primitives hidden behind semantic names + +## Related references + +- [color-theory.md](../../design-principles/references/color-theory.md): harmony, proportion, color relationships +- [logo-design.md](logo-design.md): logo color versions +- [typography-pairing.md](typography-pairing.md): text color within the type system diff --git a/plugins/design-mastery/skills/brand-systems/references/logo-design.md b/plugins/design-mastery/skills/brand-systems/references/logo-design.md new file mode 100644 index 0000000..336182f --- /dev/null +++ b/plugins/design-mastery/skills/brand-systems/references/logo-design.md @@ -0,0 +1,157 @@ +# Logo design + +A logo is an identifier, not an explanation. Paul Rand put it plainly in his essay "Logos, Flags, and Escutcheons" (1991): "A logo derives its meaning from the quality of the thing it symbolizes, not the other way around." Design the mark to be distinctive and durable; the business gives it meaning over time. + +## Logo types + +| Type | What it is | Strengths | Watch for | Well-known examples | +|------|------------|-----------|-----------|---------------------| +| **Wordmark** | The name set in custom or chosen type | Builds name recognition directly | Long names get small; needs strong type | Google, Coca-Cola | +| **Lettermark** | Initials or abbreviation | Compact, good for long names | Initials alone carry little meaning early on | IBM, HBO | +| **Symbol (pictorial)** | A recognizable picture | Memorable, language-independent | Needs time and exposure to stand alone | Apple, Twitter's former bird | +| **Abstract mark** | A non-literal shape | Ownable, flexible | Meaning must be built through use | Nike Swoosh, Mastercard circles | +| **Combination** | Symbol plus wordmark | Flexible; symbol can later stand alone | Must work split apart and together | Adidas, Lacoste | +| **Emblem** | Text enclosed in a badge or seal | Heritage, institutional feel | Detail breaks down at small sizes | Starbucks, many universities | +| **Mascot** | A character | Warm, story-friendly | Hard to use at favicon size | KFC's Colonel | + +For a new brand with no recognition, a wordmark or combination mark is usually safer than a lone abstract symbol. + +## Evaluation criteria + +Criteria that working identity designers apply, in the spirit of Rand's writing: + +| Criterion | Test | +|-----------|------| +| **Distinctive** | Put it beside competitors' marks; is it clearly different? | +| **Simple** | Can someone sketch it from memory after a brief look? | +| **Scalable** | Does it hold at 16px and on a billboard? | +| **Versatile** | Does it work in one color, reversed, on photos, embroidered, engraved? | +| **Appropriate** | Does its tone fit the audience and category? | +| **Durable** | Does it depend on a current trend (a gradient style, a fashionable typeface)? | + +## Famous marks and what they teach + +| Mark | Designer | Year | Lesson | +|------|----------|------|--------| +| Nike Swoosh | Carolyn Davidson | 1971 | A simple abstract mark gains meaning through use; she was paid $35 | +| Apple rainbow apple | Rob Janoff | 1977 | The bite gives scale and keeps it from reading as another fruit | +| I Love NY | Milton Glaser | 1977 | A rebus (I, heart, NY) can carry emotion in three glyphs | +| IBM eight-bar logo | Paul Rand | 1972 | Stripes turned a heavy slab-serif lettermark into something that feels fast | +| FedEx | Lindon Leader at Landor Associates | 1994 | Negative space (the arrow between E and x) rewards a second look | +| WWF panda | Sir Peter Scott, from sketches by Gerald Watterson | 1961 (refined by Landor, 1986) | Closure: the viewer completes the missing outlines | +| Mastercard | Pentagram (Michael Bierut) | 2016 | Reduce to the core; the circles later ran without the name (from 2019) | + +## Construction + +1. **Start from strategy**: positioning, personality, and the one idea the mark should hold (see the brand-systems SKILL) +2. **Sketch widely**: many rough directions on paper before any vector work +3. **Build on geometry, then correct optically**: circles and diagonals often need overshoot and weight compensation to look even +4. **Set the wordmark with care**: adjust kerning pair by pair; customize a few letters so the name is ownable +5. **Test in context early**: app icon, website header, social avatar, invoice, signage + +### Optical corrections that matter + +| Issue | Correction | +|-------|------------| +| Round shapes look smaller than squares of equal height | Let curves overshoot the baseline and cap height slightly | +| Horizontal strokes look heavier than vertical ones | Thin horizontals a little | +| Reversed (light on dark) marks look bolder | Supply a slightly lighter reverse version if needed | +| Tight counters fill in when small | Open them up in the small-size version | + +## Sizing and small-size versions + +Large and small uses often need different drawings, not just scaling. + +| Context | Typical size | Version | +|---------|--------------|---------| +| Favicon | 16 to 32px | Symbol only or a single letter, extra-bold, no fine detail | +| App icon | 180px (Apple touch icon), 192 and 512px (web app manifest) | Symbol on a solid field, safe padding | +| Social avatar | Circular crop | Symbol centered, nothing important near the edge | +| Header | 24 to 40px tall | Horizontal lockup | +| Print | Defined by a minimum width | Full lockup with clear space | + +Define a **minimum size** for every lockup (for example, "horizontal lockup never below 96px wide on screen"). + +### Favicon set + +```html + + + + +``` + +Browser support for SVG favicons varies, so keep the ICO or PNG fallback. + +## Clear space and lockups + +**Clear space**: the minimum empty area around the logo, defined by a unit taken from the logo itself (for example, the height of the wordmark's x-height or the width of the symbol's stroke). Nothing else enters that zone. + +**Lockups** to define: + +| Lockup | Use | +|--------|-----| +| Horizontal (symbol left, name right) | Headers, email signatures | +| Stacked (symbol above name) | Square spaces, splash screens | +| Symbol only | Favicons, avatars, app icons | +| Wordmark only | Where the symbol would be too small or redundant | + +Specify the exact spacing between symbol and wordmark in each lockup, and never let users rebuild lockups by hand. + +## Color versions + +Every logo needs: + +- [ ] Full-color version on light backgrounds +- [ ] Full-color or adapted version on dark backgrounds +- [ ] One-color (solid black) version +- [ ] Reversed (solid white) version +- [ ] A rule for photographic backgrounds (use the one-color version on a scrim, or a solid badge) + +If the mark only works in full color, it is not finished. Gradients and fine tonal effects should be optional layers, not the structure of the mark. + +## Delivering the logo + +### SVG for the web + +```html + + Acme + + +``` + +- Use `viewBox` and no fixed `width`/`height` so CSS controls size +- Use `fill="currentColor"` for one-color versions so the mark follows text color and dark mode +- Give it an accessible name (`` or `aria-label`); if the logo links home, the link needs the name +- Optimize with a tool such as SVGO, and outline text so the file does not depend on installed fonts + +### Asset package + +| Format | Purpose | +|--------|---------| +| SVG | Web, apps, scalable use | +| PNG (transparent, several sizes) | Office documents, platforms that reject SVG | +| PDF or EPS | Print vendors | +| ICO + PNG icons | Favicons, app icons | + +Name files predictably: `acme-logo-horizontal-fullcolor.svg`, `acme-logo-symbol-white.svg`. + +## Testing checklist + +- [ ] Recognizable at 16px (favicon) and at large format +- [ ] Works in one color and reversed +- [ ] Holds up on light, dark, and photographic backgrounds +- [ ] Distinct from competitors and from well-known marks (run a trademark search before launch) +- [ ] No unintended shapes or readings when rotated, cropped to a circle, or seen upside down +- [ ] Wordmark kerning checked at display size +- [ ] Clear space and minimum sizes documented +- [ ] SVG has an accessible name and uses `currentColor` where appropriate +- [ ] Full asset package exported and named consistently + +## Related references + +- [color-palettes.md](color-palettes.md): brand colors the logo sits within +- [typography-pairing.md](typography-pairing.md): type that accompanies the wordmark +- [brand-voice.md](brand-voice.md): the verbal side of the identity +- [../assets/brand-canvas-template.md](../assets/brand-canvas-template.md): strategy inputs before sketching diff --git a/plugins/design-mastery/skills/brand-systems/references/typography-pairing.md b/plugins/design-mastery/skills/brand-systems/references/typography-pairing.md new file mode 100644 index 0000000..ef65551 --- /dev/null +++ b/plugins/design-mastery/skills/brand-systems/references/typography-pairing.md @@ -0,0 +1,133 @@ +# Typography pairing + +A type system usually needs two families at most, sometimes one. Pairing is about giving each typeface a clear job and making sure the two look like they belong to the same brand. This extends [typography-fundamentals.md](../../design-principles/references/typography-fundamentals.md), which covers anatomy, scale, line length, and loading. + +## Roles first, fonts second + +Decide the roles before picking families. + +| Role | Job | Priorities | +|------|-----|------------| +| **Display** | Headlines, hero text, big numbers | Personality, shape at large sizes | +| **Text** | Paragraphs, articles, descriptions | Legibility at 14 to 18px, even texture, good italics | +| **UI** | Labels, buttons, navigation, tables | Clarity at small sizes, tabular figures, compact width | +| **Mono** | Code, IDs, aligned data | Distinct characters (0/O, 1/l/I), equal widths | + +Often text and UI share one family, and display is either the same family at a heavier weight or a second family with more character. + +## Pairing logic + +### 1. Contrast in classification + +Pair families that differ clearly in structure, so the roles are obvious. + +| Display | Text/UI | Why it works | +|---------|---------|--------------| +| High-contrast serif | Neutral sans | Serif carries voice, sans carries information | +| Geometric sans | Humanist sans or serif | Geometric shapes at large sizes, warmer forms for reading | +| Slab serif | Grotesque sans | Sturdy headlines, plain body | + +Avoid pairing two families from the same classification that differ only slightly (two similar geometric sans faces); the result looks like a mistake rather than a choice. + +### 2. Shared proportions + +Contrast in style, harmony in proportion. Check: +- **x-height**: similar x-heights make the two families look the same size when set together; `font-size-adjust` can normalize the difference in modern browsers +- **Width**: a very condensed display face with a wide text face can feel unrelated +- **Stroke weight at the chosen weights**: the text face should not look heavier than the headline face + +### 3. Superfamilies + +A superfamily is designed as matching sans, serif, and often mono versions sharing proportions. It is the lowest-risk way to get contrast without clashes. + +| Superfamily | Members | Designers | +|-------------|---------|-----------| +| IBM Plex | Sans, Serif, Mono, plus Condensed and several scripts | Mike Abbink at IBM with Bold Monday, 2017 | +| Source | Source Sans, Source Serif, Source Code | Paul D. Hunt (Sans), Frank Griesshammer (Serif), Adobe | +| Merriweather | Merriweather, Merriweather Sans | Eben Sorkin (Sorkin Type) | +| Roboto | Roboto, Roboto Slab, Roboto Mono | Christian Robertson for Google | + +## Proven pairings + +| Pairing | Classification | Character | Fits | +|---------|----------------|-----------|------| +| **Playfair Display** + **Inter** | High-contrast transitional serif (Claus Eggers Sorensen) + neo-grotesque sans for screens (Rasmus Andersson) | Editorial, polished | Magazines, portfolios, premium marketing | +| **Fraunces** + **Work Sans** | Soft "old style" variable display serif (Undercase Type: Phaedra Charles and Flavia Zimbardi) + grotesque sans (Wei Huang) | Warm, a little playful | Food, lifestyle, friendly consumer brands | +| **Source Serif** + **Source Sans** | Companion serif and humanist sans (Adobe) | Calm, trustworthy, readable | Documentation, publishing, public sector | +| **IBM Plex Sans** + **IBM Plex Mono** | Grotesque sans + matching mono | Technical, systematic | Developer tools, data products | +| **Space Grotesk** + **JetBrains Mono** | Proportional sans derived from Colophon's Space Mono (Florian Karsten) + coding mono (JetBrains) | Technical with personality | Dev tools, crypto, engineering brands | +| **Inter** alone | One family, weights and optical sizes for all roles | Neutral, efficient | Dashboards, SaaS apps | + +Verify every family's current licence and character set (languages, weights, italics) before committing. + +## Variable fonts + +OpenType variable fonts put a design space in one file. Registered axes include weight (`wght`), width (`wdth`), optical size (`opsz`), italic (`ital`), and slant (`slnt`); families can add custom axes (Fraunces adds `SOFT` and `WONK`). + +```css +@font-face { + font-family: "Brand Sans"; + src: url("/fonts/brand-sans-var.woff2") format("woff2"); + font-weight: 100 900; /* declare the supported range */ + font-display: swap; +} + +h1 { font-weight: 650; } /* any value in the range */ +body { font-optical-sizing: auto; } /* use opsz when the font has it */ +.tag { font-variation-settings: "wdth" 85; } +``` + +Benefits: fewer files, in-between weights for fine hierarchy, optical sizing that tightens display sizes and opens text sizes. Cost: a single variable file can be larger than one or two static weights, so subset it. + +## Fallback stacks + +Always end a stack with fallbacks that resemble the brand font, then a generic family. + +```css +:root { + --font-sans: "Inter", ui-sans-serif, system-ui, -apple-system, "Segoe UI", Roboto, Arial, sans-serif; + --font-serif: "Source Serif 4", ui-serif, Georgia, Cambria, "Times New Roman", serif; + --font-mono: "JetBrains Mono", ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; +} +``` + +To reduce layout shift when the web font swaps in, tune the fallback with `@font-face` descriptors such as `size-adjust`, `ascent-override`, and `descent-override`, or let a framework tool that generates adjusted fallbacks do it. + +## Fluid type with clamp() + +`clamp(min, preferred, max)` scales type smoothly between breakpoints. + +```css +h1 { font-size: clamp(2rem, 1.25rem + 3vw, 3.5rem); } +h2 { font-size: clamp(1.5rem, 1.1rem + 1.6vw, 2.25rem); } +p { font-size: clamp(1rem, 0.95rem + 0.25vw, 1.125rem); } +``` + +Keep a `rem` term in the preferred value. A preferred value of pure `vw` does not respond to the user's text-size settings or zoom in the same way, which works against WCAG 1.4.4 (Resize Text). Scale display sizes more than body sizes; body text should barely move. + +In Tailwind, arbitrary values work: `text-[clamp(2rem,1.25rem+3vw,3.5rem)]`. + +## Licensing + +- Most families on Google Fonts are released under the SIL Open Font License (OFL); a smaller number use Apache 2.0 or the Ubuntu Font Licence. OFL fonts can be used commercially and self-hosted; they cannot be sold on their own, and modified versions may not reuse Reserved Font Names +- Commercial fonts are licensed per use: desktop, web (often by pageviews or domains), app embedding, and broadcast are frequently separate licences +- A font installed on your machine is not automatically licensed for web or app use +- Record the licence and source of every font in the brand guidelines + +## Pairing checklist + +- [ ] Roles defined (display, text, UI, mono) before choosing families +- [ ] At most two families, or one superfamily +- [ ] Display and text faces differ clearly in classification or weight +- [ ] x-heights and widths look compatible when set side by side +- [ ] Text face tested at 14 to 18px in real paragraphs, including italics and numerals +- [ ] UI face has tabular figures for tables and prices (`tabular-nums`) +- [ ] Fallback stacks defined for every family +- [ ] Fluid sizes keep a `rem` component +- [ ] Licences confirmed for every platform the brand uses + +## Related references + +- [typography-fundamentals.md](../../design-principles/references/typography-fundamentals.md): anatomy, scale, readability, loading +- [logo-design.md](logo-design.md): wordmark type and its relationship to the system +- [brand-voice.md](brand-voice.md): matching type personality to verbal voice diff --git a/plugins/design-mastery/skills/design-masters/SKILL.md b/plugins/design-mastery/skills/design-masters/SKILL.md index c9b7f07..43804ae 100644 --- a/plugins/design-mastery/skills/design-masters/SKILL.md +++ b/plugins/design-mastery/skills/design-masters/SKILL.md @@ -1,6 +1,6 @@ --- name: design-masters -description: Deep knowledge of legendary designers and their enduring contributions. Learn from Saul Bass, Massimo Vignelli, Dieter Rams, Paula Scher, and others whose work defines excellence. Use when seeking inspiration, understanding design history, or applying proven approaches. +description: "Working profiles of Saul Bass, Massimo Vignelli, Dieter Rams, Paula Scher, Josef Müller-Brockmann, David Carson, and Paul Rand: key works, principles, and how to apply each in UI work. Use when a design needs a proven approach, a named reference to follow, or a lesson from a specific master." --- # Design Masters @@ -58,22 +58,23 @@ Approach: 3. **Pragmatics**: How does it function in context? 4. **Discipline**: Constraint breeds creativity 5. **Appropriateness**: Fit context, not ego -6. **Ambiguity**: Eliminate it +6. **Ambiguity**: Welcome a plurality of meanings; reject vagueness 7. **Design is One**: Universal principles apply everywhere 8. **Visual Power**: Strength through simplicity 9. **Intellectual Elegance**: Clever, not complicated 10. **Timelessness**: Enduring over fashionable -11. **Responsibility**: Design affects lives -12. **Equity**: Quality for all, not just elites +11. **Responsibility**: To the work itself, to the client (economically sound solutions), and to the public +12. **Equity**: Respect the recognition an established mark has earned; do not redesign for change's sake #### Limited Typography -Vignelli used only 5 typefaces in his career: +Vignelli argued that a designer needs only a few basic typefaces. His 1991 exhibition "A Few Basic Typefaces" showed decades of work set in only four: - Helvetica (universal clarity) - Bodoni (elegant contrast) - Century Expanded (readable serifs) -- Futura (geometric purity) - Garamond (classical warmth) +He also used Futura, and The Vignelli Canon allows a few more (Times among them) while holding that most typefaces exist for commercial reasons, not need. + #### Essential Works - **NYC Subway Map** (1972): Clarity over geography - **American Airlines** (1967): Helvetica dominance @@ -154,8 +155,8 @@ Process: #### Essential Works - **The Public Theater** (1994): Type as urban texture -- **Citibank** (1998): Humanizing corporate identity -- **Windows 8** (2012): Metro design language +- **Citi** (1999): Humanizing corporate identity after the Citicorp and Travelers merger +- **Windows 8 logo** (2012): The window flag redrawn as a window in perspective (the logo, not Microsoft's Metro design language) - **High Line** (2009): Environmental typography #### Apply Her Lesson @@ -237,9 +238,9 @@ Implementation: - Found textures #### Essential Works -- **Ray Gun Magazine** (1992-96): Design as culture +- **Ray Gun** (art director from 1992): Design as culture - **Beach Culture**: Breaking every rule -- **End of Print** (book): Philosophy articulated +- **The End of Print** (1995 book with Lewis Blackwell): His work and approach collected #### Apply His Lesson *When appropriate, prioritize feeling over reading.* @@ -260,13 +261,13 @@ Caution: Use sparingly **Philosophy**: "Simplicity is not the goal. It is the by-product of a good idea." #### Logo Philosophy -A logo must be: -- **Distinctive**: Unlike anything else -- **Visible**: Works at any size -- **Adaptable**: Applies to all media -- **Memorable**: Sticks after brief exposure -- **Universal**: Crosses cultural boundaries -- **Timeless**: Outlasts trends +From his essay "Logos, Flags, and Escutcheons" (1991): +- **A logo identifies**: It is a flag or a signature, not an advertisement +- **Meaning comes later**: A mark takes its meaning from the quality of what it stands for +- **Not a description**: It rarely needs to show what the business does +- **Reproducible**: It must work in one color and at very small sizes + +Checks that follow from this (a working list, not Rand's wording): distinctive, legible at any size, adaptable across media, memorable, and durable beyond current trends. #### The Rand Process 1. Understand the essence of the organization @@ -301,9 +302,12 @@ A logo must be: ## Resources +Read the matching profile when a task names a master or needs their method in depth. Each covers key works with dates, the principles to borrow, how to apply them in UI work, and common misreadings. + - **references/saul-bass.md**: Complete Bass analysis - **references/massimo-vignelli.md**: The Vignelli Canon explained - **references/dieter-rams.md**: 10 Principles applied to digital - **references/paula-scher.md**: Typography as expression - **references/david-carson.md**: Breaking rules intentionally - **references/josef-muller-brockmann.md**: Grid systems mastery +- **references/paul-rand.md**: Logo thinking, wit, and identity systems diff --git a/plugins/design-mastery/skills/design-masters/references/david-carson.md b/plugins/design-mastery/skills/design-masters/references/david-carson.md new file mode 100644 index 0000000..d5c28ba --- /dev/null +++ b/plugins/design-mastery/skills/design-masters/references/david-carson.md @@ -0,0 +1,129 @@ +# David Carson (1955-) + +## Who he is + +David Carson was born in Corpus Christi, Texas, earned a sociology degree from San Diego State University, and was a professional surfer before he turned to design. He had little formal design training, which is part of why his work ignored conventions that trained designers took for granted. + +He art-directed surf and skate culture magazines (Transworld Skateboarding, then Beach Culture from 1989), and became widely known as the founding art director of the alternative music magazine Ray Gun, launched in 1992. He worked on Ray Gun for about three years, then opened his own studio, David Carson Design, working for clients such as Nike, Pepsi, and Levi Strauss. He received the AIGA Medal in 2014. + +His work is usually grouped with 1990s "grunge" or deconstructive typography, alongside Neville Brody in London and the Emigre magazine circle in California. The early Macintosh made layering, distortion, and mixed type fast to produce, and Carson used that freedom for editorial expression. + +**The problem he solved**: music and youth magazines competed for readers who were bored by clean corporate layouts. Carson made each spread respond to the mood of its content, so the design itself became part of the editorial voice. + +## Key works + +| Work | Year | What it demonstrates | +|------|------|----------------------| +| Beach Culture (art director) | From 1989 | A short-lived magazine that won attention for experimental layouts | +| Ray Gun (founding art director) | From 1992 | Every spread designed as a response to its content; layered, cropped, and colliding type | +| Bryan Ferry interview, Ray Gun | 1994 | An interview Carson found dull, set entirely in the symbol font Zapf Dingbats: design as editorial commentary | +| The End of Print: The Graphic Design of David Carson (with Lewis Blackwell) | 1995 | The book that made the work known outside magazines | +| 2nd Sight | 1997 | A follow-up collection of the work and its thinking | +| Cover art for Nine Inch Nails, The Fragile | 1999 | The approach applied to music packaging | + +## Principles to borrow + +### Legibility is not the same as communication + +Carson's often-repeated position is that a page can be hard to read and still communicate strongly, and that a perfectly legible page can communicate nothing. Readers of Ray Gun were meant to feel the music coverage before reading it. + +### Respond to the content + +His layouts are not a template filled with articles. Each piece is read first, and the typography reacts to it (tone, rhythm, the subject's personality). + +### Intuition over rules + +He composes by eye: crops, overlaps, and letterspacing chosen because they feel right for this spread. The discipline is in the looking, not in a written grid. + +### Texture and imperfection + +Photocopy grain, mixed fonts, cut-off words, and visible layering make a page feel made by hand and specific to its moment. + +## Applying Carson in UI work + +### Where the approach is wrong + +Interfaces are used, not only read. Expressive illegibility fails wherever a user has a task: +- Navigation, forms, buttons, and error messages +- Legal, pricing, medical, or safety information +- Dashboards, tables, and anything scanned repeatedly +- Anything that must pass WCAG contrast, reflow, and screen reader checks + +A user who cannot find the "Pay" button is not having an aesthetic experience. + +### Where it can work + +- A campaign or event microsite whose goal is mood and memorability +- A music, fashion, or art editorial feature page +- A portfolio or a single hero moment on an otherwise conventional site +- Posters, social images, and video titles produced from the web stack + +### Keep the expressive layer decorative, keep the content real + +```html +<section class="relative isolate overflow-hidden bg-black px-6 py-24 text-white"> + <!-- Expressive layer: hidden from assistive tech, not the only copy of anything --> + <div aria-hidden="true" class="pointer-events-none absolute inset-0 select-none"> + <span class="absolute -left-8 top-4 rotate-[-8deg] text-[12rem] font-black text-white/10">NOISE</span> + <span class="absolute right-0 top-32 rotate-[4deg] text-8xl italic text-red-500/40">loud</span> + </div> + + <!-- Real, readable content on top --> + <div class="relative max-w-xl"> + <h1 class="text-5xl font-black leading-none">The Loud Issue</h1> + <p class="mt-4 text-lg text-neutral-200">Twelve bands, one basement, no rules.</p> + <a class="mt-8 inline-block bg-white px-6 py-3 font-bold text-black" href="/issue">Read the issue</a> + </div> +</section> +``` + +- Mark decorative type `aria-hidden="true"` so screen readers skip it. +- The heading, text, and call to action stay legible and meet contrast. +- Keep the experiment inside one section; the rest of the page returns to a clear structure. + +### Techniques translated to the web + +| Print technique | Web equivalent | Guardrail | +|-----------------|----------------|-----------| +| Overlapping type and images | CSS grid items sharing cells, `mix-blend-mode` | Overlaps only in decorative layers | +| Words cropped by the page edge | `overflow-hidden` on a container with oversized type | Never crop real headings or labels | +| Mixed fonts in one headline | Two contrasting families, or one variable font across weights | Keep the accessible name as one plain string | +| Photocopy grain and texture | A subtle noise `background-image` or SVG filter | Keep text contrast measured against the busiest area | +| Tight or negative letterspacing | `tracking-tighter` at display sizes | Body text keeps default tracking | +| Columns that collide | Asymmetric grid templates with deliberate overlap | Test reflow at 320px and at 200 percent zoom | + +### Motion + +Kinetic, glitchy, or jittering type must respect reduced-motion preferences: + +```css +@media (prefers-reduced-motion: reduce) { + .glitch { animation: none; } +} +``` + +## Common misreadings + +| Misreading | Correction | +|------------|------------| +| "Carson proves rules do not matter" | His work depends on a trained eye and a specific editorial context; random disorder is not the same thing | +| "Grunge style is a template" | Distressed fonts and textures copied onto a SaaS page produce a costume, not a response to content | +| "Illegible is fine if it looks good" | In print editorial the reader could opt in; in UI the user has a task and often no alternative | +| "He rejected typography" | He rejected specific conventions; his work is intensely typographic | + +## Quick reference + +**When to reference Carson**: +- Editorial, music, fashion, and culture projects +- Campaign pages where mood and memorability are the goal +- Breaking a stale house style for a single, contained moment + +**His core lesson**: +*Let the design respond to the content, and know when expression serves the reader.* + +**The Carson check**: +1. Is the goal of this surface mood, or task completion? Only mood allows this approach. +2. Is every piece of essential information also present as legible, accessible text? +3. Is the expressive layer contained (one section, one page) rather than site-wide? +4. Does it respond to this specific content, or is it grunge as a costume? +5. Does it respect reduced motion and pass contrast for the real text? diff --git a/plugins/design-mastery/skills/design-masters/references/dieter-rams.md b/plugins/design-mastery/skills/design-masters/references/dieter-rams.md new file mode 100644 index 0000000..ebd4a6b --- /dev/null +++ b/plugins/design-mastery/skills/design-masters/references/dieter-rams.md @@ -0,0 +1,132 @@ +# Dieter Rams (1932-) + +> "Weniger, aber besser." (Less, but better.) + +## Who he is + +Dieter Rams was born in Wiesbaden, Germany, and studied architecture and interior design at the Wiesbaden School of Art, with a carpentry apprenticeship along the way. He joined the electrical appliance maker Braun in 1955 as an architect and interior designer, became head of design in 1961, and stayed at the company until 1997. + +Braun's design approach grew out of collaboration with teachers from the Ulm School of Design (Hochschule für Gestaltung Ulm), including Hans Gugelot and Otl Aicher. Rams turned that approach into a consistent product language: radios, record players, shavers, calculators, and kitchen appliances that shared the same calm geometry, restrained color, and clear controls. From 1959 he also designed furniture for the manufacturer Vitsœ. + +**The problem he solved**: post-war consumer electronics were new, complicated objects. Rams made them legible: you could see what each control did, and the object did not shout for attention in a living room. + +## Key works + +| Work | Year | What it demonstrates | +|------|------|----------------------| +| Braun SK 4 radio-phonograph (with Hans Gugelot) | 1956 | Clear acrylic lid instead of a wooden cabinet; nicknamed "Snow White's coffin" | +| Braun TP 1 portable radio and phonograph | 1959 | Modular, portable listening; parts that combine | +| Braun T3 pocket radio | 1958 | A grid of perforations and one round dial; often compared with the first iPod | +| 606 Universal Shelving System (Vitsœ) | 1960 | A modular system that grows and moves with the owner; still produced | +| 620 Chair Programme (Vitsœ) | 1962 | Furniture as a reconfigurable system | +| Braun ET 66 calculator (with Dietrich Lubs) | 1987 | Color used only for meaning: one accent for the result key, convex buttons that read by touch | + +The ET 66 is the most directly useful object for interface designers. Its layout, key shapes, and single yellow accent were widely noted in the calculator app Apple shipped with early versions of iOS. + +## The ten principles of good design + +Rams formulated these in the late 1970s, in response to what he described as an impenetrable confusion of forms, colors, and noises. The order and wording below follow the version published by Vitsœ. + +| # | Principle | What it means in practice | +|---|-----------|---------------------------| +| 1 | Good design is innovative | Innovation comes with technology; design develops alongside it, never as an end in itself | +| 2 | Good design makes a product useful | A product is bought to be used; design serves function, including psychological and aesthetic needs | +| 3 | Good design is aesthetic | Aesthetic quality is part of usefulness, because the things we use every day affect our well-being | +| 4 | Good design makes a product understandable | The structure explains itself; at best the product needs no manual | +| 5 | Good design is unobtrusive | Products are tools; they should be neutral and leave room for the user | +| 6 | Good design is honest | It does not make a product seem more innovative, powerful, or valuable than it is | +| 7 | Good design is long-lasting | It avoids being fashionable and so never looks dated | +| 8 | Good design is thorough down to the last detail | Nothing is arbitrary or left to chance | +| 9 | Good design is environmentally-friendly | It conserves resources and minimizes physical and visual pollution | +| 10 | Good design is as little design as possible | Less, but better: concentrate on the essential aspects, do not burden the product with non-essentials | + +## Applying Rams in UI work + +### Principles 4 and 5: understandable and unobtrusive + +- Every control should announce what it does through label, shape, and position. Icon-only buttons need a text label or at least an accessible name and tooltip. +- The interface frames the user's content. Chrome (toolbars, borders, backgrounds) should recede. + +```html +<!-- Unobtrusive chrome: neutral surface, content carries the color --> +<header class="border-b border-neutral-200 bg-white px-4 py-3"> + <nav class="flex gap-6 text-sm text-neutral-600"> + <a class="font-medium text-neutral-900" aria-current="page" href="/files">Files</a> + <a href="/shared">Shared</a> + <a href="/settings">Settings</a> + </nav> +</header> +``` + +### Principle 6: honest + +In interfaces, honesty rules out dark patterns: fake scarcity timers, pre-checked upsells, a "cancel" link styled to be invisible, progress bars that lie. An honest UI shows real state, real prices, and a cancel path as clear as the sign-up path. + +### Principle 8: thorough down to the last detail + +Details are where products feel cared for: +- Empty states, error states, and loading states designed as carefully as the happy path. +- Consistent corner radius, icon stroke width, and spacing scale. +- Focus rings that are visible, not removed. + +```css +/* Thorough: a focus style that is designed, not deleted */ +:focus-visible { + outline: 2px solid #1d4ed8; + outline-offset: 2px; +} +``` + +### The ET 66 lesson: color only for meaning + +```html +<!-- One accent, reserved for the primary result action --> +<div class="grid grid-cols-4 gap-2"> + <button class="rounded-full bg-neutral-800 text-white">7</button> + <!-- ...digits in the same neutral... --> + <button class="rounded-full bg-amber-400 text-neutral-900">=</button> +</div> +``` + +If every button has a color, none of them does. + +### Principle 10: as little design as possible + +Remove decoration that carries no information: gradients that do not signal depth, borders that duplicate spacing, icons next to labels that already say everything. Keep anything that helps the user understand or act. + +### Worked example: a settings card + +| Before | Rams principle | After | +|--------|----------------|-------| +| Gradient header, drop shadow, border, and a background tint | 10 (as little design as possible) | Plain surface, one hairline divider between groups | +| Toggle with no label, meaning shown only by color | 4 (understandable) | Toggle with a text label and a short description of the effect | +| "Upgrade" button styled brighter than "Save" | 6 (honest) | The primary action is the one the user came to do; upsells are secondary | +| Disabled state identical to enabled | 8 (thorough) | Distinct disabled style plus a reason ("Available on the team plan") | + +## Common misreadings + +| Misreading | Correction | +|------------|------------| +| "Less, but better" means cutting features | It means concentrating on the essential. A tool with the features people need, presented clearly, fits the principle; a stripped tool that cannot do the job does not | +| Rams equals white and gray | Braun used color deliberately (the calculator key accents, small colored control details). Restraint made the color meaningful | +| Minimal means no affordances | Principle 4 demands that a product explains itself. Flat, unlabeled controls fail Rams's own test | +| Apple copied Rams, so Apple equals Rams | Some Apple products drew openly on Braun forms. The principles are about honesty, longevity, and usefulness, which a visual resemblance alone does not deliver | + +## Quick reference + +**When to reference Rams**: +- Product and interface design decisions +- Simplifying a cluttered screen without losing capability +- Settings, tools, dashboards, hardware-like controls +- Arguments about dark patterns (principle 6) + +**His core lesson**: +*Concentrate on the essential, and make it understandable.* + +**The Rams check**: +1. Can a first-time user tell what each control does without help? +2. Is anything decorating rather than informing? Remove it. +3. Does anything overstate what the product does? Fix it. +4. Are empty, error, loading, and focus states designed? +5. Is color used only where it means something? +6. Will this look reasonable when current UI fashion has moved on? diff --git a/plugins/design-mastery/skills/design-masters/references/josef-muller-brockmann.md b/plugins/design-mastery/skills/design-masters/references/josef-muller-brockmann.md new file mode 100644 index 0000000..7908b44 --- /dev/null +++ b/plugins/design-mastery/skills/design-masters/references/josef-muller-brockmann.md @@ -0,0 +1,138 @@ +# Josef Müller-Brockmann (1914-1996) + +> "The grid system is an aid, not a guarantee." (Grid Systems in Graphic Design) + +## Who he was + +Josef Müller-Brockmann was born in Rapperswil, Switzerland, and studied at the Kunstgewerbeschule Zürich (the Zurich school of arts and crafts) under teachers including Ernst Keller and Alfred Willimann. He opened his own studio in Zurich in 1936 and worked first as an illustrator before moving, after the war, to the objective, typographic approach that became known as the Swiss or International Typographic Style. + +He taught at the Kunstgewerbeschule Zürich, lectured at the Ulm School of Design, and in 1958 co-founded the trilingual journal Neue Grafik (New Graphic Design) with Richard Paul Lohse, Hans Neuburg, and Carlo Vivarelli. The journal spread the Swiss approach internationally. In 1967 he became European design consultant to IBM. + +He was one of the leading figures of the Swiss style, alongside designers such as Max Bill, Armin Hofmann, and Emil Ruder; he did not invent it alone. + +**The problem he solved**: post-war communication needed to be clear across languages and audiences. His answer was objective design: a mathematical grid, sans-serif type set flush left, and composition built from the content rather than from decoration. + +## Key works + +| Work | Year | What it demonstrates | +|------|------|----------------------| +| Tonhalle Zürich concert posters, including the musica viva series | From 1950 | Music expressed through geometry, rhythm, and type on a grid, growing more abstract over time | +| Schützt das Kind! (Automobil-Club der Schweiz) | 1953 | A photomontage road-safety poster; a car too large for the frame conveys speed and danger | +| Der Film (Kunstgewerbemuseum Zürich) | 1960 | Pure typographic composition; the words and their spacing are the whole image | +| Neue Grafik (co-founder and editor) | 1958 | A journal that set the Swiss style as an international reference | +| The Graphic Artist and His Design Problems (book) | 1961 | His method for approaching visual communication | +| A History of Visual Communication (book) | 1971 | Design history as a basis for objective practice | +| Grid Systems in Graphic Design (book) | 1981 | The practical manual for building and using typographic grids | + +## Principles to borrow + +### Objectivity + +The designer's job is to organize information clearly, not to express a personal style. Content, hierarchy, and structure come first. + +### Grid construction starts from the content + +In Grid Systems in Graphic Design the grid is derived, not imposed: +1. Choose the format (page size) and the margins. +2. Choose the typeface and body size, and set the line spacing. The baseline interval becomes the basic unit. +3. Divide the type area into columns and rows (fields) whose heights are whole multiples of the line interval, separated by gutters. +4. Place text, images, and captions so they align with field edges and baselines. +5. Vary the layout by spanning different numbers of fields, not by abandoning the structure. + +The key point: the rows are built from the text's line spacing, so images and text blocks line up with baselines. + +### Asymmetric balance + +Flush-left, ragged-right text and asymmetric layouts create movement while the grid keeps order. + +### Few elements, precisely placed + +Sans-serif type (Akzidenz-Grotesk, later Helvetica and Univers), a limited palette, and generous empty space. Tension comes from scale contrast and position. + +### The grid is an aid + +His own caution: a grid makes good design easier and more consistent, but it does not create quality by itself. + +## Applying Müller-Brockmann in UI work + +### Build a baseline and module, not only columns + +```css +:root { + --baseline: 8px; /* line-height multiple */ + --body-size: 16px; + --body-leading: calc(var(--baseline) * 3); /* 24px */ + --gutter: calc(var(--baseline) * 3); /* 24px */ +} + +body { font-size: var(--body-size); line-height: var(--body-leading); } + +.layout { + display: grid; + grid-template-columns: repeat(6, minmax(0, 1fr)); + column-gap: var(--gutter); + grid-auto-rows: var(--body-leading); /* rows are multiples of the line interval */ +} +``` + +Every spacing token is a multiple of the baseline, so vertical rhythm holds across components. + +### His grid vocabulary in CSS terms + +| Grid Systems term | Meaning | CSS translation | +|-------------------|---------|-----------------| +| Format | The page or poster size | The viewport and breakpoints | +| Type area | The region inside the margins | A container with fixed padding and `max-width` | +| Column | A vertical division of the type area | `grid-template-columns` tracks | +| Field | A column divided into rows of equal height | Grid cells where row height is a multiple of the line height | +| Gutter / field interval | Space between columns and between fields | `column-gap` and `row-gap`, ideally one line interval | +| Baseline alignment | Text lines that line up across columns | A shared `line-height` unit and spacing tokens built on it | + +On screens the format changes with the device, so define the grid per breakpoint (for example 4 columns on phones, 6 on tablets, 12 on wide screens) while keeping one baseline unit. + +### Span fields for hierarchy + +```html +<main class="grid grid-cols-6 gap-x-6 gap-y-12 px-6 md:px-12"> + <h1 class="col-span-6 text-5xl font-bold leading-tight md:col-span-4">Concert season</h1> + <p class="col-span-6 text-base leading-6 md:col-span-3 md:col-start-1">Programme and dates.</p> + <figure class="col-span-6 md:col-span-3 md:col-start-4">...</figure> +</main> +``` + +- Hierarchy comes from how many columns an element spans and where it starts. +- Leave columns empty on purpose; empty fields are part of the composition. + +### Flush left, ragged right + +Default body text to `text-left`. Avoid justified text on the web: browsers do not hyphenate reliably by default, and justified narrow columns produce rivers of white space. + +### Break the grid deliberately + +When an element leaves the grid (a full-bleed image, an oversized numeral), make the break obvious and singular so it reads as intent. + +## Common misreadings + +| Misreading | Correction | +|------------|------------| +| "Swiss grid equals a 12-column CSS framework" | His grids are built from format, margins, and the text's line spacing, with rows as well as columns; a generic 12-column container is only a column division | +| "Grids make layouts boring" | His posters are dynamic; the grid enables asymmetry and tension | +| "Helvetica is the style" | Typeface is one element; structure, hierarchy, and objectivity are the method | +| "He invented Swiss design" | He was a central figure in a movement with many contributors | + +## Quick reference + +**When to reference Müller-Brockmann**: +- Layout systems, page templates, dashboards, editorial and documentation sites +- Establishing spacing tokens and vertical rhythm +- Posters, event graphics, and typographic compositions + +**His core lesson**: +*Derive the structure from the content, then compose freely inside it.* + +**The Müller-Brockmann check**: +1. Is there a baseline unit, and are all spacing values multiples of it? +2. Do columns and rows share one gutter value? +3. Is hierarchy expressed by span and position, not only by size and color? +4. Is body text flush left, ragged right, at a comfortable measure? +5. Is every departure from the grid deliberate and visible? diff --git a/plugins/design-mastery/skills/design-masters/references/massimo-vignelli.md b/plugins/design-mastery/skills/design-masters/references/massimo-vignelli.md new file mode 100644 index 0000000..c26272c --- /dev/null +++ b/plugins/design-mastery/skills/design-masters/references/massimo-vignelli.md @@ -0,0 +1,136 @@ +# Massimo Vignelli (1931-2014) + +> "I don't believe that when you write dog the type should bark!" (The Vignelli Canon) + +## Who he was + +Massimo Vignelli was born in Milan and trained in architecture in Milan and Venice. At 16 he worked as a draftsman in the office of the Castiglioni brothers, who designed everything from lamps to exhibitions. That experience shaped his central belief: design is one discipline that applies to any subject, from a spoon to a city. + +He moved to the United States, co-founded the consultancy Unimark International in the mid-1960s, and in 1971 founded Vignelli Associates with his wife and partner Lella Vignelli. Their work covered corporate identity, transit graphics, publications, packaging, furniture, and interiors. In 2008 he gave his archive to the Rochester Institute of Technology, which opened the Vignelli Center for Design Studies. + +**The problem he solved**: large organizations (airlines, transit systems, a national park service) needed visual systems that stayed consistent across thousands of items made by people who would never meet the designer. His answer was a small set of rules, a grid, and very few typefaces. + +## Key works + +| Work | Year | What It Demonstrates | +|------|------|----------------------| +| American Airlines logo | 1967 | Two Helvetica A's, one red and one blue, with a stylized eagle; in use until 2013 | +| Knoll graphics | 1960s | A furniture brand expressed through strict typography and grids | +| NYC Transit Authority Graphics Standards Manual (with Bob Noorda, Unimark) | 1970 | Wayfinding as a system: one typeface, color-coded lines, fixed sign modules | +| New York City subway diagram | 1972 | Clarity over geography; stations and lines as a diagram, not a map | +| National Park Service Unigrid System | 1977 | One grid and format family for every park brochure | +| The Vignelli Canon (book) | 2010 | His principles written down as "intangibles" and "tangibles" | + +The 1972 subway diagram is the classic case study in tradeoffs. Designers praised its clarity, while many riders complained that it distorted geography (parks and streets did not match the city above). The MTA later replaced it with a more geographic map. Both reactions are useful: a diagram is right when the task is "which line and where to change", and wrong when the task is "where am I on the street". + +## Principles to borrow + +### The intangibles (from The Vignelli Canon) + +| Intangible | What Vignelli meant | +|------------|---------------------| +| Semantics | Find the meaning of the thing before designing it: research its purpose, history, and audience | +| Syntactics | The grammar of the design: how parts relate, consistency of grid, type, and spacing (he cites Mies: "God is in the details") | +| Pragmatics | If it is not understood, it fails; test that people can actually read and use it | +| Discipline | Attention to detail and consistency; no sloppiness | +| Appropriateness | The solution must fit the specific problem, not a house style | +| Ambiguity | Positive ambiguity: a plurality of meanings that enriches a design. He explicitly rejects ambiguity as vagueness | +| Design is One | One discipline applied to any subject, regardless of style | +| Visual Power | Design must be strong in concept, form, and color; weak design fails | +| Intellectual Elegance | Elegance of thinking, not of manners; refinement over vulgarity | +| Timelessness | Against fashion and planned obsolescence | +| Responsibility | Economic and social responsibility: the most appropriate solution, no waste, responsibility to the client and to the public | +| Equity | Logo equity: an established identity has accumulated value; refine it rather than replace it for the sake of change | + +Note: Ambiguity and Equity are often misquoted. The Canon does not say "eliminate ambiguity", and Equity is about the value an existing identity has built up, not about access to design. + +### The tangibles (selected) + +- **Grids**: the grid is the underlying structure that organizes content and gives consistency. +- **Few typefaces**: in the Canon he recalls an exhibition (A Few Basic Typefaces, 1991) of work done over many years "by using only four typefaces: Garamond, Bodoni, Century Expanded, and Helvetica." He then adds that he could include Optima, Futura, Univers, Caslon, Baskerville, "and a few other modern cuts." +- **Two type sizes**: his rule of thumb was no more than two type sizes on a printed page, with large type often twice the small (for example 10 pt text and 20 pt headings). +- **Tight leading for print columns**: the Canon gives ratios such as 8 on 9, 9 on 10, and 10 on 11 pt for columns up to 70 mm, and 12 on 13 or 14 on 16 for columns up to 140 mm. These are print values; screens usually need more line height (see below). +- **White space**: he wrote that in typography the white space is more important than the black of the type. +- **Tight margins**: he liked narrow margins to create tension between content and the edge. + +## Applying Vignelli in UI work + +### Constrain the toolkit + +```js +// tailwind.config.js: a Vignelli-style constraint set +module.exports = { + theme: { + fontFamily: { + sans: ['Helvetica Neue', 'Helvetica', 'Arial', 'sans-serif'], + serif: ['EB Garamond', 'Garamond', 'serif'], + }, + extend: { + colors: { ink: '#111111', paper: '#ffffff', signal: '#d52b1e' }, + }, + }, +}; +``` + +- One sans for interface, at most one serif for editorial text. +- Two or three type sizes per screen. Create hierarchy with weight and space before adding a size. +- One accent color that always means the same thing. + +### Two sizes, weight for the rest + +```html +<article class="max-w-prose"> + <h2 class="text-xl font-bold">Departures</h2> <!-- 20px --> + <h3 class="mt-6 text-base font-bold">Platform 2</h3> <!-- same size as body, bold --> + <p class="text-base leading-relaxed">Trains to Downtown and Airport.</p> +</article> +``` + +This mirrors his advice to keep heads and subheads the same size and separate them with weight and space. + +### Translate print rules to screens + +| Canon rule (print) | Screen translation | +|--------------------|--------------------| +| Tight leading (10 on 11 pt) | Body `leading-relaxed` (1.625) or `leading-7` at 16px; screens and long line lengths need more air | +| Two sizes per page | Two or three sizes per view; each extra size must earn its place | +| Narrow margins for tension | Tight outer padding works on dense tools; keep generous padding where reading comfort matters | +| White space defines hierarchy | Use spacing tokens (`space-y-2` inside a group, `space-y-8` between groups) before adding rules or boxes | + +Do not copy print numbers literally. Borrow the reasoning: every size, margin, and line height is a deliberate, repeated decision. + +### Wayfinding thinking for navigation + +- Treat navigation like transit signage: one consistent position, one color per section, labels that are nouns people already use. +- Test the diagram against the task. A dashboard sitemap can be a clean diagram; a map of physical locations needs real geography. + +### Protect equity + +Before redesigning a product's logo, icon set, or primary color, ask what recognition it has earned. Refine (spacing, weights, contrast fixes) before replacing. + +## Common misreadings + +| Misreading | Correction | +|------------|------------| +| "Vignelli used only five typefaces" | He argued for a short list and named several more; the point is economy, not a fixed number | +| "Eliminate ambiguity" | He valued ambiguity as layered meaning and rejected only vagueness | +| "Helvetica everywhere" | He used serif faces such as Bodoni and Garamond extensively in books and identities | +| "The subway diagram failed" | It succeeded at its task and was replaced for a different one; the lesson is fitting the representation to the task | + +## Quick reference + +**When to reference Vignelli**: +- Design systems and token sets +- Wayfinding, navigation, transit-like information +- Identity programs that many teams must apply +- Any time a team keeps adding fonts, sizes, or colors + +**His core lesson**: +*Discipline and structure matter more than the typeface.* + +**The Vignelli check**: +1. Can you name every typeface in use? Are there more than two? +2. How many type sizes are on this screen? Can one go? +3. Is there a grid, and does every element sit on it? +4. Does the accent color have exactly one meaning? +5. Are you replacing something that has earned recognition, or refining it? diff --git a/plugins/design-mastery/skills/design-masters/references/paul-rand.md b/plugins/design-mastery/skills/design-masters/references/paul-rand.md new file mode 100644 index 0000000..5db9fdf --- /dev/null +++ b/plugins/design-mastery/skills/design-masters/references/paul-rand.md @@ -0,0 +1,124 @@ +# Paul Rand (1914-1996) + +> "A logo derives its meaning from the quality of the thing it symbolizes, not the other way around." (Logos, Flags, and Escutcheons, 1991) + +## Who he was + +Paul Rand was born Peretz Rosenbaum in Brooklyn, New York, and studied at Pratt Institute, Parsons, and the Art Students League. In his twenties he was art director for the fashion pages of Esquire and designed covers for the arts magazine Direction, where he brought European modernism (collage, abstraction, play with photography and type) into American commercial design. + +He later worked in advertising and then focused on corporate identity, becoming the designer American corporations turned to when they wanted a modern image. He taught graphic design at Yale for many years and wrote several books, starting with Thoughts on Design (1947), followed by Paul Rand: A Designer's Art (1985), Design, Form, and Chaos, and From Lascaux to Brooklyn (1996). + +**The problem he solved**: large companies needed marks that worked across products, trucks, stationery, and screens, reproduced cheaply and at tiny sizes, while still feeling intelligent. Rand combined modernist reduction with wit, so marks were simple without being dull. + +## Key works + +| Work | Year | What it demonstrates | +|------|------|----------------------| +| Direction magazine covers | Late 1930s-1940s | European modernism translated for American print | +| Thoughts on Design (book) | 1947 | An early statement of modern graphic design principles in the US | +| IBM logo | 1956 | A solid slab-serif wordmark that gave the company's name a heavier, more unified form | +| Westinghouse logo | 1960 | A W built from circles and lines that suggests a circuit diagram | +| UPS logo | 1961 | A shield topped with a tied parcel: a visual pun that explains the business | +| ABC logo | 1962 | Lowercase geometric letters in a circle; reduced to circles and lines | +| IBM striped logo | 1972 | The 1956 letters cut by horizontal stripes, suggesting speed and unifying the letters | +| NeXT logo | 1986 | A tilted cube with the name split across two lines; presented to Steve Jobs as a single proposal in a bound booklet explaining the reasoning | + +## Principles to borrow + +### What a logo is (from Logos, Flags, and Escutcheons) + +- "A logo is a flag, a signature, an escutcheon." It identifies; it is not an advertisement. +- "A logo doesn't sell (directly), it identifies." +- "A logo is rarely a description of a business." It does not need to show what the company makes. +- "A logo is less important than the product it signifies; what it means is more important than what it looks like." +- A logo must be attractive and reproducible in one color and at very small sizes. + +The practical meaning: a mark gains its meaning over time from the organization behind it. Judge a proposal on distinctiveness, reproducibility, and fit, not on whether it tells the whole story. + +### Simplicity as a by-product + +> "Simplicity is not the goal. It is the by-product of a good idea and modest expectations." + +Reduction follows from finding the idea. Stripping a weak idea down only produces an empty mark. + +### Wit and play + +The UPS parcel, the Westinghouse circuit, and the stripes that turn IBM's letters into a pattern show that a serious company can have a mark with a smile in it. Humor makes marks memorable. + +### Present one solution, with reasons + +The NeXT booklet walked the client through the thinking step by step and offered one answer. Rand's view was that the designer's job is to solve the problem, not to offer a menu. + +## Applying Rand in UI work + +### App icons and favicons + +Rand's reproduction test maps directly onto product icons: +- Works in one color (monochrome icons, notification badges, system tray). +- Works at 16px (favicon) and 1024px (app store). +- Recognizable from silhouette alone. + +```html +<!-- Provide a real small-size variant instead of shrinking the detailed mark --> +<link rel="icon" href="/favicon-simple.svg" type="image/svg+xml" /> +<link rel="apple-touch-icon" href="/icon-180.png" /> +``` + +Design a simplified mark for small sizes rather than relying on the browser to scale a detailed logo. + +### Wordmarks in interfaces + +- Test the wordmark at the actual header height (often 20px to 32px tall). +- Check it on light and dark backgrounds, and as a single flat color. +- Keep clear space around it; the header should not crowd the mark. + +### Wit in product details + +Small visual puns and playful moments (an empty-state illustration, a loading animation) can carry the brand, as long as they never obscure function or slow the user down. + +### Evaluating a logo proposal + +| Question | Pass | Fail | +|----------|------|------| +| Does it identify? | Distinct from competitors at a glance | Could belong to any company in the category | +| One color? | Holds up as a single flat fill | Relies on gradients or photographic detail | +| Small size? | Readable as a 16px favicon and in a 24px header | Detail turns to noise below 48px | +| Idea? | A structure or pun you can state in one sentence | "It represents innovation, trust, and growth" | +| Longevity? | Built from lasting forms (letters, simple geometry) | Tied to a current effect or trend | +| Description trap? | Leaves room for meaning to accrue | Tries to picture every product line | + +### Worked example: a note-taking app + +- Weak brief: "show notes, sync, AI, and security in the icon." +- Rand approach: identify, do not describe. Pick one idea (a folded corner that doubles as the app's initial letter), draw it in one color, and test it in the dock, the menu bar, and the favicon before refining. +- Result: a mark that can live for years while the feature list keeps changing. + +### Presenting design work + +When you propose a direction to a team or client, borrow the NeXT approach: state the problem, show the reasoning, show the solution in real context (app header, icon grid, mobile), and explain what each alternative would lose. + +## Common misreadings + +| Misreading | Correction | +|------------|------------| +| "A logo must explain what the company does" | Rand argued the opposite: a logo identifies, and meaning accrues from the organization | +| "Simple means minimal effort" | Simplicity is the result of a strong idea; the thinking is the work | +| "Rand's marks were instantly loved" | Identity marks earn recognition through consistent use over time | +| "Wit is decoration" | In his work the joke is structural (the parcel on the shield), not an added ornament | + +## Quick reference + +**When to reference Rand**: +- Logos, wordmarks, app icons, favicons +- Identity decisions under pressure to "say everything" in a mark +- Presenting and defending a design direction + +**His core lesson**: +*Find the idea first; simplicity and memorability follow from it.* + +**The Rand check**: +1. Does the mark identify, rather than trying to describe everything? +2. Does it work in one color? +3. Is it recognizable at 16px? +4. Is there an idea (a pun, a structure, a tension), or only a shape? +5. Can you explain the reasoning in one page, as Rand did for NeXT? diff --git a/plugins/design-mastery/skills/design-masters/references/paula-scher.md b/plugins/design-mastery/skills/design-masters/references/paula-scher.md new file mode 100644 index 0000000..89228a4 --- /dev/null +++ b/plugins/design-mastery/skills/design-masters/references/paula-scher.md @@ -0,0 +1,142 @@ +# Paula Scher (1948-) + +## Who she is + +Paula Scher was born in Washington, D.C., and studied at the Tyler School of Art (BFA 1970). She began in the record industry, designing album covers at CBS Records in the 1970s, where she drew on historical typography such as Art Deco and Russian Constructivist lettering. In 1984 she co-founded the studio Koppel & Scher with Terry Koppel, and in 1991 she became a partner in the New York office of Pentagram, the partner-owned design consultancy. + +At Pentagram she built identities for cultural institutions, corporations, and public spaces, and extended graphic design into architecture through large-scale environmental typography. She also paints large typographic maps, shown in galleries. She received the AIGA Medal in 2001 and has taught at the School of Visual Arts in New York. + +**The problem she solved**: institutions that needed to feel alive and loud in a crowded city (a theater, a museum, an opera house) could not rely on a quiet logo alone. Scher made typography itself the image, so the identity could stretch across posters, buildings, and screens while staying recognizable. + +## Key works + +| Work | Year | What it demonstrates | +|------|------|----------------------| +| Swatch poster (Koppel & Scher) | Mid-1980s | A deliberate parody of a 1934 Herbert Matter Swiss tourism poster; quoting design history openly | +| The Public Theater identity | 1994 | Mixed weights of wood-type-inspired sans serif, set at street scale; type as urban noise | +| Bring in 'da Noise, Bring in 'da Funk posters (The Public Theater) | 1995 | Stacked, dense type that behaves like sound | +| Citi logo (Pentagram) | 1999 (sketched after the 1998 Citicorp and Travelers merger) | A lowercase wordmark with a red arc taken from the Travelers umbrella; merging two brands in one gesture | +| Museum of Modern Art graphic system | 2000s | Extending an institution's established typographic identity across signage, print, and screens | +| Metropolitan Opera identity | 2006 | A traditional institution given a contemporary typographic voice | +| The High Line identity | 2000s | Park signage and identity for a rail line turned into a public walkway | +| Windows 8 logo | 2012 | The Windows mark redrawn as a window in perspective instead of a waving flag (the logo only; the Metro design language was Microsoft's own) | + +Her often-cited reaction to the old flag mark was a question: your name is Windows, so why are you a flag? That framing is a useful habit: check whether the mark matches the name. + +## Principles to borrow + +### Type as image + +In Scher's work letters are not only carriers of words; the typography is the picture. Scale, weight, stacking, and color do the work that an illustration or photograph would do elsewhere. + +### Scale as identity + +Her environmental work puts type on building facades, floors, and walls. Recognition comes from a consistent typographic behavior (a family, a way of stacking, a color logic) rather than from one fixed lockup. + +### A flexible system, not a single lockup + +The Public Theater identity is a voice: posters differ, but mixed weights, tight stacking, and a limited palette make each one recognizable. Modern identity systems work the same way. + +### Quote history knowingly + +From wood type to Russian Constructivism to Herbert Matter, Scher borrows openly and transforms. The borrowed source is visible, and the new context changes its meaning. + +### Intuition backed by experience + +Scher has described the Citi mark as a quick first sketch that drew on a whole career of practice. The lesson is not "draw fast"; it is that fluency comes from volume and study. + +## Applying Scher in UI work + +### Where it fits + +Expressive typography belongs in moments where attention is the goal: +- Marketing hero sections, campaign pages, event and festival sites +- Editorial features and long-form story openers +- Brand moments: onboarding splash, empty states with personality, 404 pages + +It does not belong in dense operational UI (tables, forms, settings), where predictability is the goal. + +### Type-led hero + +```html +<section class="bg-neutral-950 px-6 py-20 text-white"> + <h1 class="font-black uppercase leading-[0.85] tracking-tight"> + <span class="block text-7xl md:text-9xl">Free</span> + <span class="block text-5xl text-amber-400 md:text-7xl">Shakespeare</span> + <span class="block text-7xl md:text-9xl">in the Park</span> + </h1> +</section> +``` + +- Vary size and color across lines, keep one family. +- Tight leading only works at display sizes; body text stays at normal line height. +- Keep the real text in the HTML (not an image) so it stays accessible and searchable. + +### A typographic identity as tokens + +```css +:root { + --brand-font: "Anton", "Helvetica Neue", Arial, sans-serif; /* one expressive family */ + --brand-weights: 400 700 900; + --brand-accent: #f5b400; + --display-leading: 0.85; +} +``` + +Define the typographic behavior (family, weights, leading, stacking rules) as the identity, so every page can produce a new composition that still reads as the same brand. + +### Responsive display type + +Large type must survive a phone screen. Fluid sizing keeps the composition's proportions without overflow: + +```css +.display-xl { + font-size: clamp(3rem, 12vw, 9rem); + line-height: 0.85; + overflow-wrap: anywhere; /* long words must not push the page sideways */ +} +``` + +Test the longest real headline at 320px wide before approving the layout. + +### Process for a type-led page + +1. Write the real words first; expressive type cannot be designed around lorem ipsum. +2. Pick one family with a wide weight range. +3. Decide the one word or phrase that must land first and give it the largest size. +4. Stack and scale the rest around it; use color for a single secondary emphasis. +5. Remove any image that only repeats what the type already says. +6. Check contrast, reading order for screen readers, and mobile wrapping. + +### Accessibility checks + +- Contrast still applies at display size (WCAG 2.x: 3:1 for large text, 4.5:1 for normal text). +- Do not rotate or overlap the only copy of essential information. +- Respect `prefers-reduced-motion` if kinetic type is animated. + +## Common misreadings + +| Misreading | Correction | +|------------|------------| +| "Scher breaks all the rules" | Her work is highly systematic; the system is typographic behavior rather than a fixed grid | +| "Loud equals good" | Loudness serves institutions that compete for attention in public space; a banking app settings page is a different problem | +| "She designed Metro for Windows 8" | She designed the Windows 8 logo; Metro was Microsoft's interface language | +| "The Citi logo was effortless" | The sketch was quick; the judgment behind it came from a career of practice, and the full identity program was a much larger job | + +## Quick reference + +**When to reference Scher**: +- Identity systems for cultural, public, or event-driven brands +- Campaign and editorial pages where type carries the visual weight +- Environmental graphics and signage +- Any brand that needs one flexible voice across many formats + +**Her core lesson**: +*Letters can be the image. Build identity from typographic behavior, not only from a mark.* + +**The Scher check**: +1. Could this composition work with type alone, without stock imagery? +2. Is there one family and a clear set of weights, or a pile of fonts? +3. Does the mark or wordmark match what the name means? +4. Is expressive type limited to places where attention is the goal? +5. Does the display text still meet contrast and remain real text? diff --git a/plugins/design-mastery/skills/design-masters/references/saul-bass.md b/plugins/design-mastery/skills/design-masters/references/saul-bass.md index d6eda1e..dceb4cb 100644 --- a/plugins/design-mastery/skills/design-masters/references/saul-bass.md +++ b/plugins/design-mastery/skills/design-masters/references/saul-bass.md @@ -16,10 +16,11 @@ Saul Bass transformed graphic design from decoration into communication. Before | Vertigo | 1958 | Spirals representing psychological descent | | Anatomy of a Murder | 1959 | Fragmented body as crime abstraction | | Psycho | 1960 | Fractured lines as shattered psyche | -| The Shining | 1980 | Aerial isolation, yellow VW Beetle | | Goodfellas | 1990 | Red text bleeding into black | | Casino | 1995 | Fire consuming identity | +Bass also designed posters for films whose titles he did not make, among them The Shining (1980); its aerial opening footage is Kubrick's. + ### Corporate Identities | Company | Year | Design Principle | @@ -27,9 +28,9 @@ Saul Bass transformed graphic design from decoration into communication. Before | AT&T | 1984 | Globe lines = global connection | | United Airlines | 1974 | 'U' as protective wings | | Minolta | 1981 | Horizon in letterform | -| Kleenex | 1981 | Tissue rising from box | +| Kleenex | 1961 | Tissue rising from box | | Girl Scouts | 1978 | Profiles creating profiles | -| Continental Airlines | 1968 | Jet trail as globe | +| Continental Airlines | 1967 | Jet trail as globe | ## Design Philosophy diff --git a/plugins/design-mastery/skills/design-movements/SKILL.md b/plugins/design-mastery/skills/design-movements/SKILL.md index cd5db04..34345ab 100644 --- a/plugins/design-mastery/skills/design-movements/SKILL.md +++ b/plugins/design-mastery/skills/design-movements/SKILL.md @@ -1,6 +1,6 @@ --- name: design-movements -description: Historical design movements and their enduring influence. Understand Bauhaus, Swiss International Style, Art Deco, Memphis, and more. Use when choosing an aesthetic direction, understanding cultural context, or predicting trend cycles. +description: "Design movements from Arts and Crafts through Bauhaus, Swiss Style, Memphis, and grunge to flat design and current styles, with context, visual markers, and UI tokens for each. Use when choosing an aesthetic direction, explaining why a style reads the way it does, or applying a period style without misusing it." --- # Design Movements @@ -161,7 +161,7 @@ shadows: sharp, dramatic #### Key Figures - Walter Gropius (architecture) - László Moholy-Nagy (photography) -- Josef Albers (color theory) +- Josef Albers (preliminary course; his color teaching came later, at Black Mountain and Yale) - Herbert Bayer (typography) #### Modern Application @@ -181,7 +181,7 @@ typography: geometric sans (Futura, Avant Garde) borders: minimal, functional ``` -**Legacy**: Google Material Design, IKEA, modern corporate identity +**Legacy**: Modern design education (the preliminary course), the New Bauhaus in Chicago, Black Mountain College, HfG Ulm, and the functional modernism behind corporate identity --- @@ -295,7 +295,7 @@ When a brand needs to feel: --- -### Memphis Group (1981-1987) +### Memphis Group (1980-1987) **Origin**: Milan, Italy **Reaction To**: Good taste and minimalist seriousness **Core Belief**: Anti-design; pleasure over function @@ -336,7 +336,7 @@ shadows: offset, colored --- ### Grunge/Deconstructivism (1990s) -**Origin**: Pacific Northwest → Global +**Origin**: Southern California editorial design (Beach Culture, Ray Gun), Seattle music graphics (Art Chantry, Sub Pop), London (Neville Brody, The Face), with the theory from Cranbrook and Emigre → Global **Reaction To**: Clean corporate design; digital tools enabling mess **Core Belief**: Destroy legibility; design as art @@ -367,7 +367,7 @@ When a brand needs to feel: ### Flat Design (2010s) **Origin**: Microsoft Metro → Apple iOS 7 → Web -**Reaction To**: Skeuomorphic excess; need for responsive design +**Reaction To**: Skeuomorphic excess (it arrived alongside responsive design and high-density screens) **Core Belief**: Digital should look digital #### Visual Markers @@ -409,7 +409,7 @@ We're in a post-ideological moment. No single style dominates. Success comes fro ## Cyclical Pattern -Styles tend to return on ~30-year cycles: +A common observation rather than a law: styles often return about a generation later. The pairs below are loose illustrations, not a measured cycle: | Original Era | Revival Era | |--------------|-------------| @@ -419,14 +419,22 @@ Styles tend to return on ~30-year cycles: | 1990s grunge | 2020s brutalism | | Y2K aesthetic | 2025-2030s (predicted) | -**Prediction**: Expect a 1990s deconstructivist/grunge revival in the late 2020s. +**Speculation**: a 1990s deconstructivist/grunge revival would fit the pattern; treat it as a hypothesis, not a forecast. --- ## Resources +Read the matching file when a task needs a movement in depth: origins and context, key figures and works with dates, visual markers, UI tokens with Tailwind or CSS snippets, accessibility cautions, and common misreadings. + +- **references/arts-and-crafts.md**: Morris, the moral case for craft, and artisanal UI +- **references/art-nouveau.md**: Whiplash curves, Mucha, Guimard, and ornament used with restraint - **references/bauhaus.md**: Complete Bauhaus history and application - **references/swiss-international.md**: Grid systems and Swiss principles +- **references/psychedelic.md**: 1960s poster art, vibrating color, and where it breaks accessibility +- **references/postmodernism.md**: Venturi, Weingart, Greiman, and layered complexity - **references/memphis-group.md**: Memphis patterns and colors +- **references/grunge-deconstructivism.md**: Carson, Brody, Emigre, Cranbrook, and expressive layers over readable text +- **references/flat-design.md**: Skeuomorphism, Metro, flat, Material, neumorphism, glassmorphism, and current styles - **references/art-deco.md**: Deco geometry and application - **references/minimalism.md**: Less-is-more philosophy diff --git a/plugins/design-mastery/skills/design-movements/references/art-deco.md b/plugins/design-mastery/skills/design-movements/references/art-deco.md new file mode 100644 index 0000000..8e4e6f3 --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/art-deco.md @@ -0,0 +1,103 @@ +# Art Deco (c. 1910s-1940) + +## Origins and context + +**Where**: Paris first, then worldwide, with major centers in New York, Miami, Shanghai, Mumbai, and Napier (New Zealand). +**Reacting against**: The organic curves of Art Nouveau, and in its American form, the gloom after the First World War. +**Core belief**: Modern life (speed, electricity, skyscrapers, luxury travel) deserves its own glamorous ornament, built from geometry. + +The style first appeared in Paris shortly before the First World War and flourished in the 1920s and early 1930s. Its showcase was the 1925 **Exposition internationale des arts décoratifs et industriels modernes** in Paris. The label "Art Deco" is a later coinage: it appeared in print around the 1966 Paris exhibition on the period at the Musée des Arts Décoratifs and was popularized by Bevis Hillier's 1968 book *Art Deco of the 20s and 30s*. People at the time called it "moderne" or simply modern. + +**Influences it absorbed**: Cubism, the Ballets Russes, Egyptian motifs after the discovery of Tutankhamun's tomb in 1922, Mesoamerican stepped architecture, and machine forms. + +**Later variant**: Streamline Moderne in the 1930s, with horizontal speed lines, rounded corners, and aerodynamic forms, applied even to objects that never move. + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| A. M. Cassandre | *Étoile du Nord* and *Nord Express* posters | 1927 | Converging lines, airbrushed gradients, travel as geometry | +| A. M. Cassandre | *Normandie* ocean-liner poster | 1935 | Monumental scale from a low viewpoint | +| A. M. Cassandre | Bifur (1929) and Peignot (1937) typefaces, Deberny & Peignot | 1929, 1937 | Display type reduced to geometric parts | +| William Van Alen | Chrysler Building, New York | 1930 | Stepped crown, sunburst arches, steel as jewelry | +| Émile-Jacques Ruhlmann | Furniture | 1920s | Luxury woods, ivory inlay, slim tapered legs | +| René Lalique | Glass | 1920s-30s | Frosted and molded glass, repeated motifs | +| Tamara de Lempicka | Portraits | 1920s-30s | Polished, faceted, metallic figures | +| Morris Fuller Benton (ATF) | Broadway typeface | 1927 | High-contrast display type associated with the Jazz Age | + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Sunbursts, fans, chevrons, zigzags | Radiating energy expressed through repetition | +| Stepped (ziggurat) silhouettes | Skyscraper setbacks and ancient temples as modern emblem | +| Strict symmetry | Formal, ceremonial balance | +| Black, gold, silver, cream, jade, lacquer red | Luxury materials translated into color | +| Geometric sans and high-contrast display type | Letters as architecture | +| Thin parallel lines (speed lines in Streamline) | Motion and modernity | + +## Applying it in UI work + +**Fits**: hospitality, cocktail bars, events and galas, premium finance or watches, jewelry, film and theatre, anything selling celebration. +**Avoid**: products that must feel humble, casual, or purely utilitarian. + +### Tokens + +```css +:root { + --deco-black: #0e0e10; + --deco-cream: #f1e6cf; + --deco-gold: #c9a24a; + --deco-jade: #1f5c4d; + --deco-lacquer: #8e1c1c; +} + +/* Sunburst background from a single conic gradient */ +.deco-sunburst { + background: repeating-conic-gradient(from 0deg at 50% 100%, + #c9a24a 0deg 4deg, #0e0e10 4deg 12deg); +} +``` + +```html +<!-- Tailwind: symmetric framed heading with gold rules --> +<header class="bg-[#0e0e10] text-[#f1e6cf] text-center py-16"> + <div class="mx-auto w-24 border-t-2 border-[#c9a24a]"></div> + <h1 class="mt-6 text-5xl uppercase tracking-[0.25em] font-light">The Grand Hall</h1> + <div class="mx-auto mt-6 w-24 border-t-2 border-[#c9a24a]"></div> +</header> +``` + +- **Type**: a geometric or high-contrast display face in uppercase with wide tracking; a quiet sans or serif for text. +- **Layout**: centered, symmetric compositions; framed panels; stepped corners with `clip-path`. +- **Ornament**: thin gold rules, fan and chevron SVGs, used sparingly as frames. +- **Motion**: crisp, short reveals; nothing bouncy. + +### Accessibility notes + +- Gold on cream fails contrast for text. Gold works as a rule or on black; check `#c9a24a` on `#0e0e10` for your text size. +- Wide-tracked uppercase slows reading. Keep it to short headings. +- Sunburst backgrounds behind text are busy. Put text on a solid panel. + +## Common misreadings + +- **"The 1920s called it Art Deco."** The term came decades later; contemporaries said "moderne". +- **"Art Deco and Bauhaus are the same modernism."** They overlap in time and geometry, but Deco embraced luxury ornament while the Bauhaus aimed at standardized, affordable production. +- **"Streamline Moderne is a different movement."** It is usually treated as the late, largely American phase of Art Deco. + +## Legacy + +- Hotel, cinema, and cocktail branding; film production design for period pieces. +- Recurring revivals whenever a brand wants glamour with discipline. + +--- + +## Quick reference + +**Reach for it when**: the product sells occasion, luxury, or nostalgia for glamour. +**Avoid it when**: the tone must be casual, humble, or purely functional. + +**Recipe**: +1. Black ground, cream text, gold only for rules and ornament. +2. Centered symmetric layout, uppercase tracked display type. +3. One radiating motif (fan, sunburst, chevron) used as a frame, not wallpaper. diff --git a/plugins/design-mastery/skills/design-movements/references/art-nouveau.md b/plugins/design-mastery/skills/design-movements/references/art-nouveau.md new file mode 100644 index 0000000..f3672f0 --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/art-nouveau.md @@ -0,0 +1,105 @@ +# Art Nouveau (c. 1890-1914) + +## Origins and context + +**Where**: Brussels and Paris first, then across Europe and the United States, under different local names. +**Reacting against**: Academic historicism, the habit of dressing new buildings and objects in borrowed Gothic, Renaissance, or Classical styles. +**Core belief**: A new ornament drawn from nature, applied to everything from buildings to cutlery to posters, with no line between fine art and applied art. + +The name comes from Siegfried Bing's Paris gallery, the Maison de l'Art Nouveau, opened in 1895. The style peaked at the Paris Exposition Universelle of 1900 and was largely exhausted by the start of the First World War. + +### One style, many names + +| Region | Name | Source of the name | +|--------|------|--------------------| +| France, Belgium, Britain | Art Nouveau | Bing's gallery (1895) | +| Germany, Scandinavia | Jugendstil | *Jugend* magazine, Munich (1896) | +| Austria | Secessionsstil | Vienna Secession (1897) | +| Italy | Stile Liberty | Liberty & Co., the London shop | +| Catalonia | Modernisme | Local movement around Barcelona | +| Belgium (nickname) | Style coup de fouet | "Whiplash style" | + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| Victor Horta | Hôtel Tassel, Brussels | 1892-93 | Exposed iron structure bent into plant forms; the style's first major building | +| Hermann Obrist | Cyclamen embroidery ("Whiplash") | 1895 | The single curling line that gave the style its nickname | +| Alphonse Mucha | *Gismonda* poster for Sarah Bernhardt | 1895 | Tall format, halo motif, integrated lettering and figure | +| Aubrey Beardsley | Illustrations for Wilde's *Salome* (English edition) | 1894 | Flat black and white, extreme contrast, sinuous line | +| Hector Guimard | Paris Métro entrances | c. 1900 | Cast iron as organic growth; mass-produced modular ornament | +| Charles Rennie Mackintosh | Glasgow School of Art | 1897-1909 | The rectilinear Glasgow branch: tall, gridded, restrained | +| Louis Comfort Tiffany, Émile Gallé | Leaded-glass lamps; Nancy school glass | 1890s-1900s | Nature motifs in luxury decorative arts | +| Antoni Gaudí | Casa Batlló, Barcelona | 1904-06 | Modernisme at its most sculptural | + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Whiplash curves, stems, tendrils | Line as the carrier of energy; structure and ornament fused | +| Stylized plants, insects, female figures with flowing hair | Nature as the vocabulary of a new, non-historical ornament | +| Lettering drawn to fit the image | Type and image as one composition | +| Decorative frames and arches around content | The page or facade as a unified object | +| Muted, harmonious palettes (sage, ochre, dusty rose, gold) in print | Lithographic color used for mood, not contrast | + +Two branches coexisted. The curvilinear Franco-Belgian branch (Horta, Guimard, Mucha) and the rectilinear branch of Glasgow and Vienna (Mackintosh, Josef Hoffmann, Koloman Moser). The second one points toward modernism; the first points toward Psychedelic revival. + +## Applying it in UI work + +**Fits**: perfume, cosmetics, tea and wine, boutique hotels, theatre and arts programming, botanical brands. +**Avoid**: data-heavy tools, anything that needs dense information. + +### Tokens + +```css +:root { + --nouveau-cream: #f3ead7; + --nouveau-sage: #7d8f69; + --nouveau-ochre: #b58b3c; + --nouveau-rose: #b7746b; + --nouveau-ink: #2f2a24; + --nouveau-gold: #a8864a; +} +``` + +```html +<!-- Tailwind: arched hero frame in the Mucha manner --> +<section class="mx-auto max-w-md bg-[#f3ead7] text-[#2f2a24] rounded-t-full border-2 border-[#a8864a] px-10 pt-24 pb-12 text-center"> + <p class="uppercase tracking-[0.3em] text-sm text-[#7d8f69]">Spring collection</p> + <h1 class="font-serif text-5xl mt-4">Jardin</h1> +</section> +``` + +- **Shape**: arches (`rounded-t-full`), ogee frames, organic SVG dividers between sections. +- **Type**: a display face with Nouveau flavor for headings only (Arnold Böcklin and Eckmann are period faces; many revivals exist). Pair with a calm serif or humanist sans for text. +- **Illustration**: flat, outlined botanical line art; SVG works well because the style is line-driven. +- **Motion**: slow, eased path drawing (`stroke-dashoffset`) for vines and borders. + +### Accessibility notes + +- Period display faces are hard to read below heading sizes. Never use them for body copy, form labels, or buttons. +- The muted palette has low internal contrast. Check sage and ochre text against cream; they usually fail 4.5:1. +- Honor `prefers-reduced-motion` for any line-drawing animation. + +## Common misreadings + +- **"Art Nouveau is just curly ornament."** The movement was an architectural and structural program; Horta's iron was load-bearing. +- **"Mackintosh is Art Deco."** Mackintosh's rectilinear work predates Art Deco and belongs to the Glasgow Style of Art Nouveau, though it anticipates later geometry. +- **"Art Deco grew straight out of Art Nouveau."** Deco reacted against Nouveau's organic curves and borrowed from Cubism, the Ballets Russes, and machine forms. + +## Legacy + +- The 1960s psychedelic poster artists drew openly on Vienna Secession lettering (Wes Wilson on Alfred Roller) and on Mucha-style figures. +- Integrated lettering and image remains a standard move in packaging and posters. + +--- + +## Quick reference + +**Reach for it when**: the brand is about nature, luxury craft, or romance. +**Avoid it when**: the interface must be dense, fast, or neutral. + +**Recipe**: +1. Cream ground, one muted natural hue, thin gold rules. +2. Arched or ogee frames and SVG vine dividers. +3. Nouveau display face for headings only, calm text face everywhere else. diff --git a/plugins/design-mastery/skills/design-movements/references/arts-and-crafts.md b/plugins/design-mastery/skills/design-movements/references/arts-and-crafts.md new file mode 100644 index 0000000..ae7b03a --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/arts-and-crafts.md @@ -0,0 +1,108 @@ +# Arts and Crafts (c. 1860-1920) + +> "Have nothing in your houses that you do not know to be useful, or believe to be beautiful." (William Morris, "The Beauty of Life", lecture, 1880) + +## Origins and context + +**Where**: Britain first, then the United States, Scandinavia, and Central Europe. +**Reacting against**: Industrial mass production of the Victorian era, which Morris and his circle saw as producing shoddy goods and degrading the people who made them. +**Intellectual roots**: John Ruskin, especially the chapter "The Nature of Gothic" in *The Stones of Venice* (volume 2, 1853), which argued that the visible freedom of the medieval craftsman was a moral good. + +The name came later than the practice. T. J. Cobden-Sanderson first used "Arts and Crafts" in 1887, at a meeting of what became the Arts and Crafts Exhibition Society. The Society's first exhibition opened in London in November 1888. + +### Key institutions + +| Institution | Founded | Role | +|-------------|---------|------| +| Morris, Marshall, Faulkner & Co. (later Morris & Co.) | 1861 | Decorative arts firm: wallpaper, textiles, stained glass, furniture | +| Arts and Crafts Exhibition Society | 1887 | Gave the movement its name and a public platform | +| Guild and School of Handicraft (C. R. Ashbee) | 1888 | Craft community in London, later in Chipping Campden | +| Kelmscott Press (William Morris) | 1891 | Private press that revived the book as a unified object | +| Roycroft (Elbert Hubbard) | 1895 | American craft community in East Aurora, New York | +| *The Craftsman* (Gustav Stickley) | 1901 | American magazine that spread the style to middle-class homes | + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| Philip Webb (for Morris) | Red House, Bexleyheath | 1859-60 | A house designed as one unified environment, inside and out | +| William Morris | Trellis wallpaper | designed 1862 | Pattern drawn from a real garden, not from historical ornament books | +| William Morris | Strawberry Thief textile | 1883 | Indigo-discharge printing, dense symmetrical repeat, birds and fruit | +| William Morris | *The Works of Geoffrey Chaucer* (Kelmscott Chaucer) | 1896 | Type, borders, and illustration (Edward Burne-Jones) designed as one page system | +| C. F. A. Voysey | Wallpapers and houses | 1890s | Lighter, flatter pattern; a bridge toward Art Nouveau | +| Gustav Stickley | Craftsman furniture | 1900s | Visible joinery, quarter-sawn oak, honest construction | + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Dense botanical repeats | Nature as the source of ornament, observed rather than copied from pattern books | +| Visible joinery, hand-tooled surfaces | Truth to materials: show how a thing is made | +| Blackletter and Venetian-revival type (Morris's Golden Type, 1890) | The book as a crafted object | +| Earthy vegetable-dye palette (indigo, madder red, weld yellow) | Materials dictate color | +| Page borders and initials integrated with text | Unity of the whole design | + +**The central paradox**: handmade goods were expensive, so Morris's work, meant as a democratic art, ended up in wealthy homes. Keep that in mind when you borrow the aesthetic for "artisanal" products: the style signals care and cost. + +## Applying it in UI work + +**Fits**: craft marketplaces, food and farm brands, bookshops and publishers, sustainability products, editorial long reads. +**Avoid**: dense dashboards and tools where ornament competes with data. + +### Tokens + +```css +/* Arts and Crafts inspired tokens */ +:root { + --paper: #f4ecd8; /* unbleached paper */ + --ink: #2b2118; /* warm near-black */ + --indigo: #2e3f63; /* woad / indigo */ + --madder: #9b3b2c; /* madder red */ + --weld: #b8912f; /* weld yellow, use for accents only */ + --leaf: #4f5d3a; /* olive leaf */ +} +``` + +```html +<!-- Tailwind: bordered editorial card with a decorated initial --> +<article class="bg-[#f4ecd8] text-[#2b2118] border-4 border-double border-[#4f5d3a] p-8 font-serif leading-relaxed"> + <h2 class="text-3xl tracking-wide mb-4">The Workshop</h2> + <p class="first-letter:text-5xl first-letter:float-left first-letter:mr-2 first-letter:text-[#9b3b2c]"> + Every piece is cut, joined and finished by hand... + </p> +</article> +``` + +- **Type**: a sturdy old-style or Venetian serif for text (for example EB Garamond, Cormorant, or a Jenson revival); keep blackletter for display only. +- **Pattern**: use repeating botanical patterns as backgrounds for bands and borders, never behind body text. +- **Shape**: rectangular frames, double rules, decorated initials. +- **Motion**: almost none. Slow fades at most. + +### Accessibility notes + +- Weld yellow and leaf green on paper fail 4.5:1 for body text. Keep them for rules and ornaments, and test every text pair. +- Patterned backgrounds behind text reduce legibility. Put text on a flat panel. + +## Common misreadings + +- **"Arts and Crafts rejected machines outright."** Morris's position was more nuanced than that, and later figures (Ashbee, and the German Werkbund that grew partly from these ideas) accepted machine production when it served good design. +- **"It is the same as Art Nouveau."** Art Nouveau grew partly out of Arts and Crafts ideas, but its whiplash curves and luxury materials were a distinct, largely continental style. +- **"Rustic means Arts and Crafts."** The movement was highly disciplined: strict repeats, controlled palettes, careful proportions. + +## Legacy + +- The idea that design has social and moral consequences. +- The private press movement and the revival of fine book typography. +- Through the Deutscher Werkbund and Gropius's 1919 Bauhaus program, which called for artists to return to the crafts, a line of influence into early modernism. + +--- + +## Quick reference + +**Reach for it when**: the product's value is craft, provenance, or care. +**Avoid it when**: speed, density, or neutrality matters more than warmth. + +**Recipe**: +1. Warm paper background, warm near-black ink, one natural-dye accent. +2. Old-style serif text, decorated initials, double-rule frames. +3. Botanical pattern in borders and section bands only. diff --git a/plugins/design-mastery/skills/design-movements/references/bauhaus.md b/plugins/design-mastery/skills/design-movements/references/bauhaus.md new file mode 100644 index 0000000..c56968e --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/bauhaus.md @@ -0,0 +1,109 @@ +# Bauhaus (1919-1933) + +## Origins and context + +The Bauhaus was a school, not a style label chosen by its members. Walter Gropius founded it on 1 April 1919 in Weimar by merging the Grand-Ducal Saxon Academy of Fine Art with the Grand-Ducal Saxon School of Arts and Crafts. Its founding manifesto called on architects, sculptors, and painters to return to the crafts and build together, with a Lyonel Feininger woodcut of a cathedral on the cover. + +**Reacting against**: The split between fine art and industry, academic art training, and the ornamented historicism of the 19th century. Its early program drew on Arts and Crafts ideals; from about 1923 it turned toward design for industrial production, summed up in the slogan "Art and technology: a new unity" of that year. + +### Three sites, three directors + +| Site | Years | Director | +|------|-------|----------| +| Weimar | 1919-1925 | Walter Gropius (1919-1928) | +| Dessau (school building by Gropius, 1925-26) | 1925-1932 | Gropius, then Hannes Meyer (1928-1930), then Ludwig Mies van der Rohe (1930-1933) | +| Berlin (private school in a former factory) | 1932-1933 | Mies van der Rohe | + +Under pressure from the Nazi regime, the leadership closed the school in 1933. Emigrant teachers carried its methods abroad: László Moholy-Nagy founded the New Bauhaus in Chicago (1937); Josef and Anni Albers taught at Black Mountain College; Max Bill, a former student, co-founded the Ulm School of Design (HfG Ulm, 1953). + +## Key figures and works + +| Person | Role or work | Year | What it shows | +|--------|--------------|------|---------------| +| Johannes Itten | Preliminary course (Vorkurs) | 1919-1923 | Foundation training in color, material, and form | +| László Moholy-Nagy | Took over the Vorkurs; typography and photography | 1923-1928 | Photography and type as the new visual language ("typophoto") | +| Joost Schmidt | Poster for the Bauhaus exhibition | 1923 | Circles, squares, and a strict axis as graphic structure | +| Marianne Brandt | Tea infuser (MT49) | 1924 | Geometric solids as a functional, reproducible object | +| Wilhelm Wagenfeld, Carl Jakob Jucker | Table lamp | 1923-24 | Glass and metal reduced to their functional parts | +| Herbert Bayer | "Universal" alphabet proposal | 1925 | A single-case geometric alphabet for efficient communication | +| Marcel Breuer | Club chair B3 (later called the Wassily) | 1925-26 | Bent tubular steel, inspired by bicycle handlebars | +| Gunta Stölzl | Weaving workshop | 1920s | Textile design for industrial production | +| Wassily Kandinsky | Questionnaire pairing yellow-triangle, red-square, blue-circle | 1923 | The school's search for a universal color-form grammar | +| Paul Klee, Josef Albers | Form and color teaching | 1920s | Systematic visual education, later published by both | + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Primary colors plus black and white | A reduced, universal palette | +| Circle, square, triangle | Elementary forms any workshop or factory can reproduce | +| Sans-serif, often lowercase-only type (Bayer) | Clarity and efficiency over tradition | +| Asymmetric layouts with strong axes and bars | Dynamic balance instead of centered symmetry | +| Photography instead of drawn illustration | Mechanical reproduction as modern truth | +| Exposed structure, standard parts | Design for industry and affordability | + +## Applying it in UI work + +**Fits**: education products, museums and cultural institutions, developer tools, architecture studios, any brand that wants to look rational and inventive. +**Avoid**: products that must feel soft, romantic, or traditional. + +### Tokens + +```css +:root { + --bh-red: #d62828; + --bh-blue: #1d3a8a; + --bh-yellow: #f2c230; + --bh-black: #111111; + --bh-white: #f7f5f0; +} +``` + +```html +<!-- Tailwind: asymmetric hero with a primary shape and a strong bar --> +<section class="relative grid grid-cols-12 gap-6 bg-[#f7f5f0] p-12 min-h-[28rem] overflow-hidden"> + <div class="col-span-7 self-end"> + <div class="h-2 w-40 bg-[#111111] mb-6"></div> + <h1 class="text-6xl font-bold lowercase leading-none tracking-tight">form and function</h1> + <p class="mt-4 max-w-md text-lg">A course in visual grammar, one shape at a time.</p> + </div> + <div class="col-span-5 flex items-start justify-end"> + <div class="h-56 w-56 rounded-full bg-[#d62828]"></div> + </div> +</section> +``` + +- **Type**: geometric or grotesque sans (Futura, released in 1927, is not a Bauhaus typeface but shares its geometry; modern options include Jost, Outfit, or Inter for text). +- **Color**: one primary per screen region carries meaning; do not paint every component in all three. +- **Layout**: asymmetric grid, generous white field, heavy rules and bars as structure. +- **Motion**: linear or simple ease, shapes sliding along the axis. + +### Accessibility notes + +- White text on the yellow fails contrast. Use black on yellow. +- Red and blue as the only difference between states will fail for color-blind users. Pair color with shape or text. + +## Common misreadings + +- **"Form follows function" is the Bauhaus motto.** The phrase comes from the American architect Louis Sullivan ("form ever follows function", 1896). The Bauhaus is associated with the idea, not the coinage. +- **"Bauhaus is a style."** Gropius resisted the idea of a Bauhaus style; the school was a teaching method and a workshop system. +- **"It was all primary colors and circles."** That describes some workshops and posters. The weaving workshop, the metal workshop, and Mies-era architecture look very different. +- **"The Bauhaus invented modern graphic design."** It was one center among several: De Stijl, Russian Constructivism, and Jan Tschichold's *Die neue Typographie* (1928, Tschichold was not a Bauhaus teacher) all shaped the New Typography. + +## Legacy + +- The foundation course model of art and design education, still used worldwide. +- Direct lines through the New Bauhaus (Chicago), Black Mountain College, and HfG Ulm, and through Max Bill into Swiss International Style. +- Claims that later corporate design languages descend directly from the Bauhaus are usually loose analogies; cite specific people and institutions instead. + +--- + +## Quick reference + +**Reach for it when**: you want rational, confident, inventive. +**Avoid it when**: the brand needs warmth, softness, or heritage. + +**Recipe**: +1. Off-white field, black bars, one primary color doing the work. +2. Geometric sans, lowercase headings, asymmetric 12-column layout. +3. Circles, squares, and rules as structure, never as decoration. diff --git a/plugins/design-mastery/skills/design-movements/references/flat-design.md b/plugins/design-mastery/skills/design-movements/references/flat-design.md new file mode 100644 index 0000000..e593c3e --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/flat-design.md @@ -0,0 +1,110 @@ +# Interface styles: skeuomorphism to flat, Material, and after (c. 2000-present) + +This file covers the digital-native lineage the SKILL.md describes as Web 2.0 skeuomorphism, Flat Design, and Contemporary Eclecticism. + +## Origins and context + +| Phase | Where it came from | Reacting against | Core belief | +|-------|--------------------|------------------|-------------| +| Skeuomorphism (2000s to 2013) | Apple's Mac OS X Aqua (2000-01) and iPhone OS (2007 onward), web 2.0 glossy buttons | Gray, abstract desktop chrome | Borrow the look of physical objects so new interfaces feel familiar | +| Metro (2006 onward) | Microsoft: Windows Media Center, the Zune interface (2006), formally introduced with Windows Phone 7 (2010), then Xbox and Windows 8 (2012) | Icon-heavy, chrome-heavy mobile UI | Typography and content first; the team cited Swiss graphic design and transit signage | +| Flat (2013 onward) | Apple's iOS 7 (2013) redesign, following Metro | Skeuomorphic textures (felt, leather, wood) | Digital surfaces should look digital | +| Material Design (2014 onward) | Google, announced at Google I/O on 25 June 2014 (lead: Matías Duarte); Material You (Material Design 3) announced 2021 with Android 12 | Flat design's lack of hierarchy and affordance cues | Flat surfaces arranged in space: paper-like layers, elevation shadows, meaningful motion | +| Contemporary eclecticism (late 2010s onward) | Dribbble, design Twitter, OS vendors | Flat monotony | Many styles available at once, chosen for meaning | + +Microsoft dropped the "Metro" name in 2012 over a trademark dispute and later moved to the Fluent Design System (2017), which reintroduced depth, light, and translucent "acrylic" material. + +## Key works + +| Product or person | Work | Year | What it shows | +|-------------------|------|------|---------------| +| Apple | Mac OS X Aqua interface | 2000-01 | Translucent, glossy, "lickable" controls | +| Apple (iOS under Scott Forstall) | Game Center felt table, Notes legal pad, iBooks wooden shelf | 2007-12 | Skeuomorphism at its peak | +| Microsoft | Zune HD and Windows Phone 7 (Metro) | 2009-10 | Big type, live tiles, content over chrome | +| Apple (Jony Ive) | iOS 7 | 2013 | Flat color, thin type, translucent layers with blur | +| Google (Matías Duarte) | Material Design | 2014 | Elevation and shadow as a hierarchy system | +| Alexander Plyuto | Skeuomorphic banking app concept on Dribbble | 2019 | The viral shot behind "neumorphism" | +| Michał Malewicz | Named "neumorphism" (with Jason Kelly) and "glassmorphism" | 2019-20 | Trend naming by practitioners | +| Apple | macOS Big Sur | 2020 | Translucent materials that popularized "glassmorphism" | +| Apple | Liquid Glass, announced at WWDC | 2025 | Refractive, translucent system material across Apple platforms | + +## Visual markers and the principles behind them + +| Style | Markers | Principle | +|-------|---------|-----------| +| Skeuomorphism | Textures, bevels, gloss, stitching, realistic icons | Familiarity through physical metaphor | +| Flat | Solid color, no shadows or gradients, simple icons, generous space | Honesty to the medium; scales cleanly across screen sizes | +| Material | Flat surfaces, consistent elevation shadows, bold color, motion that explains cause and effect | Depth as information, not decoration | +| Neumorphism | Same-color surfaces with paired light and dark soft shadows, extruded or pressed controls | Soft tactility | +| Glassmorphism | Translucent panels, background blur, thin light borders over vivid backgrounds | Layering and context: you can see what is behind | +| Web brutalism and anti-design | Raw HTML look, system fonts, harsh borders, visible structure | Reaction against polished template sameness | + +## Applying it in UI work + +- **Flat and Material** are the working default for most product UI. Use elevation (shadow) to encode hierarchy consistently, not as decoration. +- **Glassmorphism** fits overlays on rich imagery (media players, maps, wallpapers) where seeing the background matters. +- **Neumorphism** fits a small number of large, low-density controls (a smart-home dial). It fails for dense or text-heavy UI. +- **Skeuomorphic touches** still help where a physical metaphor carries meaning (a knob, a page curl in a reading app), used sparingly. + +### Tokens + +```css +/* Material-style elevation scale: shadow encodes hierarchy */ +:root { + --elev-1: 0 1px 2px rgb(0 0 0 / 0.12), 0 1px 3px rgb(0 0 0 / 0.08); + --elev-2: 0 2px 6px rgb(0 0 0 / 0.14); + --elev-3: 0 8px 24px rgb(0 0 0 / 0.16); +} + +/* Glass panel with a readable fallback */ +.glass { + background: rgb(255 255 255 / 0.72); + -webkit-backdrop-filter: blur(16px); + backdrop-filter: blur(16px); + border: 1px solid rgb(255 255 255 / 0.5); +} +@supports not (backdrop-filter: blur(1px)) { + .glass { background: rgb(255 255 255 / 0.95); } +} +``` + +```html +<!-- Tailwind: glass card with enough opacity to keep text legible --> +<div class="rounded-2xl bg-white/70 backdrop-blur-lg border border-white/50 shadow-lg p-6 text-neutral-900"> + <p class="text-sm font-medium">Now playing</p> +</div> + +<!-- Neumorphic toggle surface: pair it with a visible focus ring and a text label --> +<button class="rounded-2xl bg-[#e6e9ef] p-6 shadow-[8px_8px_16px_#c4c7cc,-8px_-8px_16px_#ffffff] focus-visible:ring-2 focus-visible:ring-blue-600"> + Lights +</button> +``` + +### Accessibility notes + +- **Neumorphism** relies on faint shadows of the same hue as the background, so control boundaries often fall below the 3:1 non-text contrast that WCAG 1.4.11 asks for, and pressed versus unpressed states are hard to tell apart. Add borders, icons, or text state labels. +- **Glassmorphism** puts text over a changing, unknown background. Raise panel opacity until text meets 4.5:1 against the worst case behind it, and provide the `@supports` fallback. Respect `prefers-reduced-transparency` where browsers support it. +- **Flat** design can remove affordances. Buttons and links still need a visible shape, underline, or other cue that they are interactive. + +## Common misreadings + +- **"iOS 7 invented flat design."** Microsoft's Metro came first; iOS 7 made the direction mainstream. +- **"Material Design is flat design."** Material is a reaction to pure flat: it brings back shadow and depth as a structured system. +- **"Flat design was caused by responsive design."** The two developed in the same period and suit each other (flat assets scale easily), but neither caused the other. +- **"Neumorphism and glassmorphism are movements."** They are visual treatments named by practitioners; treat them as effects to use deliberately. + +## Legacy and current state + +The current moment is eclectic: flat and Material structure, translucency returning at the OS level (Fluent acrylic, Big Sur, Liquid Glass), dark modes, variable fonts, and revivals (Y2K, Memphis, brutalism) used as brand layers. The durable skill is choosing a treatment for what it communicates and keeping the functional layer accessible. + +--- + +## Quick reference + +**Reach for flat or Material when**: building product UI that must scale and stay clear. +**Reach for glass when**: the background carries meaning; **neumorphism** only for a few large, labeled controls. + +**Recipe**: +1. Flat surfaces, one consistent elevation scale for hierarchy. +2. Translucency only over rich imagery, with an opaque fallback. +3. Every interactive element keeps a visible boundary, focus ring, and label. diff --git a/plugins/design-mastery/skills/design-movements/references/grunge-deconstructivism.md b/plugins/design-mastery/skills/design-movements/references/grunge-deconstructivism.md new file mode 100644 index 0000000..008b745 --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/grunge-deconstructivism.md @@ -0,0 +1,102 @@ +# Grunge and deconstructivist typography (c. 1984-2000) + +## Origins and context + +This was never one movement with one birthplace. Four strands overlapped: + +| Strand | Where | Who | What it contributed | +|--------|-------|-----|---------------------| +| Music graphics | Seattle | Art Chantry (art director of *The Rocket* in the 1980s; posters and sleeves for Sub Pop and other labels) | Photocopier degradation, collage, punk-derived hand lettering | +| Editorial experiment | Southern California | David Carson (*Beach Culture*, 1989-91; *Ray Gun*, Santa Monica, founded 1992 by Marvin Scott Jarrett, Carson art director for its first three years) | Intuitive layouts, text as texture, deliberate illegibility | +| Style and music magazines | London | Neville Brody (*The Face*, 1981-86; *Arena*, 1987-90; *FUSE* with Jon Wozencroft, 1991) | Constructed display type, magazine as experimental typography | +| Theory and type design | Cranbrook Academy of Art, Michigan; Emigre, Berkeley | Katherine McCoy (co-chair of design at Cranbrook, 1971-1995); Rudy VanderLans and Zuzana Licko (*Emigre*, 1984-2005) | Design read as text, informed by post-structuralist theory; early digital typefaces | + +**Reacting against**: Corporate modernism's clean neutrality, and (for the Cranbrook and Emigre strand) the idea that a design has one correct reading. +**Enabler**: The Apple Macintosh (1984) and early page-layout and font software, which let designers make and distort type themselves. +**Name**: "Deconstruction" was borrowed loosely from Jacques Derrida's philosophy. In architecture, the Museum of Modern Art's 1988 exhibition *Deconstructivist Architecture* (Philip Johnson and Mark Wigley) gave the architectural term currency; graphic designers used both words more loosely. + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| Neville Brody | *The Face* art direction | 1981-86 | Custom geometric display type, pages built as objects | +| Zuzana Licko | Bitmap fonts for *Emigre* (Emperor, Oakland, Emigre) | 1985 | Typefaces born from the low-resolution screen | +| Katherine McCoy | *Cranbrook Design: The New Discourse* (book and exhibition) | 1990 | Layered, theory-driven graphic design | +| Barry Deck | Template Gothic (released by Emigre) | 1990 | A typeface imitating degraded stencil lettering | +| David Carson | *Ray Gun* | 1992-95 | Carson famously set a Bryan Ferry interview entirely in the symbol font Zapf Dingbats | +| David Carson | *The End of Print* (book) | 1995 | His editorial work collected and explained | +| Art Chantry | Posters and sleeves for Seattle bands | 1980s-90s | Photocopy, label-maker, and clip-art aesthetics | + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Overlapping, colliding text blocks | Reading as an active, interpretive act | +| Distressed, photocopied, degraded textures | Authenticity signaled by imperfection | +| Many typefaces, including new digital and "damaged" fonts | The typeface as expressive voice, not neutral carrier | +| Columns that run off the page, rotated or reversed text | The grid treated as something to question | +| Dark, gritty palettes and grainy photography | Anti-corporate mood | + +## Applying it in UI work + +**Fits**: music and fashion editorial, skate and street brands, portfolios of expressive studios, campaign microsites, album and tour pages. +**Avoid**: every functional flow. Grunge treatment on forms, pricing, navigation, or legal text is a usability failure, not a style. + +### Tokens + +```css +:root { + --grunge-ink: #151515; + --grunge-paper: #e9e4d8; + --grunge-rust: #8a3b12; + --grunge-acid: #d4ff3a; + --grunge-grey: #5c5c5c; +} + +/* Photocopy texture for hero images: grayscale + contrast, no blur on text */ +.xerox { filter: grayscale(1) contrast(1.8); mix-blend-mode: multiply; } +``` + +```html +<!-- Tailwind: expressive headline layer over a plain, accessible article --> +<header class="relative overflow-hidden bg-[#151515] text-[#e9e4d8] py-24"> + <span aria-hidden="true" class="absolute -rotate-6 left-4 top-6 text-[9rem] font-black opacity-20">NOISE</span> + <h1 class="relative text-6xl font-black uppercase tracking-tight">Tour diary</h1> +</header> +<article class="mx-auto max-w-prose bg-[#e9e4d8] text-[#151515] p-8 leading-7">...</article> +``` + +- **Type**: one expressive or distressed display face for headlines; a plain, readable face for text. +- **Layout**: rotations, overlaps, and bleeds in the header or poster layer only. +- **Imagery**: grainy, high-contrast, cropped photography; texture as a separate decorative layer. +- **Motion**: glitch or jitter effects only on decorative layers, and never flashing. + +### Accessibility notes + +- Overlapping text and texture behind text break WCAG contrast (4.5:1 for body text) and are hard for people with low vision or dyslexia. Keep information text on a flat, high-contrast surface. +- Decorative text layers need `aria-hidden="true"` so screen readers do not read the noise. +- Glitch animation must not flash more than three times per second (WCAG 2.3.1) and should stop under `prefers-reduced-motion`. + +## Common misreadings + +- **"Grunge design came from the Seattle music scene."** Seattle was one strand (Chantry, Sub Pop). The editorial style most people picture came from Carson in Southern California and Brody in London, and the theory from Cranbrook and Emigre. +- **"It was careless."** Carson, Brody, and the Cranbrook students were highly trained; the disorder was composed. +- **"Legibility did not matter to them."** The argument was that legibility and communication are different things, and that some audiences read expressive type fluently. It was an argument about audience, not a rejection of reading. + +## Legacy + +- Normalized the designer as author, and custom or expressive type in mainstream editorial and advertising. +- Emigre's model of an independent digital type foundry. +- Recurring revivals in fashion and music graphics, and in the "brutalist" web of the 2010s (see flat-design.md for how that sits beside mainstream UI). + +--- + +## Quick reference + +**Reach for it when**: the audience is music, fashion, or street culture, and the surface is editorial or promotional. +**Avoid it when**: anyone must complete a task. + +**Recipe**: +1. Dark ground, paper-colored text, one acid or rust accent. +2. Distressed display type and photocopied imagery in the header layer only. +3. A plain, high-contrast article or form underneath. diff --git a/plugins/design-mastery/skills/design-movements/references/memphis-group.md b/plugins/design-mastery/skills/design-movements/references/memphis-group.md new file mode 100644 index 0000000..77f3e9b --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/memphis-group.md @@ -0,0 +1,107 @@ +# Memphis Group (1980-1987) + +## Origins and context + +**Where**: Milan. +**When**: Founded in December 1980 by Ettore Sottsass with a group of younger designers and the writer Barbara Radice, who became its chronicler. The first exhibition opened on 18 September 1981 at the Arc '74 gallery in Milan, timed with the furniture fair, and drew a crowd of more than two thousand. Sottsass left in 1985 to focus on his firm, Sottsass Associati, and the group disbanded in 1987. +**Name**: Bob Dylan's "Stuck Inside of Mobile with the Memphis Blues Again" was playing at the founding meeting. The name also evokes the ancient Egyptian capital, an ambiguity the group liked. +**Reacting against**: "Good design" as defined by rational modernism: neutral colors, noble materials, function as the only justification. +**Background**: Radical Design in 1960s-70s Italy, and Studio Alchimia (1976), where Sottsass had worked before breaking away. + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| Ettore Sottsass | Carlton room divider (bookcase) | 1981 | Totemic stacked form, diagonal shelves, plastic laminate as a noble surface | +| Ettore Sottsass | Casablanca sideboard | 1981 | Furniture as a figure with arms; patterned laminate | +| Martine Bedin | Super lamp | 1981 | A lamp on wheels, bulbs like a toy | +| Michael Graves | Plaza dressing table | 1981 | American postmodern architecture as furniture | +| Michele De Lucchi | First chair | 1983 | Circle, sphere, and line as a lightweight chair | +| Nathalie Du Pasquier, George Sowden | Printed textiles and laminate patterns | 1981-86 | Dense, clashing pattern as the surface language of the group | +| Peter Shire | Bel Air armchair | 1982 | Los Angeles color and geometry | +| Shiro Kuramata, Masanori Umeda, Andrea Branzi, Matteo Thun, Aldo Cibic | Furniture, ceramics, glass | 1981-87 | The group's international membership | + +Other members and contributors included Marco Zanini, Hans Hollein, Arata Isozaki, and Javier Mariscal. Sottsass's "Bacterio" laminate pattern, produced with the laminate manufacturer Abet Laminati, is the group's most copied surface. + +Collectors included Karl Lagerfeld and David Bowie; Bowie's collection was auctioned at Sotheby's in 2016. + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Plastic laminate printed with squiggles and "bacterial" dots | Cheap, suburban materials treated as luxury | +| Clashing primaries and pastels (pink, yellow, turquoise, black-and-white) | Color as pleasure, not coordination | +| Primitive geometry stacked like toys (cones, spheres, zigzags) | Objects as characters and totems | +| Unstable, asymmetric silhouettes | Anti-rational form; function is not the only story | +| Heavy black-and-white pattern next to flat color | Pattern and field competing on purpose | + +## Applying it in UI work + +**Fits**: youth and lifestyle brands, playful consumer apps, creative studios, events, snack and drink packaging, marketing pages that must stand out. +**Avoid**: enterprise, medical, legal, and finance interfaces; anything where playfulness reads as unserious. + +Memphis works best as a brand layer (illustration, shapes, pattern) around a disciplined functional UI. + +### Tokens + +```css +:root { + --memphis-pink: #ff6fae; + --memphis-yellow: #ffd23f; + --memphis-turquoise: #1ec8c8; + --memphis-blue: #2d5bff; + --memphis-black: #111111; + --memphis-white: #ffffff; +} + +/* Squiggle and dot pattern as a decorative band */ +.memphis-dots { + background-image: radial-gradient(var(--memphis-black) 2px, transparent 2px); + background-size: 16px 16px; +} +``` + +```html +<!-- Tailwind: offset solid shadow, thick border, decorative shape outside the content --> +<div class="relative"> + <span aria-hidden="true" class="absolute -top-6 -left-6 h-16 w-16 rounded-full bg-[#ffd23f]"></span> + <div class="relative border-4 border-black bg-white p-8 shadow-[8px_8px_0_0_#ff6fae]"> + <h3 class="text-3xl font-black">New flavors</h3> + <p class="mt-2 text-lg">Three limited recipes, one box.</p> + </div> +</div> +``` + +- **Shape**: circles, triangles, zigzags, and squiggles as SVG accents placed outside text blocks. +- **Borders and shadows**: thick black strokes, flat offset shadows (no blur). +- **Type**: a heavy geometric or grotesque sans; avoid mixing more than two faces, because the pattern already supplies noise. +- **Motion**: bouncy springs are in character, but keep them short. + +### Accessibility notes + +- Yellow and turquoise on white fail contrast for text. Put text on white or black panels and keep the palette for shapes. +- Busy patterns behind text reduce legibility. Use pattern in bands and frames only. +- Springy motion should respect `prefers-reduced-motion`. + +## Common misreadings + +- **"Memphis is 1980s pop culture in general."** It was a specific Milan design collective. Much "Memphis style" in TV graphics and merchandise was imitation or coincidence. +- **"It was cheap design."** The objects were produced in small runs and sold as expensive collector pieces, even though they used humble materials. +- **"It was pure fun."** Sottsass framed it as a serious critique of rationalist design and a question about what objects mean. + +## Legacy + +- A visible Memphis revival in fashion, illustration, and web graphics in the 2010s. +- Offset flat shadows, thick outlines, and scattered geometric confetti in current "neo-brutalist" and playful brand design owe it a debt, though often indirectly. + +--- + +## Quick reference + +**Reach for it when**: the brand is playful, young, and wants to look deliberately unserious. +**Avoid it when**: trust, calm, or professionalism is the product. + +**Recipe**: +1. White field, black outlines, three clashing accents. +2. Flat offset shadows, geometric confetti outside text blocks, one dot or squiggle band. +3. Heavy sans, short springy motion, functional UI kept plain. diff --git a/plugins/design-mastery/skills/design-movements/references/minimalism.md b/plugins/design-mastery/skills/design-movements/references/minimalism.md new file mode 100644 index 0000000..805f842 --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/minimalism.md @@ -0,0 +1,102 @@ +# Minimalism (c. 1920s-present) + +Minimalism is less a single movement than a recurring position: reduce a design to what it needs, and let proportion, material, and space do the work. It has several distinct roots, and knowing which one you are borrowing from sharpens the result. + +## Origins and context + +| Root | Where and when | Key idea | +|------|----------------|----------| +| Anti-ornament modernism | Vienna and Germany, 1900s-1920s | Adolf Loos's lecture "Ornament and Crime" (delivered 1910, often dated 1908) argued that ornament was wasted labor | +| De Stijl | Netherlands, from 1917 (Theo van Doesburg's magazine *De Stijl*, Piet Mondrian) | Reduction to horizontals, verticals, primaries, and black and white | +| Modernist architecture | Germany and the United States, 1920s-1960s | Mies van der Rohe (the phrase "less is more" is attributed to him; the words appear earlier in Robert Browning's 1855 poem "Andrea del Sarto"); Barcelona Pavilion (1929) | +| Postwar industrial design | Germany, 1950s-1990s | Dieter Rams at Braun and Vitsœ; his tenth principle: good design is as little design as possible ("Weniger, aber besser") | +| Minimal art | New York, 1960s | Donald Judd, Dan Flavin, Carl Andre, Agnes Martin; the term popularized after Richard Wollheim's essay "Minimal Art" (*Arts Magazine*, January 1965); Judd's "Specific Objects" (written 1964, published 1965) | +| Japanese aesthetics | Long tradition; in modern branding through Muji (founded 1980, art director Ikko Tanaka; Kenya Hara from 2002) | Emptiness as capacity: space left for the user, not poverty of form | +| Digital minimalism | 1990s onward | Search pages with one field, Apple product design under Jony Ive, content-first UI | + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| Piet Mondrian | Compositions with red, yellow, and blue | 1920s | Balance through asymmetric reduction | +| Ludwig Mies van der Rohe | Barcelona Pavilion | 1929 | Free plan, rich materials, almost no ornament | +| Dieter Rams (with Hans Gugelot) | Braun SK 4 radio-phonograph | 1956 | Product as a quiet, ordered object | +| Dieter Rams | Vitsœ 606 Universal Shelving System | 1960 | A modular system that lasts | +| Donald Judd | Untitled stacks | 1960s onward | Repetition and industrial fabrication without composition | +| Agnes Martin | Grid paintings | 1960s | Subtle hand-drawn grids; minimal but not mechanical | +| Kenya Hara | Muji art direction; *Designing Design* (book) | 2000s | Emptiness as a design concept | + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Large areas of empty space | Space is a material; emptiness focuses attention | +| Few colors, often neutrals plus one accent | Every color must carry a meaning | +| One or two typefaces, few weights, strict scale | Hierarchy through size and space, not decoration | +| Precise alignment and proportion | With little on the page, every misalignment shows | +| High-quality materials and imagery | Reduction exposes quality; cheap details become obvious | +| Hidden complexity | The system does the work so the surface does not have to | + +## Applying it in UI work + +**Fits**: premium consumer products, portfolios, reading and writing tools, calm productivity apps, luxury, architecture, galleries. +**Watch out**: minimalism is not the same as removing features or labels. Users still need to find things. + +### Tokens + +```css +:root { + --min-bg: #fafafa; + --min-ink: #171717; + --min-muted: #6b6b6b; /* check contrast, see below */ + --min-line: #e5e5e5; + --min-accent: #1f4ed8; /* one accent, for actions only */ + --space-unit: 8px; /* 8, 16, 24, 48, 96 */ +} +``` + +```html +<!-- Tailwind: one idea per screen, generous space, one action --> +<section class="min-h-screen bg-[#fafafa] text-neutral-900 flex items-center"> + <div class="mx-auto max-w-2xl px-6"> + <h1 class="text-5xl font-light tracking-tight">A quieter inbox.</h1> + <p class="mt-6 text-lg text-neutral-600 leading-8">Only the messages that need you.</p> + <a class="mt-12 inline-block border-b-2 border-neutral-900 pb-1 font-medium">Start free</a> + </div> +</section> +``` + +- **Type**: one family, two or three weights, a modular scale; let size and space create hierarchy. +- **Color**: neutrals plus one accent reserved for interactive elements. +- **Layout**: fewer elements per view, generous margins, consistent spacing unit. +- **Motion**: subtle, short, purposeful (state changes, not decoration). + +### Accessibility notes + +- Minimal designs often fail on low-contrast grey text and hairline borders. Check greys against 4.5:1 for text and 3:1 for input borders and focus indicators. +- Icon-only controls without labels are a common minimalist failure. Keep visible labels or at least accessible names and tooltips. +- Hiding navigation behind gestures or hover harms discoverability; keep primary paths visible. + +## Common misreadings + +- **"Minimal means empty or plain."** The Barcelona Pavilion used onyx, travertine, and chrome. Minimal design often depends on expensive precision. +- **"Less is more" is Rams's line.** It is attributed to Mies van der Rohe; Rams's formulation is "less, but better", which asks for improvement, not just removal. +- **"Minimalism means fewer features."** Rams and Muji reduce what the user must process, not necessarily what the product can do. +- **"It is neutral."** Minimalism signals premium, calm, and control, which is a brand statement like any other. + +## Legacy + +- The dominant visual language of consumer technology and premium brands. +- A constant counterpart to maximalist revivals (Memphis, postmodernism, grunge), which define themselves against it. + +--- + +## Quick reference + +**Reach for it when**: focus, calm, and quality are the product. +**Avoid it when**: users need dense information or discovery of many options; use Swiss-style structure instead. + +**Recipe**: +1. Neutral field, near-black ink, one accent for actions. +2. One type family, big scale steps, an 8px spacing system with generous margins. +3. One primary idea and one primary action per view, with labels kept visible. diff --git a/plugins/design-mastery/skills/design-movements/references/postmodernism.md b/plugins/design-mastery/skills/design-movements/references/postmodernism.md new file mode 100644 index 0000000..d1c6495 --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/postmodernism.md @@ -0,0 +1,99 @@ +# Postmodernism in design (c. 1966-1990s) + +## Origins and context + +**Where**: Architecture first (United States, Italy, Britain), then graphic and product design in Basel, Los Angeles, New York, Milan, and the Cranbrook Academy of Art near Detroit. +**Reacting against**: The authority of modernism: the grid as law, the single "correct" solution, the idea that good design is neutral. +**Core belief**: Meaning comes from context, history, and reference. Complexity, contradiction, humor, and ornament are legitimate. + +The founding text is Robert Venturi's *Complexity and Contradiction in Architecture* (1966), which answered Mies van der Rohe's attributed "less is more" with "Less is a bore." *Learning from Las Vegas* (1972, Venturi, Denise Scott Brown, and Steven Izenour) took the commercial strip seriously as a visual language. Charles Jencks's *The Language of Post-Modern Architecture* (1977) popularized the term for architecture. + +In graphic design the break came from inside Swiss modernism. Wolfgang Weingart, invited by Armin Hofmann to teach typography at the Basel School of Design from 1968, took the Swiss toolkit apart: letterspacing, stepped and layered type, photographic screens. His students, April Greiman among them, carried this "New Wave" typography to the United States. + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| Robert Venturi | *Complexity and Contradiction in Architecture* | 1966 | The intellectual case against modernist purity | +| Venturi, Scott Brown, Izenour | *Learning from Las Vegas* | 1972 | Vernacular signs as design; the "decorated shed" | +| Wolfgang Weingart | Typography teaching and posters, Basel | 1968 onward | Swiss grammar deliberately broken: layered, stepped, textured | +| Studio Alchimia (Alessandro Guerriero, Alessandro Mendini) | Proust armchair (Mendini) | 1978 | Irony: a baroque chair repainted in Pointillist dabs | +| April Greiman | *Design Quarterly* 133, "Does It Make Sense?" (Walker Art Center) | 1986 | An early bitmapped, computer-made poster issue | +| Michael Graves | Portland Building, Portland, Oregon | 1982 | Oversized classical references as flat graphic signs | +| Philip Johnson and John Burgee | AT&T Building, New York (broken pediment top) | 1984 | A skyscraper wearing furniture ornament | +| Paula Scher | Swatch advertisement parodying Herbert Matter's 1934 Swiss tourism poster | 1984-85 | Appropriation and pastiche of modernist history | +| Katherine McCoy (co-chair of design at Cranbrook, 1971-1995) | Cranbrook graduate program; *Cranbrook Design: The New Discourse* | 1990 | Design as a text readers interpret, informed by literary theory | + +Precursor worth knowing: Push Pin Studios in New York (founded 1954 by Seymour Chwast, Milton Glaser, and others) revived Victorian, Art Nouveau, and Art Deco sources long before the term "postmodern" reached graphic design. + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Mixed typefaces, weights, and scales in one composition | No single correct voice | +| Layering, overlap, textures, and screens | Meaning built up in strata | +| Historical quotation (columns, pediments, Victorian type) used flatly | Reference and irony instead of revival | +| Bright, unexpected color combinations (pink, teal, mint, terracotta) | Pleasure over restraint | +| Visible grid being broken | The rules are shown so their breaking reads as intentional | +| Early bitmap and computer artifacts (Greiman) | The tool is part of the message | + +## Applying it in UI work + +**Fits**: cultural institutions, art schools, independent publishers, fashion, music, brands that want to signal wit and self-awareness. +**Avoid**: transactional flows, enterprise software, and anywhere users need predictability over surprise. + +### Tokens + +```css +:root { + --pomo-pink: #f4a7b9; + --pomo-teal: #2a9d8f; + --pomo-mint: #b8e0d2; + --pomo-terracotta: #c8553d; + --pomo-ink: #1d1d1b; + --pomo-paper: #fbf8f1; +} +``` + +```html +<!-- Tailwind: a quoted classical element used as flat graphic, type in mixed scales --> +<section class="relative bg-[#fbf8f1] text-[#1d1d1b] p-10 overflow-hidden"> + <div aria-hidden="true" class="absolute -right-10 top-0 h-full w-24 bg-[#f4a7b9]"></div> + <p class="font-serif italic text-xl">The</p> + <h1 class="text-7xl font-black uppercase leading-none -mt-2">Archive</h1> + <p class="mt-2 ml-24 font-mono text-sm tracking-widest">is open to the public</p> +</section> +``` + +- **Type**: combine a serif, a heavy sans, and a mono deliberately; keep body text in one calm face. +- **Layout**: show a grid, then break it once per view with an overlap or offset. +- **Ornament**: flat geometric quotations (columns, arches, pediments as blocks of color). +- **Motion**: playful but short; offsets and overlaps that settle. + +### Accessibility notes + +- Layered and overlapping type must not cover information text. Keep functional content in a single reading order in the DOM, and mark decorative layers `aria-hidden`. +- Pastel pairs (pink on paper, mint on paper) fail contrast for text. Use them as fields, not as text colors. + +## Common misreadings + +- **"Postmodernism means anything goes."** Venturi, Weingart, and Greiman worked from deep knowledge of the modernist rules they bent. +- **"Memphis is the same as postmodernism."** Memphis is one Milan-based branch, focused on furniture and objects (see memphis-group.md). +- **"It ended with the 1980s."** Its ideas (context, reference, the designer as author) run through 1990s deconstruction and much contemporary branding. + +## Legacy + +- Permission to mix type, reference history, and use humor in serious contexts. +- The designer as author or critic, a thread that runs into Emigre and Cranbrook work (see grunge-deconstructivism.md). + +--- + +## Quick reference + +**Reach for it when**: the brand is witty, cultural, and literate, and wants to show it. +**Avoid it when**: users need predictability, speed, or trust in a transaction. + +**Recipe**: +1. Paper ground, one pastel field, one saturated accent. +2. Serif, heavy sans, and mono mixed in headings; one calm face for text. +3. A visible grid broken once per view, decorative layers kept out of the reading order. diff --git a/plugins/design-mastery/skills/design-movements/references/psychedelic.md b/plugins/design-mastery/skills/design-movements/references/psychedelic.md new file mode 100644 index 0000000..e1596f2 --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/psychedelic.md @@ -0,0 +1,104 @@ +# Psychedelic design (c. 1965-1972) + +## Origins and context + +**Where**: San Francisco first, around the Haight-Ashbury music scene, and London in parallel. +**Reacting against**: The clean, objective corporate modernism of the 1950s and the mainstream culture it represented. +**Core belief**: A poster should be an experience you decode slowly, the way the music and the drug culture around it asked to be experienced. + +The core body of work is the concert poster produced in 1966-1968 for two San Francisco ballrooms: the **Fillmore Auditorium** (promoter Bill Graham) and the **Avalon Ballroom** (Chet Helms and Family Dog Productions). The posters were meant to be read by insiders who would stop and puzzle out the lettering; that was part of the appeal. + +**Sources the artists drew on**: Art Nouveau and Vienna Secession lettering and ornament, Victorian engraving, Op Art's vibrating color, comics, and surf and hot-rod culture. + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| Wes Wilson | Fillmore posters | 1966-67 | Lettering that swells to fill every shape, adapted from Alfred Roller's Vienna Secession lettering | +| Victor Moscoso | Neon Rose poster series (for The Matrix club) | 1967 | Complementary colors of equal value that vibrate; Moscoso studied with Josef Albers at Yale | +| Alton Kelley and Stanley Mouse | Grateful Dead "Skeleton and Roses", Avalon Ballroom | 1966 | Appropriated Edmund J. Sullivan's illustration for the *Rubáiyát of Omar Khayyám* | +| Rick Griffin | "Flying Eyeball", Jimi Hendrix at the Fillmore and Winterland | 1968 | Surf and hot-rod iconography, dense symbolic imagery | +| Bonnie MacLean | Fillmore posters | 1967-68 | Art Nouveau figures and lettering | +| Martin Sharp | Cover of Cream's *Disraeli Gears* | 1967 | The London strand: collage, fluorescent color | +| Hapshash and the Coloured Coat (Michael English, Nigel Waymouth) | UFO Club posters, London | 1967 | Metallic inks, Art Nouveau and Pop fused | + +Wilson, Moscoso, Griffin, Kelley, and Mouse are often grouped as the "Big Five" of San Francisco poster art. + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Lettering that bends to fill a shape | Text as image; reading becomes an act of decoding | +| Complementary hues at equal value (red/green, orange/blue) | Equiluminance makes edges shimmer (Albers's color studies) | +| Dense, edge-to-edge composition | No white space; total immersion | +| Art Nouveau curves and figures | Revival of a pre-modernist ornament to reject corporate modernism | +| Split-fountain and fluorescent inks | Printing technique as part of the effect | + +## Applying it in UI work + +**Fits**: music festivals, record labels, event microsites, cannabis or wellness brands that want counterculture signals, art collectives, limited-run merch. +**Avoid**: anything functional: forms, checkout, settings, documentation, finance, healthcare. + +Use it on a single surface (hero, poster, ticket, splash art) and keep the functional UI calm around it. + +### Tokens + +```css +:root { + --psy-magenta: #e0218a; + --psy-orange: #ff7a00; + --psy-acid: #b6ff00; + --psy-violet: #5b1fa6; + --psy-teal: #00a39a; + --psy-ink: #1a0f24; +} + +/* Poster-only effect: vibrating stripes. Never behind body text. */ +.psy-poster { + background: repeating-radial-gradient(circle at 50% 40%, + var(--psy-magenta) 0 12px, var(--psy-orange) 12px 24px); +} +``` + +```html +<!-- Tailwind: calm UI around one expressive poster panel --> +<div class="grid md:grid-cols-2 gap-8"> + <figure class="psy-poster aspect-[2/3] rounded-3xl"></figure> + <section class="bg-white text-neutral-900 p-8 rounded-3xl"> + <h2 class="text-2xl font-semibold">Main stage lineup</h2> + <a class="mt-6 inline-block rounded-full bg-[#5b1fa6] px-6 py-3 text-white">Get tickets</a> + </section> +</div> +``` + +- **Type**: hand-lettered or display faces for the poster only; a plain sans for every label, price, and button. +- **Motion**: slow hue rotation or warp on the poster only, and off by default under `prefers-reduced-motion`. + +### Accessibility notes (read before shipping) + +- Equal-value complementary colors are designed to be hard to read. Any text that carries information must meet 4.5:1 on a solid background. +- Vibrating patterns and fast color cycling can trigger discomfort, and flashing content can trigger seizures: WCAG 2.3.1 limits content to no more than three flashes in any one-second period. Keep animation slow and respect `prefers-reduced-motion`. +- Deliberately illegible lettering must never be the only place key information (date, venue, price) appears. Repeat it in plain text. + +## Common misreadings + +- **"Every 1960s poster with flowing lines is San Francisco psychedelia."** Milton Glaser's 1966 Bob Dylan poster is often shown alongside psychedelic work and shares its Art Nouveau-influenced line, but Glaser worked from New York's Push Pin Studios, an eclectic illustration practice, rather than the San Francisco ballroom poster scene that defines the style. +- **"Psychedelic is random."** The best posters were carefully constructed: Moscoso's color vibration came from systematic color theory, and the lettering followed strict fill-the-shape rules. +- **"It invented its ornament."** Much of it was openly borrowed from Art Nouveau, the Vienna Secession, and Victorian engraving. + +## Legacy + +- The rave flyers of the late 1980s and 1990s, festival branding, and album art keep reviving it. +- A lasting lesson for UI: legibility is a choice. Choose illegibility only where decoding is the point, never where users must act. + +--- + +## Quick reference + +**Reach for it when**: the product is music, events, or counterculture, and the surface is a poster, not a tool. +**Avoid it when**: users must read, compare, fill in, or pay. + +**Recipe**: +1. One expressive panel with vibrating complementary color and shaped lettering. +2. Everything functional in a calm sans on solid, high-contrast surfaces. +3. Slow motion only, disabled under reduced-motion preferences. diff --git a/plugins/design-mastery/skills/design-movements/references/swiss-international.md b/plugins/design-mastery/skills/design-movements/references/swiss-international.md new file mode 100644 index 0000000..6465424 --- /dev/null +++ b/plugins/design-mastery/skills/design-movements/references/swiss-international.md @@ -0,0 +1,113 @@ +# Swiss International Style (c. 1950-1970s) + +Also called the International Typographic Style. + +## Origins and context + +**Where**: Zurich and Basel, then worldwide through corporate identity and design education. +**Roots**: Ernst Keller's teaching at the Kunstgewerbeschule Zürich from 1918, the New Typography of the 1920s (Bauhaus, Jan Tschichold, Constructivism), Théo Ballmer's grid-built posters, and Max Bill, a former Bauhaus student. +**Reacting against**: Illustrative, emotive, and nationalistic advertising; the propaganda imagery of the war years. +**Core belief**: Communication should be objective. The designer organizes information with a grid, a sans-serif, and photography, and keeps personal expression out of the way. + +### Two schools + +| School | Leading teachers | Emphasis | +|--------|------------------|----------| +| Basel (Allgemeine Gewerbeschule) | Emil Ruder, Armin Hofmann | Typographic form, contrast, rhythm, sensitivity to white space | +| Zurich (Kunstgewerbeschule) | Josef Müller-Brockmann, and the Neue Grafik circle | Systematic grids, objective photography, constructive order | + +**Neue Grafik** (*New Graphic Design / Graphisme actuel*), founded in Zurich in 1958 by Josef Müller-Brockmann, Richard Paul Lohse, Hans Neuburg, and Carlo Vivarelli, ran 18 trilingual issues between 1958 and 1965 and spread the style internationally. + +## Key figures and works + +| Person | Work | Year | What it shows | +|--------|------|------|---------------| +| Max Miedinger, Eduard Hoffmann (Haas foundry) | Neue Haas Grotesk, renamed Helvetica in 1960 | 1957 | A neutral, even grotesque for text and display | +| Adrian Frutiger (Deberny & Peignot) | Univers | 1957 | A systematically numbered family of widths and weights | +| Josef Müller-Brockmann | Tonhalle concert posters (Musica Viva series) | 1950s-70s | Geometric abstraction on a grid as a visual form of music | +| Josef Müller-Brockmann | *Grid Systems in Graphic Design* | 1981 | The standard handbook of grid construction | +| Armin Hofmann | *Graphic Design Manual: Principles and Practice* | 1965 | Point, line, contrast, and letter as formal exercises | +| Emil Ruder | *Typographie* | 1967 | Typography as a discipline of proportion, texture, and white space | +| Karl Gerstner | *Designing Programmes* | 1964 | Design as a system of rules rather than single solutions | +| Unimark International (Massimo Vignelli, Bob Noorda, and partners) | NYC Transit Authority Graphics Standards Manual | 1970 | Swiss method applied to wayfinding at city scale | + +(Akzidenz-Grotesk, the Berthold grotesque of 1898, was the workhorse sans of the early Swiss work before Helvetica and Univers existed.) + +## Visual markers and the principles behind them + +| Marker | Principle | +|--------|-----------| +| Modular grid governing every element | Order that readers can feel even when they cannot see it | +| Flush-left, ragged-right text | Even word spacing and a strong reading edge | +| Grotesque sans-serifs in few weights | Neutral voice so content speaks | +| Asymmetric composition with large empty areas | White space as an active element | +| Objective photography instead of illustration | Documentary truth over persuasion | +| Scale contrast (huge headline, small text) | Hierarchy through size and position, not ornament | + +## Applying it in UI work + +**Fits**: most software, dashboards, documentation, transit and civic services, finance, research, museum sites. Much of the web's default look descends from these ideas through corporate identity and design education. +**Avoid**: products whose value is warmth, whimsy, or craft, unless you add a counter-voice (photography, color, or illustration). + +### Tokens + +```css +:root { + --swiss-black: #111111; + --swiss-white: #ffffff; + --swiss-red: #e30613; /* one accent, used for signal only */ + --swiss-grey: #6b6b6b; + --grid-columns: 12; + --gutter: 1.5rem; + --baseline: 0.5rem; /* 8px rhythm */ +} +``` + +```html +<!-- Tailwind: 12-column grid, flush-left text, scale contrast --> +<main class="grid grid-cols-12 gap-x-6 px-8 py-16 bg-white text-neutral-900"> + <h1 class="col-span-12 md:col-span-8 text-7xl font-bold leading-[0.95] tracking-tight"> + Timetable + </h1> + <p class="col-span-12 md:col-start-1 md:col-span-4 mt-10 text-base leading-7"> + Northbound departures from platform 4. + </p> + <div class="col-span-12 md:col-start-9 md:col-span-4 mt-10 border-t-4 border-[#e30613] pt-4 text-sm"> + Service notes + </div> +</main> +``` + +- **Type**: one grotesque family (Helvetica Neue, Inter, Neue Haas Unica, Suisse-style faces), two or three weights, a clear modular scale. +- **Grid**: define columns, gutters, and a baseline unit, and make everything snap to them. +- **Color**: black, white, grey, and one signal color with a defined meaning. +- **Motion**: minimal and functional. + +### Accessibility notes + +- This style is naturally accessible when contrast is kept high. The risk is thin weights at small sizes and light greys: check greys against 4.5:1. +- Flush-left ragged-right text is easier to read than justified text without hyphenation. + +## Common misreadings + +- **"Swiss style means Helvetica."** The early work used Akzidenz-Grotesk; Helvetica and Univers arrived in 1957. The method (grid, hierarchy, objectivity) matters more than the typeface. +- **"Grids kill creativity."** Müller-Brockmann wrote that the grid is an aid, not a guarantee. The Tonhalle posters are expressive precisely because of the grid. +- **"It is cold."** Basel teaching (Ruder, Hofmann) was deeply concerned with rhythm, texture, and optical sensitivity. + +## Legacy + +- Corporate identity programs, wayfinding systems, and design education worldwide. +- Direct reaction: Wolfgang Weingart, who taught typography at Basel from 1968, pushed the style into what became Swiss Punk and New Wave typography (see postmodernism.md). +- Microsoft's Metro design language cited Swiss graphic design and transit signage as influences (see flat-design.md). + +--- + +## Quick reference + +**Reach for it when**: clarity, trust, and information density matter. +**Avoid it when**: the brand's value is personality or warmth, unless you add a counter-voice. + +**Recipe**: +1. 12-column grid, 8px baseline, flush-left text. +2. One grotesque family, big scale contrast, few weights. +3. Black, white, grey, one signal color with a defined meaning. diff --git a/plugins/design-mastery/skills/design-principles/SKILL.md b/plugins/design-mastery/skills/design-principles/SKILL.md index 63cc46d..ac23fa1 100644 --- a/plugins/design-mastery/skills/design-principles/SKILL.md +++ b/plugins/design-mastery/skills/design-principles/SKILL.md @@ -1,6 +1,6 @@ --- name: design-principles -description: Core visual design principles that underpin all great design. Master gestalt psychology, visual hierarchy, composition, color theory, and typography fundamentals. Use when making design decisions or evaluating designs against proven principles. +description: "Core visual design principles (visual hierarchy, Gestalt grouping, composition, balance, contrast, white space, color, typography) with UI fixes, a checklist, and deep-dive references. Use when making or defending a layout, type, or color decision, or when a design feels off and you need to name why." --- # Design Principles @@ -89,13 +89,15 @@ Lines don't need to be visible—implied lines work. *The mind completes incomplete shapes.* Useful for: -- Logo design (WWF panda, FedEx arrow) +- Logo design (the WWF panda) - Icon design (implied shapes) - Cards that bleed off screen (implies more content) #### Figure/Ground *Clear separation between subject and background.* +Classic example: the arrow in the negative space between the E and x of the FedEx logo. + Common failures: - Text on busy image backgrounds - Low contrast between layers @@ -125,7 +127,7 @@ For web layouts: ### 4. Golden Ratio (1:1.618) -**The Law**: Proportions found in nature feel inherently pleasing. +**The Law**: A proportion that recurs in art and architecture. Evidence for an innate preference for it is weak and mixed, so treat it as one useful ratio among others (1.25, 1.333, 1.5). Applications: - Content width to sidebar: `1:1.618` @@ -136,7 +138,7 @@ Tailwind approximation: ``` Base unit: 16px (text-base) Medium: 24px (text-2xl ≈ 16 × 1.5) -Large: 40px (text-4xl ≈ 16 × 2.5) +Large: 36px (text-4xl = 2.25rem ≈ 16 × 2.25) ``` ### 5. Visual Balance @@ -159,7 +161,7 @@ Large: 40px (text-4xl ≈ 16 × 2.5) | Size | Larger = heavier | | Color | Darker, saturated = heavier | | Complexity | Detailed = heavier | -| Position | Lower = heavier | +| Position | Higher in the frame = heavier (Arnheim) | | Isolation | Alone = heavier | ### 6. Alignment @@ -215,7 +217,7 @@ Types of contrast: **Minimum contrast requirements**: - Body text: 4.5:1 ratio (WCAG AA) -- Large text (18px+): 3:1 ratio +- Large text (24px+ regular, or about 18.66px+ bold): 3:1 ratio - UI components: 3:1 ratio ### 9. White Space (Negative Space) @@ -269,6 +271,8 @@ Take any element and place it elsewhere. Does it still feel like it belongs? If ## Resources +Read the matching file when a decision needs more depth than the summary above. + - **references/gestalt-principles.md**: Deep dive on perceptual grouping - **references/visual-hierarchy.md**: Comprehensive hierarchy techniques - **references/color-theory.md**: Color psychology and application diff --git a/plugins/design-mastery/skills/design-principles/assets/principles-checklist.md b/plugins/design-mastery/skills/design-principles/assets/principles-checklist.md index 27ce5b3..fb325f7 100644 --- a/plugins/design-mastery/skills/design-principles/assets/principles-checklist.md +++ b/plugins/design-mastery/skills/design-principles/assets/principles-checklist.md @@ -68,7 +68,7 @@ Use this checklist to evaluate any design against fundamental principles. - [ ] Generous white space around important elements - [ ] Grid system creates predictable rhythm - [ ] Responsive behavior is considered -- [ ] Touch targets are at least 44x44px +- [ ] Touch targets are at least 24x24px (WCAG 2.2 AA), ideally 44x44px ## Alignment diff --git a/plugins/design-mastery/skills/design-principles/references/color-theory.md b/plugins/design-mastery/skills/design-principles/references/color-theory.md index 2918062..e7fb529 100644 --- a/plugins/design-mastery/skills/design-principles/references/color-theory.md +++ b/plugins/design-mastery/skills/design-principles/references/color-theory.md @@ -138,7 +138,7 @@ Color meanings vary by culture: | Content Type | Minimum Ratio | Tailwind Example | |--------------|---------------|------------------| | Body text | 4.5:1 | gray-600 on white | -| Large text (18px+) | 3:1 | gray-500 on white | +| Large text (24px+ regular, about 18.66px+ bold) | 3:1 | gray-500 on white | | UI components | 3:1 | blue-600 for buttons | | Non-essential | None | Decorative elements | @@ -152,7 +152,7 @@ Color meanings vary by culture: | Type | Affected Colors | Prevalence | |------|-----------------|------------| | Protanopia | Red-green | 1% of males | -| Deuteranopia | Red-green | 6% of males | +| Deuteranopia | Red-green | About 1% of males (the milder deuteranomaly affects about 5%) | | Tritanopia | Blue-yellow | 0.01% of all | **Solutions**: @@ -192,7 +192,8 @@ const palette = { 900: '#111827', }, - // Semantic (choose accessible options) + // Semantic. The 500 steps suit fills, icons, and large graphics. + // As text on white they fail 4.5:1 (green-500 is about 2.3:1): use the 700 step for text. success: '#22c55e', // green-500 warning: '#f59e0b', // amber-500 error: '#ef4444', // red-500 diff --git a/plugins/design-mastery/skills/design-principles/references/composition-rules.md b/plugins/design-mastery/skills/design-principles/references/composition-rules.md new file mode 100644 index 0000000..514c106 --- /dev/null +++ b/plugins/design-mastery/skills/design-principles/references/composition-rules.md @@ -0,0 +1,174 @@ +# Composition rules + +Composition is the arrangement of elements inside a frame: where things go, how big they are relative to each other, and how the empty space between them behaves. Good composition makes a layout feel deliberate and easy to navigate. These are working rules, not laws; each one is a tool for a specific problem. + +## Grids + +A grid is a set of invisible lines that elements snap to. It produces alignment, consistent rhythm, and faster decisions. Josef Muller-Brockmann's *Grid Systems in Graphic Design* (1981) is the classic reference; see the design-masters skill for his work. + +### Anatomy + +| Part | Definition | Web equivalent | +|------|------------|----------------| +| **Columns** | Vertical divisions content spans | `grid-cols-12` | +| **Gutters** | Space between columns | `gap-x-6` | +| **Margins** | Space between the grid and the frame edge | Container padding `px-4 md:px-8` | +| **Modules** | Cells formed where columns cross rows | Grid areas, card slots | +| **Baseline grid** | Horizontal lines text sits on | Line-height multiples of a base unit | +| **Flowlines** | Horizontal alignment lines that break the page into bands | Section tops, consistent vertical offsets | + +### Choosing columns + +| Columns | Divides into | Good for | +|---------|--------------|----------| +| 12 | 2, 3, 4, 6 | General web layouts (most flexible) | +| 8 | 2, 4 | Simpler marketing and app layouts | +| 4 | 2 | Mobile | +| 5 or 7 | Asymmetric spans | Editorial layouts that avoid even splits | + +```html +<div class="mx-auto max-w-7xl px-4 md:px-8"> + <div class="grid grid-cols-4 gap-x-4 md:grid-cols-8 md:gap-x-6 lg:grid-cols-12"> + <main class="col-span-4 md:col-span-5 lg:col-span-8">...</main> + <aside class="col-span-4 md:col-span-3 lg:col-span-4">...</aside> + </div> +</div> +``` + +### Baseline rhythm + +Keep line heights and vertical spacing on multiples of one unit (4px or 8px). Text across adjacent columns then lines up, and sections space consistently. + +```css +:root { --unit: 0.25rem; } /* 4px */ +body { line-height: calc(var(--unit) * 6); } /* 24px at 16px text */ +h2 { margin-block: calc(var(--unit) * 12) calc(var(--unit) * 4); } +``` + +Exact baseline alignment is hard on the web (fonts sit differently in their line boxes); a consistent spacing scale gets most of the benefit. + +## Rule of thirds + +Divide the frame into a 3x3 grid; placing focal points on the lines or their intersections usually feels more dynamic than dead center. The rule comes from painting and photography (John Thomas Smith named it in *Remarks on Rural Scenery*, 1797). + +**In UI**: +- Hero text block aligned to the left third, image weight on the right two thirds +- Crop product and portrait photos so the subject's eyes or key detail sit near an upper intersection +- Use `object-position` to keep the subject on a third when images crop responsively + +```html +<img src="portrait.jpg" alt="..." class="h-80 w-full object-cover object-[center_30%]" /> +``` + +Centered compositions are not wrong; they read as formal and stable. Use thirds when you want movement. + +## Golden ratio + +The golden ratio (about 1:1.618) is a proportion system: a 1.618 type scale, a content/sidebar split near 62/38, spacing steps of 16, 26, 42. + +**Be honest about it**: claims that people innately prefer golden proportions are weakly supported. Experiments on the question, going back to Gustav Fechner in the 19th century, have produced mixed and inconsistent results, and many famous "golden" examples are fitted after the fact. Treat 1.618 as one useful ratio among others (1.5, 1.333, 1.25), chosen because it gives large, clear steps, not because it is magic. + +| Use | Golden version | Practical alternative | +|-----|----------------|------------------------| +| Two-column split | 62% / 38% | `lg:grid-cols-[2fr_1fr]` (67/33) | +| Type scale | x1.618 | x1.25 or x1.333 for more levels | +| Spacing | 16, 26, 42 | 16, 24, 40 (on a 4px/8px scale) | + +## Visual weight and balance + +Rudolf Arnheim's *Art and Visual Perception* (1954, revised 1974) remains the standard account of visual weight: the perceptual pull an element exerts on the composition. + +### What adds weight + +| Factor | Heavier when | Note | +|--------|--------------|------| +| **Size** | Larger | The most obvious lever | +| **Location** | Farther from the center; higher in the frame | Arnheim: weight in the upper part of a composition counts for more than in the lower part, so heavier masses are usually placed low for stability | +| **Isolation** | Standing alone in space | A single small element in white space can balance a dense block | +| **Contrast** | Stronger contrast with its surroundings | Dark on light or light on dark, saturated on neutral | +| **Intrinsic interest** | Faces, text, complex detail | People look at faces and words first | +| **Shape** | Regular, compact shapes | A compact circle holds more weight than a scattered shape of equal area | + +### Balance types + +| Type | Feels | Use for | +|------|-------|---------| +| **Symmetrical** | Formal, stable, calm | Institutional pages, centered heroes, legal content | +| **Asymmetrical** | Dynamic, modern | Marketing, editorial, product pages | +| **Radial** | Focused on a center | Dashboards around one metric, logo lockups | + +**Asymmetrical balance in practice**: a large image on the right balanced by a headline plus generous white space on the left; a heavy data table balanced by a narrow, high-contrast summary column. + +## Alignment + +Every element should share an edge or axis with something else. Near-misses (2 to 3px off) look like mistakes; clear offsets look like decisions. + +- Pick one text alignment per block (usually start-aligned for reading) +- Align to the text, not the container: icons and text inside buttons should share a baseline or center line +- Optical adjustments are allowed: round shapes and triangles often need to overshoot a line slightly to look aligned + +## Rhythm and repetition + +Repeated intervals create rhythm; varied intervals create emphasis. + +| Rhythm | Pattern | Effect | +|--------|---------|--------| +| Regular | Same spacing, same size | Calm, predictable (lists, grids) | +| Progressive | Steadily increasing or decreasing size/spacing | Direction, momentum | +| Alternating | A-B-A-B (image left, image right) | Interest across long pages | + +Break the rhythm once, on purpose, where you want attention. + +## White space + +White space is an active element: it groups, isolates, and signals quality. + +| Level | Controls | Typical scale | +|-------|----------|---------------| +| Micro | Letter spacing, line height, padding inside components | 4 to 16px | +| Meso | Gaps between components | 16 to 32px | +| Macro | Space between sections, page margins | 48 to 128px | + +Generous macro space reads as premium and editorial; tighter space suits dense tools where users scan data. The mistake is inconsistency, not density. + +## Focal point + +Each composition needs one place the eye lands first. Create it with the strongest contrast, the largest size, isolation, or a directional cue (a gaze, a line, an arrow) that points at it. More than one competing focal point is the most common cause of "busy" layouts. See [visual-hierarchy.md](visual-hierarchy.md). + +## Responsive composition + +Composition must survive every width, not just the one in the mockup. + +- **Reflow, do not shrink**: move from 12 to 8 to 4 columns and restack rather than scaling everything down +- **Keep the focal point first in source order** so it stays first on mobile +- **Re-crop images per breakpoint** (`object-position`, art direction with `<picture>`) so subjects stay in frame +- **Scale macro space more than micro space**: section padding can halve on mobile while component padding stays similar +- **Use container queries** (`@container`) for components that live in columns of varying width + +```html +<section class="py-16 md:py-24 lg:py-32"> + <div class="@container"> + <div class="grid gap-6 @lg:grid-cols-2">...</div> + </div> +</section> +``` + +(`@container` utilities are built into Tailwind CSS v4; v3 needs the `@tailwindcss/container-queries` plugin.) + +## Composition checklist + +- [ ] Layout snaps to a defined grid with consistent gutters and margins +- [ ] Vertical spacing uses one scale +- [ ] One clear focal point per view +- [ ] Balance is intentional (symmetrical or asymmetrical, not accidental) +- [ ] No near-miss alignments +- [ ] Rhythm breaks only where emphasis is wanted +- [ ] White space is consistent at each level +- [ ] Focal point and grouping survive at mobile width + +## Related references + +- [gestalt-principles.md](gestalt-principles.md): grouping behavior that composition relies on +- [visual-hierarchy.md](visual-hierarchy.md): ordering content within the composition +- [typography-fundamentals.md](typography-fundamentals.md): line length and vertical rhythm for text +- [../assets/principles-checklist.md](../assets/principles-checklist.md): evaluation checklist diff --git a/plugins/design-mastery/skills/design-principles/references/gestalt-principles.md b/plugins/design-mastery/skills/design-principles/references/gestalt-principles.md new file mode 100644 index 0000000..b282962 --- /dev/null +++ b/plugins/design-mastery/skills/design-principles/references/gestalt-principles.md @@ -0,0 +1,186 @@ +# Gestalt principles of perceptual grouping + +The eye does not read a screen pixel by pixel. It groups, completes, and separates before the user reads a single word. Gestalt principles describe those grouping rules, so you can make the grouping the user perceives match the grouping you intended. + +## Origins + +| Who | Contribution | +|-----|--------------| +| **Max Wertheimer** | His 1923 paper "Untersuchungen zur Lehre von der Gestalt II" (Psychologische Forschung, vol. 4) set out the "laws of organization" for grouping: proximity, similarity, common fate, continuity, closure | +| **Kurt Koffka** | Brought the ideas to English readers; *Principles of Gestalt Psychology* (1935) | +| **Wolfgang Kohler** | *Gestalt Psychology* (1929); with Wertheimer and Koffka formed the Berlin school | +| **Stephen Palmer** | Added **common region** (1992) and, with Irvin Rock, **uniform connectedness** (1994) | + +The core claim of the Berlin school: the whole is perceived as something other than the sum of its parts. For UI work the practical reading is simpler. Users see groups first, and they act on the groups they see. + +## Quick map + +| Principle | The eye groups things that... | UI lever | +|-----------|-------------------------------|----------| +| Proximity | are close together | Spacing scale | +| Similarity | look alike | Color, shape, size, type style | +| Common region | share an enclosed area | Cards, panels, background fills | +| Uniform connectedness | are visually connected | Lines, connectors, shared bars | +| Continuity | lie along a line or curve | Alignment, flow, steppers | +| Closure | form a shape when completed | Icons, logos, implied edges | +| Figure/ground | stand out from a background | Contrast, elevation, overlays | +| Common fate | move or change together | Animation, simultaneous state change | +| Symmetry | mirror each other | Balanced layouts, centered heroes | +| Pragnanz | form the simplest reading | Reduce ambiguity overall | + +--- + +## Proximity + +*Elements near each other are perceived as related.* + +**UI example**: A form where the gap between a label and its own input equals the gap between that input and the next label. Users cannot tell which label belongs to which field. + +**Fix pattern**: Internal spacing smaller than external spacing, by a clear margin (roughly 2x or more). + +```html +<!-- Label hugs its input; groups separate clearly --> +<div class="space-y-6"> + <div class="space-y-1.5"> + <label class="text-sm font-medium">Email</label> + <input class="w-full rounded-md border px-3 py-2" /> + </div> + <div class="space-y-1.5"> + <label class="text-sm font-medium">Password</label> + <input class="w-full rounded-md border px-3 py-2" /> + </div> +</div> +``` + +Proximity usually beats similarity: two items of different colors placed close together still read as a pair. + +## Similarity + +*Elements that share visual properties (color, shape, size, orientation, texture) are perceived as a group.* + +**UI example**: Links styled exactly like body text except for color, and a heading that happens to use the link color. Users click the heading. + +**Fix pattern**: Reserve one visual signature per role. If blue means "clickable", nothing non-interactive is blue. + +| Role | Signature | +|------|-----------| +| Primary action | Filled, brand color | +| Secondary action | Outline or ghost | +| Link | Brand color + underline on hover or always in body copy | +| Status | Semantic color + icon | + +## Common region + +*Elements inside the same bounded area are perceived as a group, even when they are far apart or dissimilar.* Palmer (1992) showed that a shared region can override proximity. + +**UI example**: A pricing page where each plan's features float in open space and the columns blur together. + +**Fix pattern**: Give each group a container (card, tinted panel, bordered section). Use the lightest region that works; a subtle background shift often does the job a heavy border would do. + +```html +<section class="rounded-xl bg-slate-50 p-6 ring-1 ring-slate-200"> + <!-- everything in here reads as one plan --> +</section> +``` + +## Uniform connectedness + +*Elements joined by a visible connection (line, bar, shared shape) are perceived as a unit, and this tends to be stronger than proximity or similarity.* (Palmer and Rock, 1994) + +**UI example**: A multi-step checkout with step circles but no connecting line; users do not read it as a sequence. + +**Fix pattern**: Connect sequential items with a track; connect a tooltip to its target with a pointer; connect a selected tab to its panel by merging their borders. + +## Continuity (good continuation) + +*The eye follows smooth lines and curves and prefers continuous paths over abrupt changes.* + +**UI example**: A card grid where one card's text starts at a different inset, breaking the column the eye was following. + +**Fix pattern**: Keep strong shared edges (text starts, image edges, button edges). Horizontal carousels that cut the last card at the viewport edge use continuity to signal "more this way". + +## Closure + +*The mind completes incomplete shapes and fills gaps to see a whole.* + +**Famous example**: The WWF panda. The head and back are not fully outlined, yet the viewer sees a complete animal. + +**UI example**: Icon sets drawn with open strokes; a dashed outline for an upload drop zone; a progress ring with a gap. + +**Fix pattern**: Remove lines the eye will supply anyway. Test at small sizes: closure fails when the gaps get too large relative to the shape, so check icons at 16px and 24px. + +## Figure/Ground + +*Perception separates a figure (the subject) from the ground (everything behind it).* Ambiguous figure/ground produces the classic vase-or-faces effect. + +**Famous example**: The FedEx logo (Lindon Leader at Landor, 1994). The arrow between the "E" and the "x" is negative space, the ground becoming a figure. It is a figure/ground device, not closure. + +**UI examples**: +- Text over busy photography with no scrim +- Modals whose overlay is too light to push the page back +- Dark-mode surfaces with no step between background and card + +**Fix pattern**: + +```html +<!-- Scrim restores figure/ground over imagery --> +<div class="relative"> + <img src="hero.jpg" alt="" class="h-96 w-full object-cover" /> + <div class="absolute inset-0 bg-gradient-to-t from-black/70 to-transparent"></div> + <h1 class="absolute bottom-8 left-8 text-4xl font-semibold text-white">Title</h1> +</div> +``` + +In dark mode, lift figures with lighter surfaces rather than shadows (for example `bg-slate-900` page, `bg-slate-800` card). + +## Common fate + +*Elements that move or change in the same direction at the same time are perceived as a group.* + +**UI example**: Selecting three rows in a table, then the bulk-action bar slides in while only one of the rows animates; users doubt the other two are selected. + +**Fix pattern**: Animate related elements together (same duration, easing, direction). Stagger only when you want to show order within a group. Respect `prefers-reduced-motion`; common fate can also be carried by a simultaneous color or state change instead of movement. + +## Symmetry + +*Symmetrical elements are perceived as belonging together and as a stable whole.* + +**UI example**: A centered marketing hero reads as calm and formal; a symmetrical two-column comparison implies equal weight between options. + +**Fix pattern**: Use symmetry when you want neutrality or stability. Break it on purpose when one option should win (a highlighted plan in an otherwise symmetrical pricing row). + +## Pragnanz (simplicity) + +*Perception settles on the simplest, most stable interpretation available.* Wertheimer treated this as the umbrella tendency behind the other laws. + +**Fix pattern**: When a layout can be read two ways, users pick the simpler one, which may not be yours. Remove competing groupings: one container style, one alignment system, one spacing scale. + +--- + +## Principles in conflict + +| Conflict | Usually wins | Design implication | +|----------|--------------|--------------------| +| Proximity vs. similarity | Proximity | Fix spacing before recoloring | +| Common region vs. proximity | Common region | A card groups its contents even with loose spacing | +| Connectedness vs. proximity | Connectedness | A connector line can join distant items | + +These are tendencies observed in perception research, not absolute rankings. Test with real users when the stakes are high. + +## Audit checklist + +- [ ] Spacing inside groups is clearly smaller than spacing between groups +- [ ] Each interactive role has one consistent visual signature +- [ ] Groups that must read as units share a region or a connector +- [ ] Text starts and edges line up so the eye can continue along them +- [ ] Icons still close into shapes at their smallest size +- [ ] Every text layer has clear figure/ground (check over images and in dark mode) +- [ ] Elements that change together animate together +- [ ] No area of the screen supports two competing readings + +## Related references + +- [visual-hierarchy.md](visual-hierarchy.md): ordering the groups once they exist +- [composition-rules.md](composition-rules.md): grids, alignment, balance +- [color-theory.md](color-theory.md): color as a similarity signal +- [../assets/principles-checklist.md](../assets/principles-checklist.md): full evaluation checklist diff --git a/plugins/design-mastery/skills/design-principles/references/visual-hierarchy.md b/plugins/design-mastery/skills/design-principles/references/visual-hierarchy.md new file mode 100644 index 0000000..7e14329 --- /dev/null +++ b/plugins/design-mastery/skills/design-principles/references/visual-hierarchy.md @@ -0,0 +1,150 @@ +# Visual hierarchy + +Hierarchy is the order in which a person notices things. Every screen has one, whether you designed it or not. Good hierarchy makes that order match the order of importance: the one thing that matters most is seen first, the supporting information second, the details last. + +## The tools + +Each tool raises or lowers an element's position in the reading order. Use as few as you need; stacking every tool on one element flattens everything else into noise. + +| Tool | Raises priority | Lowers priority | Tailwind levers | +|------|-----------------|-----------------|-----------------| +| **Size** | Larger | Smaller | `text-*`, `w-*`, `h-*` | +| **Weight** | Bolder | Lighter | `font-semibold`, `font-normal` | +| **Color** | Saturated, brand, warm | Muted, gray | `text-slate-900` vs `text-slate-500` | +| **Contrast** | High contrast with surroundings | Low contrast | Foreground/background pairs | +| **Position** | Top, start of reading direction, center of focus | Bottom, periphery | Order in the layout | +| **Spacing** | Isolated by white space | Packed with neighbors | `p-*`, `gap-*`, `my-*` | +| **Depth** | Elevated (shadow, overlay) | Flat, recessed | `shadow-*`, `ring-*`, `z-*` | +| **Motion** | Moving or changing | Static | `transition`, `animate-*` (sparingly) | + +Motion is the strongest attention signal and the easiest to abuse. Reserve it for state changes the user needs to notice, and honor `prefers-reduced-motion`. + +## Three levels are usually enough + +Most views work with three tiers: + +| Tier | Contains | Typical treatment | +|------|----------|-------------------| +| **Primary** | Page purpose, main headline, the main action | Largest type or strongest color, most isolation | +| **Secondary** | Section headings, key data, secondary actions | Medium size, full-contrast text | +| **Tertiary** | Metadata, captions, helper text, timestamps | Small size, muted color | + +If you find yourself inventing a fifth or sixth distinct tier, the content usually needs regrouping rather than more styling. + +## Emphasis by de-emphasis + +Making the important thing louder is only half the job. Often the better move is to quiet everything else. + +```html +<!-- Before: everything shouts --> +<div class="font-bold text-slate-900"> + <p class="text-lg">Revenue</p> + <p class="text-lg">$48,200</p> + <p class="text-lg">+12% vs last period</p> +</div> + +<!-- After: one number leads, the rest supports --> +<div> + <p class="text-sm font-medium text-slate-500">Revenue</p> + <p class="text-3xl font-semibold tracking-tight text-slate-900">$48,200</p> + <p class="text-sm text-emerald-700">+12% vs last period</p> +</div> +``` + +The label became smaller and grayer, the value became larger, and the delta kept a semantic color at small size. Hierarchy improved without adding anything. + +## Scanning patterns + +People scan before they read. Nielsen Norman Group eyetracking research documents several patterns: + +| Pattern | Source | What happens | Design response | +|---------|--------|--------------|-----------------| +| **F-pattern** | Jakob Nielsen, NN/g, 2006; reconfirmed by Kara Pernice, NN/g, 2017 and 2019 | Readers scan across the top, then a shorter line lower down, then down the left edge | Put the key words at the start of headings and list items; do not bury the point at the end of a line | +| **Layer-cake** | Pernice, NN/g, 2019 ("Text Scanning Patterns: Eyetracking Evidence") | Eyes jump from heading to heading, skipping body text until a section looks relevant | Write headings that carry meaning on their own | +| **Spotted** | Same article | Eyes skip around looking for specific things (numbers, links, keywords) | Make target items visually findable (format numbers, style links clearly) | +| **Commitment** | Same article | Motivated readers read nearly everything | Still structure the page; committed readers benefit from clear hierarchy too | + +NN/g frames the F-pattern as a symptom of content that gives readers no better path, not as a layout to aim for. Strong headings, front-loaded text, and chunking replace it with the more efficient layer-cake behavior. + +The **Z-pattern** is a layout convention rather than an eyetracking finding: on sparse pages (landing pages, hero sections) designers place logo top left, navigation or CTA top right, content across the middle, and the action bottom right, following a zig-zag. Treat it as a heuristic for simple, low-text layouts. + +## Type scale ratios (modular scale) + +A consistent ratio between sizes makes hierarchy feel intentional. Multiply a base size by the ratio for each step up. + +| Ratio | Name | Steps from 16px | Suits | +|-------|------|-----------------|-------| +| 1.125 | Major second | 16, 18, 20.25, 22.8 | Dense apps, dashboards | +| 1.2 | Minor third | 16, 19.2, 23, 27.6 | General UI | +| 1.25 | Major third | 16, 20, 25, 31.25 | Content sites, marketing | +| 1.333 | Perfect fourth | 16, 21.3, 28.4, 37.9 | Editorial, bold marketing | +| 1.5 | Perfect fifth | 16, 24, 36, 54 | Display-heavy pages | +| 1.618 | Golden ratio | 16, 25.9, 41.9, 67.8 | Dramatic heroes, few levels | + +The Tailwind default scale is hand-tuned rather than a single ratio (`text-base` 16px, `text-lg` 18px, `text-xl` 20px, `text-2xl` 24px, `text-3xl` 30px, `text-4xl` 36px). Pick steps from it that keep a clear jump between tiers, for example `text-sm` / `text-base` / `text-2xl` / `text-4xl`. A tool such as modularscale.com (Tim Brown) generates exact values if you want a strict ratio. + +See [typography-fundamentals.md](typography-fundamentals.md) for line length, leading, and tracking. + +## One primary action per view + +When two buttons are both styled as primary, neither is. Pick the single action the view exists for and give it the primary treatment; everything else steps down. + +| Action type | Treatment | Example | +|-------------|-----------|---------| +| Primary | Filled brand color, largest button | "Create project" | +| Secondary | Outline or subtle fill | "Import" | +| Tertiary | Text or ghost button | "Learn more" | +| Destructive | Red, usually secondary weight until confirmation | "Delete" | + +```html +<div class="flex gap-3"> + <button class="rounded-md bg-indigo-600 px-4 py-2 font-medium text-white">Create project</button> + <button class="rounded-md px-4 py-2 font-medium text-slate-700 ring-1 ring-slate-300">Import</button> +</div> +``` + +Exceptions exist (a confirm dialog may give "Cancel" and "Delete" similar size), but the rule holds for the view as a whole. + +## Dashboard hierarchy + +Dashboards fail when every widget competes. Order the page by the decisions it supports. + +1. **Answer first**: the few numbers that say whether things are fine (top row, largest values) +2. **Explanation second**: trend charts that explain the numbers +3. **Detail last**: tables, logs, breakdowns, below the fold or behind drill-down + +| Element | Primary signal | Keep quiet | +|---------|----------------|------------| +| KPI card | The value | Label, period, sparkline | +| Chart | The data series that matters | Gridlines, axis labels, legend | +| Table | Row identifiers and the key column | Borders, secondary columns | +| Alert | Severity color + one-line message | Timestamp, IDs | + +Muted gridlines (`stroke-slate-200`), right-aligned tabular numbers (`tabular-nums`), and one accent color for the series under discussion do more than any decoration. + +## Testing hierarchy + +**Squint or blur test**: Blur a screenshot (or squint). The primary element should still be obvious, the groups should still read as groups, and the main action should still be findable. + +**Grayscale test**: Remove color. If the hierarchy collapses, it depended on color alone, which also fails users with color vision deficiency. + +**First-glance test**: Show the screen briefly to someone unfamiliar with it, then ask what the page is for and what they would click. If the answers differ from your intent, the hierarchy is wrong. + +**Five-word test**: Describe the reading order in five words ("headline, price, button, features, footer"). If you cannot, neither can the user. + +## Common failures + +| Symptom | Cause | Fix | +|---------|-------|-----| +| "Nothing stands out" | All elements at similar size/weight | Enlarge one element, mute the rest | +| "Everything stands out" | Too many bold, colored, or large items | Remove emphasis from all but the primary tier | +| "Users miss the button" | CTA color used elsewhere, or CTA lacks space | Reserve the CTA color, isolate the button | +| "Headings look like body" | Size step too small | Use a larger ratio or add weight contrast | +| "The page feels flat" | No depth or spacing variation | Group into regions; vary spacing between tiers | + +## Related references + +- [gestalt-principles.md](gestalt-principles.md): how grouping forms before hierarchy is read +- [composition-rules.md](composition-rules.md): position, balance, focal point +- [color-theory.md](color-theory.md): contrast and emphasis through color +- [../assets/principles-checklist.md](../assets/principles-checklist.md): evaluation checklist diff --git a/plugins/design-mastery/skills/premium-saas-design/SKILL.md b/plugins/design-mastery/skills/premium-saas-design/SKILL.md index b61fb2a..99da380 100644 --- a/plugins/design-mastery/skills/premium-saas-design/SKILL.md +++ b/plugins/design-mastery/skills/premium-saas-design/SKILL.md @@ -1,11 +1,11 @@ --- name: premium-saas-design -description: Professional framework for building premium $5k+ SaaS websites with AI - the Define, Build, Review, Refine loop used by real product teams +description: "The Define, Build, Review, Refine loop and seven context artifacts (brief, content, mood boards, section specs, style guide, PRD, tasks) for building a premium SaaS marketing site with AI. Use when planning or building a SaaS landing page and you want the design context written down before any code." --- # Premium SaaS Design Framework -> "75% of users won't trust a company if the design doesn't look good." +> In Stanford's large 2002 web credibility study (B.J. Fogg and colleagues), a site's visual design was the factor people mentioned most often when they judged whether to trust it. This skill captures the professional design workflow used by senior product teams and UI/UX designers, adapted for AI-assisted development. The framework transforms AI from a "guessing machine" into a true design partner. diff --git a/plugins/developer-essentials/.claude-plugin/plugin.json b/plugins/developer-essentials/.claude-plugin/plugin.json new file mode 100644 index 0000000..25c6cbc --- /dev/null +++ b/plugins/developer-essentials/.claude-plugin/plugin.json @@ -0,0 +1,22 @@ +{ + "name": "developer-essentials", + "version": "1.0.0", + "description": "Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "git", + "sql", + "debugging", + "testing", + "authentication", + "code-review", + "monorepo", + "essential" + ] +} diff --git a/plugins/distributed-debugging/.claude-plugin/plugin.json b/plugins/distributed-debugging/.claude-plugin/plugin.json new file mode 100644 index 0000000..7e43160 --- /dev/null +++ b/plugins/distributed-debugging/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "distributed-debugging", + "version": "1.2.0", + "description": "Distributed system tracing and debugging across microservices", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "distributed-tracing", + "microservices", + "debugging", + "observability" + ] +} diff --git a/plugins/distributed-debugging/commands/debug-trace.md b/plugins/distributed-debugging/commands/debug-trace.md index 55d1256..a722865 100644 --- a/plugins/distributed-debugging/commands/debug-trace.md +++ b/plugins/distributed-debugging/commands/debug-trace.md @@ -1,3 +1,8 @@ +--- +description: "Set up debugging, distributed tracing, and diagnostic tooling for a system" +argument-hint: "[service or system]" +--- + # Debug and Trace Configuration You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments. diff --git a/plugins/documentation-generation/.claude-plugin/plugin.json b/plugins/documentation-generation/.claude-plugin/plugin.json new file mode 100644 index 0000000..abd2707 --- /dev/null +++ b/plugins/documentation-generation/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "documentation-generation", + "version": "1.2.0", + "description": "OpenAPI specification generation, Mermaid diagram creation, tutorial writing, API reference documentation", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "documentation", + "api-docs", + "diagrams", + "openapi", + "swagger", + "mermaid" + ] +} diff --git a/plugins/documentation-generation/commands/doc-generate.md b/plugins/documentation-generation/commands/doc-generate.md index 7b25151..1899e58 100644 --- a/plugins/documentation-generation/commands/doc-generate.md +++ b/plugins/documentation-generation/commands/doc-generate.md @@ -1,3 +1,8 @@ +--- +description: "Generate API docs, architecture diagrams, and guides from the codebase" +argument-hint: "[project or module]" +--- + # Automated Documentation Generation You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices. diff --git a/plugins/error-debugging/.claude-plugin/plugin.json b/plugins/error-debugging/.claude-plugin/plugin.json new file mode 100644 index 0000000..a09426d --- /dev/null +++ b/plugins/error-debugging/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "error-debugging", + "version": "1.2.0", + "description": "Error analysis, trace debugging, and multi-agent problem diagnosis", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "error-handling", + "debugging", + "diagnostics", + "troubleshooting" + ] +} diff --git a/plugins/error-debugging/commands/error-analysis.md b/plugins/error-debugging/commands/error-analysis.md index 8d4c690..cf9e26c 100644 --- a/plugins/error-debugging/commands/error-analysis.md +++ b/plugins/error-debugging/commands/error-analysis.md @@ -1,3 +1,8 @@ +--- +description: "Analyze errors and incidents to find root causes and fixes" +argument-hint: "[error, logs, or incident]" +--- + # Error Analysis and Resolution You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions. diff --git a/plugins/error-debugging/commands/error-trace.md b/plugins/error-debugging/commands/error-trace.md index 73f4b64..4c84c39 100644 --- a/plugins/error-debugging/commands/error-trace.md +++ b/plugins/error-debugging/commands/error-trace.md @@ -1,3 +1,8 @@ +--- +description: "Set up error tracking, alerting, and structured logging" +argument-hint: "[application or service]" +--- + # Error Tracking and Monitoring You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues. diff --git a/plugins/error-debugging/commands/multi-agent-review.md b/plugins/error-debugging/commands/multi-agent-review.md index 8b37727..84cde79 100644 --- a/plugins/error-debugging/commands/multi-agent-review.md +++ b/plugins/error-debugging/commands/multi-agent-review.md @@ -1,3 +1,8 @@ +--- +description: "Review code with several specialized agents and merge their findings" +argument-hint: "[path or PR]" +--- + # Multi-Agent Code Review Orchestration Tool ## Role: Expert Multi-Agent Review Orchestration Specialist diff --git a/plugins/error-diagnostics/.claude-plugin/plugin.json b/plugins/error-diagnostics/.claude-plugin/plugin.json new file mode 100644 index 0000000..12b30c4 --- /dev/null +++ b/plugins/error-diagnostics/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "error-diagnostics", + "version": "1.2.0", + "description": "Error tracing, root cause analysis, and smart debugging for production systems", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "diagnostics", + "error-tracing", + "root-cause", + "debugging" + ] +} diff --git a/plugins/error-diagnostics/commands/error-analysis.md b/plugins/error-diagnostics/commands/error-analysis.md index 8d4c690..cf9e26c 100644 --- a/plugins/error-diagnostics/commands/error-analysis.md +++ b/plugins/error-diagnostics/commands/error-analysis.md @@ -1,3 +1,8 @@ +--- +description: "Analyze errors and incidents to find root causes and fixes" +argument-hint: "[error, logs, or incident]" +--- + # Error Analysis and Resolution You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions. diff --git a/plugins/error-diagnostics/commands/error-trace.md b/plugins/error-diagnostics/commands/error-trace.md index 73f4b64..4c84c39 100644 --- a/plugins/error-diagnostics/commands/error-trace.md +++ b/plugins/error-diagnostics/commands/error-trace.md @@ -1,3 +1,8 @@ +--- +description: "Set up error tracking, alerting, and structured logging" +argument-hint: "[application or service]" +--- + # Error Tracking and Monitoring You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues. diff --git a/plugins/error-diagnostics/commands/smart-debug.md b/plugins/error-diagnostics/commands/smart-debug.md index 600a582..df498ce 100644 --- a/plugins/error-diagnostics/commands/smart-debug.md +++ b/plugins/error-diagnostics/commands/smart-debug.md @@ -1,3 +1,8 @@ +--- +description: "Debug an issue from its error, stack trace, or symptoms with root cause analysis" +argument-hint: "[error, stack trace, or issue]" +--- + You are an expert AI-assisted debugging specialist with deep knowledge of modern debugging tools, observability platforms, and automated root cause analysis. ## Context diff --git a/plugins/framework-migration/.claude-plugin/plugin.json b/plugins/framework-migration/.claude-plugin/plugin.json new file mode 100644 index 0000000..7965217 --- /dev/null +++ b/plugins/framework-migration/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "framework-migration", + "version": "1.2.2", + "description": "Framework updates, migration planning, and architectural transformation workflows", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "migration", + "framework-upgrade", + "modernization", + "angular", + "react" + ] +} diff --git a/plugins/framework-migration/commands/code-migrate.md b/plugins/framework-migration/commands/code-migrate.md index 3074213..a6759af 100644 --- a/plugins/framework-migration/commands/code-migrate.md +++ b/plugins/framework-migration/commands/code-migrate.md @@ -1,3 +1,8 @@ +--- +description: "Plan and script a migration between frameworks, languages, or versions" +argument-hint: "[source and target stack]" +--- + # Code Migration Assistant You are a code migration expert specializing in transitioning codebases between frameworks, languages, versions, and platforms. Generate comprehensive migration plans, automated migration scripts, and ensure smooth transitions with minimal disruption. diff --git a/plugins/framework-migration/commands/deps-upgrade.md b/plugins/framework-migration/commands/deps-upgrade.md index 4496ed2..7a10c4e 100644 --- a/plugins/framework-migration/commands/deps-upgrade.md +++ b/plugins/framework-migration/commands/deps-upgrade.md @@ -1,3 +1,8 @@ +--- +description: "Plan and run safe, incremental dependency upgrades that handle breaking changes" +argument-hint: "[packages or project]" +--- + # Dependency Upgrade Strategy You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration paths for breaking changes. diff --git a/plugins/framework-migration/commands/legacy-modernize.md b/plugins/framework-migration/commands/legacy-modernize.md index ab0491c..414730b 100644 --- a/plugins/framework-migration/commands/legacy-modernize.md +++ b/plugins/framework-migration/commands/legacy-modernize.md @@ -1,3 +1,8 @@ +--- +description: "Modernize a legacy system step by step with the strangler fig pattern" +argument-hint: "[legacy system or component]" +--- + # Legacy Code Modernization Workflow Orchestrate a comprehensive legacy system modernization using the strangler fig pattern, enabling gradual replacement of outdated components while maintaining continuous business operations through expert agent coordination. diff --git a/plugins/frontend-mobile-development/.claude-plugin/plugin.json b/plugins/frontend-mobile-development/.claude-plugin/plugin.json new file mode 100644 index 0000000..24b6dba --- /dev/null +++ b/plugins/frontend-mobile-development/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "frontend-mobile-development", + "version": "1.2.0", + "description": "Frontend UI development and mobile application implementation across platforms", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "frontend", + "mobile", + "react", + "ui", + "cross-platform" + ] +} diff --git a/plugins/frontend-mobile-development/commands/component-scaffold.md b/plugins/frontend-mobile-development/commands/component-scaffold.md index 7daa7c8..e2a6660 100644 --- a/plugins/frontend-mobile-development/commands/component-scaffold.md +++ b/plugins/frontend-mobile-development/commands/component-scaffold.md @@ -1,3 +1,8 @@ +--- +description: "Scaffold a typed, accessible React or React Native component with tests and styles" +argument-hint: "[component name and purpose]" +--- + # React/React Native Component Scaffolding You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, styles, and documentation following modern best practices. diff --git a/plugins/frontend-mobile-security/.claude-plugin/plugin.json b/plugins/frontend-mobile-security/.claude-plugin/plugin.json new file mode 100644 index 0000000..d565cd0 --- /dev/null +++ b/plugins/frontend-mobile-security/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "frontend-mobile-security", + "version": "1.2.0", + "description": "XSS prevention, CSRF protection, content security policies, mobile app security, and secure storage patterns", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "frontend-security", + "mobile-security", + "xss", + "csrf", + "csp" + ] +} diff --git a/plugins/frontend-mobile-security/commands/xss-scan.md b/plugins/frontend-mobile-security/commands/xss-scan.md index 07f095f..7d85e2b 100644 --- a/plugins/frontend-mobile-security/commands/xss-scan.md +++ b/plugins/frontend-mobile-security/commands/xss-scan.md @@ -1,3 +1,8 @@ +--- +description: "Scan frontend code for XSS vulnerabilities and unsafe DOM handling" +argument-hint: "[path or component]" +--- + # XSS Vulnerability Scanner for Frontend Code You are a frontend security specialist focusing on Cross-Site Scripting (XSS) vulnerability detection and prevention. Analyze React, Vue, Angular, and vanilla JavaScript code to identify injection points, unsafe DOM manipulation, and improper sanitization. diff --git a/plugins/full-stack-orchestration/.claude-plugin/plugin.json b/plugins/full-stack-orchestration/.claude-plugin/plugin.json new file mode 100644 index 0000000..7267aa1 --- /dev/null +++ b/plugins/full-stack-orchestration/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "full-stack-orchestration", + "version": "1.2.1", + "description": "End-to-end feature orchestration with testing, security, performance, and deployment", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "full-stack", + "orchestration", + "deployment", + "security", + "testing" + ] +} diff --git a/plugins/full-stack-orchestration/commands/full-stack-feature.md b/plugins/full-stack-orchestration/commands/full-stack-feature.md index f565bba..0df75a1 100644 --- a/plugins/full-stack-orchestration/commands/full-stack-feature.md +++ b/plugins/full-stack-orchestration/commands/full-stack-feature.md @@ -1,3 +1,8 @@ +--- +description: "Build a feature across database, backend, frontend, and infrastructure, API first" +argument-hint: "[feature description]" +--- + Orchestrate full-stack feature development across backend, frontend, and infrastructure layers with modern API-first approach: [Extended thinking: This workflow coordinates multiple specialized agents to deliver a complete full-stack feature from architecture through deployment. It follows API-first development principles, ensuring contract-driven development where the API specification drives both backend implementation and frontend consumption. Each phase builds upon previous outputs, creating a cohesive system with proper separation of concerns, comprehensive testing, and production-ready deployment. The workflow emphasizes modern practices like component-driven UI development, feature flags, observability, and progressive rollout strategies.] diff --git a/plugins/functional-programming/.claude-plugin/plugin.json b/plugins/functional-programming/.claude-plugin/plugin.json new file mode 100644 index 0000000..2e3abd5 --- /dev/null +++ b/plugins/functional-programming/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "functional-programming", + "version": "1.2.0", + "description": "Functional programming with Elixir, OTP patterns, Phoenix framework, and distributed systems", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "elixir", + "functional", + "phoenix", + "otp", + "distributed" + ] +} diff --git a/plugins/game-development/.claude-plugin/plugin.json b/plugins/game-development/.claude-plugin/plugin.json new file mode 100644 index 0000000..61e86bb --- /dev/null +++ b/plugins/game-development/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "game-development", + "version": "1.2.0", + "description": "Unity game development with C# scripting, Minecraft server plugin development with Bukkit/Spigot APIs", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "gaming", + "unity", + "minecraft", + "game-dev", + "bukkit", + "spigot" + ] +} diff --git a/plugins/git-pr-workflows/.claude-plugin/plugin.json b/plugins/git-pr-workflows/.claude-plugin/plugin.json new file mode 100644 index 0000000..1935601 --- /dev/null +++ b/plugins/git-pr-workflows/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "git-pr-workflows", + "version": "1.2.1", + "description": "Git workflow automation, pull request enhancement, and team onboarding processes", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "git", + "pull-request", + "workflow", + "onboarding", + "essential" + ] +} diff --git a/plugins/git-pr-workflows/commands/git-workflow.md b/plugins/git-pr-workflows/commands/git-workflow.md index 51fb152..c80ef11 100644 --- a/plugins/git-pr-workflows/commands/git-workflow.md +++ b/plugins/git-pr-workflows/commands/git-workflow.md @@ -1,3 +1,8 @@ +--- +description: "Run review, tests, and commit steps, then prepare a pull request" +argument-hint: "[target branch]" +--- + # Complete Git Workflow with Multi-Agent Orchestration Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern git best practices including Conventional Commits, automated testing, and structured PR creation. diff --git a/plugins/git-pr-workflows/commands/onboard.md b/plugins/git-pr-workflows/commands/onboard.md index 267428a..74ac887 100644 --- a/plugins/git-pr-workflows/commands/onboard.md +++ b/plugins/git-pr-workflows/commands/onboard.md @@ -1,3 +1,8 @@ +--- +description: "Create an onboarding plan and materials for a new team member" +argument-hint: "[role or person]" +--- + # Onboard You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. Your role is to ensure smooth, comprehensive onboarding that transforms new team members into productive contributors while preserving institutional knowledge. diff --git a/plugins/git-pr-workflows/commands/pr-enhance.md b/plugins/git-pr-workflows/commands/pr-enhance.md index 9f0ac22..0521e8c 100644 --- a/plugins/git-pr-workflows/commands/pr-enhance.md +++ b/plugins/git-pr-workflows/commands/pr-enhance.md @@ -1,3 +1,8 @@ +--- +description: "Write or improve a pull request description, checklist, and review aids" +argument-hint: "[PR or branch]" +--- + # Pull Request Enhancement You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability. diff --git a/plugins/hr-legal-compliance/.claude-plugin/plugin.json b/plugins/hr-legal-compliance/.claude-plugin/plugin.json new file mode 100644 index 0000000..fe44298 --- /dev/null +++ b/plugins/hr-legal-compliance/.claude-plugin/plugin.json @@ -0,0 +1,21 @@ +{ + "name": "hr-legal-compliance", + "version": "1.2.0", + "description": "HR policy documentation, legal compliance templates (GDPR/SOC2/HIPAA), employment contracts, and regulatory documentation", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "hr", + "legal", + "compliance", + "gdpr", + "soc2", + "hipaa", + "policies" + ] +} diff --git a/plugins/incident-response/.claude-plugin/plugin.json b/plugins/incident-response/.claude-plugin/plugin.json new file mode 100644 index 0000000..3cb5019 --- /dev/null +++ b/plugins/incident-response/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "incident-response", + "version": "1.2.1", + "description": "Production incident management, triage workflows, and automated incident resolution", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "incident-response", + "production", + "sre", + "troubleshooting" + ] +} diff --git a/plugins/incident-response/commands/incident-response.md b/plugins/incident-response/commands/incident-response.md index b61498d..647d7bb 100644 --- a/plugins/incident-response/commands/incident-response.md +++ b/plugins/incident-response/commands/incident-response.md @@ -1,3 +1,8 @@ +--- +description: "Coordinate incident response: triage, investigation, mitigation, and postmortem" +argument-hint: "[incident description]" +--- + Orchestrate multi-agent incident response with modern SRE practices for rapid resolution and learning: [Extended thinking: This workflow implements a comprehensive incident command system (ICS) following modern SRE principles. Multiple specialized agents collaborate through defined phases: detection/triage, investigation/mitigation, communication/coordination, and resolution/postmortem. The workflow emphasizes speed without sacrificing accuracy, maintains clear communication channels, and ensures every incident becomes a learning opportunity through blameless postmortems and systematic improvements.] diff --git a/plugins/incident-response/commands/smart-fix.md b/plugins/incident-response/commands/smart-fix.md index 8c6e661..5b0cb8b 100644 --- a/plugins/incident-response/commands/smart-fix.md +++ b/plugins/incident-response/commands/smart-fix.md @@ -1,3 +1,8 @@ +--- +description: "Diagnose and fix a production issue with coordinated debugging agents" +argument-hint: "[issue or error]" +--- + # Intelligent Issue Resolution with Multi-Agent Orchestration [Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and resolve production issues. The intelligent debugging strategy combines automated root cause analysis with human expertise, using modern 2025/2026 practices including AI code assistants (GitHub Copilot, Claude Code), observability platforms (Sentry, DataDog, OpenTelemetry), git bisect automation for regression tracking, and production-safe debugging techniques like distributed tracing and structured logging. The process follows a rigorous four-phase approach: (1) Issue Analysis Phase - error-detective and debugger agents analyze error traces, logs, reproduction steps, and observability data to understand the full context of the failure including upstream/downstream impacts, (2) Root Cause Investigation Phase - debugger and code-reviewer agents perform deep code analysis, automated git bisect to identify introducing commit, dependency compatibility checks, and state inspection to isolate the exact failure mechanism, (3) Fix Implementation Phase - domain-specific agents (python-pro, typescript-pro, rust-expert, etc.) implement minimal fixes with comprehensive test coverage including unit, integration, and edge case tests while following production-safe practices, (4) Verification Phase - test-automator and performance-engineer agents run regression suites, performance benchmarks, security scans, and verify no new issues are introduced. Complex issues spanning multiple systems require orchestrated coordination between specialist agents (database-optimizer → performance-engineer → devops-troubleshooter) with explicit context passing and state sharing. The workflow emphasizes understanding root causes over treating symptoms, implementing lasting architectural improvements, automating detection through enhanced monitoring and alerting, and preventing future occurrences through type system enhancements, static analysis rules, and improved error handling patterns. Success is measured not just by issue resolution but by reduced mean time to recovery (MTTR), prevention of similar issues, and improved system resilience.] diff --git a/plugins/javascript-typescript/.claude-plugin/plugin.json b/plugins/javascript-typescript/.claude-plugin/plugin.json new file mode 100644 index 0000000..4d75307 --- /dev/null +++ b/plugins/javascript-typescript/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "javascript-typescript", + "version": "1.2.1", + "description": "JavaScript and TypeScript development with ES6+, Node.js, React, and modern web frameworks", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "javascript", + "typescript", + "es6", + "nodejs", + "react" + ] +} diff --git a/plugins/javascript-typescript/commands/typescript-scaffold.md b/plugins/javascript-typescript/commands/typescript-scaffold.md index c70416c..14035ac 100644 --- a/plugins/javascript-typescript/commands/typescript-scaffold.md +++ b/plugins/javascript-typescript/commands/typescript-scaffold.md @@ -1,3 +1,8 @@ +--- +description: "Scaffold a TypeScript project with modern tooling, types, and tests" +argument-hint: "[project type and name]" +--- + # TypeScript Project Scaffolding You are a TypeScript project architecture expert specializing in scaffolding production-ready Node.js and frontend applications. Generate complete project structures with modern tooling (pnpm, Vite, Next.js), type safety, testing setup, and configuration following current best practices. diff --git a/plugins/julia-development/.claude-plugin/plugin.json b/plugins/julia-development/.claude-plugin/plugin.json new file mode 100644 index 0000000..972ca97 --- /dev/null +++ b/plugins/julia-development/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "julia-development", + "version": "1.0.0", + "description": "Modern Julia development with Julia 1.11+, package management, scientific computing, high-performance numerical code, and production best practices", + "author": { + "name": "Community Contribution", + "url": "https://github.com/exAClior" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "julia", + "scientific-computing", + "numerical", + "performance", + "data-science", + "multiple-dispatch" + ] +} diff --git a/plugins/jvm-languages/.claude-plugin/plugin.json b/plugins/jvm-languages/.claude-plugin/plugin.json new file mode 100644 index 0000000..61ed36e --- /dev/null +++ b/plugins/jvm-languages/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "jvm-languages", + "version": "1.2.0", + "description": "JVM language development including Java, Scala, and C# with enterprise patterns and frameworks", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "java", + "scala", + "csharp", + "jvm", + "enterprise", + "dotnet" + ] +} diff --git a/plugins/kubernetes-operations/.claude-plugin/plugin.json b/plugins/kubernetes-operations/.claude-plugin/plugin.json new file mode 100644 index 0000000..7f10a5d --- /dev/null +++ b/plugins/kubernetes-operations/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "kubernetes-operations", + "version": "1.2.1", + "description": "Kubernetes manifest generation, networking configuration, security policies, observability setup, GitOps workflows, and auto-scaling", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "kubernetes", + "k8s", + "containers", + "helm", + "argocd", + "gitops" + ] +} diff --git a/plugins/libreuiux-hooks/.claude-plugin/plugin.json b/plugins/libreuiux-hooks/.claude-plugin/plugin.json new file mode 100644 index 0000000..c459bc8 --- /dev/null +++ b/plugins/libreuiux-hooks/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "libreuiux-hooks", + "version": "1.0.0", + "description": "Optional hooks for UI projects: one line of stack context at session start, a confirmation prompt before editing secrets files, and accessibility and design-system hints after UI file edits.", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "hooks", + "accessibility", + "design-systems", + "ui-ux", + "wcag" + ] +} diff --git a/plugins/libreuiux-hooks/README.md b/plugins/libreuiux-hooks/README.md new file mode 100644 index 0000000..45fadde --- /dev/null +++ b/plugins/libreuiux-hooks/README.md @@ -0,0 +1,36 @@ +# libreuiux-hooks + +> Optional Claude Code hooks for UI projects: stack context at session start, a confirmation prompt before editing secrets files, and accessibility and design-system hints after UI file edits. + +This plugin packages the LibreUIUX hooks (first shipped as loose scripts in the repository's `hooks/` directory) so Claude Code registers them for you. The loose scripts need a `LIBREUIUX_HOOKS_DIR` variable and a hand-edited `settings.json`, parse the hook input with `grep`, return findings in a JSON shape Claude Code does not define (a top-level `additionalContext` array), set timeouts meant as milliseconds in a field Claude Code reads as seconds, and write log files into the hooks directory. These versions keep the same checks, read the JSON that Claude Code sends on stdin with `jq`, answer in the documented hook output format, and write no files. The original scripts stay in `hooks/` unchanged. + +## Install + +``` +/plugin marketplace add HermeticOrmus/LibreUIUX-Claude-Code +/plugin install libreuiux-hooks@libreuiux +``` + +Or from a terminal: `claude plugin install libreuiux-hooks@libreuiux`. Restart Claude Code to load the hooks. Requires `jq` on your PATH; without it every hook exits silently. + +## What each hook does + +| Event | Matcher | Script | Behavior | +|-------|---------|--------|----------| +| SessionStart | `startup\|resume\|clear\|compact` | `scripts/session-start.sh` | When the project has a front-end framework or styling library in `package.json`, a `tailwind.config.*`, or a shadcn/ui `components.json`, prints one line naming the detected stack, whether accessibility test tooling is present, and the LibreUIUX plugins that fit. Claude Code adds that line to Claude's context. Prints nothing for other projects. | +| PreToolUse | `Edit\|Write\|MultiEdit` | `scripts/pre-tool-use.sh` | If the target file looks like a secrets file (`.env`, `.env.*` except `.env.example`/`.sample`/`.template`/`.dist`, `*.pem`, `*.key`, `*.p12`, `*.pfx`, or a name containing `credentials` or `secret`), returns `permissionDecision: "ask"` so you confirm the edit. Otherwise exits 0 silently. | +| PostToolUse | `Edit\|Write\|MultiEdit` | `scripts/post-tool-use.sh` | After an edit to a UI file (`.css`, `.scss`, `.sass`, `.less`, `.tsx`, `.jsx`, `.vue`, `.svelte`, `.html`, `.astro`, or a theme/token/Tailwind config script), returns findings to Claude as `additionalContext`: design token and global-style impact, co-located style/test/story files, light text classes, images without `alt`, icon-only buttons without a name, clickable `div`/`span`, inputs without labels, very small targets, animation without a reduced-motion path, autoplay, font sizes under 12px, and large fixed widths. Silent when nothing matches. | + +The checks are pattern matches, not measurements: they point Claude at likely problems for it to verify, and they never block an edit. + +## Test a hook by hand + +```bash +echo '{"tool_name":"Write","tool_input":{"file_path":".env"}}' | bash scripts/pre-tool-use.sh +echo '{"tool_name":"Edit","tool_input":{"file_path":"src/components/ui/Button.tsx"}}' | bash scripts/post-tool-use.sh +echo "{\"cwd\":\"$PWD\"}" | bash scripts/session-start.sh +``` + +## Turn it off + +`/plugin` and disable `libreuiux-hooks`, or `claude plugin disable libreuiux-hooks@libreuiux`. diff --git a/plugins/libreuiux-hooks/hooks/hooks.json b/plugins/libreuiux-hooks/hooks/hooks.json new file mode 100644 index 0000000..5c6d2d6 --- /dev/null +++ b/plugins/libreuiux-hooks/hooks/hooks.json @@ -0,0 +1,41 @@ +{ + "description": "LibreUIUX UI/UX hooks: stack context at session start, a confirmation prompt before editing secrets files, and accessibility and design-system hints after UI file edits.", + "hooks": { + "SessionStart": [ + { + "matcher": "startup|resume|clear|compact", + "hooks": [ + { + "type": "command", + "command": "bash \"${CLAUDE_PLUGIN_ROOT}/scripts/session-start.sh\"", + "timeout": 10 + } + ] + } + ], + "PreToolUse": [ + { + "matcher": "Edit|Write|MultiEdit", + "hooks": [ + { + "type": "command", + "command": "bash \"${CLAUDE_PLUGIN_ROOT}/scripts/pre-tool-use.sh\"", + "timeout": 5 + } + ] + } + ], + "PostToolUse": [ + { + "matcher": "Edit|Write|MultiEdit", + "hooks": [ + { + "type": "command", + "command": "bash \"${CLAUDE_PLUGIN_ROOT}/scripts/post-tool-use.sh\"", + "timeout": 10 + } + ] + } + ] + } +} diff --git a/plugins/libreuiux-hooks/scripts/post-tool-use.sh b/plugins/libreuiux-hooks/scripts/post-tool-use.sh new file mode 100755 index 0000000..b5438ea --- /dev/null +++ b/plugins/libreuiux-hooks/scripts/post-tool-use.sh @@ -0,0 +1,136 @@ +#!/usr/bin/env bash +# LibreUIUX PostToolUse hook (Edit, Write, MultiEdit). +# +# Reads the hook input JSON on stdin. After Claude edits a UI file (stylesheet, +# component, HTML, or a theme/token script), it runs quick heuristic checks and, +# only when something is worth a look, returns the findings to Claude as +# additionalContext: +# - design-system files (tokens, global styles, Tailwind or shadcn/ui config) +# and co-located style, test, and story files that may need the same change +# - accessibility: light text classes, images without alt, icon-only buttons +# without a label, clickable div/span, inputs without labels, small targets, +# animation without a reduced-motion path, autoplay +# - responsive: very small font sizes, large fixed widths +# These are pattern matches, not measurements. Prints nothing when the file is +# not a UI file or nothing matched. Never writes files. + +set -euo pipefail +IFS=$'\n\t' + +command -v jq >/dev/null 2>&1 || exit 0 + +input=$(cat) +path=$(jq -r '.tool_input.file_path // .tool_input.path // empty' 2>/dev/null <<<"$input" || true) +[ -n "$path" ] && [ -f "$path" ] || exit 0 + +base=$(basename -- "$path") +dir=$(dirname -- "$path") +ext=$(tr '[:upper:]' '[:lower:]' <<<"${base##*.}") +lower=$(tr '[:upper:]' '[:lower:]' <<<"$base") + +case "$ext" in + css|scss|sass|less|tsx|jsx|vue|svelte|html|htm|astro) ;; + ts|js|mjs|cjs|json) + grep -qE 'style|theme|color|token|tailwind\.config|^components\.json$' <<<"$lower" || exit 0 ;; + *) exit 0 ;; +esac + +notes=() +note() { notes+=("$1"); } + +# --- Design-system impact ---------------------------------------------------- +if grep -qE '^(tokens|theme|colors|spacing|typography|design-tokens|variables)([.-]|$)' <<<"$lower"; then + note "Design token file: this change reaches every component that uses these tokens." +fi +if grep -qE '^(global|globals|base|reset|normalize|root|app|index)\.(css|scss|sass|less)$' <<<"$lower"; then + note "Global stylesheet: this change applies to every page." +fi +if grep -qE '^tailwind\.config\.(js|ts|mjs|cjs)$' <<<"$lower"; then + note "Tailwind config changed: check that the dev server picked it up, and that renamed theme keys are not still used in class names." +fi +if [ "$lower" = "components.json" ]; then + note "shadcn/ui config changed: it controls where and how new components are generated." +fi +if grep -qiE '(components/(ui|common|shared)|lib/components|packages/ui)(/|$)' <<<"$dir"; then + note "Shared component: other screens import this, so review their usage." +fi + +stem="${base%.*}" +stem="${stem%.module}" +related=() +for cand in "$stem.css" "$stem.scss" "$stem.module.css" "$stem.module.scss" "$stem.styles.ts" \ + "$stem.test.tsx" "$stem.test.jsx" "$stem.test.ts" "$stem.test.js" "$stem.spec.tsx" "$stem.spec.ts" \ + "$stem.stories.tsx" "$stem.stories.jsx" "$stem.stories.ts" "$stem.stories.js" \ + "$stem.tsx" "$stem.jsx" "$stem.vue" "$stem.svelte"; do + [ "$cand" = "$base" ] && continue + [ -f "$dir/$cand" ] && related+=("$cand") +done +if [ ${#related[@]} -gt 0 ]; then + list=$(printf '%s, ' "${related[@]}") + note "Related files that may need the same change: ${list%, }." +fi + +# --- Content checks (heuristics) --------------------------------------------- +content=$(head -c 400000 -- "$path" 2>/dev/null || true) +flat=$(tr '\n' ' ' <<<"$content") + +if grep -qE 'text-(gray|slate|zinc|neutral|stone)-(100|200|300)\b' <<<"$content"; then + note "Light text classes (for example text-gray-300): on a light background these usually fall below the 4.5:1 WCAG AA contrast for body text." +fi +if grep -qE 'text-(yellow|amber|lime)-(100|200|300|400)\b' <<<"$content"; then + note "Yellow, amber, or lime text: these rarely reach 4.5:1 on white; check the contrast." +fi + +imgs_without_alt=$({ grep -oiE '<img\b[^>]*>' <<<"$flat" || true; } | { grep -viE '\balt=' || true; } | wc -l | tr -d ' ') +if [ "$imgs_without_alt" -gt 0 ]; then + note "$imgs_without_alt <img> tag(s) without an alt attribute (use alt=\"\" for decorative images)." +fi + +if grep -qiE '<button\b[^>]*>[[:space:]]*<(svg|i|[A-Z][A-Za-z]*Icon)\b' <<<"$flat"; then + if ! grep -qiE 'aria-label|aria-labelledby|sr-only|visually-hidden' <<<"$content"; then + note "Icon-only button without an accessible name: add aria-label or visually hidden text." + fi +fi + +if grep -qE '<(div|span)\b[^>]*on[Cc]lick' <<<"$content"; then + if ! grep -qE 'role="button"' <<<"$content"; then + note "Clickable div or span: use a <button>, or add role=\"button\", tabindex=\"0\", and Enter/Space key handling." + fi +fi + +if grep -qiE '<input\b' <<<"$content"; then + if ! grep -qiE '<label\b|aria-label|aria-labelledby' <<<"$content"; then + note "Inputs without a <label> or aria-label: placeholders are not labels." + fi +fi + +if grep -qE '<(button|a)\b[^>]*class(Name)?="[^"]*\b(h|w|size)-(3|4|5)\b' <<<"$content"; then + note "Very small interactive element (16 to 20px): WCAG 2.2 target size (2.5.8, AA) asks for at least 24x24 CSS px; 44x44 is the AAA level." +fi + +if grep -qE '@keyframes|animation:|transition:|\banimate-|framer-motion|from "motion|<motion\.' <<<"$content"; then + if ! grep -qE 'prefers-reduced-motion|motion-reduce:|motion-safe:|useReducedMotion' <<<"$content"; then + note "Animation without a reduced-motion path: add a prefers-reduced-motion query (Tailwind: motion-safe: or motion-reduce:)." + fi +fi + +if grep -qiE '\bautoplay\b|autoPlay' <<<"$content"; then + note "Autoplaying media: give users a way to pause or stop it (WCAG 2.2.2)." +fi + +if grep -qE 'font-size:[[:space:]]*([0-9]|1[01])px|text-\[(1[01]|[0-9])px\]' <<<"$content"; then + note "Font sizes under 12px: hard to read on phones; body text is usually 16px." +fi + +if grep -qE '(^|[^-])width:[[:space:]]*([5-9][0-9]{2}|[1-9][0-9]{3})px' <<<"$content"; then + note "Large fixed pixel width: prefer max-width with a fluid width so it fits small screens." +fi + +[ ${#notes[@]} -gt 0 ] || exit 0 + +ctx="LibreUIUX checks for $base (pattern matches, verify before changing):" +for n in "${notes[@]}"; do ctx="$ctx +- $n"; done + +jq -n --arg ctx "$ctx" '{hookSpecificOutput: {hookEventName: "PostToolUse", additionalContext: $ctx}}' +exit 0 diff --git a/plugins/libreuiux-hooks/scripts/pre-tool-use.sh b/plugins/libreuiux-hooks/scripts/pre-tool-use.sh new file mode 100755 index 0000000..3a4d8f8 --- /dev/null +++ b/plugins/libreuiux-hooks/scripts/pre-tool-use.sh @@ -0,0 +1,33 @@ +#!/usr/bin/env bash +# LibreUIUX PreToolUse hook (Edit, Write, MultiEdit). +# +# Reads the hook input JSON on stdin. When the target file looks like a secrets +# file (.env, a .pem or .key file, or a name containing "credentials" or +# "secret"), it asks the user to confirm the edit. For every other file it exits +# 0 silently and the normal permission flow applies. Never writes files. + +set -euo pipefail +IFS=$'\n\t' + +command -v jq >/dev/null 2>&1 || exit 0 + +input=$(cat) +path=$(jq -r '.tool_input.file_path // .tool_input.path // empty' 2>/dev/null <<<"$input" || true) +[ -n "$path" ] || exit 0 + +base=$(basename -- "$path") +lower=$(tr '[:upper:]' '[:lower:]' <<<"$base") + +sensitive=0 +case "$lower" in + .env.example|.env.sample|.env.template|.env.dist) sensitive=0 ;; + .env|.env.*|*.env) sensitive=1 ;; + *.pem|*.key|*.p12|*.pfx) sensitive=1 ;; + *credentials*|*secret*) sensitive=1 ;; +esac + +[ "$sensitive" -eq 1 ] || exit 0 + +jq -n --arg reason "LibreUIUX: $base looks like a secrets file (.env, key, certificate, or credentials). Confirm before Claude changes it." \ + '{hookSpecificOutput: {hookEventName: "PreToolUse", permissionDecision: "ask", permissionDecisionReason: $reason}}' +exit 0 diff --git a/plugins/libreuiux-hooks/scripts/session-start.sh b/plugins/libreuiux-hooks/scripts/session-start.sh new file mode 100755 index 0000000..748767c --- /dev/null +++ b/plugins/libreuiux-hooks/scripts/session-start.sh @@ -0,0 +1,67 @@ +#!/usr/bin/env bash +# LibreUIUX SessionStart hook. +# +# Claude Code sends the hook input as JSON on stdin; plain stdout from a +# SessionStart hook is added to Claude's context. When the project looks like a +# UI project (a front-end framework or styling library in package.json, a +# Tailwind config, or a shadcn/ui components.json), print one line describing +# the stack and the LibreUIUX plugins that fit it. Print nothing otherwise. +# Never writes files. + +set -euo pipefail +IFS=$'\n\t' + +command -v jq >/dev/null 2>&1 || exit 0 + +input=$(cat) +dir=$(jq -r '.cwd // empty' 2>/dev/null <<<"$input" || true) +[ -n "$dir" ] && [ -d "$dir" ] || dir=$PWD + +deps="" +if [ -f "$dir/package.json" ]; then + deps=$(jq -r '[(.dependencies // {}), (.devDependencies // {}), (.peerDependencies // {})] | add | keys[]' "$dir/package.json" 2>/dev/null || true) +fi +has() { grep -qx -- "$1" <<<"$deps"; } +has_prefix() { grep -q -- "^$1" <<<"$deps"; } + +framework="" +if has next; then framework="Next.js" +elif has gatsby; then framework="Gatsby" +elif has_prefix "@remix-run/"; then framework="Remix" +elif has react; then framework="React" +elif has nuxt; then framework="Nuxt" +elif has vue; then framework="Vue" +elif has "@sveltejs/kit"; then framework="SvelteKit" +elif has svelte; then framework="Svelte" +elif has "@angular/core"; then framework="Angular" +elif has solid-js; then framework="Solid" +fi + +stack=() +[ -n "$framework" ] && stack+=("$framework") +if has tailwindcss || compgen -G "$dir/tailwind.config.*" >/dev/null; then stack+=("Tailwind CSS"); fi +has styled-components && stack+=("styled-components") +has "@emotion/react" && stack+=("Emotion") +has_prefix "@vanilla-extract/" && stack+=("vanilla-extract") +[ -f "$dir/components.json" ] && stack+=("shadcn/ui") +has_prefix "@radix-ui/" && stack+=("Radix UI") +has "@headlessui/react" && stack+=("Headless UI") +has "@chakra-ui/react" && stack+=("Chakra UI") +has_prefix "@mantine/" && stack+=("Mantine") +has antd && stack+=("Ant Design") +has "@mui/material" && stack+=("MUI") +{ has framer-motion || has motion; } && stack+=("Motion") + +[ ${#stack[@]} -gt 0 ] || exit 0 + +a11y="no accessibility test tooling found (axe-core, jest-axe, pa11y, eslint-plugin-jsx-a11y)" +if has_prefix "@axe-core/" || has axe-core || has jest-axe || has pa11y || has cypress-axe || has eslint-plugin-jsx-a11y || has eslint-plugin-vuejs-accessibility; then + a11y="accessibility tooling present" +fi + +plugins="design-mastery, accessibility-compliance" +[ -n "$framework" ] && plugins="$plugins, frontend-mobile-development" + +joined=$(printf '%s, ' "${stack[@]}") +echo "LibreUIUX: ${joined%, } detected; ${a11y}. Relevant LibreUIUX plugins: ${plugins}." +exit 0 diff --git a/plugins/llm-application-dev/.claude-plugin/plugin.json b/plugins/llm-application-dev/.claude-plugin/plugin.json new file mode 100644 index 0000000..85fa372 --- /dev/null +++ b/plugins/llm-application-dev/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "llm-application-dev", + "version": "1.2.1", + "description": "LLM application development, prompt engineering, and AI assistant optimization", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "llm", + "ai", + "prompt-engineering", + "langchain", + "gpt", + "claude" + ] +} diff --git a/plugins/llm-application-dev/commands/ai-assistant.md b/plugins/llm-application-dev/commands/ai-assistant.md index 60bdf7f..b4b1454 100644 --- a/plugins/llm-application-dev/commands/ai-assistant.md +++ b/plugins/llm-application-dev/commands/ai-assistant.md @@ -1,3 +1,8 @@ +--- +description: "Design and build an AI assistant or chatbot" +argument-hint: "[assistant purpose]" +--- + # AI Assistant Development You are an AI assistant development expert specializing in creating intelligent conversational interfaces, chatbots, and AI-powered applications. Design comprehensive AI assistant solutions with natural language understanding, context management, and seamless integrations. diff --git a/plugins/llm-application-dev/commands/langchain-agent.md b/plugins/llm-application-dev/commands/langchain-agent.md index 3471a87..ec4c541 100644 --- a/plugins/llm-application-dev/commands/langchain-agent.md +++ b/plugins/llm-application-dev/commands/langchain-agent.md @@ -1,3 +1,8 @@ +--- +description: "Build a LangChain or LangGraph agent system" +argument-hint: "[agent purpose]" +--- + # LangChain/LangGraph Agent Development Expert You are an expert LangChain agent developer specializing in production-grade AI systems using LangChain 0.1+ and LangGraph. diff --git a/plugins/llm-application-dev/commands/prompt-optimize.md b/plugins/llm-application-dev/commands/prompt-optimize.md index 0afc30b..f565d5b 100644 --- a/plugins/llm-application-dev/commands/prompt-optimize.md +++ b/plugins/llm-application-dev/commands/prompt-optimize.md @@ -1,3 +1,8 @@ +--- +description: "Turn a basic instruction into an optimized, production-ready prompt" +argument-hint: "[prompt or task]" +--- + # Prompt Optimization You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimization. diff --git a/plugins/llm-application-dev/skills/prompt-engineering-ui/SKILL.md b/plugins/llm-application-dev/skills/prompt-engineering-ui/SKILL.md index f6517c6..cfc3d86 100644 --- a/plugins/llm-application-dev/skills/prompt-engineering-ui/SKILL.md +++ b/plugins/llm-application-dev/skills/prompt-engineering-ui/SKILL.md @@ -1,6 +1,6 @@ --- name: prompt-engineering-ui -description: Prompt patterns for consistent UI generation. Covers precise design intent communication, component specification formats, and iterative refinement patterns for LLM-driven UI development. +description: "Prompt patterns for consistent UI generation: stating design intent precisely, component specification formats, few-shot examples, and structured refinement loops. Use when UI output from an LLM is inconsistent or generic, or when building reusable prompt templates for a design system." --- # Prompt Engineering for UI Generation diff --git a/plugins/machine-learning-ops/.claude-plugin/plugin.json b/plugins/machine-learning-ops/.claude-plugin/plugin.json new file mode 100644 index 0000000..334f77f --- /dev/null +++ b/plugins/machine-learning-ops/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "machine-learning-ops", + "version": "1.2.1", + "description": "ML model training pipelines, hyperparameter tuning, model deployment automation, experiment tracking, and MLOps workflows", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "machine-learning", + "mlops", + "model-training", + "tensorflow", + "pytorch", + "mlflow" + ] +} diff --git a/plugins/machine-learning-ops/commands/ml-pipeline.md b/plugins/machine-learning-ops/commands/ml-pipeline.md index 616af62..eab6760 100644 --- a/plugins/machine-learning-ops/commands/ml-pipeline.md +++ b/plugins/machine-learning-ops/commands/ml-pipeline.md @@ -1,3 +1,8 @@ +--- +description: "Design and implement an ML pipeline from data to deployment and monitoring" +argument-hint: "[ML problem or model]" +--- + # Machine Learning Pipeline - Multi-Agent MLOps Orchestration Design and implement a complete ML pipeline for: $ARGUMENTS diff --git a/plugins/mcp-integrations/.claude-plugin/plugin.json b/plugins/mcp-integrations/.claude-plugin/plugin.json new file mode 100644 index 0000000..06a5054 --- /dev/null +++ b/plugins/mcp-integrations/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "mcp-integrations", + "version": "1.0.0", + "description": "Browser DevTools through MCP for live UI inspection, screenshot-to-code, design token extraction, and visual debugging of running interfaces.", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "mcp", + "chrome-devtools", + "browser-automation", + "screenshot-to-code", + "visual-debugging", + "design-tokens" + ] +} diff --git a/plugins/mcp-integrations/skills/browser-devtools-mcp/SKILL.md b/plugins/mcp-integrations/skills/browser-devtools-mcp/SKILL.md index b2f57d8..e678c95 100644 --- a/plugins/mcp-integrations/skills/browser-devtools-mcp/SKILL.md +++ b/plugins/mcp-integrations/skills/browser-devtools-mcp/SKILL.md @@ -1,6 +1,6 @@ --- name: browser-devtools-mcp -description: Integrating Chrome DevTools and browser automation via MCP for live UI inspection, screenshot-to-code workflows, and visual debugging. Bridges the gap between design and implementation. +description: "Chrome DevTools and browser automation through MCP for live UI work: screenshots, DOM and computed-style inspection, screenshot-to-code, design token extraction, Lighthouse and accessibility audits, and visual regression checks. Use when Claude should look at a running interface instead of guessing from code." --- # Browser DevTools MCP Integration diff --git a/plugins/multi-platform-apps/.claude-plugin/plugin.json b/plugins/multi-platform-apps/.claude-plugin/plugin.json new file mode 100644 index 0000000..bb2d5e2 --- /dev/null +++ b/plugins/multi-platform-apps/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "multi-platform-apps", + "version": "1.2.1", + "description": "Cross-platform application development coordinating web, iOS, Android, and desktop implementations", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "cross-platform", + "mobile", + "web", + "desktop", + "react-native", + "flutter" + ] +} diff --git a/plugins/multi-platform-apps/commands/multi-platform.md b/plugins/multi-platform-apps/commands/multi-platform.md index 6d209f0..6503aee 100644 --- a/plugins/multi-platform-apps/commands/multi-platform.md +++ b/plugins/multi-platform-apps/commands/multi-platform.md @@ -1,3 +1,8 @@ +--- +description: "Build one feature consistently across web, mobile, and desktop" +argument-hint: "[feature description]" +--- + # Multi-Platform Feature Development Workflow Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies. diff --git a/plugins/observability-monitoring/.claude-plugin/plugin.json b/plugins/observability-monitoring/.claude-plugin/plugin.json new file mode 100644 index 0000000..ee70f18 --- /dev/null +++ b/plugins/observability-monitoring/.claude-plugin/plugin.json @@ -0,0 +1,22 @@ +{ + "name": "observability-monitoring", + "version": "1.2.1", + "description": "Metrics collection, logging infrastructure, distributed tracing, SLO implementation, and monitoring dashboards", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "observability", + "monitoring", + "metrics", + "logging", + "tracing", + "slo", + "prometheus", + "grafana" + ] +} diff --git a/plugins/observability-monitoring/commands/monitor-setup.md b/plugins/observability-monitoring/commands/monitor-setup.md index dc04934..fbf3aae 100644 --- a/plugins/observability-monitoring/commands/monitor-setup.md +++ b/plugins/observability-monitoring/commands/monitor-setup.md @@ -1,3 +1,8 @@ +--- +description: "Set up metrics, logs, traces, and dashboards for a system" +argument-hint: "[service or system]" +--- + # Monitoring and Observability Setup You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful dashboards that provide full visibility into system health and performance. diff --git a/plugins/observability-monitoring/commands/slo-implement.md b/plugins/observability-monitoring/commands/slo-implement.md index cf1b1c9..82a146d 100644 --- a/plugins/observability-monitoring/commands/slo-implement.md +++ b/plugins/observability-monitoring/commands/slo-implement.md @@ -1,3 +1,8 @@ +--- +description: "Define SLIs, SLOs, and error budgets for a service" +argument-hint: "[service]" +--- + # SLO Implementation Guide You are an SLO (Service Level Objective) expert specializing in implementing reliability standards and error budget-based engineering practices. Design comprehensive SLO frameworks, establish meaningful SLIs, and create monitoring systems that balance reliability with feature velocity. diff --git a/plugins/payment-processing/.claude-plugin/plugin.json b/plugins/payment-processing/.claude-plugin/plugin.json new file mode 100644 index 0000000..d404844 --- /dev/null +++ b/plugins/payment-processing/.claude-plugin/plugin.json @@ -0,0 +1,21 @@ +{ + "name": "payment-processing", + "version": "1.2.1", + "description": "Payment gateway integration with Stripe, PayPal, checkout flow implementation, subscription billing, and PCI compliance", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "payments", + "stripe", + "paypal", + "checkout", + "billing", + "subscriptions", + "pci" + ] +} diff --git a/plugins/performance-testing-review/.claude-plugin/plugin.json b/plugins/performance-testing-review/.claude-plugin/plugin.json new file mode 100644 index 0000000..2c2fec4 --- /dev/null +++ b/plugins/performance-testing-review/.claude-plugin/plugin.json @@ -0,0 +1,17 @@ +{ + "name": "performance-testing-review", + "version": "1.2.0", + "description": "Performance analysis, test coverage review, and AI-powered code quality assessment", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "performance-review", + "test-coverage", + "quality-analysis" + ] +} diff --git a/plugins/performance-testing-review/commands/ai-review.md b/plugins/performance-testing-review/commands/ai-review.md index 26c9657..9404e64 100644 --- a/plugins/performance-testing-review/commands/ai-review.md +++ b/plugins/performance-testing-review/commands/ai-review.md @@ -1,3 +1,8 @@ +--- +description: "Run an AI-assisted code review combining static analysis with review feedback" +argument-hint: "[PR, diff, or path]" +--- + # AI-Powered Code Review Specialist You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, Claude 4.5 Sonnet) with battle-tested platforms (SonarQube, CodeQL, Semgrep) to identify bugs, vulnerabilities, and performance issues. diff --git a/plugins/performance-testing-review/commands/multi-agent-review.md b/plugins/performance-testing-review/commands/multi-agent-review.md index 8b37727..84cde79 100644 --- a/plugins/performance-testing-review/commands/multi-agent-review.md +++ b/plugins/performance-testing-review/commands/multi-agent-review.md @@ -1,3 +1,8 @@ +--- +description: "Review code with several specialized agents and merge their findings" +argument-hint: "[path or PR]" +--- + # Multi-Agent Code Review Orchestration Tool ## Role: Expert Multi-Agent Review Orchestration Specialist diff --git a/plugins/python-development/.claude-plugin/plugin.json b/plugins/python-development/.claude-plugin/plugin.json new file mode 100644 index 0000000..df03f7f --- /dev/null +++ b/plugins/python-development/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "python-development", + "version": "1.2.1", + "description": "Modern Python development with Python 3.13+, Django, FastAPI, async patterns, and production best practices", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "python", + "django", + "fastapi", + "async", + "backend" + ] +} diff --git a/plugins/python-development/commands/python-scaffold.md b/plugins/python-development/commands/python-scaffold.md index 9ed45e0..5d9b4a1 100644 --- a/plugins/python-development/commands/python-scaffold.md +++ b/plugins/python-development/commands/python-scaffold.md @@ -1,3 +1,8 @@ +--- +description: "Scaffold a Python project with modern tooling, type hints, and tests" +argument-hint: "[project type and name]" +--- + # Python Project Scaffolding You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with modern tooling (uv, FastAPI, Django), type hints, testing setup, and configuration following current best practices. diff --git a/plugins/quantitative-trading/.claude-plugin/plugin.json b/plugins/quantitative-trading/.claude-plugin/plugin.json new file mode 100644 index 0000000..2fbea92 --- /dev/null +++ b/plugins/quantitative-trading/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "quantitative-trading", + "version": "1.2.0", + "description": "Quantitative analysis, algorithmic trading strategies, financial modeling, portfolio risk management, and backtesting", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "fintech", + "quant", + "trading", + "algorithmic-trading", + "risk-management" + ] +} diff --git a/plugins/security-compliance/.claude-plugin/plugin.json b/plugins/security-compliance/.claude-plugin/plugin.json new file mode 100644 index 0000000..74ea130 --- /dev/null +++ b/plugins/security-compliance/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "security-compliance", + "version": "1.2.0", + "description": "SOC2, HIPAA, and GDPR compliance validation, secrets scanning, compliance checklists, and regulatory documentation", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "compliance", + "soc2", + "hipaa", + "gdpr", + "secrets", + "regulatory" + ] +} diff --git a/plugins/security-compliance/commands/compliance-check.md b/plugins/security-compliance/commands/compliance-check.md index 53dbd61..416d090 100644 --- a/plugins/security-compliance/commands/compliance-check.md +++ b/plugins/security-compliance/commands/compliance-check.md @@ -1,3 +1,8 @@ +--- +description: "Check an application against GDPR, HIPAA, SOC 2, or PCI-DSS requirements" +argument-hint: "[application or regulation]" +--- + # Regulatory Compliance Check You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform comprehensive compliance audits and provide implementation guidance for achieving and maintaining compliance. diff --git a/plugins/security-scanning/.claude-plugin/plugin.json b/plugins/security-scanning/.claude-plugin/plugin.json new file mode 100644 index 0000000..014a05a --- /dev/null +++ b/plugins/security-scanning/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "security-scanning", + "version": "1.2.2", + "description": "SAST analysis, dependency vulnerability scanning, OWASP Top 10 compliance, container security scanning, and automated security hardening", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "security", + "sast", + "vulnerability-scanning", + "owasp", + "devsecops" + ] +} diff --git a/plugins/security-scanning/commands/security-dependencies.md b/plugins/security-scanning/commands/security-dependencies.md index c65d6ae..4bd5d91 100644 --- a/plugins/security-scanning/commands/security-dependencies.md +++ b/plugins/security-scanning/commands/security-dependencies.md @@ -1,3 +1,8 @@ +--- +description: "Scan dependencies for vulnerabilities, generate an SBOM, and plan fixes" +argument-hint: "[project path]" +--- + # Dependency Vulnerability Scanning You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across multiple ecosystems to identify vulnerabilities, assess risks, and provide automated remediation strategies. diff --git a/plugins/security-scanning/commands/security-hardening.md b/plugins/security-scanning/commands/security-hardening.md index 41db894..a59391a 100644 --- a/plugins/security-scanning/commands/security-hardening.md +++ b/plugins/security-scanning/commands/security-hardening.md @@ -1,3 +1,8 @@ +--- +description: "Harden an application in layers with coordinated security agents" +argument-hint: "[application or scope]" +--- + Implement comprehensive security hardening with defense-in-depth strategy through coordinated multi-agent orchestration: [Extended thinking: This workflow implements a defense-in-depth security strategy across all application layers. It coordinates specialized security agents to perform comprehensive assessments, implement layered security controls, and establish continuous security monitoring. The approach follows modern DevSecOps principles with shift-left security, automated scanning, and compliance validation. Each phase builds upon previous findings to create a resilient security posture that addresses both current vulnerabilities and future threats.] diff --git a/plugins/seo-analysis-monitoring/.claude-plugin/plugin.json b/plugins/seo-analysis-monitoring/.claude-plugin/plugin.json new file mode 100644 index 0000000..b409c58 --- /dev/null +++ b/plugins/seo-analysis-monitoring/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "seo-analysis-monitoring", + "version": "1.2.0", + "description": "Content freshness analysis, cannibalization detection, and authority building for SEO", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "seo", + "content-analysis", + "e-e-a-t", + "authority", + "monitoring" + ] +} diff --git a/plugins/seo-content-creation/.claude-plugin/plugin.json b/plugins/seo-content-creation/.claude-plugin/plugin.json new file mode 100644 index 0000000..1979aeb --- /dev/null +++ b/plugins/seo-content-creation/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "seo-content-creation", + "version": "1.2.0", + "description": "SEO content writing, planning, and quality auditing with E-E-A-T optimization", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "seo", + "content-writing", + "content-planning", + "content-audit" + ] +} diff --git a/plugins/seo-technical-optimization/.claude-plugin/plugin.json b/plugins/seo-technical-optimization/.claude-plugin/plugin.json new file mode 100644 index 0000000..d6644e7 --- /dev/null +++ b/plugins/seo-technical-optimization/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "seo-technical-optimization", + "version": "1.2.0", + "description": "Technical SEO optimization including meta tags, keywords, structure, and featured snippets", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "seo", + "meta-optimization", + "keywords", + "schema-markup", + "snippets" + ] +} diff --git a/plugins/shell-scripting/.claude-plugin/plugin.json b/plugins/shell-scripting/.claude-plugin/plugin.json new file mode 100644 index 0000000..02e4c7d --- /dev/null +++ b/plugins/shell-scripting/.claude-plugin/plugin.json @@ -0,0 +1,21 @@ +{ + "name": "shell-scripting", + "version": "1.2.1", + "description": "Production-grade Bash scripting with defensive programming, POSIX compliance, and comprehensive testing", + "author": { + "name": "Ryan Snodgrass", + "url": "https://github.com/rsnodgrass" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "bash", + "shell", + "scripting", + "automation", + "posix", + "shellcheck", + "testing" + ] +} diff --git a/plugins/systems-programming/.claude-plugin/plugin.json b/plugins/systems-programming/.claude-plugin/plugin.json new file mode 100644 index 0000000..2f27390 --- /dev/null +++ b/plugins/systems-programming/.claude-plugin/plugin.json @@ -0,0 +1,20 @@ +{ + "name": "systems-programming", + "version": "1.2.0", + "description": "Systems programming with Rust, Go, C, and C++ for performance-critical and low-level development", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "rust", + "golang", + "c", + "cpp", + "systems-programming", + "performance" + ] +} diff --git a/plugins/systems-programming/commands/rust-project.md b/plugins/systems-programming/commands/rust-project.md index 5806385..bbae25a 100644 --- a/plugins/systems-programming/commands/rust-project.md +++ b/plugins/systems-programming/commands/rust-project.md @@ -1,3 +1,8 @@ +--- +description: "Scaffold a Rust project with cargo tooling, modules, and tests" +argument-hint: "[project type and name]" +--- + # Rust Project Scaffolding You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing setup, and configuration following Rust best practices. diff --git a/plugins/tdd-workflows/.claude-plugin/plugin.json b/plugins/tdd-workflows/.claude-plugin/plugin.json new file mode 100644 index 0000000..643df02 --- /dev/null +++ b/plugins/tdd-workflows/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "tdd-workflows", + "version": "1.2.1", + "description": "Test-driven development methodology with red-green-refactor cycles and code review", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "tdd", + "test-driven", + "workflow", + "red-green-refactor" + ] +} diff --git a/plugins/tdd-workflows/commands/tdd-cycle.md b/plugins/tdd-workflows/commands/tdd-cycle.md index bdb93da..5ce0382 100644 --- a/plugins/tdd-workflows/commands/tdd-cycle.md +++ b/plugins/tdd-workflows/commands/tdd-cycle.md @@ -1,3 +1,8 @@ +--- +description: "Run a full red, green, refactor TDD cycle for a feature" +argument-hint: "[feature or requirement]" +--- + Execute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline: [Extended thinking: This workflow enforces test-first development through coordinated agent orchestration. Each phase of the TDD cycle is strictly enforced with fail-first verification, incremental implementation, and continuous refactoring. The workflow supports both single test and test suite approaches with configurable coverage thresholds.] diff --git a/plugins/tdd-workflows/commands/tdd-green.md b/plugins/tdd-workflows/commands/tdd-green.md index 8d27153..67803c6 100644 --- a/plugins/tdd-workflows/commands/tdd-green.md +++ b/plugins/tdd-workflows/commands/tdd-green.md @@ -1,3 +1,8 @@ +--- +description: "Write the minimal code that makes the failing tests pass" +argument-hint: "[failing tests or feature]" +--- + Implement minimal code to make failing tests pass in TDD green phase: [Extended thinking: This tool uses the test-automator agent to implement the minimal code necessary to make tests pass. It focuses on simplicity, avoiding over-engineering while ensuring all tests become green.] diff --git a/plugins/tdd-workflows/commands/tdd-red.md b/plugins/tdd-workflows/commands/tdd-red.md index b72ecd1..cf63aff 100644 --- a/plugins/tdd-workflows/commands/tdd-red.md +++ b/plugins/tdd-workflows/commands/tdd-red.md @@ -1,3 +1,8 @@ +--- +description: "Write failing tests that define the expected behavior" +argument-hint: "[feature or requirement]" +--- + Write comprehensive failing tests following TDD red phase principles. [Extended thinking: Generates failing tests that properly define expected behavior using test-automator agent.] diff --git a/plugins/tdd-workflows/commands/tdd-refactor.md b/plugins/tdd-workflows/commands/tdd-refactor.md index 1f23c59..e970e50 100644 --- a/plugins/tdd-workflows/commands/tdd-refactor.md +++ b/plugins/tdd-workflows/commands/tdd-refactor.md @@ -1,3 +1,8 @@ +--- +description: "Refactor code while keeping every test green" +argument-hint: "[code or module]" +--- + Refactor code with confidence using comprehensive test safety net: [Extended thinking: This tool uses the tdd-orchestrator agent (opus model) for sophisticated refactoring while maintaining all tests green. It applies design patterns, improves code quality, and optimizes performance with the safety of comprehensive test coverage.] diff --git a/plugins/team-collaboration/.claude-plugin/plugin.json b/plugins/team-collaboration/.claude-plugin/plugin.json new file mode 100644 index 0000000..f1294dc --- /dev/null +++ b/plugins/team-collaboration/.claude-plugin/plugin.json @@ -0,0 +1,18 @@ +{ + "name": "team-collaboration", + "version": "1.2.0", + "description": "Team workflows, issue management, standup automation, and developer experience optimization", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "collaboration", + "team", + "standup", + "issue-management" + ] +} diff --git a/plugins/team-collaboration/commands/issue.md b/plugins/team-collaboration/commands/issue.md index 34a3380..0700e81 100644 --- a/plugins/team-collaboration/commands/issue.md +++ b/plugins/team-collaboration/commands/issue.md @@ -1,3 +1,8 @@ +--- +description: "Investigate and resolve a GitHub issue through to a tested pull request" +argument-hint: "[issue number or URL]" +--- + # GitHub Issue Resolution Expert You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause analysis, test-driven development, and pull request management. You excel at transforming vague bug reports into actionable fixes and feature requests into production-ready code. diff --git a/plugins/team-collaboration/commands/standup-notes.md b/plugins/team-collaboration/commands/standup-notes.md index e9ac1c8..aa1f7ff 100644 --- a/plugins/team-collaboration/commands/standup-notes.md +++ b/plugins/team-collaboration/commands/standup-notes.md @@ -1,3 +1,8 @@ +--- +description: "Generate standup notes from recent commits, issues, and work in progress" +argument-hint: "[scope or team member]" +--- + # Standup Notes Generator You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns. diff --git a/plugins/unit-testing/.claude-plugin/plugin.json b/plugins/unit-testing/.claude-plugin/plugin.json new file mode 100644 index 0000000..29c9ea0 --- /dev/null +++ b/plugins/unit-testing/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "unit-testing", + "version": "1.2.0", + "description": "Unit and integration test automation for Python and JavaScript with debugging support", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "testing", + "unit-tests", + "python", + "javascript", + "automation" + ] +} diff --git a/plugins/unit-testing/commands/test-generate.md b/plugins/unit-testing/commands/test-generate.md index 3e70848..22f2d03 100644 --- a/plugins/unit-testing/commands/test-generate.md +++ b/plugins/unit-testing/commands/test-generate.md @@ -1,3 +1,8 @@ +--- +description: "Generate unit tests that cover edge cases for the given code" +argument-hint: "[file, function, or module]" +--- + # Automated Unit Test Generation You are a test automation expert specializing in generating comprehensive, maintainable unit tests across multiple languages and frameworks. Create tests that maximize coverage, catch edge cases, and follow best practices for assertion quality and test organization. diff --git a/plugins/vibe-coding/.claude-plugin/plugin.json b/plugins/vibe-coding/.claude-plugin/plugin.json new file mode 100644 index 0000000..618e1da --- /dev/null +++ b/plugins/vibe-coding/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "vibe-coding", + "version": "1.0.0", + "description": "Rapid, disposable UI prototyping: when to explore fast and when to refine, variant exploration, and how to carry a validated prototype toward production.", + "author": { + "name": "Diego Bodart", + "url": "https://github.com/HermeticOrmus" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "prototyping", + "vibe-coding", + "ui-exploration", + "rapid-iteration", + "ai-assisted-development" + ] +} diff --git a/plugins/vibe-coding/skills/rapid-prototyping/SKILL.md b/plugins/vibe-coding/skills/rapid-prototyping/SKILL.md index 530aeb0..22bd69e 100644 --- a/plugins/vibe-coding/skills/rapid-prototyping/SKILL.md +++ b/plugins/vibe-coding/skills/rapid-prototyping/SKILL.md @@ -1,6 +1,6 @@ --- name: rapid-prototyping -description: Embrace vibe coding for rapid UI exploration. Covers when to iterate vs refine, ephemeral app patterns, and the art of fast, disposable prototyping with AI-assisted development. +description: "Fast, disposable UI prototyping with AI: when to stay in vibe mode and when to switch to craft mode, throwaway prototype protocols, variant explosion, prompt patterns for quick iteration, and how to carry a validated prototype toward production. Use when exploring UI ideas, building throwaway demos for feedback, or deciding whether a prototype is ready to harden." --- # Rapid Prototyping with Vibe Coding diff --git a/plugins/web-scripting/.claude-plugin/plugin.json b/plugins/web-scripting/.claude-plugin/plugin.json new file mode 100644 index 0000000..923ffa8 --- /dev/null +++ b/plugins/web-scripting/.claude-plugin/plugin.json @@ -0,0 +1,19 @@ +{ + "name": "web-scripting", + "version": "1.2.0", + "description": "Web scripting with PHP and Ruby for web applications, CMS development, and backend services", + "author": { + "name": "Seth Hobson", + "url": "https://github.com/wshobson" + }, + "homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code", + "license": "MIT", + "keywords": [ + "php", + "ruby", + "rails", + "wordpress", + "web-scripting" + ] +} diff --git a/setup.sh b/setup.sh old mode 100644 new mode 100755 index 93f3854..3295bb8 --- a/setup.sh +++ b/setup.sh @@ -1,199 +1,89 @@ -#!/bin/bash - -# LibreUIUX Setup Script -# Bootstraps a project with LibreUIUX design system configuration - -set -e - -# Colors for output -RED='\033[0;31m' -GREEN='\033[0;32m' -YELLOW='\033[1;33m' -BLUE='\033[0;34m' -NC='\033[0m' # No Color - -# Configuration -LIBREUI_VERSION="1.0.0" -REPO_URL="https://raw.githubusercontent.com/HermeticOrmus/LibreUIUX-Claude-Code/main" - -echo "" -echo -e "${BLUE}╔══════════════════════════════════════╗${NC}" -echo -e "${BLUE}║ LibreUIUX Setup - v${LIBREUI_VERSION} ║${NC}" -echo -e "${BLUE}╚══════════════════════════════════════╝${NC}" -echo "" - -# Check if we're in a project directory -if [ ! -f "package.json" ] && [ ! -f "index.html" ] && [ ! -f "README.md" ]; then - echo -e "${YELLOW}Warning: This doesn't look like a project directory.${NC}" - read -p "Continue anyway? (y/n) " -n 1 -r - echo - if [[ ! $REPLY =~ ^[Yy]$ ]]; then - exit 1 - fi +#!/usr/bin/env bash +# LibreUIUX installer. +# +# Registers this checkout as a Claude Code plugin marketplace and installs its +# plugins through the Claude Code CLI, so Claude Code actually loads them. +# It does the same thing as running, inside Claude Code: +# /plugin marketplace add HermeticOrmus/LibreUIUX-Claude-Code +# /plugin install <plugin>@libreuiux +# +# Usage: +# ./setup.sh install every plugin +# ./setup.sh --only p1,p2 install only the named plugins +# ./setup.sh --list list the plugins in this pack +# ./setup.sh --scope project install for this project only (user|project|local) +# ./setup.sh --uninstall remove this pack's plugins and marketplace +# +# To set up a project with a LibreUIUX CLAUDE.md template and config instead, +# run ./bootstrap.sh from inside that project. +set -euo pipefail + +REPO_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" +MANIFEST="$REPO_DIR/.claude-plugin/marketplace.json" +ONLY="" +LIST=0 +UNINSTALL=0 +SCOPE="user" + +usage() { awk 'NR==1{next} /^#/{sub(/^# ?/,""); print; next} {exit}' "${BASH_SOURCE[0]}"; } + +while [[ $# -gt 0 ]]; do + case "$1" in + --only) ONLY="${2:?--only needs a comma-separated list}"; shift 2 ;; + --list) LIST=1; shift ;; + --scope) SCOPE="${2:?--scope needs user, project, or local}"; shift 2 ;; + --uninstall) UNINSTALL=1; shift ;; + --plugins-dir) + echo "note: --plugins-dir is no longer used; Claude Code manages plugin storage itself." >&2 + shift 2 ;; + -h|--help) usage; exit 0 ;; + *) echo "unknown option: $1" >&2; usage >&2; exit 1 ;; + esac +done + +command -v claude >/dev/null 2>&1 || { echo "error: the Claude Code CLI (claude) is not on PATH. Install it first: https://docs.claude.com/en/docs/claude-code" >&2; exit 1; } +command -v jq >/dev/null 2>&1 || { echo "error: jq is required (sudo apt install jq / brew install jq)." >&2; exit 1; } + +MARKETPLACE="$(jq -r '.name' "$MANIFEST")" +mapfile -t ALL < <(jq -r '.plugins[].name' "$MANIFEST") + +if (( LIST )); then + jq -r '.plugins[] | "\(.name)\t\(.description)"' "$MANIFEST" | column -t -s $'\t' + exit 0 fi -# Function to download file -download_file() { - local url=$1 - local dest=$2 - - if command -v curl &> /dev/null; then - curl -fsSL "$url" -o "$dest" 2>/dev/null - elif command -v wget &> /dev/null; then - wget -q "$url" -O "$dest" 2>/dev/null - else - echo -e "${RED}Error: curl or wget required${NC}" - exit 1 - fi -} - -# Step 1: Choose design system -echo -e "${GREEN}Step 1: Choose your design system${NC}" -echo "" -echo " 1) Modern Web App (Shadcn, Tailwind, animations)" -echo " 2) SaaS Platform (Dashboard-focused, data-dense)" -echo " 3) Mobile First (Responsive, touch-friendly)" -echo " 4) Minimal (Clean, content-focused)" -echo "" -read -p "Choose (1-4): " choice - -case $choice in - 1) TEMPLATE="modern-webapp" ;; - 2) TEMPLATE="saas-platform" ;; - 3) TEMPLATE="mobile-first" ;; - 4) TEMPLATE="minimal" ;; - *) TEMPLATE="modern-webapp" ;; -esac - -echo -e "${BLUE}Selected: ${TEMPLATE}${NC}" -echo "" - -# Step 2: Download CLAUDE.md -echo -e "${GREEN}Step 2: Setting up CLAUDE.md${NC}" +SELECTED=("${ALL[@]}") +if [[ -n "$ONLY" ]]; then + IFS=',' read -r -a SELECTED <<< "$ONLY" + for p in "${SELECTED[@]}"; do + printf '%s\n' "${ALL[@]}" | grep -qx "$p" || { echo "error: '$p' is not a plugin in this pack (see --list)" >&2; exit 1; } + done +fi -if [ -f "CLAUDE.md" ]; then - echo -e "${YELLOW}CLAUDE.md already exists.${NC}" - read -p "Overwrite? (y/n) " -n 1 -r - echo - if [[ ! $REPLY =~ ^[Yy]$ ]]; then - echo "Keeping existing CLAUDE.md" - else - download_file "${REPO_URL}/templates/CLAUDE.${TEMPLATE}.md" "CLAUDE.md" - echo -e "${GREEN}✓ CLAUDE.md updated${NC}" +if (( UNINSTALL )); then + # Only uninstall what is installed, so a partial install does not print a + # "not found" error for every other plugin in the pack. + installed=$(claude plugin list 2>/dev/null | grep -o "[^ ]*@$MARKETPLACE" || true) + for p in "${SELECTED[@]}"; do + if grep -qx -- "$p@$MARKETPLACE" <<<"$installed"; then + claude plugin uninstall "$p@$MARKETPLACE" || true fi -else - download_file "${REPO_URL}/templates/CLAUDE.${TEMPLATE}.md" "CLAUDE.md" - echo -e "${GREEN}✓ CLAUDE.md created${NC}" + done + [[ -z "$ONLY" ]] && claude plugin marketplace remove "$MARKETPLACE" || true + echo "Removed. Restart Claude Code to unload the plugins." + exit 0 fi -# Step 3: Create .libreui-config.yaml -echo "" -echo -e "${GREEN}Step 3: Creating configuration${NC}" - -if [ ! -f ".libreui-config.yaml" ]; then - cat > .libreui-config.yaml << 'EOF' -# LibreUIUX Configuration -# Customize your design system preferences - -version: "1.0.0" - -# Learning level affects prompt suggestions and documentation links -level: beginner # beginner | intermediate | advanced - -# Design system configuration -design_system: - style: modern # modern | minimal | bold | playful - - # Component libraries to reference - libraries: - primary: shadcn-ui # shadcn-ui | radix | headless-ui | mui | chakra - animation: motion-primitives # motion-primitives | framer-motion | react-spring - icons: lucide # lucide | heroicons | phosphor | feather - - # Tailwind preset (if using Tailwind) - tailwind: - enabled: true - preset: default # default | typography | forms - -# Accessibility standards -accessibility: - level: AA # A | AA | AAA - screen_reader: true - keyboard_nav: true - color_contrast: true - -# Component defaults -components: - # Default border radius - radius: md # none | sm | md | lg | xl | full - - # Default animation style - animation: subtle # none | subtle | playful | dramatic - - # Default spacing scale base (in pixels) - spacing_base: 4 - -# Personal preferences (for personalized analogies - optional) -profile: - interests: [] # e.g., ["gaming", "cooking", "music"] - experience: "" # e.g., "2 years frontend development" - -# Enabled modules -modules: - design_vocabulary: true - component_templates: true - accessibility_checker: true - responsive_validator: true - animation_suggestions: true - -# Output preferences -output: - framework: react # react | vue | svelte | html - styling: tailwind # tailwind | css-modules | styled-components | css - typescript: true -EOF - echo -e "${GREEN}✓ .libreui-config.yaml created${NC}" +if claude plugin marketplace list 2>/dev/null | grep -q "$MARKETPLACE"; then + claude plugin marketplace update "$MARKETPLACE" else - echo -e "${YELLOW}✓ .libreui-config.yaml already exists${NC}" + claude plugin marketplace add "$REPO_DIR" fi -# Step 4: Create .claude directory structure (optional) -echo "" -echo -e "${GREEN}Step 4: Setting up commands (optional)${NC}" -read -p "Install custom slash commands? (y/n) " -n 1 -r -echo - -if [[ $REPLY =~ ^[Yy]$ ]]; then - mkdir -p .claude/commands - - # Download commands - download_file "${REPO_URL}/.claude/commands/ui-modern.md" ".claude/commands/ui-modern.md" - download_file "${REPO_URL}/.claude/commands/ui-critique.md" ".claude/commands/ui-critique.md" - download_file "${REPO_URL}/.claude/commands/ui-responsive.md" ".claude/commands/ui-responsive.md" +for p in "${SELECTED[@]}"; do + claude plugin install "$p@$MARKETPLACE" --scope "$SCOPE" +done - echo -e "${GREEN}✓ Commands installed:${NC}" - echo " /ui-modern - Generate modern components" - echo " /ui-critique - Review design quality" - echo " /ui-responsive - Check responsive design" -fi - -# Step 5: Summary -echo "" -echo -e "${GREEN}╔══════════════════════════════════════╗${NC}" -echo -e "${GREEN}║ Setup Complete! ║${NC}" -echo -e "${GREEN}╚══════════════════════════════════════╝${NC}" -echo "" -echo "Files created:" -echo " • CLAUDE.md (${TEMPLATE} design system)" -echo " • .libreui-config.yaml (configuration)" -if [ -d ".claude/commands" ]; then - echo " • .claude/commands/ (custom commands)" -fi -echo "" -echo -e "${BLUE}Next steps:${NC}" -echo " 1. Run 'claude' to start Claude Code" -echo " 2. Try: 'Create a modern button with hover effects'" -echo " 3. Read QUICK_START.md for more commands" -echo "" -echo -e "${YELLOW}Tip: Edit .libreui-config.yaml to customize your design system${NC}" -echo "" +echo +echo "Installed ${#SELECTED[@]} plugin(s) from $MARKETPLACE. Restart Claude Code to load them." +echo "Tell us what worked and what is missing: https://github.com/HermeticOrmus/LibreUIUX-Claude-Code/issues/new?template=feedback.yml"