article-creation

name: article-creation description: Create newsroom-quality articles, article-style reports, explainers, and analysis pieces from prompts, source URLs, documentation, or reporting notes, then write them as Markdown files under src/content/articles/. Use when Codex needs to turn source material into a professional article that explains what is new, why it matters, and what readers can do with the information without merely paraphrasing the original source.

Article Creation

Turn source material into a newsroom-quality article and save it as a Markdown file with structured frontmatter.

Use this workflow:

1. Commission the story
2. Select the author
3. Select the category
4. Build the reporting package
5. Draft and review the article
6. Write the Markdown file
7. Confirm the result

Read these references before the later steps that depend on them:

• references/editorial-rubric.md
• references/markdown-format.md
• references/ai-authors.md

1. Commission The Story

Decide whether the topic deserves coverage.

Approve topics that are relevant, specific, useful, timely, or insight-rich for See AI News coverage areas such as AI, programming, design, UX, productivity, vibe coding, tech updates, security, and entrepreneurship.

Define these fields before reporting:

• Story type: news, analysis, opinion, or feature
• Angle
• Why it matters
• Audience
• Search intent
• Primary keyword
• Source policy: standard or factual-only-opinion

Use factual-only-opinion for opinion and advice-oriented work where the final judgment must be derived from verified facts rather than borrowed commentary.

2. Select The Author

Select exactly one active author from src/data/authors.json.

Choose the author whose domain, persona, and system prompt best match the article's topic, framing, and tone.

Prefer the most specific fit and record the selection rationale briefly before drafting.

Use references/ai-authors.md for the current author map and selection heuristics.

3. Select The Category

Read src/data/categories.json to find an existing category that fits the article.

Reuse an existing category whenever it is a reasonable fit.

Choose the broadest accurate category that matches the article's center of gravity.

Create a new category only when the existing taxonomy does not fit the article responsibly, and keep the new category broad and reusable.

When creating a new category, add it to src/data/categories.json with the fields id (same as slug), name, slug, and description.

4. Build The Reporting Package

Extract the core claims from the request and from any provided source material.

Research until the article has enough evidence to stand on its own.

Use at least 3 sources for every article. Add more when the topic needs broader coverage, stronger corroboration, or stronger support for consequential claims.

Select sources from credible, trustworthy publications, official documentation, official announcements, research institutions, public filings, and other authoritative references.

Prefer primary sources first. Use strong secondary reporting for synthesis or corroboration.

Use the research tools the same way the newsroom agents do:

• Exa for current reporting, source discovery, and reading source pages
• Context7 for official documentation, APIs, standards, and technical references
• grep for public implementation evidence when code usage claims matter

Separate verified facts from context, interpretation, and unresolved uncertainty.

If evidence is weak, narrow the claim instead of guessing.

Use references/editorial-rubric.md for the detailed reporting rules, source policy rules, and audit thresholds.

5. Draft And Review The Article

Write a professional article that explains what changed, why it matters, how it works, who should care, and what it can be used for.

Synthesize an original article from the reporting package. Do not paraphrase the source article.

Let the selected author's persona shape the voice without compromising factual accuracy.

Follow these article-format rules:

• Use a clear opening that states what happened and why it matters
• Use descriptive ## headings and ### subsection headings where needed
• Write a compelling natural headline
• Write an excerpt that works as a search snippet
• End with a clear takeaway
• Match the requested language, or default to English
• Keep the title only in the frontmatter title field
• Start the Markdown body with the opening paragraphs or with ## headings
• Do not include an H1 or # Title in the Markdown body
• Use the full Markdown formatting toolkit to improve readability: bold for key terms, italics for nuanced emphasis, blockquotes for direct quotes and callouts, code blocks and inline code for technical references, tables for comparisons, inline links for tools, documentation, and sources, and lists for parallel items or sequential steps
• Apply formatting naturally where it serves the reader — never as decoration

Review the draft against the standards bar before saving it.

Use references/editorial-rubric.md for the final review checklist and minimum thresholds.

6. Write The Markdown File

Write the final result to:

src/content/articles/<slug>.md

Use the final article slug for the filename.

Use the Markdown structure in references/markdown-format.md.

The file must include:

• YAML frontmatter with title, slug, status, categorySlug, authors, sources, and dates
• Markdown body with the article content

7. Confirm The Result

After writing the Markdown file, confirm the result to the user with:

• File path
• Author name and username
• Category
• Story type
• Source URLs

The article is immediately available through Astro's content collections after the file is saved. No database insertion is needed.

If the article is not supportable, say that the reporting is insufficient and name the missing evidence.