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

feat(viz-platform): add design-system-audit skill #364

Closed
lmiranda wants to merge 0 commits from feat/357-design-system-audit-skill into development
pull from: feat/357-design-system-audit-skill
merge into: personal-projects:development
Conversation 0 Commits - Files Changed -
lmiranda commented 2026-02-01 23:06:59 +00:00
Owner
Copy Link

Summary

  • Add comprehensive design-system-audit.md skill for viz-platform
  • Defines what to check for design system compliance (component props, theme tokens, accessibility, responsive design)
  • Provides common violation patterns at FAIL/WARN/INFO severity levels
  • Includes scanning strategy and report template

Changes

New File:

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

Acceptance Criteria (from #357)

  • Create skill file with proper frontmatter
  • Purpose section explaining design system compliance auditing
  • What to Check section (component props, theme tokens, accessibility, responsive)
  • Common Violations section with examples
  • Severity Classification (FAIL/WARN/INFO)
  • Scanning Strategy section
  • Report Template section

Test Plan

  • Verify skill file has proper YAML frontmatter
  • Verify all sections are present and complete
  • Verify MCP tool references are accurate

Closes #357

Generated with Claude Code

## Summary - Add comprehensive design-system-audit.md skill for viz-platform - Defines what to check for design system compliance (component props, theme tokens, accessibility, responsive design) - Provides common violation patterns at FAIL/WARN/INFO severity levels - Includes scanning strategy and report template ## Changes **New File:** - `plugins/viz-platform/skills/design-system-audit.md` (280 lines) ## Acceptance Criteria (from #357) - [x] Create skill file with proper frontmatter - [x] Purpose section explaining design system compliance auditing - [x] What to Check section (component props, theme tokens, accessibility, responsive) - [x] Common Violations section with examples - [x] Severity Classification (FAIL/WARN/INFO) - [x] Scanning Strategy section - [x] Report Template section ## Test Plan - [ ] Verify skill file has proper YAML frontmatter - [ ] Verify all sections are present and complete - [ ] Verify MCP tool references are accurate Closes #357 --- Generated with [Claude Code](https://claude.ai/code)
lmiranda added the Component/BackendType/FeaturePriority/High labels 2026-02-01 23:06:59 +00:00
lmiranda added 1 commit 2026-02-01 23:06:59 +00:00
feat(projman): add domain-consultation skill for cross-plugin integration 6eeb4a4e9a 
Add the core skill that enables projman agents to detect and consult
domain-specific plugins (viz-platform, data-platform) during sprint
lifecycle. Includes domain detection rules, planning protocol,
execution gate protocol, review protocol, and extensibility guidelines.

Closes #356

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lmiranda added 1 commit 2026-02-01 23:07:09 +00:00
feat(viz-platform): add design-system-audit skill 557bf6115b 
Add comprehensive design system audit skill that provides:
- What to check: component prop validity, theme token usage,
  accessibility compliance, responsive design
- Common violation patterns at FAIL/WARN/INFO severity levels
- Scanning strategy for finding DMC components in Python files
- Report template for audit output
- MCP tool integration patterns

Closes #357

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lmiranda changed title from feat(projman): add domain-consultation skill for cross-plugin integration to feat(viz-platform): add design-system-audit skill 2026-02-01 23:09:57 +00:00
lmiranda closed this pull request 2026-02-01 23:47:52 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
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 Priority/High Type/Feature
Milestone
No items
No Milestone
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#364
Delete Branch "feat/357-design-system-audit-skill"

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?