Maintainer of this skill?
Skills de Claude Code da Visant: auditoria de UI anti-slop, motion, frontend, copy. Com detectores executáveis.
# Add to your Claude Code skills
git clone https://github.com/pedrojaques99/visant-skills-publicGuides for using ai agents skills like visant-skills-public.
See how visant-skills-public compares with popular alternatives.
visant-skills-public is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by pedrojaques99. Skills de Claude Code da Visant: auditoria de UI anti-slop, motion, frontend, copy. Com detectores executáveis. It has 50 GitHub stars.
visant-skills-public's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/pedrojaques99/visant-skills-public" and add it to your Claude Code skills directory (see the Installation section above).
visant-skills-public is primarily written in JavaScript. It is open-source under pedrojaques99 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh visant-skills-public against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Claude Code skills from
Visant: how to decide interface, motion and copy, how
to audit a screen before the PR, and how to cut video, from a recorded website
to a Premiere rough cut. They work in any repo: each skill first discovers what
the target repo already has (gates, primitives, tokens) and only then acts. The
detectors are real scripts, and npm test proves every rule both ways against
fixtures.
npx skills add pedrojaques99/visant-skills-public # pick from the list
npx skills add pedrojaques99/visant-skills-public --skill visant-killer # just one
Or copy a skill folder into ~/.claude/skills/. Then just ask, in English or
Portuguese: "audit this screen", "tá com cara de IA", "make this smoother",
"edit this lesson".
A typical AI pricing card, in a shadcn project with no design lint of its own:
<section className="border rounded-2xl p-8">
<span className="font-mono text-xs uppercase tracking-widest text-white/50">01 / Pricing</span>
<h1 className="text-5xl font-serif tracking-tighter">Design that <em>converts</em></h1>
<p className="text-white/70">Unlock your full potential — a revolutionary way to ship.</p>
<div className="border rounded-xl p-4 text-purple-500">
<span className="text-white/40">per month</span>
<span className="text-white/90">$49</span>
</div>
</section>
$ node visant-killer/scripts/killer-scan.mjs demo/src
[OK] impeccable (AI tell) zero
[FAIL] audit:design (token) 1 finding(s)
src/Pricing.tsx:7 tailwind-palette <div className="border rounded-xl p-4 text-purple-500">
via killer-scan built-in FALLBACK; token layer found (shadcn components.json): palette classes bypass it
[FAIL] copy (tic) 2 finding(s)
src/Pricing.tsx:6 em-dash
src/Pricing.tsx:6 en-hype
[FAIL] noise (chrome) 3 finding(s)
src/Pricing.tsx:5 italic-headline-word <em> italic inside <h1> headline
src/Pricing.tsx:5 display-serif-tight display serif + negative tracking
src/Pricing.tsx:4 opacity-ladder text-white: /50 /70 /40 /90
gates: 4/4 ran [impeccable, audit:design (fallback), copy, noise]; none skipped
GATE CLOSED: 3 detector(s) with findings. A gate finding becomes a fix, not a proposal.
That is only the script half. The skill then judges what no detector sees (does each element move a business variable?), opens the screen in a browser, argues against its own verdict and scores the result.
Every detector was run, from outside, on three public Next.js projects with no Visant code, then calibrated until what remained was defensible:
| Repo | Token gate | Noise gate | Distribution |
|---|---|---|---|
| vercel/commerce | passes: no token layer, Tailwind palette used as the design system (3 neutral, 3 accent hues) | 2: hover-lift on a product image and gallery buttons |
1 LOW: checkout hands off to Shopify, no begin_checkout event |
| shadcn-ui/taxonomy | 9: palette classes that bypass its CSS-variable tokens (text-red-600, bg-slate-50) |
2: a hand-drawn lucide Shield while lucide-react is installed; "Enter your email below…" |
1 HIGH (public routes without description), a route without title, no sitemap |
| steven-tey/precedent | 4 raw hex (Twitter blue as a one-off class, a gauge circle) + 1 palette-chaos finding (4 accent hues) | 2: the Vercel triangle, a CTA that grows on hover | clean |
What the calibration fixed, so it holds on any repo: palette classes only count
as a bypass when there is a token layer to bypass; SVGs in an icons/ folder
and brand logos are not "hand-drawn icons"; components are never routes; a
hosted checkout is not an unmeasured form. Each fix is locked by a fixture.
| Skill | What it does | Needs |
|---|---|---|
visant-killer |
Start here. Anti-slop UI audit: detectors as a hard gate, judgment through the skills below, a devil's advocate pass and a score | Node 20+; Playwright optional (screen checks) |
visant-frontend |
Interface decisions: every element names the business variable it moves, or it goes | nothing |
visant-motion |
Easing/duration tokens for CSS and framer-motion, motion-lint, URL measurement |
Node 20+ |
visant-refine |
Charts, gauges, sparklines, sliders and metric tiles with one shared anatomy | Node 20+ |
visant-copy |
Brazilian Portuguese copy in a spoken voice, with copy-lint against AI tells in PT and English copy |
Node 20+ |
| Skill | What it does | Needs |
|---|---|---|
site-reels |
Records a website's best scenes (WebGL hero, scroll, 3D) as 1080p MP4 and builds brand or product showreels in Remotion | Chrome or Edge, ffmpeg, Node |
visant-premiere-editor |
Builds the rough cut in Premiere Pro from a JSON cut plan: frame-exact cuts, markers, punch-ins, cards, b-roll, -14 LUFS delivery | Premiere Pro + premiere-pro-mcp, Python |
visant-video-editor |
Vlogs, event videos and lessons from raw footage: breakdown, silence cuts that never clip a word, loudness, chapters | bash, ffmpeg, Python, faster-whisper |
| Skill | What it does | Needs |
|---|---|---|
visant-methodology |
Visant's 9-stage brand-building method and the dependency cascade between stages | nothing |
visant-preflight |
Preflight for a big project: one question round plus five premise checks (source of truth, fonts, photo resolution, brand files, sourced numbers) | Node 20+ |
visant-mcp-connect |
Connects and runs the Visant Labs MCP | a Visant Labs account |
Each SKILL.md opens with its exact requirements and how to check them.
The interface skills look for a finished piece before writing one:
@visant/ui, 150+ React components in a shadcn
registry, already through visant-killer. The code lands in your project; it
is not an npm package.
# components.json → "registries": { "@visant": "https://ui.visantlabs.com/r/{name}.json" }
npx shadcn@latest add @visant/gauge
Index for agents: ui.visantlabs.com/llms.txt.
Node 20+, no build step.
npm install
npm test # every detector's self-test, both ways
node visant-killer/scripts/killer-scan.mjs <app/src> # the whole gate, from any folder
node visant-motion/scripts/motion-lint.mjs <app>
node visant-copy/scripts/copy-lint.mjs <file-or-folder>
bash visant-video-editor/scripts/self-test.sh # needs ffmpeg
Much of this stands on other people's work. Each skill credits its sources in its own text; the summary:
| What | By | Used in |
|---|---|---|
| impeccable | Paul Bakaus (pbakaus/impeccable) | visant-killer gate |
| revenue-centric-design | principles by Richard (@richardrx), packaged by heliocosta-dev | visant-frontend, visant-killer |
| Emil Kowalski skills | Emil Kowalski (animations.dev) | visant-motion principles |
agent-skills (vercel-react-view-transitions) |
Vercel | visant-motion |
| premiere-pro-mcp | premiere-pro-mcp contributors | visant-premiere-editor |
| OpenTimelineIO | Academy Software Foundation | visant-premiere-editor (FCP7 XML) |
| Simple Icons (CC0) | Simple Icons contributors; marks belong to their owners | visant-premiere-editor card logos |
| Remotion, puppeteer-screen-recorder, timesnap | Remotion; prasanaworld; Tungs | site-reels |
| FFmpeg, auto-editor, faster-whisper | FFmpeg; WyattBlue; SYSTRAN | visant-video-editor |
| shadcn/ui, Radix, Playwright | shadcn; WorkOS; Microsoft | visant-killer, visant-frontend |
Slop signals 47–57 in the killer's catalog are by Pedro Jaques. Missing someone? Open an issue.
This repo is the source: these skills live nowhere else. Every commit passes a gate that blocks client names and a secret scanner (gitleaks); real client cases appear anonymized ("client K"). PRs welcome.
node link.mjs # Windows: which ~/.claude/skills folders already point here
node link.mjs --apply # point them here with junctions (needs a clean git tree)
MIT, see LICENSE. Third-party tools and skills credited above keep their own licenses.