landing overview

Truthful flagship styling without broadening the contract.

oh-my-cursor uses this landing surface as its canonical public root. The content remains Cursor-native, docs-first, and explicit about what this repository actually owns.

Checked-in proof stays visible, host-product-only behavior stays bounded, and unsupported-or-out-of-scope packaging remains negative rather than implied support.

current public-graph checks

  • The hero, metadata, and primary heading all lead with oh-my-cursor.
  • Docs, State Contract, References, and Benchmark Notes stay visible from the landing surface.
  • Hooks and agents are described only as checked-in repo-owned artifacts.
  • repo-owned, host-product-only, and unsupported-or-out-of-scope stay visibly distinct.

required landing evidence links

Docs, state, references, and benchmark notes stay one click away.

The flagship landing surface exposes the repo-owned evidence needed to audit public wording before trusting stronger claims.

surface classes

The public contract stays explicit about ownership.

Every public sentence should preserve the difference between repo-owned, host-product-only, and unsupported-or-out-of-scope surfaces.

repo-owned

Checked-in surfaces this repo ships and can validate

  • apps/cursor-backbone-site/ as a repo-owned public site surface
  • Root AGENTS.md, .cursor/rules, .cursor/hooks, .cursor/agents, bounded docs, and validators
  • Benchmark artifacts that record checked-in evidence for the canonical repo root

host-product-only

Real Cursor capabilities that the product owns

  • Cursor CLI auth and default model availability in the user environment
  • Product-managed MCP support, modes, and background agents
  • Runtime session state and other host-managed surfaces outside this repo

unsupported-or-out-of-scope

Surfaces this repo intentionally does not claim today

  • Prompt packaging, custom modes, background-agent provisioning, or MCP defaults
  • Repo-file custom mode configuration or repo-file background-agent provisioning
  • A default repo-owned .cursor/mcp.json or repo-owned product packaging claims

proof ceiling

Proof class decides how far public wording may go.

The repo stays useful by making the strongest available proof visible and refusing silent upgrades from product capability to repo-owned behavior.

checked-in-artifact

Use for repo-owned files this repository actually ships, such as AGENTS.md, .cursor/rules, validators, benchmark artifacts, and this Pages app.

official-doc

Use for Cursor product capabilities the host documents, such as CLI consumption of AGENTS.md, MCP support, modes, and background agents.

runtime-smoke

Use only when optional authenticated smoke checks succeed; never let runtime possibility silently inflate checked-in ownership claims.

workflow artifacts

Hooks and agents stay evidence-backed.

The landing surface names hooks and agents only because they are checked in, wired from the plugin manifest, and covered by local validators.

Open workflow artifact validator