Polish + export a brepjs part
SkillDev toolsPolish gives your AI design guidance so the interfaces and layouts it creates look better. Instead of guessing at visual choices, your agent follows a clear design language. The result is screens that look more considered from the start.
Use Polish + export a brepjs part in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Polish + export a brepjs part and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Polish + export a brepjs part skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add the skill, then ask your AI to build or improve an interface. It will apply the design guidance as it works.
What your AI can do with it
- Build interfaces that look more polished
- Arrange layouts so screens read more cleanly
- Apply one consistent design language across the UI it creates
- Make stronger visual choices when designing new screens
What this skill tells your AI
The instructions your AI receives, as published by andymai/brepjs in packages/brepjs-cad/skills/polish/SKILL.md and read by Ahel’s review.
A valid part is not always a designed part. A lumpy stack of overlapping primitives still reports
ok:true, so validity never catches it. Run this when the part should look manufactured; skip it
for purely functional/internal geometry. The CLI ships in the brepjs-cad package as brep.
Polish pass
Render iso + a detail view (brep snapshot part.brep.ts) and critique: manufactured, or
glued-from-primitives? Fix the worst offender:
- a primitive-blob (two solids doing one feature's job),
- a mismatched cap,
- raw sharp rims.
Prefer additive detail — fins, gussets, lightening holes, grooves, a flush rounded end — over
the failure-prone fillet/chamfer ops. Re-verify (ok stays true), re-render, repeat on the next
worst offender. Detail and rationale: references/design-polish.md.
A no-op is a valid outcome. If the part already reads as manufactured, the worst remaining offender is minor, or the only available edit is marginal, make NO edit, report the part as already-designed, and proceed to export. A marginal addition usually ties or loses against the un-touched render (it reads as decoration noise) — do not edit just to satisfy the loop. Only edit when the offender is a clear primitive-blob, mismatched cap, raw rim, or missing functional feature a human would notice.
A polish edit must never break validity: if a round/blend pushes the part to ok:false, revert it
and choose an additive alternative.
Export + hand off
brep verify part.brep.ts --step part.step
STEP is the validated primary deliverable; GLB/STL are derived. Batch behind a validity gate with
brep export part.brep.ts --all. --serve prints a clickable link to an interactive inspector
(view presets, solid/wire/x-ray, face picking, section plane, measurements) for the human to eyeball
— report that URL. Under agent/CI (non-TTY) auto-open is suppressed automatically. Report the STEP
path. Export formats and options: references/export.md.
Signals
- GitHub stars
- 113
- Forks
- 9
- Last commit
- Sep 2026
- Hacker News mentions
- 20
Advanced
- Item type
- skill
- Key
polish- Source
- github.com/andymai/brepjs