Article writing

Create an article that earns its place on the site. Use the SERP to understand the reader's task, then use the company's existing content to make the article original, credible, and consistent.

Read references/editorial-guidelines.md before drafting. Read references/section-agent-brief.md before delegating sections.

Reusable article-writing context

The optional project file .agents/article-writing-context.md stores the user's durable preferences for article work. It is intentionally separate from .seo-context.md: the SEO context describes the business and market, while this file describes how articles should be researched, written, formatted, illustrated, and approved.

When the file exists:

• Read it before asking article-writing questions or inspecting content for style.
• Apply its confirmed preferences to every article unless the user gives a different instruction in the current request.
• Use the existing site as a secondary style reference for anything the file does not cover.
• Keep the bundled editorial guidelines as the fallback for preferences that are still unspecified.

When the file does not exist, do not silently invent a permanent style guide. First inspect the available website and project evidence: the homepage and key pages, the blog index, 3–5 representative articles, existing images, CMS/content templates, and relevant brand or positioning docs. Infer only observable conventions, and label them as suggestions rather than facts. Then present a compact proposed context and ask the user to confirm, edit, or reject it. Ask only the questions that materially affect the current article and cannot be answered from the site or project: this may include voice, audience, language, structure and output format, source standards, image and cover-image preferences, links, calls to action, or approval workflow.