Agent skill

Perspective

by bergside in bergside/awesome-design-skills

Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.

MITAuto-check passedFrontend & Design

Install Perspective

skills CLI
$ npx skills add bergside/awesome-design-skills --skill perspective -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bergside/awesome-design-skills perspective --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bergside/awesome-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/perspective .claude/skills/perspective && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
perspective
GitHub stars
3.1k
Used in
1 other repo
Token cost
~904 tokens
SKILL.md length
400 words
Files
2
Skills in repo
67
Repo updated
First seen
Licence
MIT

At a glance

Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.

  • Works in 6 steps: Restate the design intent in one… → Define tokens and foundational… → Specify component anatomy, states,… → …
  • Frontend & Design work in your project
  • SKILL.md covers Mission, Brand, Style Foundations and Accessibility, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Perspective is an agent skill from bergside/awesome-design-skills. Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `DESIGN.md`).

It sits in Frontend & Design. The repository describes itself as: List of 67 awesome DESIGN.md and SKILL.md design skill files for agentic tools like Claude Design, Google Stitch, Codex, Cursor, and other AI tools. The licence is MIT.

When your agent uses it

  • Frontend & Design work in your project

Example prompts

  • “/perspective”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Restate the design intent in one sentence before proposing rules.
  2. Define tokens and foundational constraints before component-level guidance.
  3. Specify component anatomy, states, variants, and interaction behavior.
  4. Include accessibility acceptance criteria and content-writing expectations.
  5. Add anti-patterns and migration notes for existing inconsistent UI.
  6. End with a QA checklist that can be executed in code review.

What it can do on your machine

Read from SKILL.md and the folder at commit f631a09. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Perspective loads about 904 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 400 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~904

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bergside/awesome-design-skills at commit f631a09, republished under its MIT licence (© bergside). 400 words, ~904 tokens.

Download SKILL.mdSave it as .claude/skills/perspective/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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
<!-- TYPEUI_SH_MANAGED_START -->

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

  • 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

  1. Restate the design intent in one sentence before proposing rules.
  2. Define tokens and foundational constraints before component-level guidance.
  3. Specify component anatomy, states, variants, and interaction behavior.
  4. Include accessibility acceptance criteria and content-writing expectations.
  5. Add anti-patterns and migration notes for existing inconsistent UI.
  6. End with a QA checklist that can be executed in code review.
Show full SKILL.md (159 more words)Show less

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.
<!-- TYPEUI_SH_MANAGED_END -->

© bergside, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/perspective of bergside/awesome-design-skills.

  • SKILL.md
  • DESIGN.md

Open the folder on GitHubat commit f631a09

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in bergside/awesome-design-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Perspective next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Perspective compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Perspective this skillbergside/awesome-design-skills3.1k1 repos~904Automated safety check: PassMIT
Web Artifacts Builderanthropics/skills180k40 repos~769Automated safety check: PassApache-2.0
React Doctormakeplane/plane60k12 repos~657Automated safety check: PassAGPL-3.0
React Composition Patternsvercel-labs/openreview1.7k58 repos~721Automated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0

Similar skills

  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 40 repos~769 tokens
    Frontend & DesignAuto-check passed
  • React Doctor

    makeplane/plane

    Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.

    60k GitHub starsUsed in 12 repos~657 tokens
    Frontend & DesignAuto-check passed
  • React Composition Patterns

    vercel-labs/openreview

    Official

    Rules for structuring React components with composition instead of boolean props, covering compound components, lifted state, variants and React 19 changes.

    1.7k GitHub starsUsed in 58 repos~721 tokens
    Frontend & DesignAuto-check passed
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Frontend & DesignAuto-check passed

More from bergside/awesome-design-skills

All 67 skills in this repo
  • Agentic

    bergside/awesome-design-skills

    Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.

    3.1k GitHub starsUsed in 1 repo~991 tokens
    Auto-check passed
  • Ant

    bergside/awesome-design-skills

    Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.

    3.1k GitHub starsUsed in 1 repo~956 tokens
    Auto-check passed
  • Artistic

    bergside/awesome-design-skills

    High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.

    3.1k GitHub starsUsed in 1 repo~938 tokens
    Auto-check passed
  • Basic

    bergside/awesome-design-skills

    Print-inspired visual language for books, magazines, and reports with editorial grids and expressive typography.

    3.1k GitHub starsUsed in 1 repo~969 tokens
    Auto-check passed
  • Bento

    bergside/awesome-design-skills

    Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.

    3.1k GitHub starsUsed in 1 repo~878 tokens
    Auto-check passed
  • Bold

    bergside/awesome-design-skills

    Strong visual presence with heavyweight typography, high-contrast colors, and commanding layouts.

    3.1k GitHub starsUsed in 1 repo~854 tokens
    Auto-check passed

Questions about Perspective

What does Perspective do?

Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism. Perspective is an agent skill from bergside/awesome-design-skills. Spatial depth design with isometric views, vanishing points, and layered elements that guide attention through 3D-like realism.

When should I use Perspective?

Perspective fits situations like: frontend & Design work in your project.

How do I install Perspective in Claude Code?

Run `npx skills add bergside/awesome-design-skills --skill perspective -a claude-code`. Or copy the skill folder (skills/perspective in bergside/awesome-design-skills) into .claude/skills/perspective in your project. Claude Code loads it when a task matches its description.

How do I install Perspective in Codex?

Run `npx skills add bergside/awesome-design-skills --skill perspective -a codex`. Or copy the skill folder (skills/perspective in bergside/awesome-design-skills) into .agents/skills/perspective in your project. Codex loads it when a task matches its description.

Can I use Perspective in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bergside/awesome-design-skills --skill perspective -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/perspective, .gemini/skills/perspective, .github/skills/perspective and .opencode/skills/perspective in your project.

What does Perspective need to run?

SKILL.md names no scripts, command-line tools or credentials: Perspective is instructions for the agent only.

Does Perspective access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Perspective safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Perspective use?

Perspective is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Perspective use?

About 904 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Perspective?

Skills that share tags, products or a category with Perspective: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 60k stars), React Composition Patterns (vercel-labs/openreview, 1.7k stars) and Impeccable (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Perspective?

bergside (a GitHub organization) maintains it in bergside/awesome-design-skills, which has 3,070 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on June 28, 2026.

Source: bergside/awesome-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.