# Modify DB Component

> Modify DB Component is an Agent Skill for design published in the db-ux-design-system/core-web repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Modifies an existing DB UX Design System Mitosis component (add variants, update props, change styles).

- Skill name: `modify-db-component`
- Category: [Design](https://www.openparable.com/skill/design/1)
- Source: https://github.com/db-ux-design-system/core-web/blob/HEAD/packages/agent-cli/db-ux-maintainer-powers/skills/modify-db-component/SKILL.md
- Repository: db-ux-design-system/core-web (121 GitHub stars when collected)

## SKILL.md

# Skill: Modify Deutsche Bahn (DB) Component

## Variable Convention

Throughout this skill:

- `{component_slug}` = kebab-case directory/file name (e.g. `navigation-item`)
- `{component_name}` = PascalCase symbol name derived from `{component_slug}` (e.g. `navigation-item` -> `NavigationItem`)
- `DB{component_name}` = full component class name (e.g. `DBNavigationItem`)
- `.db-{component_slug}` = CSS class (e.g. `.db-navigation-item`)

## Pre-Conditions

1. `context/architecture.md` IS in context.
2. MCP (`@db-ux/mcp-server`) IS connected.
3. `component_slug` IS provided by user. Derive `component_name` from `component_slug` unless explicitly provided.
4. Component EXISTS (verify via `list_components`).
5. Modification instruction IS provided by user.
6. For visually-driven changes (new variant, layout, spacing): `figma_file_key` and `figma_node_id` SHOULD be provided. If missing for a visual change, ask user before proceeding.
7. For purely technical changes (bug fix, API cleanup, refactoring): Figma is not required.

## Execution

### Step 0: Analyze Existing Component

1. Call `list_components` to confirm the component exists.
2. Call `get_component_props` with the component name to load the current `model.ts`.
3. Call `get_component_details` to understand the current examples and showcase structure.
4. Read the existing files:
    - `packages/components/src/components/{component_slug}/model.ts`
    - `packages/components/src/components/{component_slug}/{component_slug}.lite.tsx`
    - `packages/components/src/components/{component_slug}/{component_slug}.scss`
    - `packages/components/src/components/{component_slug}/{component_slug}.spec.tsx`
5. Read and capture the FULL current state before making ANY changes.

### Step 1: RED - Update Tests First

Based on the user's instruction, update `{component_slug}.spec.tsx`:

- If adding a new variant: add screenshot and aria-snapshot tests for that variant.
- If adding a new prop: add test cases exercising the new prop.
- If changing behavior: update existing assertions to reflect the new expected behavior.

Rules:

- ALL new variants MUST get `toHaveScreenshot()` tests.
- ALL new variants MUST get aria-snapshot tests.
- Axe-core accessibility test scope (`.db-{component_slug}`) remains unchanged.

**After updating the spec, build the project, generate outputs, and run the component tests from `output/react`:**

```bash
pnpm run build && pnpm run build-outputs &&
cd output/react && pnpm run test:components
```

**The RED phase is only complete if:**

1. The command exits non-zero.
2. The failing test names are captured in the output.
3. The failure is caused by missing or incomplete implementation, NOT by syntax errors in the spec itself.

If the spec has syntax errors, fix them first and re-run until you get clean "missing implementation" failures.

### Step 2: GREEN - Implement the Change

#### 2a: Update `model.ts`

- Read the existing `model.ts` to understand the current type definitions and prop structure.
- If adding a prop: add it to `DB{component_name}DefaultProps` with a JSDoc comment.
- If changing a type: update the type definition.
- NEVER remove existing props without explicit user confirmation (breaking change).

#### 2b: Update `{component_slug}.lite.tsx`

- Read the existing `.lite.tsx` to understand the current component structure and patterns.
- Apply changes corresponding to the `model.ts` update, following the patterns already used in the component.
- Check `packages/components/src/styles/internal/` for shared internal styles and mixins. Also review other components for similar patterns that could be combined or reused, and suggest those.
- NEVER use inline styles in `.lite.tsx` components.
- PRESERVE `id={props.id ?? props.propOverrides?.id}` pattern.
- PRESERVE `cls('db-{component_slug}', props.className)` usage.

#### 2c: Update `{component_slug}.scss`

1. Read the existing `.scss` to understand the current styling patterns.
2. Call `list_design_token_categories` then `get_design_tokens` for relevant categories.
3. Add styles using SCSS variables (`variables.$db-*`) from `@db-ux/core-foundations/build/styles/variables`. Only use CSS custom properties (`var(--db-*)`) as a fallback when no SCSS variable is available.
4. Line 1 MUST remain `@use`. NO hardcoded values. NO `!important`. Max 3 levels of nesting.

#### 2d: Update Examples and Showcase (if applicable)

If the change introduces a new visual variant or feature, update files **inside `packages/components/src/components/{component_slug}/`** (NOT in `showcases/`):

1. Create or update `examples/<feature>.example.lite.tsx`.
2. Update `examples/_{component_slug}.arg.types.ts` with new control options.
3. Update `showcase/{component_slug}.showcase.lite.tsx` to include the new example.
4. Update `agent/{component_slug}.agent.lite.tsx` with new usage example.

Showcase files in `showcases/` are generated from these and must not be edited manually.

### Step 3: QUALITY CHECK

1. Run `pnpm run build`. MUST SUCCEED.
2. Run `pnpm run test`. ALL MUST PASS.
3. Verify no hardcoded values in SCSS.
4. Verify all new variants have screenshot tests.

### Step 4: Governance and Framework Outputs

1. **Build framework outputs:**

    ```bash
    pnpm run build-outputs
    ```

    This MUST succeed.

2. **Create changeset:**
    ```bash
    pnpm changeset
    ```
    Select `@db-ux/core-components` (only if the changes also affect styling: SCSS/CSS) and all JavaScript framework output packages.
    Bump type:
    - `patch` for bug fixes.
    - `minor` for new features (new variant, new prop).
    - `major` if a prop was renamed, removed, or had its type changed.

## Output Checklist

- [ ] Component confirmed to exist via `list_components`
- [ ] Existing files analyzed
- [ ] Tests updated FIRST (RED phase)
- [ ] RED phase verified: ran `test` command, non-zero exit captured
- [ ] `model.ts` updated
- [ ] `.lite.tsx` updated (no inline styles, `propOverrides` preserved)
- [ ] `.scss` updated (tokens only)
- [ ] Examples/showcase updated (if new visual feature)
- [ ] `pnpm run build` passes
- [ ] `pnpm run test` passes
- [ ] `pnpm run build-outputs` passes
- [ ] Changeset created via `pnpm changeset`

## Red Flags

| Thought                            | Response                                    |
| ---------------------------------- | ------------------------------------------- |
| "Edit React output directly"       | STOP. `.lite.tsx` ONLY.                     |
| "Hardcoded color for this variant" | STOP. Use `var(--db-*)`.                    |
| "Tests can wait"                   | STOP. Update tests FIRST. TDD is mandatory. |
| "I know the token name"            | STOP. ALWAYS query MCP.                     |
| "Removing this prop is fine"       | STOP. Breaking change. Confirm with user.   |
| "Skip showcase update"             | STOP. New visual feature = showcase update. |
| "Skip changeset"                   | STOP. Governance requires it.               |
| "build-outputs is optional"        | STOP. It is mandatory.                      |

---

Source: https://www.openparable.com/skill/design/modify-db-component (OpenParable). Cite the canonical URL above.
