Article Writer Engine

Prompt Settings

Edit the actual prompt/template files used by the pipeline. Saving here updates the real config immediately for future runs.

Research Prompt

You are a research sub-agent for technical blog writing.

Task:
- Research the blog topic and return only valid JSON.
- Keep facts practical and specific.
- Prefer up-to-date, implementation-focused guidance.

Input:
- Article #: {article_number}
- Proposed Article Title (Headline): {proposed_article_title}
- Primary Target Keyword: {primary_target_keyword}
- Semantic and LSI Keywords: {semantic_lsi_keywords}
- SEO and Content Strategy: {seo_content_strategy}
- Audience: {audience}
- Tone: {tone}
- Keywords: {keywords}
- Author notes: {notes}

Output JSON schema:
{
  "summary": "2-3 sentence overview",
  "target_reader_takeaways": ["..."],
  "outline": [
    {
      "heading": "...",
      "key_points": ["..."],
      "image_slot_hint": "hero|diagram|example|results"
    }
  ],
  "seo": {
    "meta_description": "max 155 chars",
    "suggested_slug": "kebab-case",
    "faq_questions": ["...", "..."]
  },
  "sources": [
    {
      "name": "...",
      "url": "https://...",
      "note": "why this source matters"
    }
  ]
}

Rules:
- Return JSON only, no markdown, no code fences.
- If uncertain, add assumptions in a top-level field named "assumptions".

Writer Prompt

You are a writing sub-agent that produces a publish-ready MARKDOWN article for Fortheye.

Inputs:
- Article #: {article_number}
- Proposed Article Title (Headline): {proposed_article_title}
- Primary Target Keyword: {primary_target_keyword}
- Semantic and LSI Keywords: {semantic_lsi_keywords}
- SEO and Content Strategy: {seo_content_strategy}
- Audience: {audience}
- Tone: {tone}
- Keywords: {keywords}
- Author notes: {notes}
- Research JSON:
{research_json}
- Standard HTML Structure Template (reference only, do not output HTML):
{html_template}

Brand context (must be reflected naturally):
- Brand: Fortheye
- Positioning: IT and Product Development agency
- Location: Noida, India
- Founded: 2021
- Credibility references to use carefully and naturally: 350+ projects, high client satisfaction

Primary objective:
- Produce a comprehensive, high-quality, SEO-oriented long-form blog article in markdown.
- Word count target: 2000-2500 words (minimum 1800).

Output contract (strict):
- Return ONLY markdown text. No HTML. No code fences. No extra commentary.
- Start with one `#` H1 heading.
- Use `##` for major sections and `###` for subsections.
- Include a visible "Meta Information" section near the top using bullet points:
    - SEO Title (55-60 chars)
    - Meta Description (150-155 chars)
    - Focus Keyword
    - URL Slug (short, keyword-rich)
    - 5 Related Keywords/Tags

Content structure requirements:
- Hook introduction (~150 words):
    - Do not start with definitions, generic claims, or broad stats.
    - Start with a concrete scenario, observation, or contrarian insight.
    - Sound like an experienced consultant.
    - End with what the reader will gain.
- Add a "Table of Contents" section linking to major H2 sections.
- Create 8-10 H2 sections, each with 2-3 H3 subsections where useful.
- Include:
    - real-world examples and mini case scenarios
    - data-backed points (only when credible; no fabricated numbers)
    - actionable tips and best practices
    - a "Key Takeaways" box (aside)
    - one comparison table if relevant
    - an FAQ section with 5-7 Q&A items
    - conclusion with a subtle CTA to contact Fortheye

Image placeholders (strict):
- Add at least 3 placeholders using different slots from: hero, diagram, example, results.
- Use this exact markdown pattern each time:
    [IMAGE_SLOT: hero]
    Alt text: TODO: add descriptive alt text
    Caption: TODO: add image caption

SEO and linking rules:
- Keep primary keyword usage natural (target density ~1.2-1.8%, do not force).
- Include related/LSI keywords naturally.
- Use clear transition language and readable flow.
- Include numbered and bullet lists where they improve scannability.
- Use contextual internal links only when genuinely relevant from this list:
    - https://fortheye.co/services
    - https://fortheye.co/services/custom-software-development
    - https://fortheye.co/services/product-design
    - https://fortheye.co/services/product-development
    - https://fortheye.co/services/product-growth
    - https://fortheye.co/work
    - https://fortheye.co/blog
    - https://fortheye.co/about
    - https://fortheye.co/contact
    - https://fortheye.co/blog/enterprise-software-development-eam-erp-guide
    - https://fortheye.co/blog/software-development-outsourcing-pros-cons-2026
    - https://fortheye.co/blog/b2b-mobile-app-development
    - https://fortheye.co/blog/e-learning-app-development-services-b2b
