Docs
Landing-level repo guidance and the ownership map for this Cursor-native backbone.
Open Docscanonical public root
A repo-owned flagship landing surface that keeps docs, state boundaries, references, and benchmark notes visible while preserving the distinction between repo-owned proof and host-product-only Cursor capability.
landing overview
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
required landing evidence links
The flagship landing surface exposes the repo-owned evidence needed to audit public wording before trusting stronger claims.
Landing-level repo guidance and the ownership map for this Cursor-native backbone.
Open DocsChecked-in boundary rules for repo-owned surfaces versus host-product-only user state.
Open State ContractOfficial-doc citations and access dates behind the public claims made by this repo.
Open ReferencesReporting-comparable benchmark notes for this smaller, truthful Cursor contract.
Open Benchmark Notessurface classes
Every public sentence should preserve the difference between repo-owned, host-product-only, and unsupported-or-out-of-scope surfaces.
repo-owned
host-product-only
unsupported-or-out-of-scope
proof ceiling
The repo stays useful by making the strongest available proof visible and refusing silent upgrades from product capability to repo-owned behavior.
Use for repo-owned files this repository actually ships, such as AGENTS.md, .cursor/rules, validators, benchmark artifacts, and this Pages app.
Use for Cursor product capabilities the host documents, such as CLI consumption of AGENTS.md, MCP support, modes, and background agents.
Use only when optional authenticated smoke checks succeed; never let runtime possibility silently inflate checked-in ownership claims.
validators
workflow artifacts
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