Skip to content

CompospecHQ/.github

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 

Repository files navigation

Compospec Banner

Compospec

Semantic intelligence layer for AI-ready specs

Build product specifications as structured context cards with auto-generated flow diagrams.

Website LinkedIn


The Problem: Spec Chaos

AI can't fix broken specs. If your product requirements live in scattered docs, slides, and Slack threads; you're building prompt debt.

Every hallucination. Every misalignment. Every "AI got it wrong" moment traces back to one thing; unstructured context.


The Solution: Structured Context Blocks

Compospec is a specification intelligence platform that transforms chaotic requirements into:

  • 6-level hierarchy: Product → Module → UI → Section → Component → Element
  • Card-based specifications: Persistent, linked, version-controlled
  • Auto-generated flow diagrams: Visual representation of user journeys
  • AI-ready semantic structure: No prompt engineering required

How It Works

✍️ Write → Structured context cards
🔗 Link → Parent-child relationships across hierarchy
📊 Flow → Auto-generated diagrams from card connections

Your specs become a semantic intelligence layer ready for AI agents, developers, and stakeholders.


Why Compospec for AI-Native Pipelines

AI code generation tools (Cursor, GitHub Copilot, v0.dev) work well for isolated components but fail at system-wide consistency.

The problem isn't AI capability. It's context persistence.

The Three Failure Modes

Most AI workflows break at three points:

  1. Wrong Intent: AI misinterprets vague specs
  2. Wrong Visual: Generated code doesn't match design system
  3. Wrong Patterns: Output doesn't fit codebase conventions

Compospec as Pre-AI Semantic Layer

Instead of prompting AI directly, Compospec provides structured context that AI pipelines can query:

Hierarchical Cards → preserve intent cascade and parent context flows to child cards
Decision Subcards → (coming Q2 2026) capture component behavior as queryable state machines
Journey Maps → maintain multi-step workflow context across the pipeline
MCP Protocol Integration → (coming Q1 2026) connects directly to Claude, Cursor, Figma MCP, Code Connect

Spec.md is a File. Compospec is a Schema.

That's the difference between using AI and shipping with it.


Use Cases

  • Spec-driven development: Start with structure, not chaos
  • AI-native pipelines: Pre-AI semantic layer for Cursor, Copilot, v0.dev workflows
  • AI agent context: Feed semantically rich specs to LLMs
  • Cross-team alignment: Single source of truth for product, design, engineering
  • Legacy modernization: Document existing systems with precision

Get Started

👉 Try Compospec

📧 Questions?[email protected]


Built with conviction in London 🇬🇧

About

Semantic spec layer for AI. Build product specifications as structured context cards and auto-generated flows.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors