Skip to main content
If you’re using Cursor or Claude Code with @neuraldraft/mcp installed, this isn’t strictly necessary — the MCP server already injects the right conventions. But MCP works best paired with project-level rules so the AI has the context even when MCP isn’t reachable (offline, rate-limited, exploring a side branch). Drop one of the templates below into your repo. Both Cursor and Claude Code read project-level instructions before answering — these become the model’s defaults.

CLAUDE.md (Claude Code)

Save this at your repo root as CLAUDE.md. Claude Code reads it automatically.

.cursor/rules (Cursor)

Cursor reads .cursor/rules/*.md files. Create .cursor/rules/neural-draft.md with the same content as the CLAUDE.md above. Cursor’s rules system uses YAML frontmatter for scoping; here’s the opinionated default:

Why both Cursor and Claude Code?

Different tools read different files. Some teams use both. Drop both:
  • CLAUDE.md at the repo root.
  • .cursor/rules/neural-draft.md for Cursor users.
  • @neuraldraft/mcp configured per MCP setup for live tool access.
The combination is what gets you “the AI just generates Neural Draft-native code without you reminding it” reliably across editors.

Pairing rules with the MCP server

The MCP server injects a system prompt at runtime, but it’s terse — the kind of thing the model sees once at handshake. Project-level rules, by contrast, are scoped to this project: tech stack, file layout, brand specifics. They complement each other. When the model thinks “where do I put the webhook handler?”, it asks the project rules. When it thinks “what’s the latest brand voice?”, it queries brand://current via MCP. That’s the split.

Working example — full SDK + MCP loop

A complete, copy-paste working scaffold for a Next.js project — wired to SDK 0.3.0 and the Neural Draft MCP server.
Now ask Claude Code (or Cursor with MCP enabled):
“Read brand://current and conventions://editable-html. Generate a three-tier pricing section with index-aware data-translate keys (pricing.tiers.0.name, .price, .description, etc.). Then call register_component with the rendered HTML and intent='pricing tiers for the home page' so the customer can edit each tier in the admin.”
The MCP server reads brand for you, returns conventions, and exposes register_component as a tool — the model wires the rest.