AI content engineering app
This example packages content engineering as a product-level Agent App, not as a single “content expert”. It has its own UI, storage, workflows, worker, expert-chat entry, Knowledge bindings, Artifacts, and Evals.
It declares:
dashboardandcontent_factorypage entries.knowledge_builderandcontent_calendarworkflows.content_strategistexpert-chat entry.content-engineering-appstorage namespace and schema.- Knowledge slots for
project_knowledge,personal_ip, andcontent_operations. - Tool Broker requirements such as document parsing and competitor research.
- Artifact types for content tables, article drafts, and strategy reports.
- Evals for anti-AI tone and fact grounding.
Customer-specific facts such as founder stories, brand voice, private-domain SOPs, and operation data do not belong in the official app package. They should be bound as Agent Knowledge, workspace files, app storage, or overlays.
Reference package: docs/examples/content-engineering-app/APP.md