konradcinkusz

The architectural constitution (P1-P15), the review/modernize/recover session playbook, the repository baseline, the greenfield initializer that scaffolds an empty repo into a compliant containerized application, and the GitHub Pages one-pager generator. Install this one first; the other plugins assume it.

Getting services deployed and kept running: Fly.io, Azure AI Foundry, Azure operations, per-PR preview environments, customer-hosted private-cloud delivery, and GitHub Actions on local self-hosted runners.

Proving the system works and keeping the repo presentable: LLM evaluation, test strategy, E2E acceptance suites, security review, open-source release, and README badges.

How a repository documents scientific research, and how any document in the estate is authored so it compiles to PDF: the docs/research layout, the study document shape, the evidence rules, the house LaTeX preamble as a file every document \inputs, Beamer, diagrams called by slug, language and variant editions from one trunk, the LaTeX .gitignore, the CI build, and the templates and conformance check as bundled assets.

Recurring patterns inside services and the clients that call them: HTTP/API plumbing, identity, payments, Next.js frontends and BFFs, and browser extensions.

The per-ticket delivery procedure as phases you invoke: ticket analysis against an analysis document you refine run by run, the generation of a self-contained master prompt from it, the implementation phase itself, the review of a pull request against the ticket, and a feedback phase that lands a correction in the artifact that owns it. Unlike the other plugins, which are rules you consult, these are procedures you run — expressed in the constitution's terms rather than a generic checklist.