@clickminded/coauthor-cli 0.0.15 → 0.0.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@clickminded/coauthor-cli",
3
- "version": "0.0.15",
3
+ "version": "0.0.16",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "coauthor": "dist/index.js",
@@ -98,10 +98,109 @@ This skill guides agent use of the CoAuthor CLI.
98
98
 
99
99
  - Use `reading_commitment.kind: "preset"` with a preset id for quick length choices; use `"custom"` with explicit `length_guidance` when the user gives a custom range.
100
100
  - Use top-level `canonical_entities`, `outline_seed`, `style_rules`, `must_not_change`, `structure_preference`, and `confidence_notes`. A legacy nested `handoff` object may be normalized, but top-level fields are clearer for agents.
101
- - Example:
101
+ - Field guidance:
102
+ - `topic`: The concrete subject or assignment. Include the search keyword, product, debate, or source brief if that is the true starting point.
103
+ - `angle`: The editorial thesis or framing. Use this to explain what makes this piece different from a generic article on the same topic.
104
+ - `target_audience`: Who the piece is for, including their sophistication, context, objections, and buying or reading intent.
105
+ - `core_promise`: The reader outcome. Phrase it as what the reader will understand, decide, or be able to do after reading.
106
+ - `format`: Human-readable format label, such as `blog post`, `guide`, `listicle`, `case study`, or `long-form SEO comparison guide`.
107
+ - `reading_commitment`: Use a preset when the user picked or implied a length tier. Use `custom` plus `length_guidance` when the user gave a specific range.
108
+ - `length_guidance`: Word-count bounds. Use positive integers or `null`; keep `min_words <= target_words <= max_words` when known.
109
+ - `audience_knowledge_assumptions`: What the reader already knows, so the draft does not over-explain or under-explain.
110
+ - `desired_reader_experience`: How the finished piece should feel to read, such as fast and scannable, authoritative and comprehensive, funny but informative, or practical and no-fluff.
111
+ - `structure_preferences`: List of preferred sections, ordering, comparison/table requirements, intro/conclusion instructions, or other structural choices.
112
+ - `must_include`: Specific points, keywords, URLs, products, claims, examples, or sections that must appear.
113
+ - `must_avoid`: Things to leave out, weak arguments, banned phrasings, unsupported claims, or misleading positioning.
114
+ - `non_negotiables`: Hard constraints that would make the draft wrong if violated. Use this for stricter requirements than ordinary `must_avoid` guidance.
115
+ - `evidence_expectations`: What kind of support the argument needs, such as official docs, pricing pages, public data, examples, or completed research.
116
+ - `citation_expectations`: Which claims need links or citations, preferred source types, and any source URLs that should be used.
117
+ - `liked_examples`: URLs, titles, patterns, or descriptions of examples to emulate.
118
+ - `rejected_examples`: URLs, titles, patterns, or descriptions of examples to avoid.
119
+ - `additional_editorial_guidance`: Any important prose brief that does not fit another field, including voice, pacing, product positioning, or inherited brief details.
120
+ - `editorial_profile`: Structured style controls. Use `notes` for nuance that enum values cannot capture.
121
+ - `canonical_entities`: Stable names for products, people, companies, characters, or concepts that must be referred to consistently. `actor_key` is the stable snake-case id used by `outline_seed.required_actor_keys`.
122
+ - `outline_seed`: Suggested section plan. Use `required_actor_keys` to tie sections to entries in `canonical_entities`.
123
+ - `style_rules`: Reusable sentence-level or formatting rules, such as short paragraphs, markdown tables, direct second person, or no academic hedging.
124
+ - `must_not_change`: Facts, names, positioning statements, URLs, or product limitations that must survive editing unchanged.
125
+ - `structure_preference`: A one-string summary of the overall structure. Use `structure_preferences` for the detailed list.
126
+ - `confidence_notes`: Explain what the contract was based on and where uncertainty remains.
127
+ - Real saved contract examples from the database, compacted for agent reuse:
128
+
129
+ Deep SEO comparison guide:
130
+
131
+ ```json
132
+ {
133
+ "topic": "Write a comprehensive long-form SEO comparison guide targeting the keyword \"mailchimp alternatives\" for ClickMinded Newsletter Generator.",
134
+ "angle": "Satisfy standard Mailchimp alternatives search intent, then show the category-aware distinction between email sending platforms and newsletter production workflows.",
135
+ "target_audience": "Busy founders, creators, consultants, solo marketers, agency owners, and small marketing teams evaluating Mailchimp competitors.",
136
+ "core_promise": "Help readers choose the right Mailchimp alternative by use case while making clear that ClickMinded may be the better fix when the real bottleneck is newsletter production.",
137
+ "format": "long-form SEO comparison guide",
138
+ "reading_commitment": { "kind": "custom", "preset_id": null, "source": "user_explicit" },
139
+ "length_guidance": { "min_words": 3200, "target_words": 3700, "max_words": 4200 },
140
+ "desired_reader_experience": "Comprehensive, practical, fair, and category-aware.",
141
+ "structure_preferences": ["Preserve the existing article structure and heading flow.", "Expand comparison depth for every platform."],
142
+ "must_include": ["Primary keyword \"mailchimp alternatives\" in the H1, intro, one H2 or H3, and conclusion naturally.", "Cover MailerLite, Brevo, Kit, ActiveCampaign, beehiiv, Substack, Klaviyo, Omnisend, Constant Contact, Drip, and Campaign Monitor."],
143
+ "must_avoid": ["Do not make ClickMinded sound like an ESP or Mailchimp replacement.", "Do not imply ClickMinded handles list management, deliverability, automations, forms, ecommerce, analytics, compliance management, or sending."],
144
+ "non_negotiables": ["The article must satisfy search intent for \"mailchimp alternatives\" before pitching ClickMinded.", "The ClickMinded positioning must be category-accurate and honest."],
145
+ "evidence_expectations": ["Use completed research and official pricing/features sources.", "Qualify pricing as current at time of writing."],
146
+ "citation_expectations": ["Use current source links for pricing/features, especially official sources.", "Include the ClickMinded product page and CTA URLs exactly as required."],
147
+ "editorial_profile": { "tone": "balanced", "form": "guide", "depth": "deep", "humor": "none", "section_length": "adaptive", "cadence": "moderate", "notes": "Long-form SEO comparison guide; practical, fair, and category-aware." },
148
+ "canonical_entities": [
149
+ { "actor_key": "clickminded_newsletter_generator", "character_name": "ClickMinded Newsletter Generator", "role_title": "AI newsletter generator and production workflow", "description": "A newsletter production layer. It is not an ESP.", "aliases": ["ClickMinded Newsletter Generator", "ClickMinded"], "must_preserve": true },
150
+ { "actor_key": "mailchimp", "character_name": "Mailchimp", "role_title": "Email marketing platform / ESP", "description": "Email marketing software for list management, sending, automations, forms, templates, analytics, and related ESP functions.", "aliases": ["Mailchimp"], "must_preserve": true }
151
+ ],
152
+ "outline_seed": [
153
+ { "id": "intro_quick_comparison", "heading": "The Best Mailchimp Alternatives in 2026", "intent": "Satisfy core search intent quickly and clarify replacement versus production workflow.", "must_include_points": ["Primary keyword in H1 and intro", "Clarify that some tools replace Mailchimp and ClickMinded complements it by solving production"], "required_actor_keys": ["mailchimp", "clickminded_newsletter_generator"], "notes": "" }
154
+ ],
155
+ "style_rules": ["Use Markdown headings and tables where helpful.", "Keep ClickMinded category-accurate and honest."],
156
+ "must_not_change": ["ClickMinded is not an ESP.", "ClickMinded direct integrations: Mailchimp, GoHighLevel, Kit."],
157
+ "structure_preference": "Preserve the same 10-section structure from the existing draft while expanding depth and word count.",
158
+ "confidence_notes": "Based on a saved draft expansion request and a successful research run."
159
+ }
160
+ ```
102
161
 
