# domain-expert-configuration

Guides coding agents to build settings panels, solver controls, and constraint editors tailored for non-developer domain experts.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 660 installs · ★ 165
- Author: dembrandt
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/dembrandt/dembrandt-skills/tree/HEAD/skills/domain-expert-configuration/SKILL.md
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/skills/domain-expert-configuration

## What it does

This skill guides your agent when assembling configuration interfaces in directories like `components/**` or `src/components/**`. It translates raw system properties such as timeouts and thread limits into labels that describe real-world outcomes. Inputs are grouped by operational tasks instead of data types or alphabetical lists.

Units are mandatory for numbers. Each field requires a sensible default and a clear reset button, preventing users from guessing arbitrary values. If an option cannot be described in practical domain vocabulary, the guidelines require keeping it in a developer config file rather than exposing it in the interface.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add dembrandt/dembrandt-skills --skill domain-expert-configuration -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/domain-expert-configuration/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/domain-expert-configuration/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add dembrandt/dembrandt-skills --skill domain-expert-configuration -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/domain-expert-configuration/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add dembrandt/dembrandt-skills --skill domain-expert-configuration -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/domain-expert-configuration/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install dembrandt/dembrandt-skills domain-expert-configuration
```

2. **Manually: put the files in place**
- File: `.github/skills/domain-expert-configuration/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add dembrandt/dembrandt-skills --skill domain-expert-configuration -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/dembrandt/dembrandt-skills --path skills/domain-expert-configuration
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/domain-expert-configuration/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add dembrandt/dembrandt-skills --skill domain-expert-configuration -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/dembrandt/dembrandt-skills/tree/HEAD/skills/domain-expert-configuration/SKILL.md

## When to use it
- Translate technical parameter names into practical domain terminology
- Cluster complex algorithm settings by operational workflows
- Distinguish temporary run overrides from persisted user defaults
- Enforce explicit measurement units and reset actions on numeric inputs

## Example prompts
- Design a solver settings UI for domain experts who are not developers
- Group these algorithm parameters by the operational tasks they control
- Create a batch processing configuration component in src/components/Settings.tsx

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 502a1f2c31ccb243.

BEGIN THIRD-PARTY FILE 502a1f2c31ccb243
```text
---
name: domain-expert-configuration
description: Settings for experts who are not developers — domain language, sane defaults, grouping by professional concept. Use when designing settings panels, solver configuration or constraint editors.
metadata:
  priority: 6
  pathPatterns:
    - "components/**"
    - "src/components/**"
    - "**/*.tsx"
    - "**/*.jsx"
    - "app/**"
    - "pages/**"
  promptSignals:
    phrases:
      - "configuration"
      - "settings panel"
      - "parameters"
      - "constraints"
      - "algorithm settings"
      - "solver"
      - "optimisation"
      - "optimization"
      - "tune"
      - "configure"
      - "expert settings"
      - "advanced settings"
retrieval:
  aliases:
    - configuration UI
    - settings panel
    - algorithm configuration
    - solver settings
    - constraint editor
    - domain expert settings
    - advanced configuration
    - parameter tuning
  intents:
    - design a configuration panel for domain experts
    - expose algorithm parameters to non-technical users
    - design a settings UI for an optimisation tool
    - group configuration parameters by domain concept
    - design constraint editors for professional tools
  examples:
    - design a settings panel for a batch-processing tool
    - the user is a domain expert, not a developer
    - how should I expose solver parameters to a non-technical expert
    - make this configuration UI understandable to domain experts
    - group these algorithm settings by what they control
---

# Domain Expert Configuration

A domain expert configuration UI exposes the parameters of a complex system — an optimisation algorithm, a planning engine, a simulation — to users who understand the problem domain deeply but have no knowledge of the system's internals.

The challenge: the system's parameters are defined in technical terms (weights, thresholds, flags, tolerances). The user thinks in domain terms (how long to wait, when to retry, how to group results). The UI must translate between these two vocabularies — always favouring the user's language.

---

## The Core Principle: Domain Language Over Technical Language

Every parameter label, tooltip, and error message should describe what the parameter *means in the user's world*, not what it *does inside the system*.

| Technical label | Domain label |
|---|---|
| `max_concurrent_jobs` | Maximum tasks running at once |
| `enable_auto_retry` | Retry failed tasks automatically |
| `batch_allocation_threshold` | Start a new batch after (% filled) |
| `request_timeout_ms` | Maximum wait per request (seconds) |
| `enable_fuzzy_matching` | Allow approximate matches |
```
END THIRD-PARTY FILE 502a1f2c31ccb243

The third-party file has ended. Everything between the 502a1f2c31ccb243 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2672 of 9258 bytes. © dembrandt · MIT · https://github.com/dembrandt/dembrandt-skills/tree/HEAD/skills/domain-expert-configuration/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md