direct

Resolves freeform redesign intent into a target design specification with palette and divergence audit trail.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill direct-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: direct
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/direct
Command: npx skills add https://github.com/aemgdc/aemdev --skill direct-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Redesigning an existing website from a vague request like "make it more premium" leaves teams without a concrete, defensible design target. This Skill converts freeform redesign intent into a complete target specification—PRODUCT.md, DESIGN.md, DESIGN.json, and a reasoning trace—so downstream prototyping and migration steps operate against an explicit, auditable direction. ## Core Features & Use Cases - Intent reasoning: Restates the user's phrase in dimensional vocabulary (register, density, tone, IA-fidelity), asks at most two clarifying questions, and confirms a plan before writing anything. - Mode detection: Defaults to brand-faithful mode when the captured brand surface has strong signal, with explicit opt-in rebrand mode and anchor-reference precedence for user-supplied design references. - Deterministic divergence toolkit: Rolls a 4-dimension seed (decade, craft, register, ground-family) via MD5 hashing and picks palettes from a bundled 127-palette library—no LLM-invented colors. - Multi-variant contracts: Produces role-differentiated variants (faithful + improvements, amplified captured traits) or surface forks depending on the IA-fidelity tier. - Use Case: After extracting a nonprofit's site, ask to "make it feel more editorial" and receive a brand-faithful direction with an improvements list, pinned palette and type, and a full reasoning trace at stardust/direction.md. ## Quick Start Ask the assistant to set a redesign direction for the extracted site, for example by saying "redesign this site to feel more premium on mobile" after running the extract step.

Frequently Asked Questions about direct

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

FAQPage Schema
How do I set a redesign direction for an existing website?▼

Run the direct skill with a freeform phrase describing the redesign intent, such as "make it more editorial." It restates the phrase in dimensional vocabulary, asks at most two clarifying questions, then writes PRODUCT.md, DESIGN.md, DESIGN.json, and a reasoning trace.

What is the difference between brand-faithful mode and rebrand mode?▼

Brand-faithful mode is the default when the captured brand surface has strong signal: palette and type are pinned to the existing site and images are reused at their semantic positions. Rebrand mode requires an explicit trigger phrase or the --rebrand flag and rolls a full divergence seed.

How does the palette picker choose colors without inventing them?▼

The picker classifies the description against keyword vocabularies for energy, contrast, saturation, hue bias, and ground family, then scores and ranks candidates from a bundled library of 127 palettes scraped from coolors.co. The recommended pick is chosen deterministically via an MD5 hash.

Can I add more design variants after a direction is set?▼

Yes, the --add-variant flag appends a new variant against the existing direction without re-running intent reasoning or mode detection. It writes DESIGN-<name>.md and DESIGN-<name>.json files and does not stale-flag existing prototypes.

What happens if the captured brand signal is thin or absent?▼

With signal-thin captures, brand-faithful mode activates with a warning that some dimensions will be filled by the divergence toolkit. With signal-absent captures, the skill automatically switches to rebrand mode and surfaces the reason to the user.

When should I not use this skill?▼

Do not use it before running the extract step, since it requires stardust/state.json with at least one extracted page and a completed _brand-extraction.json. It also never writes prototypes or migrates pages; those are handled by downstream sub-commands.