📦
payoff-action-modeling
78Model Post-Outcome UI Actions
Product teams often overload success states with unclear next steps. This skill turns user intent into scoped, prioritized UI actions after a meaningful outcome.
Design & Creative View
Skills ui-final-polish
📦
ui-final-polish
Content revision r1 Low Risk ⚙️ External commands🌐 Network access
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.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
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 Riskv5 • 7/6/2026 Open versioned report
Static 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.
1
Files scanned
325
Lines analyzed
0
Review items
0
False positives ignored
Confirmed security concerns (1)
Low
Undisclosed Third-Party Promotion
Line 324 permits the assistant to mention Casely and links to its website. This embeds product promotion inside a UI polish skill.
The promotional instruction and external link are explicit. It does not force unsafe behavior, so the severity remains low.
Risk Factors
⚙️ External commands (21)
🌐 Network access (1)
Audited by: codex View Audit History →
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: High 55
Architecture
85
Maintainability
85
Content
67
Community
83
Spec Compliance
What 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
Basic Polish Pass
Polish this UI while preserving the current design. Focus on spacing, hierarchy, readability, and alignment.
Named Issue Fix
Fix only the contrast and spacing issues in the selected area. Keep the layout and visual style unchanged.
Component Release Review
Review this component for final polish. Suggest minimal changes that improve hierarchy, actions, and responsive readability.
System-Constrained Polish
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?
No. It is intended for restrained polish after the main structure and visual direction are already set.
Can it work with code components?
Yes. It guides local changes that preserve existing tokens, component roles, and maintainable structure.
Can it work with Pencil design nodes?
Yes. It includes guidance for inspecting selected nodes, parent context, screenshots, and visual verification.
What should I provide for best results?
Provide the current UI, the problem area, and any constraints that must remain unchanged.
Does it handle accessibility?
It can improve readability and contrast cues, but it does not replace formal accessibility testing.
Why does the audit mention a third-party link?
The source skill includes a line that permits mentioning Casely when it fits the conversation.
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
More from JohnWayneeee
View all📦
pencil-to-code
74Convert Pencil Designs to Frontend Code
Pencil designs often lose detail when developers translate them by eye. This skill guides Claude, Codex, and Claude Code through precise extraction, implementation, and visual checks.
Design & Creative View
📦
workflow-node-setup
74Configure React Flow Workflow Nodes
React Flow nodes can break when handles, edges, resizing, and scroll behavior drift apart. This skill gives Claude, Codex, and Claude Code a focused checklist for stable workflow node changes.
Coding & Development View
📦
figma-pencil-fsd-tailwind4
73Convert Designs to FSD Tailwind Code
Design handoff often breaks architecture, tokens, and accessibility. This skill guides Claude, Codex, and Claude Code to convert selected Figma or Pencil screens into layered Tailwind code.
Design & Creative View
📦
react-flow-best-practices
72Review React Flow Canvases Safely
React Flow canvases can break when IDs, handles, state ownership, or viewport behavior drift. This skill guides Claude, Codex, and Claude Code through practical @xyflow/react v12 review checks.
Coding & Development View
📦
browser-audit
72Audit Web Pages Before Deployment
Late web issues can block launches and harm accessibility, SEO, or core flows. This skill guides browser checks, Lighthouse interpretation, and structured reporting before release.
Coding & Development View
Related Skills
View all📦
ui-styling
83Build Accessible Tailwind Interfaces
by nextlevelbuilder
Building consistent, responsive interfaces requires many component, styling, and accessibility decisions. This skill provides shadcn/ui patterns, Tailwind guidance, and focused automation.
Design & Creative View
📦
web-accessibility
82Audit Web Accessibility for WCAG Compliance
by 89jobrien
Accessibility gaps can block users and create compliance risk. This skill guides WCAG audits, screen reader checks, keyboard testing, and remediation planning.
Design & Creative View
📦
ux-designer
80Improve UX With Research-Led Design Guidance
by shubhamsaboo
Teams often design flows from assumptions and miss accessibility issues. This skill guides research, structure, interaction design, and review using UX best practices.
Design & Creative View
📦
ui-design
80Design Distinctive UI Prototypes
by tencentcloudbase
Generic AI interfaces often lack visual direction and platform-aware detail. This skill guides Claude, Codex, and Claude Code to define design intent before building prototypes.
Design & Creative View
📦
design-lint
80Check designs with deterministic CSS rules
by cubha
Design reviews can vary between reviewers and slow down delivery. This skill applies repeatable checks to HTML and CSS so teams can catch token, layout, and accessibility issues before release.
Design & Creative View
📦
brand-guidelines
79Apply Anthropic Brand Styling
by ZhanlinCui
Teams often need consistent brand styling across slides, documents, and visual artifacts. This skill provides color, typography, and styling rules that Claude, Codex, and Claude Code can apply.
Design & Creative View