design-exploration

Generate distinct design directions from jobs and stories, then record the chosen direction with rationale.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill design-exploration-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-exploration
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/design-exploration
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill design-exploration-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight from a product requirement to the first design idea, which gets silently locked in and re-litigated later. This Skill structures the exploration step so multiple genuinely distinct directions are considered and one is chosen with its reasoning recorded. ## Core Features & Use Cases - Divergent exploration: Produces two to four directions, each explicitly optimising for something different (speed of the common case, first-timer legibility, power-user density). - Recorded convergence: Captures which direction was chosen, why, and what each rejected direction would have been better at, so decisions are not re-opened later. - Grounded inputs: Starts from the ready story, its scenarios, and the job's outcome, and can pull cited references from the design vault via design-reference. - Use Case: A ready story for a new onboarding surface needs ideas. Run design exploration to get three distinct directions, pick one with documented trade-offs, and hand it to design-flows for scenario walkthroughs. ## Quick Start Ask the agent to explore design directions for a ready story, for example: explore some directions for the onboarding story before any hi-fi work starts.

Frequently Asked Questions about design-exploration

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

FAQPage Schema
How do I explore design directions before starting hi-fi design?▼

Start from the ready story, its scenarios, and the job's outcome, then produce two to four directions that each optimise for something different. Choose one and record why, plus what the rejected directions would have been better at.

What makes design directions genuinely distinct rather than variations?▼

Each direction must name a different optimisation, such as speed of the common case, first-timer legibility, or power-user density. If two directions share the same optimisation, they count as one direction.

When should design exploration happen in the product workflow?▼

It runs after a story has passed ready-review and before any flow design or hi-fi work. If the story is not ready, that is a question for discovery-lead rather than a reason to start exploring early.

Can I use existing product designs as references during exploration?▼

Yes. The design-reference companion finds what the design vault already holds and breaks it down cited to frames, and ui-teardown findings on comparable products are legitimate inputs. Cite the source shot rather than relying on memory.

What are the limitations of design exploration?▼

It produces directions, not flows or hi-fi screens, and it does not re-open decisions already settled in the register. Directions must use the existing design system; needing a new system is a separate founder conversation.