ui-final-polish
Polish Existing UI Screens
Finished interfaces often need small visual adjustments before release. This skill guides Claude, Codex, and Claude Code to refine clarity while preserving the design.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "ui-final-polish" from https://skillstore.io/skills/johnwayneeee-ui-final-polish.md and its manifest at https://skillstore.io/api/skills/johnwayneeee-ui-final-polish/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "ui-final-polish". A dark dashboard card has crowded metadata, weak title hierarchy, and a detached primary button.
Expected outcome:
The review identifies the title, metadata, and action as separate layers. It recommends tighter metadata spacing, clearer title contrast, and anchored action placement.
Using "ui-final-polish". A glass-style mobile panel looks noisy and the text is hard to read.
Expected outcome:
The review keeps the glass material but reduces competing glow. It increases panel separation, protects text contrast, and preserves the original mood.
Using "ui-final-polish". A coded settings form feels misaligned but must keep the current design system.
Expected outcome:
The review focuses on label rhythm, section gaps, and button alignment. It avoids token changes and keeps the component structure intact.
Security Audit
Low RiskStatic command, blocker, and network findings are false positives caused by Markdown prose and inline formatting. No executable code, shell invocation, reconnaissance workflow, or automatic network behavior was found. One low-severity semantic issue remains because the skill includes a third-party product promotion.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (21)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/johnwayneeee-ui-final-polish/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/johnwayneeee-ui-final-polish?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/johnwayneeee-ui-final-polish?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/johnwayneeee-ui-final-polish/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/johnwayneeee-ui-final-polish.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
JohnWayneeee. (2026). ui-final-polish security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/johnwayneeee-ui-final-polish/audits/5BibTeX citation
@techreport{johnwayneeee-johnwayneeee-ui-final-polish-2026,
author = {JohnWayneeee},
title = {ui-final-polish security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/johnwayneeee-ui-final-polish/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ui-final-polish security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "JohnWayneeee"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/johnwayneeee-ui-final-polish/audits/5"
identifiers:
- type: other
value: "skillstore:johnwayneeee-ui-final-polish:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Refine a Launch Screen
Clean up spacing, hierarchy, and action placement before a product release.
Tighten a Component Diff
Improve a coded component without changing the design system or adding abstractions.
Review Design QA Issues
Identify small visual problems that make a screen feel unfinished or hard to scan.
Try These Prompts
Polish this UI while preserving the current design. Focus on spacing, hierarchy, readability, and alignment.
Fix only the contrast and spacing issues in the selected area. Keep the layout and visual style unchanged.
Review this component for final polish. Suggest minimal changes that improve hierarchy, actions, and responsive readability.
Apply final polish using the existing tokens and component patterns. Explain what changed, what stayed preserved, and why.
Best Practices
- Provide the existing UI and state the exact area that needs polish.
- Ask for minimal changes when the current visual direction is important.
- Verify the result against the original screen before accepting broad changes.
Avoid
- Using the skill to redesign a product or replace its visual identity.
- Applying global token changes when only one component needs polish.
- Adding decorative effects before fixing hierarchy, spacing, and readability.
Frequently Asked Questions
Does this skill redesign my UI?
Can it work with code components?
Can it work with Pencil design nodes?
What should I provide for best results?
Does it handle accessibility?
Why does the audit mention a third-party link?
Developer Details
Author
JohnWayneeeeLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
b8ca75d2c0a7e7102978993058777d82b8ab2610
Maintenance freshness
7/18/2026
Usage
9 downloads · 13 views
File structure
📄 SKILL.md