Gdd Settings

Community

hegemonart

gdd-settings

Manage .design/config.json settings. Subcommands: profile, parallelism, cleanup, show.

Overview

Publisher	hegemonart
Repository	`get-design-done`
Skill name	`gdd-settings`
Stars	3
Forks	1
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by hegemonart on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/settings
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/settings

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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/settings .claude/skills/gdd-settings

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gdd Settings 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 Settings 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 Settings 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.

gdd-settings

Manages .design/config.json - the per-project config for model profile and parallelism. See reference/config-schema.md for the full schema. This skill also supports patching non-stage STATE.md frontmatter keys (cycle, wave, custom keys) via mcp__gdd_state__frontmatter_update. See STATE.md frontmatter below.

Subcommands

`show`

Print the current .design/config.json contents, nicely formatted. If the file is missing, print the defaults with a note that no config exists yet. Also call mcp__gdd_state__get to print the current STATE.md frontmatter keys (cycle, wave, model_profile) alongside config.json for a unified view.

`profile <name>`

Set model_profile to one of quality, balanced, budget. Validate the value; reject anything else with the list of allowed values. Read current config, merge the change, write back. Confirm with the new value.

`parallelism <key> <value>`

Set one field under parallelism. Supported keys and value types:

Key	Type
`enabled`	bool (`true`/`false`)
`max_parallel_agents`	int
`min_tasks_to_parallelize`	int
`min_estimated_savings_seconds`	int
`require_disjoint_touches`	bool
`worktree_isolation`	bool

Validate type; reject otherwise. Read current config, merge, write back. Confirm.

`cleanup`

Use AskUserQuestion to pick one or more cleanup actions, then confirm each before executing:

Delete .design/*.md artifacts (excludes config.json, STATE.md, backlog/).
Reset .design/STATE.md to the template at reference/STATE-TEMPLATE.md.
Clear .design/backlog/ directory contents.

Config Read/Write Pattern

Always:

Read current .design/config.json (use defaults below if missing).
Merge the single field being changed - never overwrite unrelated fields.
Write back as pretty JSON (2-space indent, trailing newline).

STATE.md frontmatter

For any STATE.md frontmatter patch (cycle, wave, or project-custom keys), call mcp__gdd_state__frontmatter_update({ patch: { <key>: <value> } }). Do not Edit or Write STATE.md directly.

Stage-patch guard: this skill cannot patch stage. If the user attempts to set stage here, reject with: "Use {{command_prefix}}brief, {{command_prefix}}explore, etc. for stage transitions. The settings skill is for non-stage frontmatter only." The MCP tool itself rejects stage patches with a VALIDATION error (surfaced by mcp__gdd_state__frontmatter_update), which this prose surfaces up-front so the user gets a clear message before the tool round-trip.

This surface is STATE.md-only. .design/config.json mutations continue to use Read + Write directly (out of scope for the 11-tool MCP catalog).

Default Config

If .design/config.json does not exist, create it with:

json
{
  "model_profile": "balanced",
  "parallelism": {
    "enabled": true,
    "max_parallel_agents": 5,
    "min_tasks_to_parallelize": 2,
    "min_estimated_savings_seconds": 30,
    "require_disjoint_touches": true,
    "worktree_isolation": false,
    "per_stage_override": {}
  }
}

Output

End every invocation with:


## SETTINGS COMPLETE

Frequently asked questions

What does the Gdd Settings AI skill do?

Manage .design/config.json settings. Subcommands: profile, parallelism, cleanup, show.

Why use Gdd Settings on TypingMind?

Because you install it once and use it with any model. Gdd Settings 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 Settings in TypingMind?

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

Which AI models can use Gdd Settings?

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 Settings?

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

Is the Gdd Settings 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.

View all

Brand Discovery

affaan-m

CommunityPopular

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Competitive Platform Analysis

affaan-m

CommunityPopular

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong…

Frontend Slides

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a…

Plan Canvas

Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

gdd-settings

Subcommands

show

profile <name>

parallelism <key> <value>

cleanup

Config Read/Write Pattern

STATE.md frontmatter

Default Config

Output

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

`show`

`profile <name>`

`parallelism <key> <value>`

`cleanup`