The Code/X ArchiveView on X
Vox

@Voxyz_ai

๐—–๐—ผ๐—ฑ๐—ฒ๐˜… ๐˜๐—ถ๐—ฝ: if you still have half your quota left when it resets, youโ€™re throwing away days of Sol.

Use `/goal` to squeeze every last bit out of it: audit your entire site, map your codebase, speed up your app, or even clear out the half-finished work in your workspace.

Here are 5 copy-paste prompts. โ†“
25589572.2K
Vox

@Voxyz_ai

1/5 ๐—ฅ๐˜‚๐—ป ๐—ฎ ๐—ฐ๐—ผ๐—บ๐—ฝ๐—น๐—ฒ๐˜๐—ฒ ๐—จ๐—œ/๐—จ๐—ซ ๐—ฎ๐˜‚๐—ฑ๐—ถ๐˜ ๐˜„๐—ถ๐˜๐—ต 3 ๐˜€๐—ธ๐—ถ๐—น๐—น๐˜€

/goal Launch the real site for this project and use the three skills below to audit and improve it:

โ†’ `$ux-audit`: click, type, and complete the core flows like a real user. Find anything confusing, hard to use, or simply broken.

โ†’ `$impeccable`: review the visual hierarchy, typography, spacing, component consistency, mobile experience, and every important UI state.

โ†’ `$transitions-dev`: review the existing motion and add the right transitions wherever feedback or a state change needs to feel clearer.

First check whether all three skills are available. If one is missing, use the skill installer to install it from the original source, load it, and continue.

If `$ux-audit` is marked Claude Code-only and canโ€™t be called directly, read its `SKILL.md` and follow its interaction-first workflow.

Start with `$ux-audit` to walk through the entire product. Then use `$impeccable` to fix the visual and UX issues. Finish with `$transitions-dev` to review dropdowns, modals, tabs, loading, success, error, and other state changes.

Donโ€™t stop at a report. Fix the issues, then run through the core flows again.

Finish with:

โ†’ Desktop and mobile before/after screenshots
โ†’ The 5 most important improvements
โ†’ Anything still unresolved
โ†’ A final version I can open and test
1244121
End of thread