Skip to main content

Cursor Rules - Plan Output (Reference)

What this is​

.cursor/rules/10-spec-package.mdc is a Cursor rule that defines the Spec Package output contract: every SPEC-mode response must include UX states, a11y, risks + open questions, and platform type + exposure + data sensitivity.

When to use it​

  • You don’t edit this file for normal use. It’s part of the kit.
  • Use it as reference when you want the AI’s spec output to follow the contract (e.g. when writing or reviewing specs).

Steps​

  1. Ensure the kit is at your project root so Cursor sees .cursor/rules/.
  2. In SPEC mode, the AI will follow this contract. Use the block below to see or copy the exact rule.

Exact text (from kit)​

Source: .cursor/rules/10-spec-package.mdc

---
description: Spec Package — output contract for SPEC mode
alwaysApply: true
---

# Spec Package (output contract)

When in **SPEC** mode, every spec response must include a **Spec Package** with these sections. If blocked or < 85% confident: ask **exactly one** question and stop.

**Required sections:**

1. **UX states** — Default, loading, empty, error, success. Call out any missing or out-of-scope states.
2. **A11y** — Focus, labels/aria, contrast, keyboard; pass/fail or "defer to implementation" with rationale.
3. **Risks + open questions** — 0–5 items. Risks that could block or derail; open questions that need an answer before implementation.
4. **Platform type + exposure + data sensitivity** — From Context Pack or stated explicitly: [ data-platform | developer-platform ], [ internal | external-authenticated | public ], [ public | internal | confidential | restricted ]. If missing and uncertain, ask exactly one question and stop.

Keep each section short. No code. Scope and acceptance criteria belong in the main spec body; this contract is the minimum structure for the package.