Skills baseline-ui
๐Ÿ“ฆ

baseline-ui

Content revision r2 Safe โš™๏ธ External commands๐ŸŒ Network access

Refine Interface Code with a Clear UI Baseline

Inconsistent interface code creates visual, accessibility, and performance problems. This skill reviews UI work against focused rules and recommends concrete improvements.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "baseline-ui" from https://skillstore.io/skills/ibelick-baseline-ui.md and its manifest at https://skillstore.io/api/skills/ibelick-baseline-ui/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 "baseline-ui". Review the checkout confirmation dialog.

Expected outcome:

  • The destructive action uses a generic modal instead of an alert dialog.
  • This weakens focus handling and confirmation semantics.
  • Replace it with the project's accessible alert dialog primitive.

Using "baseline-ui". Review the dashboard loading transition.

Expected outcome:

  • The transition animates width and lasts 450 milliseconds.
  • Use opacity or transform and keep interaction feedback under 200 milliseconds.
  • Disable or reduce the motion for users who prefer reduced motion.

Using "baseline-ui". Review the analytics table.

Expected outcome:

  • The numeric columns use proportional figures, which makes values harder to compare.
  • Apply tabular numerals and truncate dense labels where space is limited.
  • Use the established z-index scale for sticky controls.

Security Audit

Safe
v6 โ€ข 7/23/2026 Open versioned report

All 30 static findings are false positives caused by Markdown inline code, a documentation hyperlink, and ordinary UI terminology. SKILL.md contains frontend review guidance without executable scripts, network requests, system reconnaissance, credential access, or prompt injection. No semantic security findings were identified.

1
Files scanned
86
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/ibelick-baseline-ui/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/ibelick-baseline-ui/security.svg)](https://skillstore.io/skills/ibelick-baseline-ui?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/ibelick-baseline-ui?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/ibelick-baseline-ui/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/ibelick-baseline-ui.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

ibelick. (2026). baseline-ui security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/ibelick-baseline-ui/audits/6

BibTeX citation

@techreport{ibelick-ibelick-baseline-ui-2026, author = {ibelick}, title = {baseline-ui security audit report (audit version 6)}, institution = {Skillstore}, year = {2026}, number = {6}, url = {https://skillstore.io/skills/ibelick-baseline-ui/audits/6}, 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: "baseline-ui security audit report (audit version 6)" version: "unspecified" type: report authors: - name: "ibelick" date-released: "2026-07-23" url: "https://skillstore.io/skills/ibelick-baseline-ui/audits/6" identifiers: - type: other value: "skillstore:ibelick-baseline-ui:audit:6" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Clean up a feature

Review a new interface before merging and receive focused corrections for layout, typography, interaction, and performance.

Enforce component consistency

Compare feature code with established primitives, theme tokens, sizing rules, and layering conventions.

Prepare an accessibility review

Identify likely issues with keyboard behavior, focus management, labels, destructive actions, and reduced motion.

Try These Prompts

Quick page review
Apply the baseline UI rules to this page. List important violations, explain each impact, and propose concise fixes.
Focused file review
Review [file path] against every baseline UI constraint. Quote each relevant snippet, explain the issue, and give a code-level correction.
Accessibility and motion pass
Audit [component files] for accessible primitives, focus behavior, destructive actions, motion performance, and reduced-motion support. Prioritize fixes by user impact.
System-wide consistency review
Compare [feature files] with the existing component system and theme. Identify baseline violations, cross-file inconsistencies, and a staged remediation plan.

Best Practices

  • Provide targeted files and describe the intended user flow before requesting a review.
  • Share the project's component library, theme rules, and intentional exceptions.
  • Validate recommendations in the rendered interface, including keyboard and reduced-motion testing.

Avoid

  • Do not apply every rule blindly when project requirements document a valid exception.
  • Do not mix component primitive libraries within one interaction surface.
  • Do not add motion, gradients, or custom styling without a clear product requirement.

Frequently Asked Questions

Which frameworks does this skill support?
Its guidance favors React and Tailwind CSS, but many accessibility, layout, typography, and performance rules apply to other frontend stacks.
Can this skill edit interface code?
Yes. Ask for concrete fixes after providing the relevant files and project conventions.
Does this skill require network access?
No. The skill includes one documentation link but does not require network requests.
Can it review an entire project?
It can review multiple files, but targeted features produce clearer findings and more practical recommendations.
Does it replace accessibility testing?
No. It promotes accessible patterns, but keyboard, screen reader, contrast, and browser testing remain necessary.
Will it add animations automatically?
No. Its rules prohibit new animation unless the user explicitly requests it.

Developer Details

Author

ibelick

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

c43861a65bb95efcae259cd161c9d6f4dc7eec6f

Maintenance freshness

7/25/2026

Usage

29 downloads ยท 133 views

File structure

๐Ÿ“„ SKILL.md

More from ibelick

View all
View all