v0.3.0 — four new prompts, three new categories

v0.3.0 — breadth, made visible

The library was broader than its positioning claimed. This release both
extends it and finally says so.

42 prompts. 4 new. 3 new categories.

Four new prompts

Prompt	Category	What it covers
platform-engineering.md	platform (new)	Kubernetes, packaging, GitOps, networking, policy, secrets, progressive delivery, cost
backend-services.md	architecture	Language-neutral service design: boundaries, idempotency, consistency, versioning, resilience
data-platforms.md	data (new)	Lakehouse, data contracts, late-arriving data, lineage, quality gates, cost
jvm-backend.md	java (new)	Spring Boot vs Quarkus vs Micronaut, persistence, concurrency, JVM operations

Why platform engineering

The audit found zero infrastructure prompts in a library whose owner runs
K3s, Talos, and ArgoCD. It is written around what breaks when an agent writes
it: drift from a hand-mutated cluster, secrets in a ConfigMap or an image
layer, a change reaching 100% in one step, and a PodDisruptionBudget ignored
during a routine node upgrade.

Why backend services is language-neutral

The cross-stack claim was an assertion until this existed. Every
recommendation is a property of the operation rather than of a stack:
idempotency belongs to the operation, not the caller; a timeout means
unknown, not failed; a shared write needs a precondition; retries need a
budget and jitter. It names no language framework deliberately.

Why the JVM prompt is a comparison

The audit found Java was the only genuinely absent language, and the request
was for a comparison rather than a Spring manual. Each framework is stated
with its cost: Spring for ecosystem breadth, Quarkus for startup and native
image against a steeper extension model, Micronaut for compile-time DI
against the smallest ecosystem of the three.

Breadth, generated rather than claimed

A new Browse by Language table is generated from frontmatter, split on
implementation languages only, with framework and platform tags excluded so a
developer searching for their stack does not miss architecture or testing.

	Prompts
Go	17
Python	7
TypeScript	2
Any stack	16

Generating it also caught a mis-tagged prompt: llm-integration.md has 15
Python code blocks and no python tag. Fixed, which moved the "any stack"
count from 17 to 16. Three other candidates were checked and are genuinely
multi-language, so the number is honest rather than convenient.

Metadata

Description now leads with cross-stack practice rather than Go. Topics went
from 15 to 20, adding java, python, typescript, software-architecture,
and kubernetes. golang and aws stay — they are real search hooks.

Enforcement

All four new prompts carry anti-patterns and guardrails from the start, so
check_prompt_sections.py gates them like any other. Verified by injection:
stripping the guardrails from jvm-backend.md produces a non-zero exit
naming the file.

42 prompts, 44 pages, 2815 internal links resolve, all three structural
checks pass.

Also worth reading

The 0.1.1 section still documents the four wrong vendor facts corrected after
the first release. If you built an adapter from v0.1.0, read it before
trusting any value.

License

MIT.