Design Direction
Choose an intentional, non-template visual direction (style, palette, type, motion) BEFORE writing any UI. Use at the start of a new site/page or when output looks generic. Enforces the anti-template policy.
Install
$ agentstack add skill-m-binimran-dev-pack-design-direction ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-m-binimran-dev-pack-design-direction) 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
design-direction
The fastest way to ship template-looking UI is to start coding without a direction. Don't.
Do this first
- Pick a named direction — editorial/magazine, neo-brutalism, glass-with-real-depth, dark or light
luxury, bento, scrollytelling, Swiss/International, retro-futurism. NOT "clean minimal." NOT auto dark mode.
- Palette intentionally: a base, 1–2 surfaces, a semantic accent (success/warn/danger), and ONE
brand-defining color used with purpose. Define as Tailwind v4 @theme tokens (hand to theme-tokens).
- Type pairing: a display/heading face with character + a readable body face. State the pairing and why.
- Reference set: name 2–3 real sites/products this should feel like.
- Motion intent: how motion clarifies this product (subtle micro vs. cinematic scroll). Hand to
animation-implement.
Output
- A short "direction brief": style name, palette tokens, type pairing, references, motion intent.
- This brief is the contract the rest of the build is judged against.
Guardrails (anti-template)
- Every surface must show ≥4 of: scale hierarchy, spacing rhythm, depth/layering, real type, semantic color,
designed interaction states, grid-breaking composition, texture, purposeful motion, designed data viz.
- Final gut check: "would this look believable in a real product screenshot?" If no, iterate before building more.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: m-binimran
- Source: m-binimran/dev-pack
- License: MIT
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.