Futurecx-nl

Create image concepts, prompts, asset plans, and generated raster image guidance for Future CX blog articles. Use when Codex is asked to create or plan hero images, article thumbnails, Open Graph images, visual directions, prompt variants, or image assets for content/*.html pages about ecommerce, customer experience, enterprise architecture, integration, composable architecture, CRM, data, AI, or technology selection.

Relentless plan, design, and requirements interrogation. Use when Codex should interview the user to reach shared understanding, pressure-test a proposal, walk a decision tree, uncover assumptions, resolve dependencies between decisions, clarify implementation plans, or challenge drafts before execution. If a question can be answered by inspecting the local codebase, files, docs, tests, or repository history, Codex should explore those artifacts instead of asking the user.

Create or update Future CX static blog article HTML pages under content/*.html from article drafts, briefs, Markdown, research output, or existing page requests. Use when Codex is asked to turn blog copy into a publishable HTML page, scaffold a new content article, align SEO/JSON-LD metadata, add an article to content.html, update related links, or prepare a Future CX article page for validation.

Draft, rewrite, expand, or structure Future CX blog articles and article briefs for content/*.html pages. Use when Codex is asked to write blog content, create article outlines, turn research into publishable Future CX prose, improve article readability, prepare SEO titles/descriptions, or produce article copy for ecommerce, customer experience, enterprise architecture, integration, composable architecture, CRM, data, AI, or technology selection topics.

Validate trend research outputs, proposed trends, source lists, and trends.json changes for factual support, source quality, duplicate overlap, taxonomy fit, adoption-stage evidence, summary accuracy, and JSON readiness. Use after trend-research or whenever Codex is asked to fact-check, verify, audit, approve, reject, or improve trend findings before publication.

Research a user-provided topic or YAML-configured topic by scanning current web sources, collecting credible evidence, extracting key findings, identifying claims that need validation, grouping themes, and producing structured research output for downstream fact-checking, trend analysis, SEO, writing, or content workflows.

Scan the internet for emerging market, technology, ecommerce, retail, CRM, advertising, and software architecture trends; validate whether candidate trends are new or materially changing; and return structured trend findings with sources, category, adoption stage, summary, and rationale. Use when Codex is asked to research new trends, refresh trend datasets, find trend opportunities, or add researched trends to files such as trends.json.

Review static HTML pages for this Future CX website for structure, SEO metadata, readability, accessibility, links, assets, JSON-LD, sitemap inclusion, and project conventions. Use when Codex is asked to validate, review, audit, improve, or edit HTML pages such as root *.html files or content/*.html article pages.