personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Sprint 9] feat: Create design-system-audit.md skill (viz-platform) #357

New Issue
Closed
opened 2026-02-01 22:49:13 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-02-01 22:49:13 +00:00
Owner
Copy Link

Description

Create the design system audit skill that defines what to check, severity levels, and common violation patterns for viz-platform code reviews.

Implementation

Wiki: Change V5.6.0 (Sprint 9 Implementation)

File: plugins/viz-platform/skills/design-system-audit.md

Acceptance Criteria

  • Create skill file with proper frontmatter
  • Purpose section explaining design system compliance auditing
  • What to Check section:
    • Component prop validity (typos, invalid values)
    • Theme token usage (hardcoded colors vs theme tokens)
    • Accessibility (color contrast, ARIA labels)
    • Responsive design (breakpoint usage)
  • Common Violations section with examples
  • Severity Classification:
    • FAIL: Breaking issues (invalid props, missing required)
    • WARN: Quality issues (accessibility, best practices)
    • INFO: Suggestions (optimizations, patterns)
  • Scanning Strategy section (file types, patterns to check)
  • Report Template section (output format)

Technical Notes

This skill is loaded by the design-reviewer agent. It provides the domain knowledge for what constitutes a design system violation.

Risk: Low - standalone knowledge file

## Description Create the design system audit skill that defines what to check, severity levels, and common violation patterns for viz-platform code reviews. ## Implementation **Wiki:** [Change V5.6.0 (Sprint 9 Implementation)](https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/wiki/Change-V5.6.0%3A-Domain-Advisory-Pattern-%28Sprint-9-Implementation%29) **File:** `plugins/viz-platform/skills/design-system-audit.md` ## Acceptance Criteria - [ ] Create skill file with proper frontmatter - [ ] Purpose section explaining design system compliance auditing - [ ] What to Check section: - Component prop validity (typos, invalid values) - Theme token usage (hardcoded colors vs theme tokens) - Accessibility (color contrast, ARIA labels) - Responsive design (breakpoint usage) - [ ] Common Violations section with examples - [ ] Severity Classification: - FAIL: Breaking issues (invalid props, missing required) - WARN: Quality issues (accessibility, best practices) - INFO: Suggestions (optimizations, patterns) - [ ] Scanning Strategy section (file types, patterns to check) - [ ] Report Template section (output format) ## Technical Notes This skill is loaded by the design-reviewer agent. It provides the domain knowledge for what constitutes a design system violation. **Risk:** Low - standalone knowledge file
lmiranda added this to the Sprint 9 - Domain Advisory Pattern (viz-platform) milestone 2026-02-01 22:50:08 +00:00
lmiranda commented 2026-02-01 23:10:07 +00:00
Author
Owner
Copy Link

Progress Update

Status: Implementation Complete

Completed

  • Created plugins/viz-platform/skills/design-system-audit.md (280 lines)
  • Proper YAML frontmatter with name and description
  • Purpose section explaining design system compliance auditing
  • What to Check section covering:
    • Component prop validity (typos, invalid values, missing required)
    • Theme token usage (hardcoded colors, fonts, spacing)
    • Accessibility compliance (contrast, ARIA labels)
    • Responsive design (breakpoints, fixed widths)
  • Common Violations section with Python code examples
  • Severity Classification (FAIL/WARN/INFO with decision tree)
  • Scanning Strategy (file types, scan process)
  • Report Template (structured output format)
  • MCP tool integration patterns

PR

Files Changed

  • plugins/viz-platform/skills/design-system-audit.md (new file, 280 lines)

Implementation by Executor Agent

## Progress Update **Status:** Implementation Complete ### Completed - [x] Created `plugins/viz-platform/skills/design-system-audit.md` (280 lines) - [x] Proper YAML frontmatter with name and description - [x] Purpose section explaining design system compliance auditing - [x] What to Check section covering: - Component prop validity (typos, invalid values, missing required) - Theme token usage (hardcoded colors, fonts, spacing) - Accessibility compliance (contrast, ARIA labels) - Responsive design (breakpoints, fixed widths) - [x] Common Violations section with Python code examples - [x] Severity Classification (FAIL/WARN/INFO with decision tree) - [x] Scanning Strategy (file types, scan process) - [x] Report Template (structured output format) - [x] MCP tool integration patterns ### PR - PR #364: http://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/pulls/364 ### Files Changed - `plugins/viz-platform/skills/design-system-audit.md` (new file, 280 lines) --- Implementation by Executor Agent
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label Component/Backend Complexity/Simple Effort/S Priority/High Type/Feature
Milestone
No items
No Milestone Sprint 9 - Domain Advisory Pattern (viz-platform)
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#357
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?