Write clearer payment documentation

Atlas Payments English · Open source

Review payment procedures, API explanations and operational instructions while preserving the meaning that people need to act.

Atlas Payments English combines payments terminology with selected ASD-STE100 Issue 9 writing principles. It is an independent adaptation, not an ASD-approved or certified tool.

255
payment terminology entries
4
stable review rules
2
editing modes

A clearer sentence keeps the conditions

Capture permission, before and after
BeforeUpon receipt of an approved authorization, the merchant may capture the payment after the order ships.
AfterIf the authorization is approved and the order has shipped, the merchant may capture the payment.

The merchant remains the actor. Both conditions remain. May remains permission. Capture does not become settlement.

Choose Review or Rewrite

Review is the default. Results quote the source excerpt and identify the rule ID, issue, severity and suggested edit. Missing facts produce focused questions.

Request Rewrite explicitly to receive revised text, remaining questions and checks not completed. If an ambiguity affects meaning, the editor retains that passage and asks what the writer means.

For “Reverse the payment,” the useful response is a question: “What is the current payment state, and do you mean cancellation, authorization reversal, or refund?”

Four rules, with different responsibilities

The Atlas review rules
RuleWhat it protects
STYLE-01Clear procedural instructions and sentence limits: 20 words for procedures and 25 for descriptive text, using Issue 9’s counting rules.
PAY-01Actors, payment states, event order, and the difference between a request and its outcome.
PAY-02Conditions, explicit modal words, amounts, currencies, deadlines, status values, UI labels and technical identifiers.
PAY-03Focused clarification when a missing fact changes the instruction.

STYLE-01 draws on selected ASD writing principles. The PAY rules are Atlas editorial requirements. The 255 glossary entries include 56 single-word headwords and 199 multiword terms; they are not a complete approved general-English dictionary.

Install from GitHub

The code and reference files are available under MIT. The Atlas Payments English repository contains installation details, the rules, examples and source references.

Codex

codex plugin marketplace add Dan1shs1d/atlas-payments-english
codex plugin add atlas-payments-english@atlas-payments

Start a new session and invoke $atlas-payments-english.

Claude Code

claude plugin marketplace add Dan1shs1d/atlas-payments-english
claude plugin install atlas-payments-english@atlas-payments

Start a new authenticated session and invoke /atlas-payments-english:atlas-payments-english.

Download the public release or read the verification record. This is a third-party GitHub distribution; official directory listing is not claimed.

Know what has been checked

The public 0.2.1 skill passed 20 Codex model acceptance cases. Its 27 local regression tests also passed. Claude Code’s structural checks passed; its model acceptance cases remain unrun. A finite test suite does not establish reliable performance on every document or full STE conformance.

Use the editor with care

The selected model host processes your text under its own policies. Use synthetic or redacted material. Do not paste live card data, authentication data, credentials or customer records. The package includes no payment execution, MCP server, hooks, telemetry or billing.

Human review is still needed for consequential instructions. The editor does not independently establish current network permission, legal correctness or operational safety.

Read why this matters for global teams.