Frontend UI Design System — Tokens, Components & QA
by Stanislav Ivanov
Make shared controls consistent across screens. Consolidate tokens and component states, then check the views they affect.
by Stanislav Ivanov
Make shared controls consistent across screens. Consolidate tokens and component states, then check the views they affect.
by Stanislav Ivanov
Check the files you will publish against your brand guide. Find the export to fix, the rule it breaks and the correction to recheck.
by Stanislav Ivanov
Make supplied copy clearer while keeping its numbers, links and caveats intact. Get the rewrite and a short check against the original.
by Stanislav Ivanov
Find which PR comments need a fix. Check each claim against current code, its contract and a focused reproduction.
by Stanislav Ivanov
Find the declared prerequisite blocking setup: a runtime version, required file or environment name. Get the next repair to hand to its owner.
by Stanislav Ivanov
Catch missing files and broken supported local links before uploading a skill. Recheck the rebuilt release and keep its exact-byte receipt.
by Stanislav Ivanov
Check that staged files match your intended change. Spot missing or extra paths before asking an agent to describe the commit.
by Stanislav Ivanov
Find duplicate and recovery failures before enabling an automation. See what each replay created and what needs fixing.
by Stanislav Ivanov
Turn a bug report into a failure another engineer can rerun, then check the same case after a requested fix.
by Stanislav Ivanov
See what a prompt or context change loses. Compare the same cases for missing facts, citations and output fields.
by Stanislav Ivanov
Close one on-page SEO ticket with exact before and after values. See which local, live and search checks are complete.
by Stanislav Ivanov
Catch broken README and API examples before release. Get the stale line, the evidence and the exact correction.
by Stanislav Ivanov
Check whether one MCP update landed before retrying it. Get the observed result and the next safe action.
by Stanislav Ivanov
Compare supplied search results before and after a change. See clicks, impressions, CTR and the gaps that limit the comparison.
by Stanislav Ivanov
Recheck the same UI states and widths. Export paired results with failed and unfinished checks in view.
by Stanislav Ivanov
Put a real component's difficult states on a local workbench. Repeat the cases and see which layouts or interactions need attention.
by Stanislav Ivanov
Polish one existing screen, keep its design language and behavior, and compare the result at compact and wide sizes.
by Stanislav Ivanov
Find files that differ between your skill folder and release ZIP, then hand over the exact artifact, blocker and next action.
by Stanislav Ivanov
Give one software change a clear quality workflow: decide what to test, follow the evidence and see who owns the next action.