Cursor rules for how-to documentation development with integration

Cursor rules for how-to documentation development with integration is a skill for Claude Code, Codex from AmariahAK/atlarix-skills. It costs 9 tokens per session (1,085 once invoked), scanned A, original, Apache-2.0.

A set of guidelines for writing how-to documentation that explains software features in clear, step-by-step language for people who may not be technical.

In plain words
What is it for?
Use it to write feature guides with action-focused titles, numbered steps, interface labels, and expected results.
Why use it?
It provides a consistent way to turn technical details, tests, or screenshots into instructions that readers can follow.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Cursor.

Good fit Use it to write feature guides with action-focused titles, numbered steps, interface labels, and expected results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amariahak/atlarix-skills/acr-how-to-documentation-cursorrules-prompt-file
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.

Any agent
npx skills add AmariahAK/atlarix-skills --skill acr-how-to-documentation-cursorrules-prompt-file
Clone the repo
git clone --depth 1 https://github.com/AmariahAK/atlarix-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Cursor rules for how-to documentation development with integration

README.md
[![agentmods](https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-how-to-documentation-cursorrules-prompt-file/github.svg)](https://agentmods.dev/skills/amariahak/atlarix-skills/acr-how-to-documentation-cursorrules-prompt-file)
Your own site
<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/acr-how-to-documentation-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-how-to-documentation-cursorrules-prompt-file/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Cursor rules for how-to documentation development with integration

Your own site · 80×15
<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/acr-how-to-documentation-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-how-to-documentation-cursorrules-prompt-file.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,085 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00009 $0.01085
Opus 5 $0.00005 $0.00543
Sonnet 5 $0.00002 $0.00217
Haiku 4.5 $0.00001 $0.00109

Measured 9d ago against content hash 3024b7f44bc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

Cursor rules for how-to documentation development with integration 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 9d 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.

skills/acr-how-to-documentation-cursorrules-prompt-file/SKILL.md · 131 lines

How it starts

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

Cursor rules for how-to documentation development with integration

When to use this skill

Cursor rules for how-to documentation development with integration.

Source

Synced from https://github.com/PatrickJS/awesome-cursorrules/tree/main/rules/how-to-documentation-cursorrules-prompt-file.mdc.

Persona

You are an expert technical writer tasked with creating "How To" documentation for software features to help non-technical users understand how to use them.

Documentation Focus

Create clear, step-by-step instructions that non-technical users can follow Convert technical information, test scripts, or screenshots into user-friendly guides Use simple language and avoid technical jargon Focus on user actions and expected outcomes for specific features

Best Practices

1 Clear Title: Use action-oriented titles like "How To Log In" or "How To Export Reports" 2 Brief Introduction: Begin with a short explanation of the feature's purpose and value 3 Numbered Steps: Present instructions as numbered steps in a logical sequence 4 Visual Cues: Reference UI elements as they appear to users (buttons, fields, menus) 5 Expected Results: Clearly describe what users should see after each action 6 Troubleshooting Tips: Include common issues and their solutions 7 Related Features: Mention related features or next steps when appropriate 8 Platform Compatibility: Note any differences between devices or platforms

Document Format

The document should follow this structure:

  1. Title: Clear, action-oriented heading
  2. Introduction: Brief explanation of the feature's purpose (1-3 sentences)
  3. Prerequisites: Any required accounts, permissions, or prior steps
  4. Step-by-Step Instructions: Numbered steps with clear actions
  5. Expected Results: What the user should see when successful
  6. Troubleshooting: Common issues and solutions
  7. Additional Information: Tips, shortcuts, or related features

Read the full file on GitHub · 131 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 131 lines · 9 tokens per session scan A 3024b7f44bc4

Subscribe to this mod's changes

Cursor rules for how-to documentation development with integration is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 9 tokens to every session and 1,085 once invoked, about $0.0000 per session on Opus 5. 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-09-03.

Related

Other skills, from other repositories

document-extraction

Use this skill for intelligent document processing and content extraction using LandingAI's Agentic Document Extraction (ADE). Trigger when users need to (1) Parse documents (PDFs, images, spreadsheets, presentations) into structured Markdown with layout understanding, (2) Extract specific structured data from…

nrl-ai/chub · 222 tokens

document-workflows

Use this skill for building end-to-end document processing workflows and pipelines using LandingAI ADE. Trigger when users need to: (1) Process batches of documents in parallel or async, (2) Build classify-then-extract pipelines for mixed document types, (3) Prepare parsed documents for RAG systems with chunking and…

nrl-ai/chub · 259 tokens

typescript-providers

Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, and Claude Agent SDK. Use for provider-specific TS work; do not use for core-only changes.

ComposioHQ/composio · 70 tokens

memstack-business-scope-of-work

Use this skill when the user says 'scope of work', 'SOW', 'define scope', 'project scope', 'write SOW', 'scope document', or is defining project boundaries, deliverables, and acceptance criteria for a formal engagement. Do NOT use for proposals, contracts, or invoicing.

cwinvestments/memstack · 70 tokens

slides

A slide generator that creates PNG images for presentation decks, including simple backgrounds for spoken-video scripts and fuller layouts for standalone presentations.

majiayu000/spellbook · 41 tokens

idea-team

A structured group discussion for exploring a product idea through three roles: researcher, critic, and analogy finder. The roles look for evidence, weaknesses, and useful comparisons.

majiayu000/spellbook · 182 tokens