Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Final quality pass before shipping. An agent skill from boussadjra/vuestrata.
Install I Polish
$ npx skills add boussadjra/vuestrata --skill i-polish -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boussadjra/vuestrata i-polish --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/boussadjra/vuestrata.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/i-polish .claude/skills/i-polish && 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 "i-polish" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-polish into .claude/skills/i-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-polish", 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/boussadjra/vuestrata/tree/main/.github/skills/i-polishType 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 boussadjra/vuestrata --skill i-polish -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boussadjra/vuestrata i-polish --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/i-polish .agents/skills/i-polish && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "i-polish" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-polish into .agents/skills/i-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-polish", 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 boussadjra/vuestrata --skill i-polish -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boussadjra/vuestrata i-polish --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/i-polish .cursor/skills/i-polish && 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 "i-polish" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-polish into .cursor/skills/i-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-polish", 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/boussadjra/vuestrata.git --path .github/skills/i-polish--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 boussadjra/vuestrata --skill i-polish -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boussadjra/vuestrata i-polish --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/i-polish .gemini/skills/i-polish && 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 "i-polish" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-polish into .gemini/skills/i-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-polish", 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 boussadjra/vuestrata i-polishInstalls 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 boussadjra/vuestrata --skill i-polish -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/i-polish .github/skills/i-polish && 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 "i-polish" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-polish into .github/skills/i-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-polish", 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 boussadjra/vuestrata --skill i-polish -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boussadjra/vuestrata i-polish --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/i-polish .opencode/skills/i-polish && 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 "i-polish" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-polish into .opencode/skills/i-polish/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-polish", 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
i-polish- GitHub stars
- 111
- Used in
- 12 other repos
- Token cost
- ~1.9k tokens
- SKILL.md length
- 944 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Final quality pass before shipping. An agent skill from boussadjra/vuestrata.
- Works in 2 steps: Review completeness → Identify polish areas
- Frontend & Design work in your project
- SKILL.md covers Pre-Polish Assessment, Polish Systematically, Polish Checklist and Final Verification
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
I Polish is an agent skill from boussadjra/vuestrata. Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. The repository describes itself as: An opinionated Vue application foundation with enforced architecture, generators, and 12 distinct design personalitie. The licence is MIT.
When your agent uses it
- Frontend & Design work in your project
Example prompts
- “/i-polish”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Review completeness
- Identify polish areas
What it can do on your machine
Read from SKILL.md and the folder at commit 73cbf9f. 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.
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
I Polish loads about 1.9k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 944 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 boussadjra/vuestrata at commit 73cbf9f, republished under its MIT licence (© boussadjra). 944 words, ~1,943 tokens.
Download SKILL.mdSave it as
.claude/skills/i-polish/SKILL.md (or your agent's skills folder).- name
- i-polish
- description
- Final quality pass before shipping. Fixes alignment, spacing, consistency, and detail issues that separate good from great.
- user-invokable
- true
- argument-hint
- TARGET=<value>
First: Use the i-frontend-design skill for design principles and anti-patterns.
Perform a meticulous final pass to catch all the small details that separate good work from great work. The difference between shipped and polished.
Pre-Polish Assessment
Understand the current state and goals:
Review completeness:
- Is it functionally complete?
- Are there known issues to preserve (mark with TODOs)?
- What's the quality bar? (MVP vs flagship feature?)
- When does it ship? (How much time for polish?)
Identify polish areas:
- Visual inconsistencies
- Spacing and alignment issues
- Interaction state gaps
- Copy inconsistencies
- Edge cases and error states
- Loading and transition smoothness
CRITICAL: Polish is the last step, not the first. Don't polish work that's not functionally complete.
Polish Systematically
Work through these dimensions methodically:
Visual Alignment & Spacing
- Pixel-perfect alignment: Everything lines up to grid
- Consistent spacing: All gaps use spacing scale (no random 13px gaps)
- Optical alignment: Adjust for visual weight (icons may need offset for optical centering)
- Responsive consistency: Spacing and alignment work at all breakpoints
- Grid adherence: Elements snap to baseline grid
Check:
- Enable grid overlay and verify alignment
- Check spacing with browser inspector
- Test at multiple viewport sizes
- Look for elements that "feel" off
Typography Refinement
- Hierarchy consistency: Same elements use same sizes/weights throughout
- Line length: 45-75 characters for body text
- Line height: Appropriate for font size and context
- Widows & orphans: No single words on last line
- Hyphenation: Appropriate for language and column width
- Kerning: Adjust letter spacing where needed (especially headlines)
- Font loading: No FOUT/FOIT flashes
Color & Contrast
- Contrast ratios: All text meets WCAG standards
- Consistent token usage: No hard-coded colors, all use design tokens
- Theme consistency: Works in all theme variants
- Color meaning: Same colors mean same things throughout
- Accessible focus: Focus indicators visible with sufficient contrast
- Tinted neutrals: No pure gray or pure black—add subtle color tint (0.01 chroma)
- Gray on color: Never put gray text on colored backgrounds—use a shade of that color or transparency
Interaction States
Every interactive element needs all states:
- Default: Resting state
- Hover: Subtle feedback (color, scale, shadow)
- Focus: Keyboard focus indicator (never remove without replacement)
- Active: Click/tap feedback
- Disabled: Clearly non-interactive
- Loading: Async action feedback
- Error: Validation or error state
- Success: Successful completion
Missing states create confusion and broken experiences.
Micro-interactions & Transitions
- Smooth transitions: All state changes animated appropriately (150-300ms)
- Consistent easing: Use ease-out-quart/quint/expo for natural deceleration. Never bounce or elastic—they feel dated.
- No jank: 60fps animations, only animate transform and opacity
- Appropriate motion: Motion serves purpose, not decoration
- Reduced motion: Respects
prefers-reduced-motion
Content & Copy
- Consistent terminology: Same things called same names throughout
- Consistent capitalization: Title Case vs Sentence case applied consistently
- Grammar & spelling: No typos
- Appropriate length: Not too wordy, not too terse
- Punctuation consistency: Periods on sentences, not on labels (unless all labels have them)
Icons & Images
- Consistent style: All icons from same family or matching style
- Appropriate sizing: Icons sized consistently for context
- Proper alignment: Icons align with adjacent text optically
- Alt text: All images have descriptive alt text
- Loading states: Images don't cause layout shift, proper aspect ratios
- Retina support: 2x assets for high-DPI screens
Forms & Inputs
- Label consistency: All inputs properly labeled
- Required indicators: Clear and consistent
- Error messages: Helpful and consistent
- Tab order: Logical keyboard navigation
- Auto-focus: Appropriate (don't overuse)
- Validation timing: Consistent (on blur vs on submit)
Show full SKILL.md (400 more words)Show less
Edge Cases & Error States
- Loading states: All async actions have loading feedback
- Empty states: Helpful empty states, not just blank space
- Error states: Clear error messages with recovery paths
- Success states: Confirmation of successful actions
- Long content: Handles very long names, descriptions, etc.
- No content: Handles missing data gracefully
- Offline: Appropriate offline handling (if applicable)
Responsiveness
- All breakpoints: Test mobile, tablet, desktop
- Touch targets: 44x44px minimum on touch devices
- Readable text: No text smaller than 14px on mobile
- No horizontal scroll: Content fits viewport
- Appropriate reflow: Content adapts logically
Performance
- Fast initial load: Optimize critical path
- No layout shift: Elements don't jump after load (CLS)
- Smooth interactions: No lag or jank
- Optimized images: Appropriate formats and sizes
- Lazy loading: Off-screen content loads lazily
Code Quality
- Remove console logs: No debug logging in production
- Remove commented code: Clean up dead code
- Remove unused imports: Clean up unused dependencies
- Consistent naming: Variables and functions follow conventions
- Type safety: No TypeScript
anyor ignored errors - Accessibility: Proper ARIA labels and semantic HTML
Polish Checklist
Go through systematically:
- Visual alignment perfect at all breakpoints
- Spacing uses design tokens consistently
- Typography hierarchy consistent
- All interactive states implemented
- All transitions smooth (60fps)
- Copy is consistent and polished
- Icons are consistent and properly sized
- All forms properly labeled and validated
- Error states are helpful
- Loading states are clear
- Empty states are welcoming
- Touch targets are 44x44px minimum
- Contrast ratios meet WCAG AA
- Keyboard navigation works
- Focus indicators visible
- No console errors or warnings
- No layout shift on load
- Works in all supported browsers
- Respects reduced motion preference
- Code is clean (no TODOs, console.logs, commented code)
IMPORTANT: Polish is about details. Zoom in. Squint at it. Use it yourself. The little things add up.
NEVER:
- Polish before it's functionally complete
- Spend hours on polish if it ships in 30 minutes (triage)
- Introduce bugs while polishing (test thoroughly)
- Ignore systematic issues (if spacing is off everywhere, fix the system)
- Perfect one thing while leaving others rough (consistent quality level)
Final Verification
Before marking as done:
- Use it yourself: Actually interact with the feature
- Test on real devices: Not just browser DevTools
- Ask someone else to review: Fresh eyes catch things
- Compare to design: Match intended design
- Check all states: Don't just test happy path
Remember: You have impeccable attention to detail and exquisite taste. Polish until it feels effortless, looks intentional, and works flawlessly. Sweat the details - they matter.
© boussadjra, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/i-polish of boussadjra/vuestrata.
Open the folder on GitHubat commit 73cbf9f
Used in 12 other repositories
We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 12 other GitHub owners. This page covers the copy in boussadjra/vuestrata, which our catalogue first saw on October 7, 2026.
- sudomakes/backroad.agents/skills/polish
- growupanand/ConvoForm.agents/skills/polish
- mims-harvard/OptimusKG.agents/skills/polish
- zhushen12580/smart-screenshot.agents/skills/polish.claude/skills/polish
- zacharyfmarion/openscad-studio.agents/skills/polish
- nexmoe/eve.agents/skills/polish
- netaart/cohub.agents/skills/polish
- AkaraChen/aghub.agents/skills/polish
- owshq-mec/semana-ai-data-engineer.claude/skills/polish
- ucsandman/marketing-studioskills/polish
- theexperiencecompany/gaia.agents/skills/polish.claude/skills/polish
- aiskillstore/marketplaceskills/pbakaus/polish
Compare with similar skills
I Polish 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 |
|---|---|---|---|---|---|---|
| I Polish this skillboussadjra/vuestrata | 111 | 12 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
- Official
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
More from boussadjra/vuestrata
All 21 skills in this repoI Delight
boussadjra/vuestrata
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use.
I Optimize
boussadjra/vuestrata
Improve interface performance across loading speed, rendering, animations, images, and bundle size.
I Frontend Design
boussadjra/vuestrata
Create distinctive, production-grade frontend interfaces with high design quality.
I Harden
boussadjra/vuestrata
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management.
I Onboard
boussadjra/vuestrata
Design or improve onboarding flows, empty states, and first-time user experiences.
I Teach Impeccable
boussadjra/vuestrata
One-time setup that gathers design context for your project and saves it to your AI config file.
Related
Categories
Questions about I Polish
What does I Polish do?
Final quality pass before shipping. An agent skill from boussadjra/vuestrata. I Polish is an agent skill from boussadjra/vuestrata. Final quality pass before shipping.
When should I use I Polish?
I Polish fits situations like: frontend & Design work in your project.
How do I install I Polish in Claude Code?
Run `npx skills add boussadjra/vuestrata --skill i-polish -a claude-code`. Or copy the skill folder (.github/skills/i-polish in boussadjra/vuestrata) into .claude/skills/i-polish in your project. Claude Code loads it when a task matches its description.
How do I install I Polish in Codex?
Run `npx skills add boussadjra/vuestrata --skill i-polish -a codex`. Or copy the skill folder (.github/skills/i-polish in boussadjra/vuestrata) into .agents/skills/i-polish in your project. Codex loads it when a task matches its description.
Can I use I Polish 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 boussadjra/vuestrata --skill i-polish -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/i-polish, .gemini/skills/i-polish, .github/skills/i-polish and .opencode/skills/i-polish in your project.
What does I Polish need to run?
SKILL.md names no scripts, command-line tools or credentials: I Polish is instructions for the agent only.
Does I Polish 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 I Polish 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 I Polish use?
I Polish is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does I Polish use?
About 1.9k tokens (SKILL.md is roughly 7.8k 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 I Polish?
Skills that share tags, products or a category with I Polish: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains I Polish?
boussadjra (a GitHub user) maintains it in boussadjra/vuestrata, which has 111 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 5, 2026.
Source: boussadjra/vuestrata on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.