TypingMindTypingMindThe best frontend for AI
Gdd Explore logo

Gdd Explore

Community
hegemonart
gdd-explore

Stage 2 of 5 - unified exploration merging inventory grep + design interview. Probes 6 connections, scans the codebase, conducts the AskUserQuestion interview, and writes .design/DESIGN.md + DESIGN-DEBT.md + DESIGN-CONTEXT.md. Use after {{command_prefix}}brief to map the existing system and lock decisions before planning. Activates for requests involving researching design direction, gathering references, or exploring visual options.

Overview

Publisherhegemonart
Repositoryget-design-done
Skill namegdd-explore
Stars
3
Forks
1
Bundled files
1
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by hegemonart on GitHub. Read the source before you install it.

Installation

Install the Gdd Explore AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/explore
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hegemonart/get-design-done.git /tmp/get-design-done
mkdir -p .claude/skills
cp -r /tmp/get-design-done/scripts/skill-templates/explore .claude/skills/gdd-explore
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gdd Explore in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gdd Explore on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gdd Explore is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Get Design Done - Explore

Role: You are the Explore stage. Stage 2 of 5 in the get-design-done pipeline.

Purpose: Unified exploration merging the former scan (inventory grep) and discover (context interview) stages. Produces .design/DESIGN.md, .design/DESIGN-DEBT.md, and .design/DESIGN-CONTEXT.md.

Full procedure detail: ./explore-procedure.md.

Stage entry

All STATE.md persistence goes through gdd-state MCP tools - no direct edits. Plain design docs (DESIGN.md / DESIGN-DEBT.md / DESIGN-CONTEXT.md) use Write.

  1. mcp__gdd_state__transition_stage with to: "explore". On gate failure: print blockers from error.context.blockers verbatim, do not advance.
  2. mcp__gdd_state__get (no args) -> snapshot state for downstream steps.

Step 1 - Connection probe

Probe six connections, then batch-write results via ONE mcp__gdd_state__probe_connections call (unspecified connections keep their existing value):

  • A - Figma (variant-agnostic): ToolSearch + regex parse of get_metadata / use_figma prefixes -> tiebreaker selection (both-sets > reads-only, figma > others, non-figma-desktop, alphabetical) -> live {prefix}get_metadata call -> available / unavailable / not_configured (with prefix= + writes=).
  • B - Refero: ToolSearch presence sufficient.
  • C - 21st.dev: ToolSearch mcp__21st presence.
  • D - Magic Patterns: ToolSearch mcp__magic_patterns presence.
  • E - paper.design: ToolSearch mcp__paper + live get_selection call.
  • F - pencil.dev: find . -name "*.pen" file-presence.

Full probe specs + commit-results JSON shape: ./explore-procedure.md §Step 1.

Step 1.5 - 21st.dev Prior-Art Check (when 21st-dev: available)

For each greenfield component in scope: 21st_magic_component_search(component_name, limit: 3). Fit >= 80% -> add <prior-art> block to DESIGN.md recommending adoption; fit < 80% -> note as reference, build custom. If svgl_get_brand_logo available and brand assets are in scope, call per logo and save SVGs to .design/assets/. Skip entirely if no greenfield components in scope. Detail: ./explore-procedure.md §Step 1.5.

Step 2 - Inventory scan (unless --skip-scan)

Map pre-check: if .design/map/ exists with all 5 files (tokens.md, components.md, visual-hierarchy.md, a11y.md, motion.md) fresher than src/, consume them and skip the grep pass. Otherwise grep and, after Step 4, suggest {{command_prefix}}map for the next cycle.

Parallelism decision: read .design/config.json + reference/parallelism-rules.md. Record verdict via mcp__gdd_state__set_status ("explore_parallel" / "explore_serial"). Parallel -> multiple Task() in one response; serial -> sequential.

Incremental batching (Phase 53, default): --incremental (default; --full opts out) runs the change classifier first via the fingerprint store, groups the DesignContext graph into Louvain community batches, and dispatches mappers per the verdict (SKIP=0, PARTIAL=affected batches only, FULL=all). Engine: scripts/lib/explore-parallel-runner + scripts/lib/mappers/incremental-discover.cjs; dispatch concurrency comes from concurrency-tuner.cjs. Detail: ./explore-procedure.md §Incremental Batching.

