Install
$ agentstack add skill-arnie016-codex-prompt-templates-open-design-ui-library ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
OpenDesign UI Library
Goal: use proven product design systems and craft rules from sources/open-design before inventing UI styling.
When To Use
- Building a new page, app, dashboard, mobile flow, deck, or marketing surface.
- Improving an existing UI that looks generic, noisy, or "AI-generated."
- Choosing CSS tokens, typography, spacing, component shape, and interaction states.
Workflow
- Identify the product surface: dashboard, SaaS landing, docs, pricing, mobile, content/editorial, or workflow tool.
- If editing an existing app, inspect its local tokens, theme, component
primitives, screenshots, or visual tests before loading external inspiration.
- Read
references/open-design-ui-library.mdand choose one source design system, plus at most one secondary influence. - If the fit is unclear, use the catalog in
references/open-design-ui-library.mdbefore reading source files. - Load only the matching
sources/open-design/design-systems//DESIGN.mdfile and any needed craft file fromsources/open-design/craft/. - Translate the system into local tokens/components instead of copying brand assets, marks, or proprietary copy.
- Apply craft gates before finalizing:
- no default purple/blue gradient hero unless the selected system calls for it
- no emoji feature icons
- no invented metrics
- no filler copy
- visible focus states and labelled inputs for interactive UI
- Validate visually with screenshots when a browser target is available.
Output
Design system used:
Reference files:
Key tokens/components applied:
Existing local design system preserved or mapped:
Craft checks:
Validation:
Skip When
- The user provided a Figma/design spec that must be followed exactly.
- The task is backend, data, CLI, infra, or test-only.
- The requested UI is intentionally unstyled or wireframe-only.
Validation
- The selected design-system reference is named.
- Existing local tokens/components are preserved, or the mapping is stated.
- UI changes are checked in a browser/screenshot when available.
- Accessibility basics are present: focus states, labels, contrast, and non-overlapping text.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Arnie016
- Source: Arnie016/codex-prompt-templates
- License: MIT
- Homepage: https://github.com/Arnie016/codex-prompt-templates
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.