Create high-concept visual philosophies for frontend work
A skill for naming and articulating a high-concept visual design philosophy, with a subtle woven-in conceptual reference.
Why it matters
This skill helps you establish and articulate a named design movement with detailed visual philosophy for high-concept frontend projects, campaigns, and art-direction that requires a cohesive aesthetic manifesto.
Outcomes
What it gets done
Name a unique design movement in 1-2 words that captures the aesthetic direction
Articulate how the philosophy manifests through space, color, scale, composition, and hierarchy
Embed subtle conceptual references that sophisticated audiences recognize intuitively
Guide implementation with craft-focused direction while leaving room for interpretive execution
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-design-philosophy | bash Overview
Design philosophy
This skill names a design movement and articulates its visual philosophy across space, color, scale, composition, and hierarchy, emphasizing craftsmanship and a subtle woven-in conceptual reference. Use it alongside a design skill for high-concept work, campaigns, or when a visual philosophy or manifesto is requested. Not for routine, text-heavy UI work.
What it does
This skill guides creating a named design movement and expressing it visually for high-concept frontend work, campaigns, or when a user asks for a visual philosophy, manifesto, or unmistakable art-like aesthetic. Its canonical generation procedure starts by naming the movement in one or two words, then articulating it in four to six non-redundant paragraphs covering how the philosophy manifests through space and form, color and material, scale and rhythm, composition and balance, and visual hierarchy, with each aspect addressed exactly once. It stresses craftsmanship throughout, emphasizing that the work should look meticulously crafted and the product of deep, master-level expertise. It keeps text minimal, since information should live in the design rather than in paragraphs, with any text sparse, essential, and integrated as a visual element itself. It leaves enough creative space - specific in direction but concise - so the executor can make high-level interpretive choices at the same level of craft. Before building, it also identifies one subtle conceptual thread from the request - a niche, non-literal reference woven into form, color, and composition following a jazz-quote principle, where those familiar with the reference feel it intuitively while everyone else still experiences a strong abstract composition.
When to use - and when NOT to
Use it alongside a design skill for high-concept work, campaigns, or when the user asks for a visual philosophy, manifesto, or art-like aesthetic - not for routine UI work needing conventional, text-heavy interfaces.
Inputs and outputs
Given a creative brief, it produces a named movement, a multi-paragraph philosophy statement covering space, color, scale, composition, and hierarchy, and a woven-in subtle conceptual reference guiding the visual execution.
Integrations
Pairs with a design skill for the actual visual and frontend execution; a companion reference file provides worked philosophy examples.
Who it's for
Designers and creative directors producing art-directed, high-concept visual work who want a structured procedure for articulating and naming a design philosophy rather than starting from a blank page.
Source README
Design philosophy
When to Use
Use this skill when you need visual philosophy and art-direction for frontend. Use when creating high-concept work, campaigns, or when the user asks for a visual philosophy, manifesto, or unmistakable art-like aesthetic.
Apply with design for high-concept work, campaigns, or when the user asks for a visual philosophy, manifesto, or art-like aesthetic. This skill guides creating a named movement and expressing it visually.
Visual philosophy (when creating "art" or high-concept work)
- Name the movement (1-2 words): e.g. "Brutalist Joy," "Chromatic Silence," "Metabolist Dreams."
- Articulate in 4-6 paragraphs how the philosophy manifests through: space and form; color and material; scale and rhythm; composition and balance; visual hierarchy. Avoid redundancy; each aspect once.
- Craftsmanship: Stress that the work should look meticulously crafted, labored over with care, the product of deep expertise - "painstaking attention," "master-level execution." Repeat this framing.
- Minimal text: Information lives in design, not paragraphs. Text sparse and essential; integrated as visual element.
- Creative space: Be specific about direction but concise so the executor can make high-level interpretive choices with the same level of craft.
For philosophy examples, see reference.md. The numbered checklist above is the canonical generation procedure.
Deducing the subtle reference
Before building: identify one subtle conceptual thread from the request. The topic is a subtle, niche reference embedded in the work - not literal, always sophisticated. Someone familiar with the subject should feel it intuitively; others experience a strong abstract composition. Weave it into form, color, and composition. "Jazz quote" principle: only those who know catch it; everyone benefits.
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.