aesthetic-direction

Convert vague visual mood into ranked aesthetic goals and a direction document.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill aesthetic-direction-eugenelim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aesthetic-direction
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packs/design-craft/.apm/skills/aesthetic-direction
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill aesthetic-direction-eugenelim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill turns an unarticulated mood, vibe, or brand feeling into a clear aesthetic direction that a team can actually use to make consistent design decisions.

Core Features & Use Cases

  • Mood to goals: Converts vague input like “premium,” “calm,” or “playful” into a short set of named emotional and brand goals.
  • Ranking and arbitration: Orders the goals so conflicts have a clear winner instead of reopening taste debates during the build.
  • Documented direction: Captures what each goal means, what would violate it, and the open questions that still need resolution.
  • Use case: A product team has a strong visual instinct but no shared language; this Skill helps them define the direction before choosing tokens, layout details, or visual values.

Quick Start

Ask the aesthetic-direction skill to turn the user’s vague mood into three to five ranked design goals and record the result as an aesthetic-direction doc.

Frequently Asked Questions about aesthetic-direction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague brand mood into clear design goals?

Aesthetic direction translates unarticulated visual moods into a short set of ranked emotional and brand goals. It applies to branding and product design when a team has a felt vibe but lacks a shared language for the desired emotional direction.

How do I stop taste debates during visual identity design?

To define an aesthetic direction, you interrogate the brief to convert vague input into three to five named goals. You then rank these goals to establish design arbitration, and record the result as a durable direction document for the team.

What is the best way to document visual identity goals for a product team?

Aesthetic direction is needed when a product team has strong visual instincts but no shared language, and has not yet named the desired emotional direction. It should be used before selecting tokens, layout details, or visual values.

When do I need to define an aesthetic direction before starting product design?

You should not use aesthetic direction if you are ready to choose specific token values or perform screen critique. The process intentionally stops before establishing visual values to focus solely on ranking emotional goals and resolving open questions.

Does defining an aesthetic direction include choosing design tokens?

Aesthetic direction differs from general style guides by focusing on interrogating the brief to rank emotional goals and record conflict arbitration. It stops before token selection, providing a durable direction document rather than specific visual values.