content-factory-plugin
AGENTS.md0 starsChanged 19 days agoApache-2.0View on GitHub
Read openspec/README.md first. The repository currently contains a design baseline, not a released plugin. The V1 baseline is establish-content-factory-v1. Its channel-awareness completion is add-platform-aware-content-orchestration. Read both before implementing the harness. The latter makes content-platform recognition and channel-specific recipes mandatory; host capability discovery alone is insufficient. Read docs/architecture/Content-Factory-Architecture.zh_CN.md and openspec/changes/implement-content-factory-architecture/ alongside both existing changes. The third change decomposes the same CF-001–CF-058 parents into 232 execution steps; it is not a new product phase. Preserve the three presentation sections and four text…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository8 other files it gives its agents.
- baoyu-format-markdownSkill
- baoyu-markdown-to-htmlSkill
- content-harnessSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- product-marketingSkill
- socialSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Read openspec/README.md first.
- Very specific: line 11
Keep exactly one plugin-local skill: content-harness.
- Distinctive: line 12
Prefer reviewed, immutable vendor skills.
- Distinctive: line 13
Keep source platform, target channel, execution host, content format, and destination account separate.
- Distinctive: line 19
Never automatically install candidate skills, disable unrelated skills, suppress provenance, bypass permission checks, or fabricate …
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Factory — repository guidance
Read openspec/README.md first. The repository currently contains a design baseline, not a released plugin.
Active scope
The V1 baseline is establish-content-factory-v1. Its channel-awareness completion is add-platform-aware-content-orchestration. Read both before implementing the harness. The latter makes content-platform recognition and channel-specific recipes mandatory; host capability discovery alone is insufficient.
Invariants
- Keep exactly one plugin-local skill:
content-harness. Channel profiles and recipes are data/reference files, not new local skills. - Prefer reviewed, immutable vendor skills. A discovered skill is not installed, approved, compatible, or safe merely because a catalog lists it.
- Keep source platform, target channel, execution host, content format, and destination account separate.
- Delegate generated visuals to Image Factory. Video/audio production remains an external capability; a script is not a finished video.
- Kernel services own revisions, facts, consent, budgets, detection validity, delivery intents, recovery, and verification.
- Preserve CF-001 through CF-042 and their original business gates. CF-043 through CF-058 add channel integration; do not mark tasks complete for documentation work.
- Preserve previous planning/history. Do not sync pending changes into canonical specs or publish a runtime version before implementation acceptance.
- Record actual validation. Static document checks, official OpenSpec validation, vendor conformance, and live delivery are different evidence classes.
- Never automatically install candidate skills, disable unrelated skills, suppress provenance, bypass permission checks, or fabricate engagement metrics.
Complete architecture and execution decomposition
Read docs/architecture/Content-Factory-Architecture.zh_CN.md and openspec/changes/implement-content-factory-architecture/ alongside both existing changes. The third change decomposes the same CF-001–CF-058 parents into 232 execution steps; it is not a new product phase. Preserve the three presentation sections and four text blocks. CF-058 precedes CF-042. Do not roll up parent completion without original acceptance and actual evidence.
<!-- partme-agent-plugin-policy:v1 -->Partme Agent Plugin Architecture Rules v1
- 组织级架构规范（唯一事实源）：Partme Agent Plugin Architecture Rules v1。
- Harness 可选：默认直接使用 Skills + CLI/MCP；只有确有必要时才保留最多一个可发现的
skills/*-harness/SKILL.md，其scripts/harness.py也可选。 - 不复制宿主 Agent Runtime 或已有 CLI/MCP 的业务执行、任务数据库与权威状态；代码能力必须能追踪到真实 Agent → Skill/Command → Tool → 结果的调用链。
- 保留本仓库现有 OpenSpec、安全门禁、发布及验证要求。静态校验不代表真实宿主可执行性；所有上线宣称均需实际宿主验收。
- CI 统一使用组织级 Partme Plugin Architecture 检查器，不得复制实现或禁用检查。
<!-- /partme-agent-plugin-policy:v1 -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.