103
- ```bash
104
- coauthor project create --title "AI search attribution" --contract '{"topic":"AI search attribution","angle":"How marketing teams should measure source visibility across AI answer engines","target_audience":"B2B marketing leaders","core_promise":"Give readers a practical measurement framework they can use this quarter.","must_include":["source provenance","measurement tradeoffs","examples of query-level visibility checks"],"must_avoid":["generic SEO advice","unsupported vendor claims"],"evidence_expectations":["Use current platform documentation or credible examples for factual claims."],"editorial_profile":{"tone":"serious","form":"guide","depth":"deep","cadence":"moderate"}}' --json
162
+ Search-intent listicle with examples:
163
+
164
+ ```json
165
+ {
166
+ "topic": "A long-form SEO comparison/listicle article targeting \"mailchimp alternatives\" for ClickMinded Newsletter Generator.",
167
+ "angle": "Compare email platforms by the expected criteria, then add the insight that switching ESPs does not solve the weekly newsletter production problem.",
168
+ "target_audience": "Busy founders, creators, consultants, solo marketers, and small teams evaluating email marketing platforms.",
169
+ "core_promise": "Help readers choose the right Mailchimp alternative while showing when newsletter production is the real bottleneck.",
170
+ "format": "blog post",
171
+ "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
172
+ "structure_preferences": ["Use an SEO-friendly H1 such as \"The Best Mailchimp Alternatives in 2026\".", "Include a quick comparison table before the detailed reviews."],
173
+ "must_include": ["Primary keyword: mailchimp alternatives.", "ClickMinded Newsletter Generator product page: https://www.clickminded.com/products/newsletter/"],
174
+ "must_avoid": ["Do not claim ClickMinded replaces Mailchimp for list management, deliverability, automations, forms, ecommerce, or sending.", "Do not use generic AI hype or imply a one-prompt ChatGPT-style wrapper."],
175
+ "non_negotiables": ["The article must satisfy the \"Mailchimp alternatives\" search intent first.", "The ClickMinded pitch must be honest and category-accurate."],
176
+ "citation_expectations": ["Include useful source links inline for competitor information and pricing claims.", "Use SERP references as structure/gap examples."],
177
+ "liked_examples": ["Zapier alternatives posts for skimmable structure and practical recommendations.", "MailerLite comparison page for direct competitor positioning."],
178
+ "rejected_examples": ["Thin SEO listicles that merely paraphrase feature pages without judgment.", "Vendor pages that pretend their tool is best for every use case."],
179
+ "editorial_profile": { "tone": "balanced", "form": "essay", "depth": "standard", "humor": "low", "section_length": "adaptive", "cadence": "moderate", "notes": "Satisfy search intent first, then make the production-workflow insight feel obvious." },
180
+ "style_rules": ["Use short paragraphs.", "Use clear H2s/H3s matching search intent."],
181
+ "must_not_change": ["ClickMinded is not an ESP.", "ClickMinded direct integrations: Mailchimp, GoHighLevel, Kit."],
182
+ "structure_preference": "Comparison/listicle with a strategic bridge section and a dedicated ClickMinded companion-workflow section.",
183
+ "confidence_notes": "Created from ClickMinded product context and SERP research."
184
+ }
185
+ ```
186
+
187
+ Persuasive opinion essay:
188
+
189
+ ```json
190
+ {
191
+ "topic": "Whether people are justified in pressuring or shaming wealthy individuals into spending their money differently",
192
+ "angle": "Directly address readers who complain about billionaire spending, then pivot to the deeper diagnosis: external locus of control and projected helplessness.",
193
+ "target_audience": "Politically engaged readers who follow wealth and inequality debates and know the standard talking points.",
194
+ "core_promise": "Readers get a confrontational but empowering argument: policing billionaire spending is often emotional, the exploitation narrative is weaker than it looks, and the better answer is to build agency.",
195
+ "format": "blog post",
196
+ "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
197
+ "length_guidance": { "min_words": 1200, "target_words": 1500, "max_words": 1800 },
198
+ "must_include": ["Confrontational second-person opening hook about outrage at billionaire spending.", "Name external locus of control explicitly.", "Central reframe: stop outsourcing your sense of agency to what someone else does with their money."],
199
+ "must_avoid": ["Do not turn this into a money-printing, COVID-spending, or MMT thread.", "Do not use the word communism or slippery-slope-to-communism phrasing.", "Do not soften, hedge, or both-sides the core argument."],
200
+ "citation_expectations": ["Cost of a single NYC subway station.", "Annual US Medicare cost and approximate Elon Musk net worth for scale comparison.", "Rolex foundation ownership and limits on public profit claims."],
201
+ "editorial_profile": { "tone": "balanced", "form": "essay", "depth": "standard", "humor": "low", "section_length": "adaptive", "cadence": "moderate", "notes": "Reasoned and persuasive; do not make it a pure political rant or strawman the opposing view." },
202
+ "style_rules": ["Confident first-person or direct second-person OK.", "No hedge-everything academic tone.", "Use concrete scale comparisons rather than abstract moralizing."]
203
+ }
105
204
  ```
106
205
 
107
206
  ## Safety
@@ -98,10 +98,109 @@ This skill guides agent use of the CoAuthor CLI.
98
98
 
99
99
  - Use `reading_commitment.kind: "preset"` with a preset id for quick length choices; use `"custom"` with explicit `length_guidance` when the user gives a custom range.
100
100
  - Use top-level `canonical_entities`, `outline_seed`, `style_rules`, `must_not_change`, `structure_preference`, and `confidence_notes`. A legacy nested `handoff` object may be normalized, but top-level fields are clearer for agents.
101
- - Example:
101
+ - Field guidance:
102
+ - `topic`: The concrete subject or assignment. Include the search keyword, product, debate, or source brief if that is the true starting point.
103
+ - `angle`: The editorial thesis or framing. Use this to explain what makes this piece different from a generic article on the same topic.
104
+ - `target_audience`: Who the piece is for, including their sophistication, context, objections, and buying or reading intent.
105
+ - `core_promise`: The reader outcome. Phrase it as what the reader will understand, decide, or be able to do after reading.
106
+ - `format`: Human-readable format label, such as `blog post`, `guide`, `listicle`, `case study`, or `long-form SEO comparison guide`.
107
+ - `reading_commitment`: Use a preset when the user picked or implied a length tier. Use `custom` plus `length_guidance` when the user gave a specific range.
108
+ - `length_guidance`: Word-count bounds. Use positive integers or `null`; keep `min_words <= target_words <= max_words` when known.
109
+ - `audience_knowledge_assumptions`: What the reader already knows, so the draft does not over-explain or under-explain.
110
+ - `desired_reader_experience`: How the finished piece should feel to read, such as fast and scannable, authoritative and comprehensive, funny but informative, or practical and no-fluff.
111
+ - `structure_preferences`: List of preferred sections, ordering, comparison/table requirements, intro/conclusion instructions, or other structural choices.
112
+ - `must_include`: Specific points, keywords, URLs, products, claims, examples, or sections that must appear.
113
+ - `must_avoid`: Things to leave out, weak arguments, banned phrasings, unsupported claims, or misleading positioning.
114
+ - `non_negotiables`: Hard constraints that would make the draft wrong if violated. Use this for stricter requirements than ordinary `must_avoid` guidance.
115
+ - `evidence_expectations`: What kind of support the argument needs, such as official docs, pricing pages, public data, examples, or completed research.
116
+ - `citation_expectations`: Which claims need links or citations, preferred source types, and any source URLs that should be used.
117
+ - `liked_examples`: URLs, titles, patterns, or descriptions of examples to emulate.
118
+ - `rejected_examples`: URLs, titles, patterns, or descriptions of examples to avoid.
119
+ - `additional_editorial_guidance`: Any important prose brief that does not fit another field, including voice, pacing, product positioning, or inherited brief details.
120
+ - `editorial_profile`: Structured style controls. Use `notes` for nuance that enum values cannot capture.
121
+ - `canonical_entities`: Stable names for products, people, companies, characters, or concepts that must be referred to consistently. `actor_key` is the stable snake-case id used by `outline_seed.required_actor_keys`.
122
+ - `outline_seed`: Suggested section plan. Use `required_actor_keys` to tie sections to entries in `canonical_entities`.
123
+ - `style_rules`: Reusable sentence-level or formatting rules, such as short paragraphs, markdown tables, direct second person, or no academic hedging.
124
+ - `must_not_change`: Facts, names, positioning statements, URLs, or product limitations that must survive editing unchanged.
125
+ - `structure_preference`: A one-string summary of the overall structure. Use `structure_preferences` for the detailed list.
126
+ - `confidence_notes`: Explain what the contract was based on and where uncertainty remains.
127
+ - Real saved contract examples from the database, compacted for agent reuse:
128
+
129
+ Deep SEO comparison guide:
130
+
131
+ ```json
132
+ {
133
+ "topic": "Write a comprehensive long-form SEO comparison guide targeting the keyword \"mailchimp alternatives\" for ClickMinded Newsletter Generator.",
134
+ "angle": "Satisfy standard Mailchimp alternatives search intent, then show the category-aware distinction between email sending platforms and newsletter production workflows.",
135
+ "target_audience": "Busy founders, creators, consultants, solo marketers, agency owners, and small marketing teams evaluating Mailchimp competitors.",
136
+ "core_promise": "Help readers choose the right Mailchimp alternative by use case while making clear that ClickMinded may be the better fix when the real bottleneck is newsletter production.",
137
+ "format": "long-form SEO comparison guide",
138
+ "reading_commitment": { "kind": "custom", "preset_id": null, "source": "user_explicit" },
139
+ "length_guidance": { "min_words": 3200, "target_words": 3700, "max_words": 4200 },
140
+ "desired_reader_experience": "Comprehensive, practical, fair, and category-aware.",
141
+ "structure_preferences": ["Preserve the existing article structure and heading flow.", "Expand comparison depth for every platform."],
142
+ "must_include": ["Primary keyword \"mailchimp alternatives\" in the H1, intro, one H2 or H3, and conclusion naturally.", "Cover MailerLite, Brevo, Kit, ActiveCampaign, beehiiv, Substack, Klaviyo, Omnisend, Constant Contact, Drip, and Campaign Monitor."],
143
+ "must_avoid": ["Do not make ClickMinded sound like an ESP or Mailchimp replacement.", "Do not imply ClickMinded handles list management, deliverability, automations, forms, ecommerce, analytics, compliance management, or sending."],
144
+ "non_negotiables": ["The article must satisfy search intent for \"mailchimp alternatives\" before pitching ClickMinded.", "The ClickMinded positioning must be category-accurate and honest."],
145
+ "evidence_expectations": ["Use completed research and official pricing/features sources.", "Qualify pricing as current at time of writing."],
146
+ "citation_expectations": ["Use current source links for pricing/features, especially official sources.", "Include the ClickMinded product page and CTA URLs exactly as required."],
147
+ "editorial_profile": { "tone": "balanced", "form": "guide", "depth": "deep", "humor": "none", "section_length": "adaptive", "cadence": "moderate", "notes": "Long-form SEO comparison guide; practical, fair, and category-aware." },
148
+ "canonical_entities": [
149
+ { "actor_key": "clickminded_newsletter_generator", "character_name": "ClickMinded Newsletter Generator", "role_title": "AI newsletter generator and production workflow", "description": "A newsletter production layer. It is not an ESP.", "aliases": ["ClickMinded Newsletter Generator", "ClickMinded"], "must_preserve": true },
150
+ { "actor_key": "mailchimp", "character_name": "Mailchimp", "role_title": "Email marketing platform / ESP", "description": "Email marketing software for list management, sending, automations, forms, templates, analytics, and related ESP functions.", "aliases": ["Mailchimp"], "must_preserve": true }
151
+ ],
152
+ "outline_seed": [
153
+ { "id": "intro_quick_comparison", "heading": "The Best Mailchimp Alternatives in 2026", "intent": "Satisfy core search intent quickly and clarify replacement versus production workflow.", "must_include_points": ["Primary keyword in H1 and intro", "Clarify that some tools replace Mailchimp and ClickMinded complements it by solving production"], "required_actor_keys": ["mailchimp", "clickminded_newsletter_generator"], "notes": "" }
154
+ ],
155
+ "style_rules": ["Use Markdown headings and tables where helpful.", "Keep ClickMinded category-accurate and honest."],
156
+ "must_not_change": ["ClickMinded is not an ESP.", "ClickMinded direct integrations: Mailchimp, GoHighLevel, Kit."],
157
+ "structure_preference": "Preserve the same 10-section structure from the existing draft while expanding depth and word count.",
158
+ "confidence_notes": "Based on a saved draft expansion request and a successful research run."
159
+ }
160
+ ```
102
161
 
103
- ```bash
104
- coauthor project create --title "AI search attribution" --contract '{"topic":"AI search attribution","angle":"How marketing teams should measure source visibility across AI answer engines","target_audience":"B2B marketing leaders","core_promise":"Give readers a practical measurement framework they can use this quarter.","must_include":["source provenance","measurement tradeoffs","examples of query-level visibility checks"],"must_avoid":["generic SEO advice","unsupported vendor claims"],"evidence_expectations":["Use current platform documentation or credible examples for factual claims."],"editorial_profile":{"tone":"serious","form":"guide","depth":"deep","cadence":"moderate"}}' --json
162
+ Search-intent listicle with examples:
163
+
164
+ ```json
165
+ {
166
+ "topic": "A long-form SEO comparison/listicle article targeting \"mailchimp alternatives\" for ClickMinded Newsletter Generator.",
167
+ "angle": "Compare email platforms by the expected criteria, then add the insight that switching ESPs does not solve the weekly newsletter production problem.",
168
+ "target_audience": "Busy founders, creators, consultants, solo marketers, and small teams evaluating email marketing platforms.",
169
+ "core_promise": "Help readers choose the right Mailchimp alternative while showing when newsletter production is the real bottleneck.",
170
+ "format": "blog post",
171
+ "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
172
+ "structure_preferences": ["Use an SEO-friendly H1 such as \"The Best Mailchimp Alternatives in 2026\".", "Include a quick comparison table before the detailed reviews."],
173
+ "must_include": ["Primary keyword: mailchimp alternatives.", "ClickMinded Newsletter Generator product page: https://www.clickminded.com/products/newsletter/"],
174
+ "must_avoid": ["Do not claim ClickMinded replaces Mailchimp for list management, deliverability, automations, forms, ecommerce, or sending.", "Do not use generic AI hype or imply a one-prompt ChatGPT-style wrapper."],
175
+ "non_negotiables": ["The article must satisfy the \"Mailchimp alternatives\" search intent first.", "The ClickMinded pitch must be honest and category-accurate."],
176
+ "citation_expectations": ["Include useful source links inline for competitor information and pricing claims.", "Use SERP references as structure/gap examples."],
177
+ "liked_examples": ["Zapier alternatives posts for skimmable structure and practical recommendations.", "MailerLite comparison page for direct competitor positioning."],
178
+ "rejected_examples": ["Thin SEO listicles that merely paraphrase feature pages without judgment.", "Vendor pages that pretend their tool is best for every use case."],
179
+ "editorial_profile": { "tone": "balanced", "form": "essay", "depth": "standard", "humor": "low", "section_length": "adaptive", "cadence": "moderate", "notes": "Satisfy search intent first, then make the production-workflow insight feel obvious." },
180
+ "style_rules": ["Use short paragraphs.", "Use clear H2s/H3s matching search intent."],
181
+ "must_not_change": ["ClickMinded is not an ESP.", "ClickMinded direct integrations: Mailchimp, GoHighLevel, Kit."],
182
+ "structure_preference": "Comparison/listicle with a strategic bridge section and a dedicated ClickMinded companion-workflow section.",
183
+ "confidence_notes": "Created from ClickMinded product context and SERP research."
184
+ }
185
+ ```
186
+
187
+ Persuasive opinion essay:
188
+
189
+ ```json
190
+ {
191
+ "topic": "Whether people are justified in pressuring or shaming wealthy individuals into spending their money differently",
192
+ "angle": "Directly address readers who complain about billionaire spending, then pivot to the deeper diagnosis: external locus of control and projected helplessness.",
193
+ "target_audience": "Politically engaged readers who follow wealth and inequality debates and know the standard talking points.",
194
+ "core_promise": "Readers get a confrontational but empowering argument: policing billionaire spending is often emotional, the exploitation narrative is weaker than it looks, and the better answer is to build agency.",
195
+ "format": "blog post",
196
+ "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
197
+ "length_guidance": { "min_words": 1200, "target_words": 1500, "max_words": 1800 },
198
+ "must_include": ["Confrontational second-person opening hook about outrage at billionaire spending.", "Name external locus of control explicitly.", "Central reframe: stop outsourcing your sense of agency to what someone else does with their money."],
199
+ "must_avoid": ["Do not turn this into a money-printing, COVID-spending, or MMT thread.", "Do not use the word communism or slippery-slope-to-communism phrasing.", "Do not soften, hedge, or both-sides the core argument."],
200
+ "citation_expectations": ["Cost of a single NYC subway station.", "Annual US Medicare cost and approximate Elon Musk net worth for scale comparison.", "Rolex foundation ownership and limits on public profit claims."],
201
+ "editorial_profile": { "tone": "balanced", "form": "essay", "depth": "standard", "humor": "low", "section_length": "adaptive", "cadence": "moderate", "notes": "Reasoned and persuasive; do not make it a pure political rant or strawman the opposing view." },
202
+ "style_rules": ["Confident first-person or direct second-person OK.", "No hedge-everything academic tone.", "Use concrete scale comparisons rather than abstract moralizing."]
203
+ }
105
204
  ```
