perspective skill | PlugMCP
Skip to content Home / Skills / perspective perspective Design Tools
Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.
Install The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add bergside/awesome-design-skills --skill perspective -a cursor -y Copy Download skill skills/perspective/SKILL.md on GitHub C
check Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose. H
health Audits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review. H
hunt Finds root cause before any fix. Use when something errors, crashes, regresses, or used to work. Not for code review or new features. Questions
How do I install perspective? Download skills/perspective/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does perspective live? The publisher keeps it at https://github.com/bergside/awesome-design-skills.
Which agents can use perspective? Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository. SKILL.md About FAQ
Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.
name: perspective
description: Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.
license: MIT
metadata:
author: typeui.sh
Perspective Design Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Perspective Design.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
This style moves beyond flat design by employing techniques like isometric views, vanishing points, and layered elements to guide the user's attention and create a sense of realism or "spatial" depth.
Style Foundations
plugmcp Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.
PlugMCP, 2026
Visual style: modern, clean, high-contrast
Typography scale: 12/14/16/20/24/32 | Fonts: primary=Poppins, display=Oswald, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
Color palette: primary, neutral, success, warning, danger | Tokens: primary=#00BD7D, secondary=#00BD7D, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
Spacing scale: 4/8/12/16/24/32
Accessibility WCAG 2.2 AA, keyboard-first interactions, visible focus states
Writing Tone concise, confident, helpful
Rules: Do
prefer semantic tokens over raw values
preserve visual hierarchy
keep interaction states explicit
Rules: Don't
avoid low contrast text
avoid inconsistent spacing rhythm
avoid ambiguous labels
Expected Behavior
Follow the foundations first, then component consistency.
When uncertain, prioritize accessibility and clarity over novelty.
Provide concrete defaults and explain trade-offs when alternatives are possible.
Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
Restate the design intent in one sentence before proposing rules.
Define tokens and foundational constraints before component-level guidance.
Specify component anatomy, states, variants, and interaction behavior.
Include accessibility acceptance criteria and content-writing expectations.
Add anti-patterns and migration notes for existing inconsistent UI.
End with a QA checklist that can be executed in code review.
Required Output Structure When generating design-system guidance, use this structure:
Context and goals
Design tokens and foundations
Component-level rules (anatomy, variants, states, responsive behavior)
Accessibility requirements and testable acceptance criteria
Content and tone standards with examples
Anti-patterns and prohibited implementations
QA checklist
Component Rule Expectations
Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
Describe interaction behavior for keyboard, pointer, and touch.
State spacing, typography, and color-token usage explicitly.
Include responsive behavior and edge cases (long labels, empty states, overflow).
Quality Gates
No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
Every accessibility statement must be testable in implementation.
Prefer system consistency over one-off local optimizations.
Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
Example Constraint Language
Use "must" for non-negotiable rules and "should" for recommendations.
Pair every do-rule with at least one concrete don't-example.
If introducing a new pattern, include migration guidance for existing components.
How do I install perspective? Download skills/perspective/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does perspective live? The publisher keeps it at https://github.com/bergside/awesome-design-skills.
Which agents can use perspective? Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.