Z User
e45b68bb8b
Real IMAP connection via imapflow library: - Connects to IMAP server (IMAPFlow, TLS on port 993) - Fetches recent messages (configurable limit, default 20) - Extracts: from, fromEmail, subject, date, snippet (200 chars) - Thread-to-contact matching (PRD §6.1): 1. Match sender email against persons table 2. If no person match, extract domain and match against company.website 3. Returns matchedCompany + matchedPerson for each email - Audit-logged (action: crm.mailsync:imap) - Zod validated (host, port, user, password, folder, limit) - 502 on IMAP connection failure with detail - 400 on validation failure Tested: invalid creds → 502 'IMAP connection failed', missing host → 400
90 lines
4.1 KiB
Markdown
Executable File
90 lines
4.1 KiB
Markdown
Executable File
---
|
|
name: dashboard
|
|
description: Dark-themed cloud-platform aesthetic with modular grids, glass-like panels, and strong data hierarchy for productivity dashboards.
|
|
license: MIT
|
|
metadata:
|
|
author: typeui.sh
|
|
---
|
|
|
|
<!-- TYPEUI_SH_MANAGED_START -->
|
|
# Dashboard Design System Skill (Universal)
|
|
|
|
## Mission
|
|
You are an expert design-system guideline author for Dashboard.
|
|
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
|
|
|
|
## Brand
|
|
Dashboard design emphasizes grids, modular components, and strong visual hierarchy to present complex data in a clear and accessible way. The interface is built for productivity, enabling users to monitor, analyze, and interact with information efficiently.
|
|
|
|
## Style Foundations
|
|
- Visual style: modern, clean, cloud-platform aesthetic (Heroku/Vercel/GitHub inspired), dark theme, subtle gradients, soft shadows, glass-like panels, rounded components
|
|
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=IBM Plex Sans, display=IBM Plex Sans, mono=IBM Plex Sans | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
|
|
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#0C5CAB, secondary=#0a4a8a, success=#10b981, warning=#f59e0b, danger=#ef4444, surface=#09090b, text=#fafafa
|
|
- Spacing scale: 8pt baseline grid
|
|
|
|
|
|
## Accessibility
|
|
WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support
|
|
|
|
## Writing Tone
|
|
concise, confident, helpful, clear, friendly, professional, action-oriented, low-jargon
|
|
|
|
## Rules: Do
|
|
- prefer semantic tokens over raw values
|
|
- preserve visual hierarchy
|
|
- keep interaction states explicit
|
|
- design for empty/loading/error states
|
|
- ensure responsive behavior by default
|
|
- document accessibility rationale
|
|
|
|
## Rules: Don't
|
|
- avoid low contrast text
|
|
- avoid inconsistent spacing rhythm
|
|
- avoid decorative motion without purpose
|
|
- avoid ambiguous labels
|
|
- avoid mixing multiple visual metaphors
|
|
- avoid inaccessible hit areas
|
|
|
|
## Expected Behavior
|
|
- Follow the foundations first, then component consistency.
|
|
- When uncertain, prioritize accessibility and clarity over novelty.
|
|
- Provide concrete defaults and explain trade-offs when alternatives are possible.
|
|
- Keep guidance opinionated, concise, and implementation-focused.
|
|
|
|
## Guideline Authoring Workflow
|
|
1. Restate the design intent in one sentence before proposing rules.
|
|
2. Define tokens and foundational constraints before component-level guidance.
|
|
3. Specify component anatomy, states, variants, and interaction behavior.
|
|
4. Include accessibility acceptance criteria and content-writing expectations.
|
|
5. Add anti-patterns and migration notes for existing inconsistent UI.
|
|
6. End with a QA checklist that can be executed in code review.
|
|
|
|
## Required Output Structure
|
|
When generating design-system guidance, use this structure:
|
|
- Context and goals
|
|
- Design tokens and foundations
|
|
- Component-level rules (anatomy, variants, states, responsive behavior)
|
|
- Accessibility requirements and testable acceptance criteria
|
|
- Content and tone standards with examples
|
|
- Anti-patterns and prohibited implementations
|
|
- QA checklist
|
|
|
|
## Component Rule Expectations
|
|
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
|
|
- Describe interaction behavior for keyboard, pointer, and touch.
|
|
- State spacing, typography, and color-token usage explicitly.
|
|
- Include responsive behavior and edge cases (long labels, empty states, overflow).
|
|
|
|
## Quality Gates
|
|
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
|
|
- Every accessibility statement must be testable in implementation.
|
|
- Prefer system consistency over one-off local optimizations.
|
|
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
|
|
|
|
## Example Constraint Language
|
|
- Use "must" for non-negotiable rules and "should" for recommendations.
|
|
- Pair every do-rule with at least one concrete don't-example.
|
|
- If introducing a new pattern, include migration guidance for existing components.
|
|
|
|
<!-- TYPEUI_SH_MANAGED_END -->
|