design

Establish and document intentional visual direction for digital artifacts.

1|1|Updated Aug 3, 2020
One-click install
npx skills add https://github.com/lolwierd/dotfiles --skill design-lolwierd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/lolwierd/dotfiles/tree/main/ai/dot-agents/skills/design
Command: npx skills add https://github.com/lolwierd/dotfiles --skill design-lolwierd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Visual design is often driven by trend or habit, producing surface-level polish without a clear reason or context. This Skill provides a disciplined approach to establishing and sustaining intentional visual direction across projects, ensuring every choice has purpose and meaning.

Core Features & Use Cases

  • Guided concept-to-craft framework: define a concise concept, a memorable hook, typography strategy, color rationale, and layout structure to steer design decisions.
  • Context-driven decision making: adapt the direction to project goals, audience, medium, and workflow, balancing aesthetics with usability.
  • Documentation and handoff artifacts: generate a DESIGN.md that records rationale, trade-offs, and rejected options to guide teams through decisions.

Quick Start

Provide a complete design concept brief for a project, detailing the concept, hook, typography choices, color rationale, layout structure, and trade-off notes, plus a DESIGN.md to capture the rationale.

Frequently Asked Questions about design

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

FAQPage Schema
How do I establish an intentional visual direction for a digital interface?

Intentional visual direction requires defining a guiding concept, memorable hook, typography rationale, color rationale, and layout structure to steer concept-to-craft design decisions with purpose. This approach prevents surface-level polish driven by habit without clear context.

What is the best way to document design rationale and trade-offs for a team handoff?

Documenting design rationale is best achieved by generating a DESIGN.md file that records reasoning, trade-offs, and rejected options for visual decisions. This artifact guides teams through intentional choices made from mood to typography and color.

Can I use this design framework for both digital dashboards and printed materials?

Yes, you can use this design framework for digital dashboards and printed materials. The system adapts visual direction to project goals, audience, and medium, balancing aesthetics with usability across interfaces, presentations, and physical artifacts.

Why does my visual design lack intentionality and context across different projects?

Visual design lacks intentionality when choices are driven by trend or habit rather than a disciplined framework. Establishing a guiding concept, hook, and rationale for typography and color ensures every choice has purpose and meaning tailored to context.

How do I structure a complete design concept brief from mood to typography?

Structuring a design concept brief involves detailing the guiding concept, memorable hook, typography strategy, color rationale, layout structure, and trade-off notes. This framework steers decisions and balances aesthetics with usability for the target audience.

When should I not use a trend-driven approach for layout and color decisions?

You should not use a trend-driven approach when a project requires context-driven decision making. Applying a disciplined framework ensures typography and color choices have purpose, producing intentional visuals rather than surface-level polish without clear reasoning.