106
205
 
107
206
  ## Safety
@@ -98,10 +98,109 @@ This skill guides agent use of the CoAuthor CLI.
98
98
 
99
99
  - Use `reading_commitment.kind: "preset"` with a preset id for quick length choices; use `"custom"` with explicit `length_guidance` when the user gives a custom range.
100
100
  - Use top-level `canonical_entities`, `outline_seed`, `style_rules`, `must_not_change`, `structure_preference`, and `confidence_notes`. A legacy nested `handoff` object may be normalized, but top-level fields are clearer for agents.
101
- - Example:
101
+ - Field guidance:
102
+ - `topic`: The concrete subject or assignment. Include the search keyword, product, debate, or source brief if that is the true starting point.
103
+ - `angle`: The editorial thesis or framing. Use this to explain what makes this piece different from a generic article on the same topic.
104
+ - `target_audience`: Who the piece is for, including their sophistication, context, objections, and buying or reading intent.
105
+ - `core_promise`: The reader outcome. Phrase it as what the reader will understand, decide, or be able to do after reading.
106
+ - `format`: Human-readable format label, such as `blog post`, `guide`, `listicle`, `case study`, or `long-form SEO comparison guide`.
107
+ - `reading_commitment`: Use a preset when the user picked or implied a length tier. Use `custom` plus `length_guidance` when the user gave a specific range.
108
+ - `length_guidance`: Word-count bounds. Use positive integers or `null`; keep `min_words <= target_words <= max_words` when known.
109
+ - `audience_knowledge_assumptions`: What the reader already knows, so the draft does not over-explain or under-explain.
110
+ - `desired_reader_experience`: How the finished piece should feel to read, such as fast and scannable, authoritative and comprehensive, funny but informative, or practical and no-fluff.
111
+ - `structure_preferences`: List of preferred sections, ordering, comparison/table requirements, intro/conclusion instructions, or other structural choices.
112
+ - `must_include`: Specific points, keywords, URLs, products, claims, examples, or sections that must appear.
113
+ - `must_avoid`: Things to leave out, weak arguments, banned phrasings, unsupported claims, or misleading positioning.
114
+ - `non_negotiables`: Hard constraints that would make the draft wrong if violated. Use this for stricter requirements than ordinary `must_avoid` guidance.
115
+ - `evidence_expectations`: What kind of support the argument needs, such as official docs, pricing pages, public data, examples, or completed research.
116
+ - `citation_expectations`: Which claims need links or citations, preferred source types, and any source URLs that should be used.
117
+ - `liked_examples`: URLs, titles, patterns, or descriptions of examples to emulate.
118
+ - `rejected_examples`: URLs, titles, patterns, or descriptions of examples to avoid.
119
+ - `additional_editorial_guidance`: Any important prose brief that does not fit another field, including voice, pacing, product positioning, or inherited brief details.
120
+ - `editorial_profile`: Structured style controls. Use `notes` for nuance that enum values cannot capture.
121
+ - `canonical_entities`: Stable names for products, people, companies, characters, or concepts that must be referred to consistently. `actor_key` is the stable snake-case id used by `outline_seed.required_actor_keys`.
122
+ - `outline_seed`: Suggested section plan. Use `required_actor_keys` to tie sections to entries in `canonical_entities`.
123
+ - `style_rules`: Reusable sentence-level or formatting rules, such as short paragraphs, markdown tables, direct second person, or no academic hedging.
124
+ - `must_not_change`: Facts, names, positioning statements, URLs, or product limitations that must survive editing unchanged.
125
+ - `structure_preference`: A one-string summary of the overall structure. Use `structure_preferences` for the detailed list.
126
+ - `confidence_notes`: Explain what the contract was based on and where uncertainty remains.
127
+ - Real saved contract examples from the database, compacted for agent reuse:
128
+
129
+ Deep SEO comparison guide:
130
+
131
+ ```json
132
+ {
133
+ "topic": "Write a comprehensive long-form SEO comparison guide targeting the keyword \"mailchimp alternatives\" for ClickMinded Newsletter Generator.",
134
+ "angle": "Satisfy standard Mailchimp alternatives search intent, then show the category-aware distinction between email sending platforms and newsletter production workflows.",
135
+ "target_audience": "Busy founders, creators, consultants, solo marketers, agency owners, and small marketing teams evaluating Mailchimp competitors.",
136
+ "core_promise": "Help readers choose the right Mailchimp alternative by use case while making clear that ClickMinded may be the better fix when the real bottleneck is newsletter production.",
137
+ "format": "long-form SEO comparison guide",
138
+ "reading_commitment": { "kind": "custom", "preset_id": null, "source": "user_explicit" },
139
+ "length_guidance": { "min_words": 3200, "target_words": 3700, "max_words": 4200 },
140
+ "desired_reader_experience": "Comprehensive, practical, fair, and category-aware.",
141
+ "structure_preferences": ["Preserve the existing article structure and heading flow.", "Expand comparison depth for every platform."],
142
+ "must_include": ["Primary keyword \"mailchimp alternatives\" in the H1, intro, one H2 or H3, and conclusion naturally.", "Cover MailerLite, Brevo, Kit, ActiveCampaign, beehiiv, Substack, Klaviyo, Omnisend, Constant Contact, Drip, and Campaign Monitor."],
143
+ "must_avoid": ["Do not make ClickMinded sound like an ESP or Mailchimp replacement.", "Do not imply ClickMinded handles list management, deliverability, automations, forms, ecommerce, analytics, compliance management, or sending."],
144
+ "non_negotiables": ["The article must satisfy search intent for \"mailchimp alternatives\" before pitching ClickMinded.", "The ClickMinded positioning must be category-accurate and honest."],
145
+ "evidence_expectations": ["Use completed research and official pricing/features sources.", "Qualify pricing as current at time of writing."],
146
+ "citation_expectations": ["Use current source links for pricing/features, especially official sources.", "Include the ClickMinded product page and CTA URLs exactly as required."],
147
+ "editorial_profile": { "tone": "balanced", "form": "guide", "depth": "deep", "humor": "none", "section_length": "adaptive", "cadence": "moderate", "notes": "Long-form SEO comparison guide; practical, fair, and category-aware." },
148
+ "canonical_entities": [
149
+ { "actor_key": "clickminded_newsletter_generator", "character_name": "ClickMinded Newsletter Generator", "role_title": "AI newsletter generator and production workflow", "description": "A newsletter production layer. It is not an ESP.", "aliases": ["ClickMinded Newsletter Generator", "ClickMinded"], "must_preserve": true },
150
+ { "actor_key": "mailchimp", "character_name": "Mailchimp", "role_title": "Email marketing platform / ESP", "description": "Email marketing software for list management, sending, automations, forms, templates, analytics, and related ESP functions.", "aliases": ["Mailchimp"], "must_preserve": true }
151
+ ],
152
+ "outline_seed": [
153
+ { "id": "intro_quick_comparison", "heading": "The Best Mailchimp Alternatives in 2026", "intent": "Satisfy core search intent quickly and clarify replacement versus production workflow.", "must_include_points": ["Primary keyword in H1 and intro", "Clarify that some tools replace Mailchimp and ClickMinded complements it by solving production"], "required_actor_keys": ["mailchimp", "clickminded_newsletter_generator"], "notes": "" }
154
+ ],
155
+ "style_rules": ["Use Markdown headings and tables where helpful.", "Keep ClickMinded category-accurate and honest."],
156
+ "must_not_change": ["ClickMinded is not an ESP.", "ClickMinded direct integrations: Mailchimp, GoHighLevel, Kit."],
157
+ "structure_preference": "Preserve the same 10-section structure from the existing draft while expanding depth and word count.",
158
+ "confidence_notes": "Based on a saved draft expansion request and a successful research run."
159
+ }
160
+ ```
102
161
 
