scaffold-message-handler
/scaffold-message-handler
Tworzy szkielet konsumenta wiadomości w workspace .NET (MassTransit, RabbitMQ, Azure Service Bus lub podobne), najpierw zbierając wymagania.
- Autor
- tibursocampos ↗
- Repozytorium
- agent-dev-toolkit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 21.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 10
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 21.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Tworzy szkielet konsumenta wiadomości w workspace .NET (MassTransit, RabbitMQ, Azure Service Bus lub podobne), najpierw zbierając wymagania.
Oryginalny opis (EN)
Scaffold a message consumer in a .NET workspace (MassTransit, RabbitMQ, Azure Service Bus when detected, or similar). Collects requirements first. Use when creating a consumer or invoking /scaffold-message-handler.
Jak działa
- STOP - Read before ANY tool call
- Status
- Trigger
- Outcome
- Lazy-load
- Process
- Must not
- Handoff examples
Podgląd SKILL.md
---
name: scaffold-message-handler
description: Scaffold a message consumer in a .NET workspace (MassTransit, RabbitMQ, Azure Service Bus when detected, or similar). Collects requirements first. Use when creating a consumer or invoking /scaffold-message-handler.
---
## STOP - Read before ANY tool call
1. Read `{{GUARDRAILS_PATH}}`
2. Read `_shared/sdd-artifacts/SESSION.md`; load session-state for `$Cwd`
3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell
4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only
5. This skill body is **English**; user-facing prompts may be **(pt-BR)**
### Step -1 - Gate check (report in chat before continuing)
```
Gate check:
[ ] guardrails.mdc read
[ ] SESSION.md read; session-state loaded
[ ] PIPELINE.md read (SDD skills only)
[ ] User confirmed current action (sim)
-> If any unchecked: STOP
```
---
# Skill: scaffold-message-handler
## Status
**Scaffold** - guides discovery, requirements, and implementation in the **target repository**. This toolkit ships **no** embedded corporate consumer templates or org-specific wiring.
## Trigger
**Negative signal:** Do not activate this skill when the request lacks one of the positive signals below or its required context; topic similarity or an isolated keyword alone is insufficient.
Invoke when the user asks for: `/scaffold-message-handler`, `create message consumer`, `/scaffold-message-handler`, or when a PLAN step adds a new queue/topic handler.
Optional arguments: message or event name, queue/topic name, or path to an existing consumer to mirror.
## Outcome
In the **target workspace** (not this toolkit repo unless it is the .NET repo under work):
1. Detected messaging stack and reference consumer(s)
2. Confirmed requirements (payload, errors, idempotency, retry, DLQ)
3. Proposed file layout aligned with the repo
4. Scaffold code and tests **only after** user confirmation - following **existing** project patterns, not copied templates from this repo
## Lazy-load
| When | Path |
|------|------|
| Reference index (routing only) | `skills/scaffold-message-handler/reference.md` or `{{TOOLKIT_ROOT}}/skills/scaffold-message-handler/reference.md` after sync |
| Process step detail (lazy) | `skills/scaffold-message-handler/references/<section>.md` |
| Generating or reviewing .NET code | `{{TOOLKIT_ROOT}}/skills/_shared/dotnet-guidelines/clean-architecture.md` |
| C# conventions | `{{TOOLKIT_ROOT}}/skills/_shared/dotnet-guidelines/csharp-patterns.md` |
| .NET test patterns | `{{TOOLKIT_ROOT}}/skills/_shared/dotnet-guidelines/dotnet-test-patterns.md` |
| Structure / quality (when coding) | `{{TOOLKIT_ROOT}}/skills/_shared/code-guidelines/principles/structure-and-quality.md` |
| Small follow-up without SDD | `/dotnet-developer` |
**Never by default:** do not preload all `references/*.md`, full messaging docs, or unrelated guideline packs. Load **one** `references/<section>.md` per Process step (`SKILL-REFERENCE-RETRIEVAL.md`).
## Process
Read `references/<section>.md` for detection/checklists — **not** full `reference.md`.
### 0. Workspace
Confirm **target .NET repository** (`.sln` or worker/API with messaging). If the workspace is the toolkit only, stop and ask which repo to open.
### 1. Detect messaging stack
Grep/Glob per `references/stack-detection.md`. Report:
| Signal | Likely stack |
|--------|----------------|
| `MassTransit`, `IConsumer<T>` | MassTransit (transport varies) |
| `RabbitMQ.Client`, `ConnectionFactory` | RabbitMQ direct |
| `Azure.Messaging.ServiceBus` (or similar ASB packages) | Azure Service Bus SDK |
| Other | Describe generically; read one existing consumer |
**Default when none detected:** MassTransit with RabbitMQ transport (implicit). Still collect requirements before scaffolding. Use Azure Service Bus only when ASB packages or existing ASB wiring are already in the repo.
Do **not** require corporate `docs/consumidores/` paths.
### 2. Find conventions
Glob existing consumers/handlers in the repo. Note: namespace layout, registration (`AddMassTransit`, hosted service, etc.), message contract location, test project pattern.
If **no** consumer exists, say so and propose a layout consistent with Clean Architecture after reading `clean-architecture.md` (`references/layering.md`).
### 3. Collect requirements (blocker before code)
Ask using `references/requirements-checklist.md`. Minimum:
- Queue or topic name (and subscription if applicable)
- Message contract (type name, key fields, schema source)
- Processing responsibility (what changes in the system)
- Error handling: retry count/backoff, DLQ or error queue
- Idempotency strategy (natural key, outbox, dedup store)
- Test expectations (unit vs integration)
Wait for answers. Do not invent queue names or payloads.
### 4. Propose scaffold plan
Present (`references/scaffold-checklist.md`):
- Files to add or extend (paths from repo conventions)
- Registration point (DI / MassTransit config)
- Test files and how to run them
Ask explicit confirmation before writing code.
### 5. Implement (target repo only)
After confirmation:
1. Load `clean-architecture.md` and `csharp-patterns.md`; when adding tests, load `dotnet-test-patterns.md` (`references/layering.md`, `references/test-guidance.md`)
2. Mirror naming and folder structure from step 2
3. Add consumer/handler, contract if missing, registration, and tests
4. Run `dotnet build` and targeted `dotnet test` for affected projects
### 6. Summarize handoff
Report: stack detected, paths touched, how to run locally, open risks (idempotency, poison messages). See `references/related-skills.md`, `references/exclusions.md`, `references/context-management.md`.
| Situation | Next |
|-----------|------|
| Commit | `/commit` |
| Part of SDD PLAN step | Mark PLAN step; continue in new session if another step remains |
| Build failure | `/repair-dotnet-build` |
## Must not
- Ship or copy hardcoded consumer templates from ai-prompts or internal org repos into the toolkit
- Assume a specific organization or proprietary observability tools
- Generate code before requirements are collected and the user confirms the plan
- Preload entire `dotnet-guidelines/` tree beyond clean-architecture and csharp-patterns when coding
## Handoff examples
```
/repair-dotnet-build
```
```
/sdd-develop - <full-plan-path> - Step N
```
SDD `PLAN` paths: resolve per `{{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/STORAGE.md` (`features/**/PLAN/PLAN_*.md` or global `{{SDD_ROOT}}/<repo-id>/features/**/PLAN/` only). Not root/flat `PLAN/` and not `docs/documentation-plan/plan.md`.
Pliki w paczce (10)
- SKILL.md 7 KB
- reference.md 1 KB
- references/context-management.md 1 KB
- references/exclusions.md 1 KB
- references/layering.md 1 KB
- references/related-skills.md 1 KB
- references/requirements-checklist.md 1 KB
- references/scaffold-checklist.md 1 KB
- references/stack-detection.md 1 KB
- references/test-guidance.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie scaffold-message-handler.
Migawka bazy z 13.11.2026 · wersja paczki 273273f376ce (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100messaging
Omawia wzorce wiadomości asynchronicznych w aplikacjach .NET: Wolverine, MassTransit, outbox, sagi, choreografię i konfigurację brokerów RabbitMQ oraz Azure Service Bus. - 100masstransit
Pomaga budować rozproszone systemy komunikatów w .NET z MassTransit: pub/sub, request/response, sagi i wzorzec outbox, z RabbitMQ, Azure Service Bus i Amazon SQS. - 100rebus
Pomaga budować aplikacje .NET oparte na komunikatach z Rebus: lekka szyna usług, pub/sub z RabbitMQ lub Azure Service Bus, sagi, routing i wiadomości odroczone. - 100message-queue
Tworzy kompletną warstwę kolejki wiadomości w module Magento 2: temat w communication.xml, powiązania queue_topology, publisher i consumer, typowany DTO oraz idempotentny handler. - 100azure-servicebus-ts
Buduje aplikacje komunikacyjne z Azure Service Bus SDK dla JavaScriptu (@azure/service-bus): kolejki, tematy i subskrypcje, sesje wiadomości oraz obsługa dead letter. - 100azure-service-bus
Obsługuje Azure Service Bus jako korporacyjne kolejkowanie wiadomości: kolejki, tematy, sesje i transakcje, także w scenariuszach hybrydowych z managed identity i filtrami subskrypcji.