CogentSpec

CogentSpec for Claude

CogentSpec

Contract-driven project accelerators for Claude...

CogentSpec equips Claude with engineered Contract Packs—production-ready frameworks and built-in guardrails that take your idea from concept to controlled release while reducing costly trial and error.

Set up Claude DesktopCogentSpec Q&A

Build Strong

Select from a growing number of contract to ensure foundational stability.

Build Qualty

Production-ready assets and guardrails keep Claude focused and consistent.

Build Fast

Move from first prompt to finished product with a clear path to production.

Contract matched

Website Contract

Software
project-type.website
Executable foundationWebsite Contract Pack v2.1.0 ready
  • Runtime and delivery
  • Functional behaviour
  • Security and resilience
  • Acceptance evidence
Use Website contract

Step 1

Install Claude Desktop

Use the Claude Desktop Code tab on Windows or macOS. CogentSpec runs as a Claude Code plugin and does not require the separate CogentSpec Desktop installer.

Get Claude Desktop

Step 2

Add CogentSpec

Add the CogentSpec Git marketplace, install the plugin, then enter $cogentspec. The command connects that Claude project to its logical CogentSpec context and returns the matching web workspace.

Open setup

For Claude Web

Use Claude in Chrome

Open the CogentSpec web workspace and keep Claude in the Chrome side panel beside it. Claude in Chrome requires a paid Pro, Max, Team, or Enterprise plan.

Explore the Web workflow

Choose the closest project type. CogentSpec will bind the standards, obligations, and release gates that apply to the build.

Engineered Contract Packs

Skip the setup. Start from a production system.

CogentSpec defines 34 engineered project-type contracts. Website v2.1.0 is the first fully executable Contract Pack, with additional packs being progressively activated.

34engineered project-type contracts

Website Contract Pack v2.1.0 contains

  • Starter application
  • General and showcase patterns
  • Pinned contract binding
  • Selected project profile
  • Semantic application shell
  • Responsive safeguards
  • Accessibility controls
  • Foundation test suite
  • SEO discovery routes
  • Acceptance evidence map
  • Local launch automation
  • Release recipes
  • Content release gate
  • Local, private, and public modes

A curated, opinionated production library with an AI operating layer

Repeatable work should not restart from zero.

Freelancers and agencies rebuild authentication, administration, security controls, test harnesses, and deployment configuration across the same categories of project. CogentSpec starts with those decisions engineered and the acceptance criteria already defined, turning time saved into something measurable rather than a vague claim about better guardrails.

Evidence, not assertion

Inspect the evidence that makes Website v2.1.0 release-ready.

These sanitised diagrams come directly from the current Website Contract Pack structure, acceptance map, foundation tests, and release checks. Protected contract rules remain server-side; the production evidence does not.

01

Generated architecture

What the pack instantiates

  1. Contract pin.coge/contract-binding.json
  2. Selected profile.coge/project-profile.json
  3. Website foundationapp/ + components + configuration
  4. Acceptance evidence.coge/acceptance-map.json
  5. Release recipe.coge/release-recipe.json

The contract version and checksum are pinned. A mismatched Contract Pack stops rather than presenting an incompatible build as compliant.

02

Verification architecture

What blocks an incomplete release

  1. Build and foundation testsDeterministic source, semantic structure, keyboard readiness, and rendered output.
  2. Accessibility and discoveryResponsive safeguards, focus visibility, reduced motion, robots, sitemap, and not-found recovery.
  3. Content release gateStarter content, missing assets, and unresolved decision markers block release.
  4. Controlled release modeLocal, private, or explicitly confirmed public deployment.
Sanitised foundation-test excerpt
assert.equal(binding.packVersion, "2.1.0");
assert.match(html, /<main\b[^>]*id="main-content"/i);
assert.equal(robots.status, 200);
Inspect the Website v2.1.0 evidence

Architectural difference

Direct dialogue.Governed delivery.

CogentSpec keeps you in direct conversation with the AI while an approved project contract provides the structure, requirements, controls, and acceptance criteria alongside that conversation.

01

Agentic builders

The agent mediates the work.

Platforms such as Replit-style builders place an AI agent inside their own execution environment. The agent edits files, runs commands, maintains working state, and reports through the platform's agent loop.

YouAgent loopBuild
02

CogentSpec

The contract governs the work.

You discuss refinements naturally with the AI rather than routing every change through a separate builder agent. The contract keeps delivery controlled without becoming a translation layer between you and the model.

You ↔ AIApproved contract