Skip to content
skillsafebeta
← Report library
Purpose / Development

Baseline Ui Skill Security Audit

What the author says it does (original text)

Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.

Independent security check

No obvious risks found in this check

Files checked
1
Risks found
0
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.No risks found
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

8 instruction sections

This Skill is a rule set for polishing and reviewing UI code. Without a file argument, it applies the rules to UI work in the current conversation; with a file argument, it reports exact violations, a short reason, and a code-level fix suggestion.

View source
SKILL.md:12In the instructionsOpen original file
- `/baseline-ui`  Apply these constraints to any UI work in this conversation.- `/baseline-ui <file>`  Review the file against all constraints below and output:  - violations (quote the exact line/snippet)  - why it matters (1 short sentence)  - a concrete fix (code-level suggestion)

The rules prioritize existing project primitives, require accessible primitives for keyboard or focus behavior, and call for a confirmation dialog around destructive or irreversible actions.

View source
SKILL.md:30In the instructionsOpen original file
- MUST use accessible component primitives for anything with keyboard or focus behavior (`Base UI`, `React Aria`, `Radix`)- MUST use the project’s existing component primitives first- NEVER mix primitive systems within the same interaction surface- SHOULD prefer [`Base UI`](https://base-ui.com/react/components) for new primitives if compatible with the stack- MUST add an `aria-label` to icon-only buttons- NEVER rebuild keyboard or focus behavior by hand unless explicitly requested
SKILL.md:39In the instructionsOpen original file
- MUST use an `AlertDialog` for destructive or irreversible actions- SHOULD use structural skeletons for loading states- NEVER use `h-screen`, use `h-dvh`- MUST respect `safe-area-inset` for fixed elements- MUST show errors next to where the action happens- NEVER block paste in `input` or `textarea` elements

The Skill places conservative limits on animation and visual styling, such as adding animation or gradients only when explicitly requested and accounting for reduced-motion preferences.

View source
SKILL.md:48In the instructionsOpen original file
- NEVER add animation unless it is explicitly requested- MUST animate only compositor props (`transform`, `opacity`)- NEVER animate layout properties (`width`, `height`, `top`, `left`, `margin`, `padding`)- SHOULD avoid animating paint properties (`background`, `color`) except for small, local UI (text, icons)- SHOULD use `ease-out` on entrance- NEVER exceed `200ms` for interaction feedback- MUST pause looping animations when off-screen- SHOULD respect `prefers-reduced-motion`- NEVER introduce custom easing curves unless explicitly requested- SHOULD avoid animating large images or full-screen surfaces
SKILL.md:79In the instructionsOpen original file
- NEVER use gradients unless explicitly requested- NEVER use purple or multicolor gradients- NEVER use glow effects as primary affordances- SHOULD use Tailwind CSS default shadow scale unless explicitly requested- MUST give empty states one clear next action- SHOULD limit accent color usage to one per view- SHOULD use existing theme or Tailwind CSS color tokens before introducing new ones
Start here · InstructionsSKILL.md
baseline-ui
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source. 1 more sections are available in the original file.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions

Operations mentioned in code and instructions

Connect to websites
SKILL.md:33In the instructionsOpen original file
- NEVER mix primitive systems within the same interaction surface- SHOULD prefer [`Base UI`](https://base-ui.com/react/components) for new primitives if compatible with the stack- MUST add an `aria-label` to icon-only buttons
Lines read
86
File checksum (to compare versions)
ce4fecc1a2c2bbffe5f18060da0a9868a9056cb6f0935b1d1534ed17bcb4fb36