Interface Design for Dashboards and Apps
holaboss-ai/holaOS
Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.
Audit multi-surface UI/UX in the personal-assistant Obsidian plugin with the current PA framework, real interface evidence, structured scoring, adversarial finding verification, and product-decision…
Install UI UX Design Audit
$ npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install edonyzpc/personal-assistant ui-ux-design-audit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ui-ux-design-audit .claude/skills/ui-ux-design-audit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ui-ux-design-audit" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/ui-ux-design-audit into .claude/skills/ui-ux-design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-ux-design-audit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/ui-ux-design-auditType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install edonyzpc/personal-assistant ui-ux-design-audit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/ui-ux-design-audit .agents/skills/ui-ux-design-audit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ui-ux-design-audit" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/ui-ux-design-audit into .agents/skills/ui-ux-design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-ux-design-audit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install edonyzpc/personal-assistant ui-ux-design-audit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/ui-ux-design-audit .cursor/skills/ui-ux-design-audit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ui-ux-design-audit" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/ui-ux-design-audit into .cursor/skills/ui-ux-design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-ux-design-audit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/edonyzpc/personal-assistant.git --path .agents/skills/ui-ux-design-audit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install edonyzpc/personal-assistant ui-ux-design-audit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/ui-ux-design-audit .gemini/skills/ui-ux-design-audit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ui-ux-design-audit" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/ui-ux-design-audit into .gemini/skills/ui-ux-design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-ux-design-audit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install edonyzpc/personal-assistant ui-ux-design-auditInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/ui-ux-design-audit .github/skills/ui-ux-design-audit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ui-ux-design-audit" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/ui-ux-design-audit into .github/skills/ui-ux-design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-ux-design-audit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install edonyzpc/personal-assistant ui-ux-design-audit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edonyzpc/personal-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/ui-ux-design-audit .opencode/skills/ui-ux-design-audit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ui-ux-design-audit" agent skill from https://github.com/edonyzpc/personal-assistant/tree/master/.agents/skills/ui-ux-design-audit into .opencode/skills/ui-ux-design-audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-ux-design-audit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ui-ux-design-audit- GitHub stars
- 148
- Token cost
- ~1.8k tokens
- SKILL.md length
- 778 words
- Files
- 2
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Audit multi-surface UI/UX in the personal-assistant Obsidian plugin with the current PA framework, real interface evidence, structured scoring, adversarial finding verification, and product-decision…
- Works in 5 steps: Bound the Audit → Observe and Score → Fan Out Broad Audits → …
- Design retrospectives
- SKILL.md covers Core Boundaries, Evidence Standard, Workflow and Artifacts, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
UI UX Design Audit is an agent skill from edonyzpc/personal-assistant. Audit multi-surface UI/UX in the personal-assistant Obsidian plugin with the current PA framework, real interface evidence, structured scoring, adversarial finding verification, and product-decision routing. Use for design retrospectives, visual quality baselines, cross-surface consistency audits, accessibility/mobile evaluations, or requests such as "帮我看看设计" and "audit the UI". Default to audit-only; implement findings only when explicitly requested, and require separate authorization for commit or archive…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Frontend & Design, covering UI design, Design review and critique and Retrospectives. It works with Obsidian. The repository describes itself as: A plugin that harnesses AI agents and streamlining techniques to help you automatically manage Obsidian. The licence is AGPL-3.0.
When your agent uses it
- Design retrospectives
- Visual quality baselines
- Cross-surface consistency audits
- Accessibility/mobile evaluations
Example prompts
- “帮我看看设计”
- “audit the UI”
- “/ui-ux-design-audit”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4f02170. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
UI UX Design Audit loads about 1.8k tokens when it runs. Until then it costs about 156 tokens; SKILL.md has 778 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from edonyzpc/personal-assistant at commit 4f02170, republished under its AGPL-3.0 licence (© edonyzpc). 778 words, ~1,766 tokens.
Download SKILL.mdSave it as
.claude/skills/ui-ux-design-audit/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- ui-ux-design-audit
- description
- Audit multi-surface UI/UX in the personal-assistant Obsidian plugin with the current PA framework, real interface evidence, structured scoring, adversarial finding verification, and product-decision routing. Use for design retrospectives, visual quality baselines, cross-surface consistency audits, accessibility/mobile evaluations, or requests such as "帮我看看设计" and "audit the UI". Default to audit-only; implement findings only when explicitly requested, and require separate authorization for commit or archive actions. For review of a current code diff or PR, use `personal-assistant-review` instead.
UI/UX Design Audit
Core Boundaries
Default to audit-only:
- Inspect, observe, score, verify, and report findings.
- Do not edit runtime/product code unless the user explicitly asks to fix the verified findings.
- Create or update a durable audit artifact only when the user asks for one; otherwise report in chat.
- Do not commit or archive artifacts without separate explicit authorization.
Use this skill for cross-surface design quality. Route a current diff/PR review
to personal-assistant-review, even when the diff is UI-heavy.
Read:
AGENTS.mddocs/product/pa-product-north-star.mddocs/product/pa-low-burden-review-product-principles.mddocs/development/workflows/pa-ui-ux-review-framework.md- The source files and tests for the audited surfaces
Reuse the current PA framework before inventing a new instrument. Treat its four Layer A dimensions—Design Coherence, Visual Polish, Interaction Quality, and Content Clarity—as a PA adaptation, not a verbatim external framework. Research external frameworks only when the current instrument needs revision; use authoritative sources and preserve citations for adapted claims.
Evidence Standard
Separate evidence into three lanes:
| Lane | Can prove | Cannot prove alone |
|---|---|---|
| Source and tests | State, lifecycle, copy, accessibility markup, CSS intent, product contract | Rendered visual quality or interaction feel |
| Runtime/DOM | Mounting, state transitions, computed structure, fresh console behavior | Visual polish or real user interaction by itself |
| Visible UI | Layout, hierarchy, contrast, clipping, focus, keyboard/touch flow, perceived burden | Hidden code paths not exercised |
Require obsidian-test-vault-smoke at full-ui tier before assigning visual or
interaction scores. Capture the visible path, interaction, observed state, and
screenshot evidence. If the app cannot be observed, mark those dimensions
UNSCORED or BLOCKED; do not infer a score from source code.
Use obsidian-ios-real-device-smoke for claims about real iOS touch behavior.
Do not generalize desktop evidence to mobile.
Workflow
1. Bound the Audit
- Confirm the requested surfaces, platforms, themes, and key user journeys.
- Inventory views, panels, modals, overlays, commands, settings, and navigation transitions in scope.
- Select only the framework dimensions relevant to the request.
- Define the evidence needed for every score before auditing.
2. Observe and Score
- Deploy and observe the real test-vault UI through
obsidian-test-vault-smokewhen visual or interaction scoring is requested. - Trace each visible issue to source, CSS, state, or product-contract evidence.
- Score with the current PA framework. Use short evidence-backed rationales; do not manufacture numerical precision.
- Check the North Star explicitly:
- capture friction
- right-time return
- quietness and ignorable states
- source-backed trust
- reversible maintenance and earned action
- net review burden
For layered surfaces, use Mermaid for topology or flow diagrams. Use a Markdown table for the score heatmap.
3. Fan Out Broad Audits
If multi-agent tools are available and the audit is broad or the user asks for an agent team, partition surfaces across independent agents. Give every agent the same framework and different surfaces. If subagents are unavailable, run the same partitions locally.
Require this schema from each lane:
## Surface: <name>
### Evidence
- visible path and screenshot
- source/test anchors
### Scores
| Dimension | Score or UNSCORED | Evidence |
| --- | --- | --- |
### Findings
| Finding | Severity | Trigger | Suggested direction |
| --- | --- | --- | --- |Add one cross-surface pass for terminology, design tokens, navigation, progressive disclosure, accessibility, and desktop/mobile consistency.
Show full SKILL.md (302 more words)Show less
4. Verify Findings
Verify every P0/P1/P2 finding against the actual source and the relevant visible flow before presenting it as confirmed.
Classify each finding:
CONFIRMED: the trigger and impact match the evidencePARTIALLY CONFIRMED: the issue exists but scope or severity changesFALSE POSITIVE: current source or observed behavior contradicts itBLOCKED: required runtime/device evidence is unavailable
Recalibrate severity after verification. Do not force findings per surface or dimension.
5. Route Decisions and Fixes
End an audit-only request after verified findings, decisions, and validation gaps.
If the user explicitly asks to fix findings:
- Use
personal-assistant-review-followupto classify and confirm the fix set. - Ask before changing product semantics, visible capability, confirmation burden, information architecture, or review cadence.
- Route structural changes to
sdd-lifecycle; do not reproduce the refactor workflow here. - Implement only the approved fix set.
- Use
personal-assistant-reviewon the resulting diff. - Re-run the relevant
full-uiflow and record before/after evidence.
Implementation authorization does not authorize commit, push, archive, or release actions.
Artifacts
- Reuse
docs/development/workflows/pa-ui-ux-review-framework.md; do not create a duplicate framework. - Follow
docs/development/documentation-workflow.mdwhen the user requests a durable audit report. - Keep an active audit package under
docs/development/active/<audit>/only while work is active. - Add unresolved follow-up to
docs/backlog.mdonly when requested and avoid copying the full audit into the backlog. - Archive a completed report only when the user explicitly asks.
Output
Lead with verified findings ordered by severity. Include:
- surface and user-visible trigger
- score or
UNSCORED, with evidence - source/test and visible-UI anchors
- confirmation status and suggested direction
- validation completed, blocked, and not run
- decisions required before any fix
If there are no actionable findings, say ✅ OK and list only material evidence
gaps.
Related Skills
personal-assistant-review: current diff/PR reviewpersonal-assistant-review-followup: finding triage and approved fixessdd-lifecycle: structural design and implementation lifecycleobsidian-test-vault-smoke: local full-UI evidenceobsidian-ios-real-device-smoke: iOS real-device evidence
© edonyzpc, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/ui-ux-design-audit of edonyzpc/personal-assistant.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 4f02170
Compare with similar skills
UI UX Design Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| UI UX Design Audit this skilledonyzpc/personal-assistant | 148 | — | ~1.8k | Automated safety check: Pass | AGPL-3.0 | |
| Interface Design for Dashboards and Appsholaboss-ai/holaOS | 11k | 3 repos | ~6k | Automated safety check: Pass | MIT | |
| Tastemaker UI Designcodeswithroh/tastemaker | 444 | — | ~16k | Automated safety check: Pass | MIT | |
| UI Aesthetics Judgmentkasonye/ui-aesthetics-skill | 383 | — | ~3.2k | Automated safety check: Pass | None | |
| Agentos UI UXSapienXai/AgentOS | 118 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Distinctive UI Buildertw93/Waza | 7.2k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Tastemaker UI Design
codeswithroh/tastemaker
Grounds AI-built interfaces in real reference images and a saved personal taste profile, so UI work avoids the generic defaults of typical generated apps.
UI Aesthetics Judgment
kasonye/ui-aesthetics-skill
Sets rules for web UI work that favor hierarchy, spacing and restrained styling, with routes for generating, reviewing and polishing interfaces.
Agentos UI UX
SapienXai/AgentOS
Design, review, or implement AgentOS UI and UX work using the project’s operator-console visual system.
Distinctive UI Builder
tw93/Waza
Builds or restyles production UI with a clear point of view, checks the result against screenshots and responsive states, and hands document typography to other skills.
Fix PR Design Notes
different-ai/openwork
Reads the advisory design review attached to a pull request's screenshots, fixes the flagged UI problems in product code, and proves each note is gone.
More from edonyzpc/personal-assistant
All 19 skills in this repoObsidian Dataview
edonyzpc/personal-assistant
Dataview plugin query syntax, inline expressions, DataviewJS API, and common vault analysis patterns.
Obsidian Test Vault Smoke
edonyzpc/personal-assistant
Validate Personal Assistant runtime and UI changes in the repo-local Obsidian test vault.
Obsidian Community Check
edonyzpc/personal-assistant
Trigger and inspect Obsidian Community checks for personal-assistant.
Pa Brat Beta Release
edonyzpc/personal-assistant
Manage Personal Assistant BRAT beta prerelease workflow. An agent skill from edonyzpc/personal-assistant.
Pa Docs Lifecycle Manager
edonyzpc/personal-assistant
Maintain PA task records and documentation lifecycle. An agent skill from edonyzpc/personal-assistant.
Personal Assistant Review
edonyzpc/personal-assistant
Review uncommitted or PR diffs in the personal-assistant Obsidian plugin with project-specific risk lanes, second-layer future-risk checks, severity discipline, subagent review routing, and…
Related
Works with
Categories
Questions about UI UX Design Audit
What does UI UX Design Audit do?
Audit multi-surface UI/UX in the personal-assistant Obsidian plugin with the current PA framework, real interface evidence, structured scoring, adversarial finding verification, and product-decision…. UI UX Design Audit is an agent skill from edonyzpc/personal-assistant. Audit multi-surface UI/UX in the personal-assistant Obsidian plugin with the current PA framework, real interface evidence, structured scoring, adversarial finding verification, and product-decision routing.
When should I use UI UX Design Audit?
UI UX Design Audit fits situations like: design retrospectives; visual quality baselines; cross-surface consistency audits; accessibility/mobile evaluations.
How do I install UI UX Design Audit in Claude Code?
Run `npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a claude-code`. Or copy the skill folder (.agents/skills/ui-ux-design-audit in edonyzpc/personal-assistant) into .claude/skills/ui-ux-design-audit in your project. Claude Code loads it when a task matches its description.
How do I install UI UX Design Audit in Codex?
Run `npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a codex`. Or copy the skill folder (.agents/skills/ui-ux-design-audit in edonyzpc/personal-assistant) into .agents/skills/ui-ux-design-audit in your project. Codex loads it when a task matches its description.
Can I use UI UX Design Audit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add edonyzpc/personal-assistant --skill ui-ux-design-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ui-ux-design-audit, .gemini/skills/ui-ux-design-audit, .github/skills/ui-ux-design-audit and .opencode/skills/ui-ux-design-audit in your project.
What does UI UX Design Audit need to run?
SKILL.md names no scripts, command-line tools or credentials: UI UX Design Audit is instructions for the agent only.
Does UI UX Design Audit access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is UI UX Design Audit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does UI UX Design Audit use?
UI UX Design Audit is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does UI UX Design Audit use?
About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to UI UX Design Audit?
Skills that share tags, products or a category with UI UX Design Audit: Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Tastemaker UI Design (codeswithroh/tastemaker, 444 stars), UI Aesthetics Judgment (kasonye/ui-aesthetics-skill, 383 stars) and Agentos UI UX (SapienXai/AgentOS, 118 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains UI UX Design Audit?
edonyzpc (a GitHub user) maintains it in edonyzpc/personal-assistant, which has 148 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 10, 2026.
Source: edonyzpc/personal-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.