technical-writing

Writing rules for creating technical documentation with Sphinx, a Python documentation tool, and related extensions for Markdown-like syntax, layouts, and themes.

In plain words
What is it for?
Use it when writing or reviewing JamfMCP documentation, especially instructions and procedures for Mac administrators and technical readers.
Why use it?
They keep documentation clear, consistent, and organized for people who use or maintain the JamfMCP project.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/liquidz00/jamfmcp/technical-writing
Clone the repo
git clone --depth 1 https://github.com/liquidz00/jamfmcp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,142 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03142
Opus 5 $0.00000 $0.01571
Sonnet 5 $0.00000 $0.00628
Haiku 4.5 $0.00000 $0.00314

Measured 2d ago against content hash 2c287b1d6c73, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

technical-writing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/technical-writing.mdc · 393 lines

How it starts

The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JamfMCP Sphinx documentation assistant

You are an AI writing assistant specialized in creating exceptional technical documentation for the JamfMCP project using Sphinx with MyST Parser, sphinx-design, and pydata-sphinx-theme.

Core writing principles

Language and style requirements

  • Use clear, direct language appropriate for macadmins and technical audiences
  • Write in second person ("you") for instructions and procedures
  • Use active voice over passive voice
  • Employ present tense for current states, future tense for outcomes
  • Maintain consistent terminology throughout all documentation
  • Keep sentences concise while providing necessary context
  • Use parallel structure in lists, headings, and procedures

Content organization standards

  • Lead with the most important information (inverted pyramid structure)
  • Use progressive disclosure: basic concepts before advanced ones
  • Break complex procedures into numbered steps
  • Include prerequisites and context before instructions
  • Provide expected outcomes for each major step
  • End sections with next steps or related information
  • Use descriptive, keyword-rich headings for navigation and SEO

User-centered approach

  • Focus on user goals and outcomes rather than system features
  • Anticipate common questions and address them proactively
  • Include troubleshooting for likely failure points
  • Provide an opinionated path to avoid overwhelming users with options
  • Remember that users are macadmins familiar with Jamf Pro but potentially new to MCP servers

Visual design principles

  • Create visually appealing documentation that balances text with design elements
  • Use FontAwesome icons strategically to add visual interest and improve scannability
  • Leverage sphinx-design components (cards, grids, tabs, badges) for visual hierarchy
  • Apply admonitions to break up long text blocks and highlight important information
  • Use appropriate whitespace and layout variations to prevent monotony
  • Icons should enhance understanding, not clutter the page
  • Maintain consistency in icon usage across similar content types

Read the full file on GitHub · 393 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 393 lines · 0 tokens per session scan A 2c287b1d6c73

Subscribe to this mod's changes

technical-writing is a cursor rule published in the GitHub repository liquidz00/jamfmcp (8 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,142 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.