ui-ux-pro-max
Professional UI/UX design research skill with a bundled searchable database for product patterns, visual styles, color palettes, typography, landing-page structure, dashboard charts, UX practices, and stack guidance. Use when designing, building, reviewing, or improving interfaces.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 336
- Forks
- 69
01 前言 Front Matter
- name
- ui-ux-pro-max
- description
- Professional UI/UX design research skill with a bundled searchable database for product patterns, visual styles, color palettes, typography, landing-page structure, dashboard charts, UX practices, and stack guidance. Use when designing, building, reviewing, or improving interfaces.
02 资源文件 2
- 参考文档data/catalog.json21.2 KB
- 脚本scripts/search.py5.1 KB
03 SKILL.md 正文
UI/UX Pro Max
Use this skill for UI/UX design work: visual direction, landing pages, dashboards, app screens, responsive layouts, design critique, and frontend implementation guidance.
Search First
The local database lives in this skill package. In Nomi workspaces the skill is linked at .nomi/skills/ui-ux-pro-max/.
python3 .nomi/skills/ui-ux-pro-max/scripts/search.py "<keywords>" --domain <domain> -n 5
If you are already inside this skill directory, the shorter form also works:
python3 scripts/search.py "<keywords>" --domain <domain> -n 5
Available domains:
product- product type patterns and structurestyle- visual style systems and compositiontypography- font pairings and type hierarchycolor- palette recommendations with roleslanding- landing-page section structurechart- dashboard and data visualization patternsux- interaction, accessibility, responsive, and state guidancestack- framework-specific implementation guidanceprompt- design brief and generation prompt structure
Examples:
python3 .nomi/skills/ui-ux-pro-max/scripts/search.py "saas dashboard enterprise" --domain product
python3 .nomi/skills/ui-ux-pro-max/scripts/search.py "glassmorphism minimal" --domain style
python3 .nomi/skills/ui-ux-pro-max/scripts/search.py "healthcare calm trust" --domain color
python3 .nomi/skills/ui-ux-pro-max/scripts/search.py "layout responsive" --stack html-tailwind
python3 .nomi/skills/ui-ux-pro-max/scripts/search.py --list-domains
Workflow
- Extract product type, audience, visual tone, industry, and stack from the user request.
- Search
productfirst, then search the most relevant ofstyle,typography,color,landing,chart,ux, andstack. - Combine results into a concrete design direction: layout, hierarchy, palette, type, states, and component behavior.
- If implementing code, follow the existing project's framework and design conventions first; use this database to resolve gaps.
- Verify every layout target supported by the current project. In
nomifun-desktop, test only the desktop shell and desktop WebUI at viewports of 880x600 or larger; do not add or run phone/tablet layout checks. Also verify text fit, contrast, focus states, hover states, loading/empty/error states, and any chart or media rendering.
Design Rules
- Build the actual usable screen first, not a marketing explanation of the screen.
- Use domain-specific layout density: dashboards and operational tools should be quiet and scannable; games and playful products can be more expressive.
- Prefer stable responsive constraints over viewport-scaled font sizes.
- Keep typography readable: explicit heading/body hierarchy, no negative letter spacing, no text overflow.
- Keep palettes intentional: one dominant color, one support color, one accent, plus neutrals; avoid one-hue UIs unless the brand requires it.
- Use real product, place, object, state, chart, or gameplay imagery when the page needs inspection or trust.
- Treat accessibility, keyboard focus, contrast, and empty/loading/error states as part of the design, not cleanup.
04 同仓库更多 Skills
drive-nomifun
Connect an authorized external client to NomiFun's canonical Remote ingress. Use an installation access token and a local-owner-created RemoteBinding, then operate the explicit open/turn/observe/cancel AgentSession lifecycle.
example-skill
Fixture skill used by startup_materialize integration tests.
planning-with-files
Maintain durable task plans, findings, and progress logs in workspace files for long-running or research-heavy work. Use when a task spans many steps or sessions, needs an auditable evidence trail, or risks losing important decisions to context limits. Do not use for short tasks that fit comfortably in the active conversation.
officecli
Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
officecli-xlsx
Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV/TSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx/.csv filename.
officecli-word-form
Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document', 'onboarding form', 'HR intake', 'survey template', 'contract / SOW template', 'mail-merge template', 'compliance checklist', 'medical intake questionnaire'. Output is a single .docx where specific fields are editable and the rest is locked. This skill is INDEPENDENT, not a scene layer on docx — payload is `<w:sdt>` + `<w:ffData>` + `<w:fldChar>` + `documentProtection`, none of which docx base skill covers. Do NOT trigger for regular reports, letters, memos, academic papers, pitch decks, or any document with no user-fillable fields — route those to officecli-docx or its scene layers.