design-ops

Guided setup for adding a new tool to DESIGN-OPS. Uses the evaluation cascade to determine the best connection method.

Update specific settings without running full setup. Pillar-based configuration with re-evaluation options.

**Legacy alias** for `/design-ops:dashboard daily`

Generate a static HTML dashboard viewable in any browser. Outputs a single HTML file with embedded CSS and JavaScript — no build step required.

Unified dashboard command that generates pillar × timeframe reports from connected tools.

Complete command reference for DESIGN-OPS.

Browse and discover utility commands organized by category.

Create structured content briefs for articles, blog posts, case studies, and other long-form content.

Generate and score copy variations for A/B testing. Creates multiple headline, CTA, and body copy options aligned with brand voice.

Guided workflow for creating social content tailored to LinkedIn, Instagram, or Substack.

Accessibility compliance check against WCAG A, AA, and AAA standards.

Quick competitive design analysis. Extracts design patterns, color palettes, typography, and positioning from competitor websites.

Automated design system compliance check. Validates components, screens, or files against your design tokens and patterns.

Curated design inspiration from web sources. Analyzes design patterns, color palettes, and techniques from inspiration sites.

Generate multiple design variations within brand constraints. Creates 3-5 alternative approaches with trade-off analysis.

Challenge assumptions, identify weaknesses, and stress-test current thinking. A constructive sparring partner, not an adversary.

Synthesize research into actionable insights. Analyzes multiple sources and produces executive summaries with recommendations.

This reference contains analysis workflows, heuristics, and LLM prompts for website intelligence gathering.

This document defines the YAML schema for machine-readable component specifications. These specs are generated per template family and designed for AI implementation.

Complete Markdown scaffolds for the deliverable files. Each file includes a standard header explaining its purpose and target audience.

This document shows abbreviated examples of expected output quality from the Website Intelligence Skill.

This reference contains deterministic patterns for classifying page sections and URL clusters.

Analyze any website and generate structured intelligence reports with site architecture, SEO insights, and component analysis.

Generate project kickoff materials from a brief or proposal.

Interactive workflow to create a focused meeting agenda through guided questions.

Post-meeting documentation workflow that generates summaries with action items, owners, and deadlines.

Reset DESIGN-OPS configuration to start fresh.

Main onboarding wizard for DESIGN-OPS. Guides users through connecting data sources across three business pillars: Operations, Design, and Analytics.

Show current configuration status organized by pillars, integration health, and available commands.

**Legacy alias** for `/design-ops:dashboard design daily` with team focus

Verification suite that checks all integrations, skills, and commands are working correctly. Organized by pillars.

Re-validate all configured tool connections. Use this to check tool status after setup, after changing API keys, or when troubleshooting connection problems.

**Legacy alias** for `/design-ops:dashboard weekly`

Dynamic MCP package discovery at runtime. Instead of relying on a static registry, this skill verifies MCP availability by querying npm, GitHub, and vendor documentation.

Sub-agent skill for evaluating tools during `/design-ops:setup`. Coordinates MCP availability checks and API capability evaluation.

Use when user mentions "brand", "Open Session colors", "Aperol", "Charcoal", "Vanilla", "brand guidelines", or works on UI following Open Session standards.

Generate static HTML dashboards from DESIGN-OPS data.

Use when reviewing UI/frontend code, conducting PR reviews for components, checking design system compliance, or after any UI component work.

Use when building UI components, making design decisions for frontend work, reviewing UI implementation quality, or planning interaction patterns.