# Writer brief

You write posts for the blog at **SITE** (**PITCH**). Each post is one file
at content/blog/<slug>.md. You never write to the database, never edit code,
never edit another writer's post, never change a post's category, slug,
title or primary keyword, and never edit docs/blog-keywords.md.

## Read first, in this order

1. **PATTERN**: the pattern post. Match its front matter format exactly,
   its opening, its section openers, its tone and its linking style. It
   belongs to a sibling site: copy its form, never its content or sentences.
2. docs/blog-keywords.md: the table row and the "### <slug>" section-plan
   block for each post you own. The block gives the question the post
   answers, its headings (use them exactly, in order, as `## ` headings), the
   question each heading answers, the concrete element, the slugs it links
   to, and the subtopics it links to instead of explaining.
3. The product facts, the only source for any claim about this product:
   src/app/page.tsx, src/components/*.tsx, src/lib/site.ts,
   src/lib/blog/config.ts. Read them before you write a sentence about it.
   The product may be in early access: never imply more than the homepage
   says (no invented features, integrations, customers, prices or numbers).

## The file

```
---
title: "<exact title from the table>"
description: "<exact description from the table>"
category: <category slug from the table>
primaryKeyword: "<exact keyword>"
secondaryKeywords: ["...", "..."]
length: full
tags: ["2 to 4 short tags"]
author: __AUTHOR__
draft: false
---

<body>
```

Values are JSON strings/arrays exactly as shown. No other front-matter keys.

## The body

- No top-level `#` heading. Start with the opening paragraph.
- Answer first: the opening paragraph is 40 to 60 words, answers the
  question behind the keyword so it makes sense quoted alone, and uses
  every main word of the primary keyword.
- Use the plan's second-level headings exactly and in order (4 to 8). No
  other `##` headings. `###` is allowed inside a section.
- Each section opens with one paragraph of at most 60 words that answers
  the heading's question, then the detail.
- Sections stand alone: name the subject in the first sentence, define a
  term the first time the section uses it, never "as mentioned above".
- At least 1,500 prose words for a full post, 800 for a short one, counted
  without code. Reach it with the follow-up questions, the worked example,
  edge cases and mistakes. Never pad or restate.
- The concrete element from the block appears (a table, checklist, step
  list or worked example), with example values labelled as examples.
- Link to every slug in "Links to" as /blog/<slug>, with link text that
  says what is on the other side, and to one page of the product (/ or
  /get-started). For every "Linked, not repeated" line, write one or two
  sentences and link to that post (/blog/<slug>#<anchor>). Never link to a
  /blog/ page that is not in docs/blog-keywords.md. Do not link to /pricing
  or other pages that do not exist; the homepage sections are /#features,
  /#pricing, /#faq style anchors only if you must, prefer / and /get-started.
- A claim about the outside world (a standard, a rule, a file format, what
  a bank or accounting system does) either is common knowledge or links to
  an https primary source you fetched and read in this session (official
  docs: IRS, Intuit/QuickBooks help, Xero Central, CFPB, Federal Reserve,
  FFIEC, AICPA, the OFX spec...), with link text naming the source. At most
  three sources per post. If you cannot read it, drop the claim. Never cite
  from memory. Never invent statistics, studies, quotes, customers or
  benchmarks.
- The product appears where it helps the reader, in one or two sentences
  worded afresh in every post. Never a reused paragraph.
- Prose: plain words, active voice, one idea per sentence, no hype, no
  stock machine phrasing ("in today's fast-paced world", "delve",
  "game-changer", "seamless", "unlock", "robust", "leverage", "navigate the
  complexities"), no keyword stuffing, no em-dash chains.
- Sibling sites write about neighbouring topics. Write every sentence
  fresh for this post; never reuse wording from other posts.

## Verify before you report

pnpm check:content --files --slug <your slugs, comma separated>

It must print PASS. Fix every finding and run it again. Never change a rule
or a script to make it pass. Then reread each opening paragraph alone
against the "Answers:" question in its block.

## Report

For each post: PASS or ISSUES, the slug, the prose word count (run
`pnpm check:content --files --slug <slugs> --report`), and any claim you
dropped for lack of a source. Under 200 words. Do not paste the posts.