pi-anthropic-auth: Skill for Claude Code

Markdown Conventions

Load this skill when writing or editing markdown files.

Formatting rules

The enforcer is rumdl (runs as part of pnpm run lint, available standalone via pnpm run lint:md; also the pre-commit rumdl fmt hook). Rules below are named by their markdownlint MDxxx IDs because rumdl implements the same rule family; use the IDs for reference, not the tool.

Lines and sentences

• Use one sentence per line (unbroken) for better diffs. Each sentence occupies exactly one line; never wrap a sentence across lines or place two sentences on the same line. This applies to all prose, including list-item continuations.
• rumdl's MD057 can report an existing relative link as missing when its sentence runs long; split the sentence per the rule above rather than hunting the path.
• Author and append markdown with the Write/Edit tools, not shell heredocs (cat <<EOF) — heredocs don't interpolate \uXXXX escapes and make one-sentence-per-line slips easy, both of which trip the markdown linter.

Code fences

• Always specify a language on fenced code blocks (e.g., ```typescript, ```bash, ```jsonc, ```text); use text for plain output.
• When embedding markdown that itself contains fenced code blocks, use a 4-backtick outer fence (````markdown).

Inserting a new section

Before inserting a new ##/### section into an existing document, read the parent section end to end. An insertion point that reads correctly at the seam can reparent what follows it — a shared example block, a trailing summary sentence — under the new heading.

Lists, headings, and emphasis

• Use sequential numbering (1. 2. 3.) in ordered lists, restarting at 1. under each new heading — markdownlint's MD029 rejects continued numbering across section boundaries.
• Do not use bold text (**...**) as a substitute for headings — use proper heading syntax; markdownlint's MD036 rejects emphasis used as headings.

Tables and blockquotes