Methodology

Use Case Pattern

An architectural methodology: a language-neutral contract plus Java, Python, and Node bindings

↓ consists of

Knowledge

Standards

1,472 rules with codes R-AGG-X4, PG-T-013 across 17 style guides.

Contract

Specifications (spec-as-code)

16 sections in the repo alongside the code. Section depth is chosen to match the service's maturity level.

Depth

4 maturity levels

The team picks a level to fit the task — from MVP to hexagonal.

Implementation

Reference libraries

The reference Java binding, open-source, Apache-2.0. Python and Node bindings are assembled from their ecosystems.

↓ implemented by bindings

Binding · ready

Java

Spring Boot, jOOQ, reference libraries. Articles are in Standards.

Binding · ready

Python

FastAPI, SQLAlchemy, Pydantic. Style guide and ucp-py-* skills.

Binding · ready

Node

NestJS, TypeORM, class-validator. Style guide and ucp-node-* skills.

Binding · in progress

Go

net/http + chi, sqlc. Code prefixes are reserved.

↓ applied through

AI executors · open .md format

130+ Claude AI skills

Design: read the spec, generate services by maturity level and libraries.   Review: check PRs against the standards, citing specific rules. Each binding has its own set: ucp-* (Java), ucp-py-*, ucp-node-*.
Every skill is a plain .md file. The team reads, edits, and forks it — no black box.

↓ outcome for the team

Services are written consistently and fast. Every PR is reviewed against one and the same standard — automatically, without hiring another architect.

→ Detailed description of each entity and its relationships

→ How to apply Discuss on Telegram

Who benefits

A backend team of 5+ (Java/Kotlin, Python, or Node), a product built for years ahead. If even one symptom feels familiar, it's worth talking.

The code is becoming hard to maintain

Every feature costs more than the last. Juniors write "the way they're used to," seniors spend reviews on style instead of the domain.

→ How to start applying UCP

AI writes code, but there's no consistency

Three Claude sessions give three different solutions. A year later — ten services in ten styles.

→ Why a methodology when you have AI

Specs go stale before they're even approved

The analyst writes, the developer rewrites, and a month later no one knows where the truth is.

→ Spec-as-code

How UCP differs from other approaches

BMAD-METHOD: agent roles and a delivery loop

BMAD organizes thinking before code but carries no rules for the code itself. UCP is the opposite: domain, architecture and executable standards.

→ UCP vs BMAD-METHOD

OpenSpec, Spec Kit, Kiro: a spec of a change

Spec-driven tools describe the delta of the current change. The UCP specification describes the system and lives with the service.

→ UCP vs spec-driven tools

Recognize yourself?

A 30-minute chat on Telegram — we'll discuss the context and agree on a format. No "about the company" slides.

→ Get in touch