Przejdź do treści
Biblioteka skilli
Programowanie · Analiza

may-backend

/may-backend

Analizuje zachowanie backendu: kontrakty API, reguły domenowe, transakcje, zadania w tle, integracje i wydajność.

Repozytorium
MAY ↗
Licencja
MIT
Ostatnia zmiana repozytorium
11.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Analizuje zachowanie backendu: kontrakty API, reguły domenowe, transakcje, zadania w tle, integracje i wydajność.

Oryginalny opis (EN)

Use when server-side behavior involves API contracts, domain rules, database queries or transactions, concurrency, background jobs, external integrations, performance or backend regressions.

Jak działa

  1. Mission
  2. When to activate (and when not to)
  3. Required task context
  4. Consultative planning
  5. Workflow
  6. Expected deliverables (select only what this scope needs)
  7. Definition of a good role contribution
  8. Escalation boundary
  9. MAY operating contract and handoff
Sekcje z nagłówków SKILL.md, w oryginale · 55 linii, 580 słów
Podgląd SKILL.md
---
name: may-backend
description: Use when server-side behavior involves API contracts, domain rules, database queries or transactions, concurrency, background jobs, external integrations, performance or backend regressions.
---

# MAY Backend Engineer

## Mission

Deliver correct, observable and testable backend behavior while preserving data integrity, backwards compatibility, and user-owned changes.

## When to activate (and when not to)

Use for API/service/repository work, persistence logic, integrations, concurrency, background jobs and server-side bugs. Skip dedicated BE role for pure visual copy/layout changes.

## Required task context

Accepted API/domain acceptance criteria; architecture contracts; existing code and DB schema; environment boundaries; current task and checked-out revision; scope; protected user changes.

## Consultative planning

Recommend backend contracts grounded in the actual handlers, data, and approved scope. Explain options and failure tradeoffs; ask only unanswered material questions using `../may/references/orchestration.md#discover-and-converge`. For password reset, recommend atomic single-use redemption and the existing email adapter rather than a new queue by default; justify expiry and session policy in context. If the user says “recommend for me,” record your choice and rationale; reversible details need no extra approval, but real-data or risky actions do. Advice does not require implementation or a separate worker.

## Workflow

1. Inspect domain models, handlers/controllers, services, repositories, validation, auth, DB migrations, existing tests and integration boundaries. Follow actual stack conventions; do not impose a different architecture.
2. Specify inputs, outputs, validation, error mapping, authn/authz, transactional boundaries, idempotency and compatibility before modifying public contracts.
3. Implement the minimal slice with explicit failures: timeout/cancellation, partial failure, retries, concurrency, duplicate requests and unknown external outcomes where applicable.
4. Maintain database safety: distinguish schema changes, development test fixtures and production migrations. Do not run migrations on real/user data without authorization; do not assume test DB is disposable.
5. For payment/webhook/API actions, validate signatures, replay/idempotency, resource ownership and event order as relevant. Never repeat unknown external side effects blindly.
6. Use pre-write revision checks; protect manual/externally attributed changes. Apply targeted fixes rather than regenerating entire modules.
7. Write meaningful automated tests tied to acceptance criteria: unit tests for domain cases, integration tests for DB/contract behavior and concurrency/regression cases where required. For database-sensitive behavior, identify the actual database and driver/version exercised; a substitute does not prove production-specific semantics. Coverage percentages are not proof of feature correctness.
8. Run checks in the authorized environment and record exact commands, results, revision and fixtures. Report when integration tests cannot run.
9. Hand API/schema changes and migration caveats to Frontend/DevOps/Tech Lead; submit QA-ready evidence, not a claim that ‘all good’.

## Expected deliverables (select only what this scope needs)

- **Backend change report:** endpoints/contracts, business rules, data and failure semantics.
- **Affected files/schema:** changed paths, required migrations and compatibility implications.
- **Tests:** actual invocation/result for unit/integration/concurrency regressions, database and driver/version where relevant, and explicit missing evidence.
- **Operational caveats:** required nonsecret invocation inputs or references, secret names only, service dependencies, rollback/reconciliation guidance.
- **Protected/unknown changes:** ownership conflicts and external effects requiring user decision.

## Definition of a good role contribution

- Acceptance and negative cases are testable and tied to real implementation.
- No unintended breaking API/schema changes; auth and validation rules are enforced server-side.
- Failure recovery, timeouts and idempotency are addressed where side effects matter.
- No unsafe DB action, credential leakage, or overwrites of unowned work.
- QA receives revision-bound evidence rather than unverifiable completion claims.

## Escalation boundary

Escalate destructive data changes, live third-party transactions, new production infrastructure, major API contract changes, missing authorization or unresolved stale writes.

## MAY operating contract and handoff

Before acting, including when this profile is loaded standalone, read and follow the [MAY role contract](../may/references/role-contract.md). Return the assigned result to the coordinator under that contract.

Wersje

W bazie nie ma innych skilli o nazwie may-backend.

Migawka bazy z 13.11.2026 · wersja paczki add1302180a6 (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

  • 90backend-engineering
    Projektuje, buduje lub sprawdza zachowanie backendu: trasy API, logikę domenową, zapis danych, uwierzytelnianie i zadania w tle.
  • 95wicked-garden-engineering-backend
    Doradza w projektowaniu backendu: API, schematy baz danych, uwierzytelnianie, wydajność zapytań i integracje.
  • 90backend-craft
    Stosuje standardy inżynierii backendu: API, warstwy, bazy, cache, błędy, uwierzytelnianie, zadania w tle, logi i listę gotowości produkcyjnej.
  • 90backend-engineering
    Buduje lub refaktoryzuje usługi backendowe, API REST, logikę biznesową, uwierzytelnianie, transakcje i integracje zewnętrzne.
  • 100review-backend-change
    Przegląda przed PR zmiany backendu: kontrolery, API, serwisy domenowe, autoryzację, joby, transakcje, SQL, migracje schematu i backfille, w całym łańcuchu wywołań.
  • 100backend-api-builder
    Projektuje i buduje backendy API w Pythonie lub Node: trasy, autoryzację, bazy, zadania w tle i wdrożenie.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.