geometric-design
Skill0 starsChanged 29 days agoMITView on GitHub
Plan and inspect geometric logos, nested compositions, UI proportions, and source-backed audits in ChatGPT WebUI; probe actual runtime/renderer capabilities, distinguish exact from inferred φ, and produce verifiable handoffs rather than invented test passes.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AVANT-ICONIC/skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- AVANT-ICONIC/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- anti-sloprushSkill
- dev-modeSkill
- game-conceptSkill
- intent-modeSkill
- openspec-workflowSkill
- plan-modeSkill
- seo-aiseoSkill
- spec-modeSkill
- video-watchSkill
- visual-chatSkill
- visual-gauntletSkill
- visual-prototypeSkill
The file
Files
Geometric Design · WebUI
EXPERIMENTAL ALPHA technical preview. Supported technical workflow only. No independent blind recognition review or matched-agent creative-uplift proof (T3/T4 NOT_EVALUATED).
Read bundled canonical policy first. This skill works with this folder alone. It never assumes the portable engine, a Node process, a browser or an image renderer is available in the ChatGPT session.
Specialist routing
- Symbol construction / repair: lock user geometry and reference; check connected foreground, counters and true source circle-vs-ellipse semantics. The current portable engine supports only a bounded inert SVG subset and white-painted, not transparent, counters.
- Composition: preserve hierarchy and reading order, create genuinely different region-tree families unless exact reference fidelity is requested; name intentional φ/diagonal relationships rather than decorating with post-hoc golden overlays.
- Standalone source audit: report actual source digest, field-linked metrics and declared constraints. A visual match to φ without source provenance is inferred, never established design intent. No automatic modification of approved artwork.
- Responsive UI tokens: bounded ratio-based typography, spacing, modal sizes and touch targets; content at 320/390/768/1280/1920 and 200% text takes precedence over ratios; verify actual browser output if possible.
- Grammar and QA: enforce split/align/focal/safe-zone/rhythm/vary rules and distinguish mathematical, pixel, accessibility and human-creative evidence. Owner-approved Spacing Option 0 preserves existing CSS. The composition contract now references the shipped rem-based
gap-cardtoken (~12.944px at root16; ~25.888px at root32); a declared model is not a measured browser layout.
Capabilities and handoff
Probe tools and permissions actually available: source bytes/file hashes, Node.js 22+, optional installed free Inkscape/browser, screenshot inspection and repo access. Only report what really executed. Do not inspect sealed private holdouts, confidential project art, or credentials without explicit separate authorization. Without a runnable engine, present scope/constraints and a concrete local-agent handoff, never a fabricated CLI log or visual PASS:
- Source file, revision/digest and relevant private-data boundaries.
- Frozen layout/logo reference, expected geometry, supported and unsupported features, exact proposed versus owner-approved changes.
- Portable skill install source:
AVANT-ICONIC/skills/geometric-design/(a separate install, not implicitly available here). - Command(s), input/output paths, renderer viewports/sizes and actual required verification evidence.
- Open blockers and exact next operation; no automatic source overwrite, release or merge.
A real imported PNG alone offers pixel-visible measurements but not exact original vector radii. Real screenshots and browser interaction are required for render/functional acceptance; independent human judgement is required for recognizability claims. Existing presentation and single-agent quality skills keep their own responsibilities. No paid API, autonomous background work or Universal Gauntlet integration.
The vendored shared policy is pinned by sync-manifest.json; run node verify-sync.mjs when Node 22+ exists. Actual canonical cross-repo comparison uses the manifest's immutable portable-source commit, never an unverified floating branch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.