---
name: bomber-mcp
description: Use this skill when an AI agent needs to use Bomber MCP or MCP-style automation to implement, update, or maintain Atomic Bomb architecture.
---

# Bomber MCP Skill

Bomber MCP provides AI-driven code generation and project automation through the Model Context Protocol.

Repository: <https://codeberg.org/ReneKrewinkel/bomber>
Site: <https://atomic-bomb.io/bomber-mcp>

## Use When

Use Bomber MCP when an agent needs to create or update Atomic Design-compliant components, generate features from structured context, maintain hooks and services, or preserve an existing Atomic Bomb architecture while implementing behavior.

## Role in the Toolkit

Atomic Resources creates design foundations.

Atomic Bomb creates architecture.

Bomber MCP implements and maintains architecture.

## Required Context for MCP Tasks

Provide:

- Project framework.
- Language.
- Existing component layer.
- Target folder and naming conventions.
- Data contracts and interfaces.
- Existing design tokens and resource paths.
- Storybook and test expectations.
- Domain or feature ownership.
- Acceptance criteria.

## Agent Prompt Shape

Good MCP requests include:

```text
Create a molecule named SearchField in src/components/molecules.
Use existing Button, Icon, and Input atoms.
Add SearchField.interface.tsx, SearchField.mock.ts, SearchField.stories.tsx,
SearchField.test.tsx, _SearchField.style.scss, _index.scss, and index.tsx.
Use Atomic Resources tokens for spacing and colors.
The component must render in Storybook without page data.
```

## Implementation Rules

- Preserve generated file structure.
- Keep components typed.
- Keep mocks realistic and small.
- Keep stories isolated.
- Keep API calls in services or hooks.
- Keep domain behavior in domains.
- Keep atoms presentation-only.
- Update barrels after adding files.
- Run project checks after generation.

## Maintenance Workflow

1. Inspect current files first.
2. Identify generated conventions.
3. Update the smallest responsible layer.
4. Keep interfaces and mocks aligned.
5. Verify Storybook isolation.
6. Verify build and tests.