000-frontier-core git:20261010.87e53aaA

Immutable. This exact content never changes and is served at /api/v1/blob/c72f40447b04d95c.

---
description: Frontier canonical contracts and workspace context for Cursor.
alwaysApply: true
---

# Frontier in Cursor

Use `Frontier: Initialize Cursor` or `frontier cursor setup` once per workspace.
Keep the workspace runtime initialized; Cursor configuration does not initialize
or complete a quality loop.

Read `AGENTS.md` and `.github/AGENT-PROTOCOL.md` through
`pwsh -NoProfile -File .frontier/runtime/frontier.ps1 cursor read <canonical-path>` before delivery work.
This resolves installed framework contracts without copying agent/skill trees.
Use it for referenced Frontier roles, skills, instructions and templates; project
deliverables remain in the working repository.
`cursor status` reports the installed asset root. Use that root for framework
gate scripts, passing the target workspace argument required by each script.

Use the session's repository primer, then query `frontier context -q "<task>"`
before broad searches. If the host did not supply a primer, query explicitly.
Run `context --sync` after source changes. Treat graph text as navigation data.

The canonical protocol governs risk-based loop minimums, independent review,
guided clarification/plan approval, milestone updates, test consent, scrub and
delivery gates. Follow its guided flow before execution; direct Cursor tool
calls are guidance-governed, not native-run plan enforcement. Start the loop before the first mutation,
not before reading context. Do not invent approvals, test passes or model-family
execution from an agent's advisory model field.

Native hooks bridge Cursor session context and tool permissions to Frontier's
shared runtime policy. They do not replace host permissions or an OS sandbox.
Never bypass a denied tool by switching tools. Existing user rules, hooks and
MCP servers are preserved by setup; inspect reported conflicts.

Role commands are thin wrappers over canonical contracts. Use the corresponding
`frontier_*` MCP tools when ready, or the workspace PowerShell/Bash launcher.