Home — specdir.com

One Clear Definition for Each App Module

A Spectral Domain is a complete application context. In plain words: it is one module definition (for example users, orders, or billing) that your team and AI tools can both understand.

Step 1: define data, screens, actions, and APIs once.
Step 2: implement that module in your own stack.
Step 3: serve it via MCP so consumers know what comes in and how to visualize it.

domain.modelFields, types, constraints, relations

domain.viewsPresentation intent for any renderer

domain.interactionsActions, permissions, events

domain.interfacesREST and MCP exposure contracts

How It Works See a Real Package Browse Directory Publish a Package

Why Spectral Exists

No-code builders made app creation easier for non-coders. Coding teams still need a clean way to communicate business context across people, codebases, and AI tools.

Spectral is that missing layer: a text-first definition of an application module that includes data model, UI intent, interactions, and interfaces.

Publish it once, implement it in your own stack, or consume it through MCP with clear visualization guidance.

Using a Package

Reference any Spectral package by URL in your .spectral file:

dependencies:
  - https://specdir.com/packages/juice.users/index.spectral

Then tell your AI agent: "Integrate the juice.users package from the dependency URL into this application." The agent fetches the spec, reads the nodes, and implements it against your stack.

Implementing with AI

Every package page includes a ready-to-use prompt. Copy it into any AI coding tool to generate a full-stack implementation from the spec.

Try it with juice.users →

For AI Agents

Fetch the full registry programmatically:

GET https://specdir.com/registry.yaml
GET https://specdir.com/registry.json