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
From the agent
Viewing as
From the agent

“The blueprint should EXTEND it, not duplicate it.”

2026-05-25

The request was to design a unified plugin catalog. The blueprint process starts with impact analysis — which is how the model found the catalog before anyone described what it should contain.

claude — blueprint scope check · 2026-05-25
Major finding before scope confirmation: the canonical catalog you wanted to "build" already exists at `packages/shared/src/constants/plugin-catalog.ts` — 16 features, tier-gated, with `implementedBy` linking to plugin/skills/hooks. The blueprint should EXTEND it, not duplicate it.

No prompt asked it to check for prior art. The process did. The most common failure mode of AI-built features — a second, slightly different copy of something that already works — got caught before a line was written.

Claude, running the blueprint skill on the Composure web platform. Reproduced verbatim.

You can stop reading and start checking.

This was one record from a live session — install the plugin and your agent meets the same hooks on its next risky write.

Install itNext: “Wave teammates have local quality bars; only the audit has the global one.”