// Audit the Resend dashboard for design system alignment. Routes here when a user says "audit design", "design alignment", "dashboard design audit", or when triggered by the scheduled weekly routine.
Use when needing Resend design resources. Routes to brand guidelines, visual identity, UI components, design tokens, and marketing page patterns.
Use when building or modifying UI in the Resend codebase. Provides component APIs, variant options, design tokens, and composition patterns for all src/ui/ primitives.
Use when creating, updating, editing, or deleting marketing/public pages in the Resend codebase. Covers page structure, component reuse rules, and the distinction between public and product design systems.
Use when creating Resend marketing materials, documents, presentations, or visual content. Triggers for Resend brand, Resend style, or Resend visual identity requests.
| name | design-audit |
| description | Audit the Resend dashboard for design system alignment. Routes here when a user says "audit design", "design alignment", "dashboard design audit", or when triggered by the scheduled weekly routine. |
| metadata | {"author":"resend","version":"1.0.0"} |
Audits src/app/(dashboard)* for design system compliance and src/ui/ for documentation coverage. Reports findings without modifying any source files or opening PRs.
This skill is read-only. Never edit source files, create branches, or open PRs.
src/app/(internal)/design/_common/sidebar-data.ts to extract:
_common, layout.tsx, shared.ts, page.tsx, todo)"avatar team" → "avatar", "command" → "combobox")src/app/(internal)/design/_common/documented-components.json for the list of documented componentssrc/app/(internal)/design/_common/documented-patterns.json for the list of documented patternsgit rev-parse HEADFollow references/rubric.md exactly. Run all categories:
Cross-reference the resend-design-system skill to verify whether a DS primitive exists for a flagged use case before marking it a violation.
Emit the structured JSON defined in references/report-format.md, then render it as markdown per the template in that file.
Follow references/linear-delivery.md to file or update the Linear issue. Before creating any tickets, run the triage-backlog preflight in that doc — if 10+ tickets are already pending in Triage, defer non-error tickets this run.
Load these when running the audit:
design-audit/references/rubric.md — what counts as a violation and how to detect itdesign-audit/references/report-format.md — exact JSON + markdown report structuredesign-audit/references/linear-delivery.md — Linear MCP playbook for filing the issue