Stats
Actions
Available In
Tags
Plugin
be
Engineering base: 25 skills (process, backend, frontend, QA, security, ops), 12 specialized agents, session-continuity automation, ADR/SDD/release workflows.
What's Inside
Slash Commands7
Adr
/adr
Create a new Architecture Decision Record — /be:adr <short decision title>
Bootstrap
/bootstrap
Bootstrap the engineering base in the current project — docs structure, CLAUDE.md, and session protocol
Impact
/impact
Analyze the blast radius of the current changes — risk level + targeted review checklist
Release Check
/release-check
Run the pre-go-live checklist and draft the changelog entry for the release
Session End
/session-end
Close a work session — update HISTORY.md, structural-analysis, lessons-learned, and commit docs with the code
Agents12
mgmt-project-manager
/mgmt-project-manager
Use for coordination work — sequencing multi-agent features, maintaining API contracts before development, removing blockers, and running the sprint protocol. Analysis role: does not edit application code.
ops-sre
/ops-sre
Use for reliability and operations work — defining SLOs, configuring monitoring and alerts, writing runbooks, incident response coordination, and postmortems.
qa-engineer
/qa-engineer
Use for test design and implementation — unit, integration, and E2E tests, coverage analysis, and bug reproduction. Rule: a bug becomes a failing test before it gets fixed.
dev-backend
/dev-backend
Use for backend implementation tasks — REST endpoints, business rules, persistence, database migrations, and server-side security. Delegates security review to qa-security-reviewer and test design to qa-engineer.
dev-data-analyst
/dev-data-analyst
Use for BI, analytics, and automatic-insight tasks — designing analytical queries, defining metrics and KPIs, and implementing anomaly/trend detection. Read-only over production data: never creates, changes, or removes records.
Skills25
be-api-error-handling
/be-api-error-handling
Use when creating a centralized exception handler, adding new error types, or defining a REST API's error response contract. Exception hierarchy, HTTP status mapping, and RFC 9457 problem-details format, with a Spring Boot example as a resource.
be-api-versioning
/be-api-versioning
Use when creating the initial structure of a REST API, introducing a breaking change, or migrating unversioned endpoints to a versioned model. URL-prefix strategy (/api/v1/), breaking-change criteria, deprecation lifecycle with Sunset headers, and a phased migration checklist.
be-db-migrations
/be-db-migrations
Use when creating tables, adding columns, creating indexes, changing constraints, or migrating data with any versioned migration tool (Flyway, Liquibase, Alembic, Prisma Migrate, Rails migrations). Naming, idempotency, and safe schema evolution rules.
be-jwt-auth-patterns
/be-jwt-auth-patterns
Use when implementing token-based authentication (JWT), deciding how to revoke tokens on logout, or choosing where to store tokens on the client. Stack-agnostic flow, secret handling, blocklist revocation, and client storage rules, with Java/Spring examples as a resource.
be-pagination-patterns
/be-pagination-patterns
Use when implementing or fixing any REST endpoint that returns a collection. Never return an unbounded list — server-side pagination with offset or cursor strategies, response contract, and limits. Spring Boot and Angular examples as on-demand resources.
Stats
Version2.0.0
LanguageJavaScript
Stars0
MaintenanceGood
LicenseMIT
Last Commit
Added
Available In
Safety Signals
Caution
Uses power tools
Uses Bash, Write, or Edit tools