Run the canonical scan grep/glob inventory (POSIX ERE, preserving PLAT-01/02): component detection (Glob **/*.{tsx,jsx,vue,svelte}), color extraction (hex / rgb / hsl / Tailwind arbitrary), typography scan (font-family / Tailwind font-* / text-*), motion scan (transition / animate- / @keyframes / framer-motion), token detection (tailwind.config / CSS custom properties / token JSON), layout detection (ordered fallback src/ -> app/ -> pages/ -> lib/ -> unknown). Write .design/DESIGN.md + .design/DESIGN-DEBT.md. Then mcp__gdd_state__update_progress for scan progress. Detail: ./explore-procedure.md §Step 2.

Step 2.x - i18n readiness probe (informational, per D-04): check package.json deps against {react-intl, next-intl, i18next, vue-i18n, formatjs, lingui} -> framework-managed; else grep Intl.(DateTimeFormat|NumberFormat|...) in src/ -> partial; else none. Emit single line Localization readiness: <state> in the report. NO gate, NO blocking - surface signal only (D-07). Detail: ./explore-procedure.md §Step 2.x.

Step 2.5 - Detect prior sketches and project-local conventions

  • Sketches: list .design/sketches/* slugs, group by WINNER.md present (completed) vs absent (pending). Record via mcp__gdd_state__set_status: "explore_sketches_present". Include in DESIGN.md "Prior Explorations" section.
  • Project-local skills: read ./.claude/skills/design-*-conventions.md -> include in DESIGN-CONTEXT.md <project_conventions> (these override defaults).
  • Global skills: ~/.claude/gdd/global-skills/*.md (other than README) -> prepend to <project_conventions> under <global_conventions> sub-block. Project-local D-XX wins on conflict.

Step 2.6 - Graph review (gate then reviewer)

Runs only when Step 2's mapper batch + synthesizer produced .design/context-graph.json. Skip the whole step if the file is absent (pre-Phase-52 project, or --skip-scan).

  1. Gate first (cheap Haiku check). Spawn design-context-reviewer-gate via Task() with the classifier signal from Step 2's incremental batching pass: change_pct (fingerprint classifier pct), classifier_action (SKIP / PARTIAL_UPDATE / ARCHITECTURE_UPDATE / FULL_UPDATE), and graph_path: ".design/context-graph.json". Gate emits a single-line {spawn, rationale} JSON decision then ## GATE COMPLETE.
  2. If spawn: false: record mcp__gdd_state__set_status: "explore_graph_review_skipped", log the gate rationale (e.g., "project change 3% < 5% threshold"), set telemetry lazy_skipped: true. Done - proceed to Step 3.
  3. If spawn: true: spawn design-context-reviewer via Task() with <required_reading> pointing at .design/STATE.md, .design/context-graph.json, reference/design-context-schema.md, reference/design-context-tag-vocab.md. The reviewer runs scripts/validate-design-context.cjs --json as the deterministic floor (checks 1/2/3/5) then layers the semantic checks (4/6/7/8/9) and returns the 9-check verdict inline (APPROVED or REJECT).
  4. Capture verdict (read-only contract). The reviewer does NOT write .design/DESIGN-CONTEXT-REVIEW.md - it is reads-only: true, writes: []. WARN findings surface through scripts/lib/health-mirror#getHealthChecks as status: 'warn'; a hard-reject maps to status: 'fail'. Record the overall verdict via mcp__gdd_state__set_status: "explore_graph_review_approved" (or "_rejected").
  5. On REJECT: record mcp__gdd_state__add_blocker with the reviewer's blocking-issues list verbatim. Do not advance to Step 3 until the synthesizer or the implicated mapper is re-run. On APPROVED (with or without WARNs): proceed.

Step 3 - Design interview (unless --skip-interview)

Run inline - NEVER spawn design-discussant as a subagent. AskUserQuestion only renders the native picker from the top-level skill context; spawning degrades to plain markdown (broken in Claude Desktop).

  • 3.a Pre-load context: state.decisions snapshot -> BRIEF.md -> DESIGN.md -> DESIGN-CONTEXT.md <gray_areas> -> project conventions. If figma: available, call {prefix}get_variable_defs and draft tentative D-XX entries.
  • 3.b Identify question set: skip areas already covered by D-XX or project convention. Default coverage: cycle goal, audience, brand direction (if no tokens), color/typography/spacing primitives (if undetected), motion preferences, gray areas from DESIGN-CONTEXT.md.
  • 3.c Ask one at a time: AskUserQuestion with 4 concrete options + "Other" / "Skip". Reject generic answers ("modern", "clean") with one follow-up.
  • 3.d Record after each answer: mcp__gdd_state__add_decision (atomic, auto-assigns D-NN); append a quality-classified JSON line to .design/learnings/question-quality.jsonl.
  • 3.e Produce DESIGN-CONTEXT.md: summarize locked decisions, remaining gray areas, Figma tentatives. Frontmatter status: complete.

Full interview protocol + JSON line schema: ./explore-procedure.md §Step 3.

Step 4 - Close out explore

  • If the synthesizer / mapper batch ran in Step 2: mcp__gdd_state__update_progress with task_progress: "<done>/<total>", status: "explore_mappers_done".
  • If Step 2.6 ran the graph review: ensure the verdict status is recorded (explore_graph_review_approved / _rejected / _skipped); on _rejected do NOT checkpoint until re-run.
  • mcp__gdd_state__checkpoint - bumps last_checkpoint.
  • Stage advance to plan happens at the next stage's entry (plan owns its own transition_stage); do not edit frontmatter directly.

After Writing

Print: "=== Explore complete ===\nSaved: .design/DESIGN.md, .design/DESIGN-DEBT.md, .design/DESIGN-CONTEXT.md\nNext: @get-design-done plan".

Rationalizations - Thought to Reality

The shortcut excuses an agent reaches for during explore, and the drift each one introduces:

ThoughtReality
"I already know this codebase, I can skip the inventory scan."An unscanned codebase hides the tokens/components you'll duplicate - the grep pass exists to stop you reinventing what's there.
"The six connection probes are noise, I'll assume Figma is off."A skipped probe means a wrong connection assumption silently breaks the design stage's tool dispatch.
"--skip-interview is fine, the brief covered it."The interview locks the gray areas the brief left fuzzy; skipping it ships undecided D-XX into planning.
"I'll batch all the interview questions to save round-trips."Batched questions overwhelm the user and smuggle in coupled assumptions - one-at-a-time keeps each decision clean.
"DESIGN-DEBT.md is optional, the scan was clean enough."Unrecorded debt resurfaces as an unexplained constraint three stages later with no provenance.
"Prior sketches and project conventions don't apply this cycle."Ignored conventions get overridden by defaults, producing inconsistency the audit will flag against the rest of the system.

EXPLORE COMPLETE

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Gdd Explore AI skill do?

Stage 2 of 5 - unified exploration merging inventory grep + design interview. Probes 6 connections, scans the codebase, conducts the AskUserQuestion interview, and writes .design/DESIGN.md + DESIGN-DEBT.md + DESIGN-CONTEXT.md. Use after {{command_prefix}}brief to map the existing system and lock decisions before planning. Activates for requests involving researching design direction, gathering references, or exploring visual options.

Why use Gdd Explore on TypingMind?

Because you install it once and use it with any model. Gdd Explore is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gdd Explore in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/explore. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Gdd Explore?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gdd Explore?

As many as you like. As long as a model supports skills, you can use Gdd Explore with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gdd Explore AI skill free?

Yes. It is published on GitHub by hegemonart under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
NousResearch logo

Hyperframes

NousResearch
OrganizationPopular

Render MP4/WebM videos from HTML compositions.

53.5K
250.4K
7 files
View
NousResearch logo

Ip As Logo

NousResearch
OrganizationPopular

Design minimal cute IP mascot marks readable at 32px.

53.5K
250.4K
Instructions
View
NousResearch logo

Mono Color

NousResearch
OrganizationPopular

Generate one- or two-ink editorial print poster images.

53.5K
250.4K
9 files
View
NousResearch logo

Pretext

NousResearch
OrganizationPopular

Build creative browser demos with DOM-free text layout.

53.5K
250.4K
3 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