diego3g/craft

craft-explore

Use when asked for options, alternatives, variations, directions or "a few ideas" for a screen, flow or element, when the person rejects a design or says they don't like it, or says "rethink this", "try something else" or "design both so I can pick".

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/diego3g/craft --skill craft-explore

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Three proposals

Overview

When someone asks for options, they want to choose, not to be handed a winner. Give them three directions that solve the problem in genuinely different ways, side by side, at the same fidelity, next to what exists today, with your recommendation first. Then wait for the pick.

When to use

  • "Give me options", "3 variations", "other directions", "what else could this be?"
  • "I don't like this", "rethink it", "try something different".
  • "Design both so I can choose": that means two.

When NOT to use

  • A specific change ("change the title to Preferences", "make it blue"): make it.
  • One clear fix the person already described.

Before you start

  1. Read DESIGN.md at the project root if it exists: it is the project's design brief.
  2. Read the project's design system and the screen in question. All options use the system's pieces and tokens: options differ in design, not in brand.
  3. Pick your tool's adapter in references/adapters/ (paper.md, pen.md, figma.md, html.md). If no adapter matches your tool, do the same verbs in your tool and say which you mapped by hand. With no design tool at all, build in HTML (html.md). If an image is all you have, say that values read from it are estimates.

Steps

  1. Restate the problem in one or two sentences: what's wrong today, and what a good result must do. If the request was only "make it better", name the problem you see. Stop and confirm it with the person before designing. If they already named the problem, go on.
  2. Choose the directions on different axes (divergence axes): structure or placement, interaction model, density, emphasis, or what gets removed. Write each direction as one line: the idea and its trade-off. Directions must differ: a different axis, or clearly different values on one axis when the person names the axis ("too dense" → three density answers). A change of colour, theme or font is never an axis.
  3. Build the comparison board in a temporary area (comparison board):
  • a legend card (each option's idea, what it's good at, what it costs, and the recommendation with its reason);
  • "Current", a copy of today's design, when one exists;
  • options A, B, C, the same size and with the same realistic data.

Never edit the real screens.

  1. Draw every option with final-screen care, including the states that its difference affects. If B moves an action into a menu, show the menu open.
  2. Present the recommendation first, then one line per option. Stop. The person picks, combines ("B with A's header"), or rejects all of them.
  3. After the answer:
  • Pick or combination: apply it to the real screens and the design system (and its propagation to every screen that uses a changed piece), then clear the temporary area.
  • All rejected: go back to step 1 with their reason as the new problem statement. Allow changes to the surrounding parts. Never answer a rejection with small tweaks of the same options.

Rules

RuleWhy
Three by default; two for "both" (when they named both options, skip the bolder-option rule); exactly the number they ask for otherwiseThe count is theirs; three is enough to compare without fatigue
Different axes, not different paintThree layouts in three colour schemes is one idea with three skins
Always recommend, and say whyThey asked an expert; "tell me which you like" hands the work back
"Current" sits on the boardPeople judge change against what they know
Same data, same size, same fidelityA polished option next to sketches is a vote, not a choice
No straw men: every option is one you'd defendFake options waste the person's attention and trust
One option is deliberately bolderOtherwise the set only covers safe variations
Real screens stay untouched until the pickOptions that leak into the product are decisions nobody made

Done when

The board shows the legend, Current and every option at equal fidelity; the recommendation is stated first; you have stopped for the pick. After the pick: applied to the real screens and the system, and the temporary area cleared.

Common mistakes

ThoughtReality
"Option C: the same page in a dark theme"Theme is paint, not a direction. Change structure, interaction, density, emphasis or what's removed.
"I'll let them choose without biasing them"Not recommending isn't neutral, it's unhelpful. Recommend first, with the reason.
"The original file is unchanged, so they can compare"Put Current on the board, next to the options.
"They rejected all three, I'll adjust the closest one"A rejection is new information about the problem. Restate it and diverge again.
"They asked for 5, but 3 is the method"Give 5. The divergence rule still applies to all of them.
"Options share the same fixes, so they look alike"Shared fixes are fine. Say so once in the legend and make the main axis differ.
do mesmo repositório

Mais Skills

Todos os Skills
diego3g
Comunidade

craft

Use when asked to design, create, mock up or redesign one or more pages, screens, flows or UI elements, or when the person runs /craft (/craft:craft in the Claude Code plugin).

Instalações / 1h
2
GitHub Stars
366
Atualizado
17 de nov.
diego3g
Comunidade

craft-critique

Use when asked to review, critique, refine or polish a design or screen, when something "feels off", "looks busy" or "isn't good yet", after finishing a screen and before showing it, or before handing a design to code.

Instalações / 1h
2
GitHub Stars
309
Atualizado
17 de nov.
diego3g
Comunidade

craft-setup

Use when a request to design or create a page, screen or element starts in a project with no DESIGN.md at its root, when the person asks to set up, define or start the design, style, brand or guidelines of a product, or runs /craft-setup (/craft:craft-setup in the Claude Code plugin).

Instalações / 1h
2
GitHub Stars
309
Atualizado
17 de nov.
diego3g
Comunidade

craft-states

Use when designing or redesigning a screen, flow or component, when asked to cover all states or find missing ones, or before handing a screen to code. Also use when a design only shows the happy path, uses short tidy sample data, or assumes a single user.

Instalações / 1h
2
GitHub Stars
309
Atualizado
17 de nov.