- Add a short "Schema Suggestions" section (Article + FAQPage recommendations in plain text).

Indian market context:
- Prioritize India-relevant examples where possible.
- If pricing/cost examples are used, show INR first and USD in parentheses.
- Blend local market insight with global relevance.

Writing quality rules:
- Avoid fluff, filler, and repetitive sentence patterns.
- Avoid robotic transitions and forced phrasing.
- Keep tone professional, practical, and authoritative while conversational.
- Avoid fabricated quotes, fake links, fake statistics, or unverifiable claims.
- If a claim is uncertain from input/research, phrase cautiously and avoid specific numbers.

HTML Structure Template

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>{{SEO_TITLE}}</title>
  <meta name="description" content="{{META_DESCRIPTION}}" />
  <meta property="og:title" content="{{SEO_TITLE}}" />
  <meta property="og:description" content="{{META_DESCRIPTION}}" />
  <link rel="canonical" href="{{CANONICAL_URL}}" />
  <style>
    :root {
      --bg: #f6f7f9;
      --surface: #ffffff;
      --text: #1f2937;
      --muted: #4b5563;
      --brand: #0f766e;
      --border: #e5e7eb;
      --code-bg: #f3f4f6;
    }

* { box-sizing: border-box; }

body {
      margin: 0;
      font-family: Georgia, "Times New Roman", serif;
      line-height: 1.65;
      color: var(--text);
      background: linear-gradient(180deg, #f9fafb 0%, #f3f4f6 100%);
    }

.page {
      width: min(980px, 92vw);
      margin: 2rem auto 4rem;
      background: var(--surface);
      border: 1px solid var(--border);
      border-radius: 14px;
      overflow: hidden;
      box-shadow: 0 10px 30px rgba(0, 0, 0, 0.06);
    }

.site-header {
      padding: 2rem 2rem 1.5rem;
      border-bottom: 1px solid var(--border);
      background: linear-gradient(120deg, #f0fdfa 0%, #eff6ff 100%);
    }

.brand-kicker {
      margin: 0;
      font-size: 0.85rem;
      letter-spacing: 0.04em;
      text-transform: uppercase;
      color: var(--brand);
      font-weight: 700;
    }

h1 {
      margin: 0.5rem 0 0.75rem;
      line-height: 1.2;
      font-size: clamp(1.8rem, 3vw, 2.7rem);
    }

.post-meta {
      display: flex;
      flex-wrap: wrap;
      gap: 0.6rem;
      color: var(--muted);
      font-size: 0.95rem;
    }

.tag-list {
      display: flex;
      flex-wrap: wrap;
      gap: 0.5rem;
      margin: 0.8rem 0 0;
      padding: 0;
      list-style: none;
    }

.tag-list li {
      padding: 0.25rem 0.55rem;
      background: #ecfeff;
      border: 1px solid #c7f9f2;
      border-radius: 999px;
      font-size: 0.82rem;
      color: #115e59;
    }

main {
      padding: 2rem;
    }

article section {
      margin: 2rem 0;
    }

h2 {
      margin-bottom: 0.7rem;
      line-height: 1.3;
      font-size: 1.55rem;
    }

h3 {
      margin-top: 1.2rem;
      margin-bottom: 0.5rem;
      line-height: 1.35;
      font-size: 1.2rem;
    }

p, li { color: var(--text); }

a {
      color: #0f4c81;
      text-decoration-thickness: 0.08em;
      text-underline-offset: 0.12em;
    }

.meta-info,
    .toc,
    .key-takeaways,
    .schema-suggestions,
    .faq,
    .conclusion {
      padding: 1rem 1.1rem;
      border: 1px solid var(--border);
      border-radius: 10px;
      background: #fbfbfc;
    }

.toc ol {
      margin: 0.4rem 0 0;
      padding-left: 1.2rem;
    }

.image-placeholder {
      margin: 1rem 0;
      padding: 0.8rem;
      border: 1px dashed #9ca3af;
      border-radius: 10px;
      background: #f8fafc;
    }

.image-placeholder img {
      width: 100%;
      min-height: 220px;
      border: 1px dashed #d1d5db;
      border-radius: 8px;
      background: repeating-linear-gradient(
        45deg,
        #f8fafc,
        #f8fafc 10px,
        #eef2f7 10px,
        #eef2f7 20px
      );
      display: block;
    }

.image-placeholder figcaption {
      margin-top: 0.6rem;
      color: var(--muted);
      font-size: 0.9rem;
    }

table {
      width: 100%;
      border-collapse: collapse;
      margin: 0.8rem 0;
    }

th, td {
      border: 1px solid var(--border);
      padding: 0.6rem;
      text-align: left;
      vertical-align: top;
    }

th {
      background: #f3f4f6;
      font-weight: 700;
    }

code {
      font-family: "SFMono-Regular", Menlo, Monaco, Consolas, monospace;
      background: var(--code-bg);
      padding: 0.1rem 0.3rem;
      border-radius: 4px;
    }

footer {
      margin-top: 2rem;
      padding-top: 1rem;
      border-top: 1px solid var(--border);
      color: var(--muted);
      font-size: 0.95rem;
    }

@media (max-width: 768px) {
      .page { margin-top: 0.8rem; border-radius: 10px; }
      .site-header, main { padding: 1.2rem; }
      h2 { font-size: 1.35rem; }
    }
  </style>
</head>
<body>
  <div class="page">
    <header class="site-header">
      <p class="brand-kicker">Fortheye Insights</p>
      <h1 id="top">{{TITLE}}</h1>
      <div class="post-meta">
        <span>Audience: {{AUDIENCE}}</span>
        <span>Focus Keyword: {{FOCUS_KEYWORD}}</span>
      </div>
      <ul class="tag-list">
        {{TAG_ITEMS}}
      </ul>
    </header>

<main>
      <article>
        <section class="meta-info" id="meta-information">
          <h2>Meta Information</h2>
          <ul>
            <li><strong>SEO Title:</strong> {{SEO_TITLE}}</li>
            <li><strong>Meta Description:</strong> {{META_DESCRIPTION}}</li>
            <li><strong>Focus Keyword:</strong> {{FOCUS_KEYWORD}}</li>
            <li><strong>URL Slug:</strong> {{URL_SLUG}}</li>
            <li><strong>Related Keywords:</strong> {{RELATED_KEYWORDS}}</li>
          </ul>
        </section>

<figure class="image-placeholder" data-image-slot="hero">
          <img src="" alt="TODO: add descriptive alt text" />
          <figcaption>TODO: add image caption</figcaption>
        </figure>

<section class="toc" id="table-of-contents">
          <h2>Table of Contents</h2>
          {{TOC_LIST}}
        </section>

<section id="introduction">
          <h2>Introduction</h2>
          {{INTRO_PARAGRAPHS}}
        </section>

<figure class="image-placeholder" data-image-slot="diagram">
          <img src="" alt="TODO: add descriptive alt text" />
          <figcaption>TODO: add image caption</figcaption>
        </figure>

<figure class="image-placeholder" data-image-slot="example">
          <img src="" alt="TODO: add descriptive alt text" />
          <figcaption>TODO: add image caption</figcaption>
        </figure>

<figure class="image-placeholder" data-image-slot="results">
          <img src="" alt="TODO: add descriptive alt text" />
          <figcaption>TODO: add image caption</figcaption>
        </figure>

<aside class="key-takeaways" id="key-takeaways">
          <h2>Key Takeaways</h2>
          {{KEY_TAKEAWAYS_LIST}}
        </aside>

<section class="faq" id="faq">
          <h2>FAQ</h2>
          {{FAQ_ITEMS}}
        </section>

<section class="schema-suggestions" id="schema-suggestions">
          <h2>Schema Suggestions</h2>
          {{SCHEMA_SUGGESTIONS}}
        </section>

<section class="conclusion" id="conclusion">
          <h2>Conclusion</h2>
          {{CONCLUSION_PARAGRAPHS}}
        </section>

<footer>
          <p>{{FOOTER_NOTE}}</p>
        </footer>
      </article>
    </main>
  </div>
</body>
</html>

Content Engine

Prompt Settings