ompsure
  • Reviews
  • Pro
  • Pricing
  • Template
Sign InSign Up
ompsure

Code quality that happens automatically.
Free for personal use.

Audience

  • Who's It For?
  • For Creators
  • For Developers

Features

  • Code Graph
  • Security
  • Code Review
  • Testing
  • Deployment
  • Memory

Product

  • Plugins
  • Control Panel
  • Proof
  • Catalog
  • How It Works

Plans

  • Pricing
  • Pro Patterns
  • Commercial License
  • Starter Template

Resources

  • Getting Started
  • Documentation
  • Reviews
  • Affiliate Program

© 2026 Et'al Software Solutions. All rights reserved.

  • Template License
  • Plugin License
  • Refund Policy
  • GitHub
Viewing as
ProofMechanismClassifierExamplesA real feature
Examples

One sentence in. The right rules out.

Several patterns, the owning skill carrying the build.

AllA first askA real featureA whole build

a mailing-metrics tool · a planning ask

$ “help me plan what our AI agents are going to be — that could be a blueprint on its own”

Force-read before the turn

AI agentsAGENCYwebhook receiversPROInbox threads messagesPRO

The work runs through

/composure:blueprint

A tracked, three-phase build — schema, roster, runtime — plus an admin fleet surface, every phase spec'd from the fetched patterns before a line was written.

an agency CRM · a build request

$ “replace the calendar's create/edit with a multi-step wizard, like the account one”

Force-read before the turn

Multi step wizardPRO

The work runs through

/composure:blueprint

The wizard shipped by mirroring the existing pattern — and a follow-up blueprint reused the same meeting-token API instead of building new invite infrastructure.

a mailing-metrics tool · a build request

$ “launch the MCP server build — the blueprint queued it as its own task”

The work runs through

/composure:blueprint/composure:mcp-builder

One blueprint's task queue dispatched a second named skill — the MCP server and its connections UI shipped in the same run. Skills compose.

a dance-studio SaaS · a security catch, at write time

$ “(no prompt — a write tripped the guard mid-build)”

The work runs through

[sentinel] secret-guard

The guard flagged a required database-role grant as a leaked credential — a false positive. The agent refused to bypass it, surfaced the tradeoff, and the owner approved a scoped fix that kept the real leak rule live everywhere. Protection, not just automation.

Composure's own repos (dogfooding) · a routing question

$ “why did the generic review skill run instead of ours?”

The work runs through

/composure:blueprint/composure:critique

The classifier's own routing gap became a blueprint, the docs were corrected, and the fixed pipeline reviewed the fix — the system catching and correcting itself, live.

a nutrition-coaching app · a product-planning ask

$ “auto-generate the captions — and build our own engagement dashboard”

The work runs through

/design-forge:product-planner/composure:blueprint

The planner mapped per-tier screen depth first; its output directly scoped an expanded blueprint that superseded the narrower one — plugins composing across the suite.

a nutrition-coaching app · an enforcement misfire, handled with judgment

$ “(no prompt — an enforcement hook fired on the wrong trigger)”

The work runs through

[testbench] skill-enforcement

A sub-agent's brief tripped the testing hook on ordinary prose. The orchestrator recognized the misfire, refused to obey the injected directive blindly, verified nothing was lost, and documented the gotcha — enforcement AND skepticism, both real.

Every walkthrough traces to a real session in the archive — prompts paraphrased, project flavors generalized, no client specifics. Where a skill had no real moment to show, it isn't shown.

Browse everything it can pullHow the classifier works