Content Generator

Content Generator

Core Standard

Create pages that would save a serious reader time. Condense the best available material into one coherent, useful page. Do not write filler, keyword soup, or generic AI-shaped prose.

Prefer evergreen framing, but use dates when precision matters. Avoid brittle claims like "recently" or "today" unless the user explicitly wants current-news language.

Workflow

1. Map the content surface. Inspect the current site voice, page model, route structure, metadata, schema, internal links, and any existing FAQ or source patterns before drafting.
2. Research current sources. Browse for current primary or high-quality sources when the topic is technical, scientific, legal, market-sensitive, or likely to have changed. Prefer primary sources, standards bodies, original papers, official docs, major labs, and reputable technical explainers. Keep source links for citations or bibliography.
3. Extract only what matters. Identify the reader's real questions, the technical mechanics, the practical implications, what the topic can and cannot do, common misunderstandings, and how it connects to the site owner's expertise.
4. Draft in the site's voice. Match the site's established tone and rhythm. Use human, confident prose with some wit where natural. Avoid "unlock," "transform," "leverage" reflexes unless they are genuinely the right word.
5. Add meaningful FAQ. Use FAQs only when they answer real search/user questions. Make answers specific, useful, and non-duplicative. If FAQ schema exists, wire it correctly; if not, add it in the existing content architecture.
6. Revise at least three passes.
   • Pass 1: factual accuracy, source grounding, and technical correctness.
   • Pass 2: structure, flow, scannability, internal links, and search intent.
   • Pass 3: voice, redundancy removal, readability, and "would I actually read this?" quality.
7. Verify the page. Build or render locally, inspect metadata/schema/sitemap output, run browser checks for layout, and confirm live behavior after deployment when shipping.

Research Rules

• Use citations for technical claims that are not common knowledge or that may change over time.
• Prefer original sources for algorithms, standards, and policy: papers, NIST/IETF/NSA/CISA, official product pages, standards projects, and major research-lab documentation.
• Use secondary explainers only when they clarify pedagogy, not as authority for sensitive claims.
• Compare multiple sources when claims affect strategy, security, finance, medicine, law, or infrastructure.
• Record uncertainty directly. Good content says "not a silver bullet" when the technology is not a silver bullet.

FAQ Rules

Strong FAQ questions usually start from:

• "What is..."
• "How does..."
• "Can it..."
• "Will it replace..."
• "What are the risks..."
• "How do we evaluate..."
• "What should a buyer ask..."
• "What is the difference between..."

Avoid FAQs that merely restate headings. Each answer should teach something or resolve a real objection.

Style Rules

• Lead with a clear thesis.
• Use concrete mechanisms before abstractions.
• Prefer short paragraphs with occasional dense technical sections where the reader benefits.
• Bold sparingly to mark high-value ideas, not to decorate.
• Keep humor dry and earned.
• Internal links should feel helpful, not like SEO confetti.
• Write for intelligent readers who do not need condescension and may not know the math yet.

Line Discipline

Review every line for intention before shipping. For each sentence, ask two questions: does this line have a purpose, and does it fulfill it? Cut or rewrite any line that cannot answer both. A line earns its place by doing work, never by sounding nice or filling space.

Delivery Checklist

Before reporting completion:

• The route is in the sitemap and prerenders.
• Title and meta description are present and specific.
• FAQ appears visibly where relevant and, if supported, in JSON-LD.
• Source links or bibliography render cleanly.
• The content has passed three revision passes.
• Local browser checks and screenshots were reviewed.
• Live links were verified after deploy when deployment is requested.

Final pass

List the information the page must carry, then compress it into the fewest exact words. Keep every fact while removing every filler word.

Language pass

End every draft by stripping machine tells: reflexive antithesis, hollow intensifiers, echo summaries, and manufactured triads.