103
- ```bash
104
- coauthor project create --title "AI search attribution" --contract '{"topic":"AI search attribution","angle":"How marketing teams should measure source visibility across AI answer engines","target_audience":"B2B marketing leaders","core_promise":"Give readers a practical measurement framework they can use this quarter.","must_include":["source provenance","measurement tradeoffs","examples of query-level visibility checks"],"must_avoid":["generic SEO advice","unsupported vendor claims"],"evidence_expectations":["Use current platform documentation or credible examples for factual claims."],"editorial_profile":{"tone":"serious","form":"guide","depth":"deep","cadence":"moderate"}}' --json
162
+ Search-intent listicle with examples:
163
+
164
+ ```json
165
+ {
166
+ "topic": "A long-form SEO comparison/listicle article targeting \"mailchimp alternatives\" for ClickMinded Newsletter Generator.",
167
+ "angle": "Compare email platforms by the expected criteria, then add the insight that switching ESPs does not solve the weekly newsletter production problem.",
168
+ "target_audience": "Busy founders, creators, consultants, solo marketers, and small teams evaluating email marketing platforms.",
169
+ "core_promise": "Help readers choose the right Mailchimp alternative while showing when newsletter production is the real bottleneck.",
170
+ "format": "blog post",
171
+ "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
172
+ "structure_preferences": ["Use an SEO-friendly H1 such as \"The Best Mailchimp Alternatives in 2026\".", "Include a quick comparison table before the detailed reviews."],
173
+ "must_include": ["Primary keyword: mailchimp alternatives.", "ClickMinded Newsletter Generator product page: https://www.clickminded.com/products/newsletter/"],
174
+ "must_avoid": ["Do not claim ClickMinded replaces Mailchimp for list management, deliverability, automations, forms, ecommerce, or sending.", "Do not use generic AI hype or imply a one-prompt ChatGPT-style wrapper."],
175
+ "non_negotiables": ["The article must satisfy the \"Mailchimp alternatives\" search intent first.", "The ClickMinded pitch must be honest and category-accurate."],
176
+ "citation_expectations": ["Include useful source links inline for competitor information and pricing claims.", "Use SERP references as structure/gap examples."],
177
+ "liked_examples": ["Zapier alternatives posts for skimmable structure and practical recommendations.", "MailerLite comparison page for direct competitor positioning."],
178
+ "rejected_examples": ["Thin SEO listicles that merely paraphrase feature pages without judgment.", "Vendor pages that pretend their tool is best for every use case."],
179
+ "editorial_profile": { "tone": "balanced", "form": "essay", "depth": "standard", "humor": "low", "section_length": "adaptive", "cadence": "moderate", "notes": "Satisfy search intent first, then make the production-workflow insight feel obvious." },
180
+ "style_rules": ["Use short paragraphs.", "Use clear H2s/H3s matching search intent."],
181
+ "must_not_change": ["ClickMinded is not an ESP.", "ClickMinded direct integrations: Mailchimp, GoHighLevel, Kit."],
182
+ "structure_preference": "Comparison/listicle with a strategic bridge section and a dedicated ClickMinded companion-workflow section.",
183
+ "confidence_notes": "Created from ClickMinded product context and SERP research."
184
+ }
185
+ ```
186
+
187
+ Persuasive opinion essay:
188
+
189
+ ```json
190
+ {
191
+ "topic": "Whether people are justified in pressuring or shaming wealthy individuals into spending their money differently",
192
+ "angle": "Directly address readers who complain about billionaire spending, then pivot to the deeper diagnosis: external locus of control and projected helplessness.",
193
+ "target_audience": "Politically engaged readers who follow wealth and inequality debates and know the standard talking points.",
194
+ "core_promise": "Readers get a confrontational but empowering argument: policing billionaire spending is often emotional, the exploitation narrative is weaker than it looks, and the better answer is to build agency.",
195
+ "format": "blog post",
196
+ "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
197
+ "length_guidance": { "min_words": 1200, "target_words": 1500, "max_words": 1800 },
198
+ "must_include": ["Confrontational second-person opening hook about outrage at billionaire spending.", "Name external locus of control explicitly.", "Central reframe: stop outsourcing your sense of agency to what someone else does with their money."],
199
+ "must_avoid": ["Do not turn this into a money-printing, COVID-spending, or MMT thread.", "Do not use the word communism or slippery-slope-to-communism phrasing.", "Do not soften, hedge, or both-sides the core argument."],
200
+ "citation_expectations": ["Cost of a single NYC subway station.", "Annual US Medicare cost and approximate Elon Musk net worth for scale comparison.", "Rolex foundation ownership and limits on public profit claims."],
201
+ "editorial_profile": { "tone": "balanced", "form": "essay", "depth": "standard", "humor": "low", "section_length": "adaptive", "cadence": "moderate", "notes": "Reasoned and persuasive; do not make it a pure political rant or strawman the opposing view." },
202
+ "style_rules": ["Confident first-person or direct second-person OK.", "No hedge-everything academic tone.", "Use concrete scale comparisons rather than abstract moralizing."]
203
+ }
105
204
  ```
106
205
 
107
206
  ## Safety
@@ -93,6 +93,113 @@ alwaysApply: true
93
93
 
94
94
  - Use `reading_commitment.kind: "preset"` with a preset id for quick length choices; use `"custom"` with explicit `length_guidance` when the user gives a custom range.
95
95
  - Use top-level `canonical_entities`, `outline_seed`, `style_rules`, `must_not_change`, `structure_preference`, and `confidence_notes`. A legacy nested `handoff` object may be normalized, but top-level fields are clearer for agents.
96
+
97
+ ## Editorial Contract Field Guidance
98
+
99
+ - `topic`: The concrete subject or assignment. Include the search keyword, product, debate, or source brief if that is the true starting point.
100
+ - `angle`: The editorial thesis or framing. Use this to explain what makes this piece different from a generic article on the same topic.
101
+ - `target_audience`: Who the piece is for, including their sophistication, context, objections, and buying or reading intent.
102
+ - `core_promise`: The reader outcome. Phrase it as what the reader will understand, decide, or be able to do after reading.
103
+ - `format`: Human-readable format label, such as `blog post`, `guide`, `listicle`, `case study`, or `long-form SEO comparison guide`.
104
+ - `reading_commitment`: Use a preset when the user picked or implied a length tier. Use `custom` plus `length_guidance` when the user gave a specific range.
105
+ - `length_guidance`: Word-count bounds. Use positive integers or `null`; keep `min_words <= target_words <= max_words` when known.
106
+ - `audience_knowledge_assumptions`: What the reader already knows, so the draft does not over-explain or under-explain.
107
+ - `desired_reader_experience`: How the finished piece should feel to read, such as fast and scannable, authoritative and comprehensive, funny but informative, or practical and no-fluff.
108
+ - `structure_preferences`: List of preferred sections, ordering, comparison/table requirements, intro/conclusion instructions, or other structural choices.
109
+ - `must_include`: Specific points, keywords, URLs, products, claims, examples, or sections that must appear.
110
+ - `must_avoid`: Things to leave out, weak arguments, banned phrasings, unsupported claims, or misleading positioning.
111
+ - `non_negotiables`: Hard constraints that would make the draft wrong if violated. Use this for stricter requirements than ordinary `must_avoid` guidance.
112
+ - `evidence_expectations`: What kind of support the argument needs, such as official docs, pricing pages, public data, examples, or completed research.
113
+ - `citation_expectations`: Which claims need links or citations, preferred source types, and any source URLs that should be used.
114
+ - `liked_examples`: URLs, titles, patterns, or descriptions of examples to emulate.
115
+ - `rejected_examples`: URLs, titles, patterns, or descriptions of examples to avoid.
116
+ - `additional_editorial_guidance`: Any important prose brief that does not fit another field, including voice, pacing, product positioning, or inherited brief details.
117
+ - `editorial_profile`: Structured style controls. Use `notes` for nuance that enum values cannot capture.
118
+ - `canonical_entities`: Stable names for products, people, companies, characters, or concepts that must be referred to consistently. `actor_key` is the stable snake-case id used by `outline_seed.required_actor_keys`.
119
+ - `outline_seed`: Suggested section plan. Use `required_actor_keys` to tie sections to entries in `canonical_entities`.
120
+ - `style_rules`: Reusable sentence-level or formatting rules, such as short paragraphs, markdown tables, direct second person, or no academic hedging.
121
+ - `must_not_change`: Facts, names, positioning statements, URLs, or product limitations that must survive editing unchanged.
122
+ - `structure_preference`: A one-string summary of the overall structure. Use `structure_preferences` for the detailed list.
123
+ - `confidence_notes`: Explain what the contract was based on and where uncertainty remains.
124
+
125
+ ## Real Saved Contract Examples
126
+
127
+ Deep SEO comparison guide:
128
+
129
+ ```json
130
+ {
131
+ "topic": "Write a comprehensive long-form SEO comparison guide targeting the keyword \"mailchimp alternatives\" for ClickMinded Newsletter Generator.",
132
+ "angle": "Satisfy standard Mailchimp alternatives search intent, then show the category-aware distinction between email sending platforms and newsletter production workflows.",
133
+ "target_audience": "Busy founders, creators, consultants, solo marketers, agency owners, and small marketing teams evaluating Mailchimp competitors.",
134
+ "core_promise": "Help readers choose the right Mailchimp alternative by use case while making clear that ClickMinded may be the better fix when the real bottleneck is newsletter production.",
135
+ "format": "long-form SEO comparison guide",
136
+ "reading_commitment": { "kind": "custom", "preset_id": null, "source": "user_explicit" },
137
+ "length_guidance": { "min_words": 3200, "target_words": 3700, "max_words": 4200 },
138
+ "desired_reader_experience": "Comprehensive, practical, fair, and category-aware.",
139
+ "structure_preferences": ["Preserve the existing article structure and heading flow.", "Expand comparison depth for every platform."],
140
+ "must_include": ["Primary keyword \"mailchimp alternatives\" in the H1, intro, one H2 or H3, and conclusion naturally.", "Cover MailerLite, Brevo, Kit, ActiveCampaign, beehiiv, Substack, Klaviyo, Omnisend, Constant Contact, Drip, and Campaign Monitor."],
141
+ "must_avoid": ["Do not make ClickMinded sound like an ESP or Mailchimp replacement.", "Do not imply ClickMinded handles list management, deliverability, automations, forms, ecommerce, analytics, compliance management, or sending."],
142
+ "non_negotiables": ["The article must satisfy search intent for \"mailchimp alternatives\" before pitching ClickMinded.", "The ClickMinded positioning must be category-accurate and honest."],
143
+ "evidence_expectations": ["Use completed research and official pricing/features sources.", "Qualify pricing as current at time of writing."],
144
+ "citation_expectations": ["Use current source links for pricing/features, especially official sources.", "Include the ClickMinded product page and CTA URLs exactly as required."],
145
+ "editorial_profile": { "tone": "balanced", "form": "guide", "depth": "deep", "humor": "none", "section_length": "adaptive", "cadence": "moderate", "notes": "Long-form SEO comparison guide; practical, fair, and category-aware." },
146
+ "canonical_entities": [
147
+ { "actor_key": "clickminded_newsletter_generator", "character_name": "ClickMinded Newsletter Generator", "role_title": "AI newsletter generator and production workflow", "description": "A newsletter production layer. It is not an ESP.", "aliases": ["ClickMinded Newsletter Generator", "ClickMinded"], "must_preserve": true },
148
+ { "actor_key": "mailchimp", "character_name": "Mailchimp", "role_title": "Email marketing platform / ESP", "description": "Email marketing software for list management, sending, automations, forms, templates, analytics, and related ESP functions.", "aliases": ["Mailchimp"], "must_preserve": true }
149
+ ],
150
+ "outline_seed": [
151
+ { "id": "intro_quick_comparison", "heading": "The Best Mailchimp Alternatives in 2026", "intent": "Satisfy core search intent quickly and clarify replacement versus production workflow.", "must_include_points": ["Primary keyword in H1 and intro", "Clarify that some tools replace Mailchimp and ClickMinded complements it by solving production"], "required_actor_keys": ["mailchimp", "clickminded_newsletter_generator"], "notes": "" }
152
+ ],
153
+ "style_rules": ["Use Markdown headings and tables where helpful.", "Keep ClickMinded category-accurate and honest."],
154
+ "must_not_change": ["ClickMinded is not an ESP.", "ClickMinded direct integrations: Mailchimp, GoHighLevel, Kit."],
155
+ "structure_preference": "Preserve the same 10-section structure from the existing draft while expanding depth and word count.",
156
+ "confidence_notes": "Based on a saved draft expansion request and a successful research run."
157
+ }
158
+ ```
159
+
160
+ Search-intent listicle with examples:
161
+
162
+ ```json
163
+ {
164
+ "topic": "A long-form SEO comparison/listicle article targeting \"mailchimp alternatives\" for ClickMinded Newsletter Generator.",
165
+ "angle": "Compare email platforms by the expected criteria, then add the insight that switching ESPs does not solve the weekly newsletter production problem.",
166
+ "target_audience": "Busy founders, creators, consultants, solo marketers, and small teams evaluating email marketing platforms.",
167
+ "core_promise": "Help readers choose the right Mailchimp alternative while showing when newsletter production is the real bottleneck.",
168
+ "format": "blog post",
169
+ "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
170
+ "structure_preferences": ["Use an SEO-friendly H1 such as \"The Best Mailchimp Alternatives in 2026\".", "Include a quick comparison table before the detailed reviews."],
171
+ "must_include": ["Primary keyword: mailchimp alternatives.", "ClickMinded Newsletter Generator product page: https://www.clickminded.com/products/newsletter/"],
172
+ "must_avoid": ["Do not claim ClickMinded replaces Mailchimp for list management, deliverability, automations, forms, ecommerce, or sending.", "Do not use generic AI hype or imply a one-prompt ChatGPT-style wrapper."],
173
+ "non_negotiables": ["The article must satisfy the \"Mailchimp alternatives\" search intent first.", "The ClickMinded pitch must be honest and category-accurate."],
174
+ "citation_expectations": ["Include useful source links inline for competitor information and pricing claims.", "Use SERP references as structure/gap examples."],
175
+ "liked_examples": ["Zapier alternatives posts for skimmable structure and practical recommendations.", "MailerLite comparison page for direct competitor positioning."],
176
+ "rejected_examples": ["Thin SEO listicles that merely paraphrase feature pages without judgment.", "Vendor pages that pretend their tool is best for every use case."],
177
+ "editorial_profile": { "tone": "balanced", "form": "essay", "depth": "standard", "humor": "low", "section_length": "adaptive", "cadence": "moderate", "notes": "Satisfy search intent first, then make the production-workflow insight feel obvious." },
178
+ "style_rules": ["Use short paragraphs.", "Use clear H2s/H3s matching search intent."],
179
+ "must_not_change": ["ClickMinded is not an ESP.", "ClickMinded direct integrations: Mailchimp, GoHighLevel, Kit."],
180
+ "structure_preference": "Comparison/listicle with a strategic bridge section and a dedicated ClickMinded companion-workflow section.",
181
+ "confidence_notes": "Created from ClickMinded product context and SERP research."
182
+ }
183
+ ```
184
+
185
+ Persuasive opinion essay:
186
+
187
+ ```json
188
+ {
189
+ "topic": "Whether people are justified in pressuring or shaming wealthy individuals into spending their money differently",
190
+ "angle": "Directly address readers who complain about billionaire spending, then pivot to the deeper diagnosis: external locus of control and projected helplessness.",
191
+ "target_audience": "Politically engaged readers who follow wealth and inequality debates and know the standard talking points.",
192
+ "core_promise": "Readers get a confrontational but empowering argument: policing billionaire spending is often emotional, the exploitation narrative is weaker than it looks, and the better answer is to build agency.",
193
+ "format": "blog post",
194
+ "reading_commitment": { "kind": "preset", "preset_id": "balanced_post", "source": "user_explicit" },
195
+ "length_guidance": { "min_words": 1200, "target_words": 1500, "max_words": 1800 },
196
+ "must_include": ["Confrontational second-person opening hook about outrage at billionaire spending.", "Name external locus of control explicitly.", "Central reframe: stop outsourcing your sense of agency to what someone else does with their money."],
197
+ "must_avoid": ["Do not turn this into a money-printing, COVID-spending, or MMT thread.", "Do not use the word communism or slippery-slope-to-communism phrasing.", "Do not soften, hedge, or both-sides the core argument."],
198
+ "citation_expectations": ["Cost of a single NYC subway station.", "Annual US Medicare cost and approximate Elon Musk net worth for scale comparison.", "Rolex foundation ownership and limits on public profit claims."],
199
+ "editorial_profile": { "tone": "balanced", "form": "essay", "depth": "standard", "humor": "low", "section_length": "adaptive", "cadence": "moderate", "notes": "Reasoned and persuasive; do not make it a pure political rant or strawman the opposing view." },
200
+ "style_rules": ["Confident first-person or direct second-person OK.", "No hedge-everything academic tone.", "Use concrete scale comparisons rather than abstract moralizing."]
201
+ }
202
+ ```
96
203
  - Never print tokens, service-role keys, cookies, or authorization headers.
97
204
  - Never ask the user to paste Anthropic, OpenAI, or Gemini provider API keys into chat or the terminal; key entry belongs in CoAuthor AI settings.
98
205
  - Pass tokens through environment variables or secret-backed CLI options only.