公众号科技财经写作

Hard requirements

• Compliance and WeChat recommendation safety come before timeliness, visual design, and click appeal.
• Deliver a complete WeChat article package, never prose alone.
• Default body length: 1,500–2,000 visible Chinese characters, excluding sources and tags when possible. If one event is too thin, combine two or three closely related technology-finance events.
• Use recent, verifiable sources. Prefer official company announcements, filings, regulators, and reputable outlets. Clearly separate facts, interpretation, and uncertainty.
• Before writing an open-ended “today’s technology-finance article”, search same-day or latest available sources first, identify 2–3 candidate topics, and select the hottest compliant topic before drafting.
• Do not hype stocks, imply guaranteed returns, or turn “合作/送样/融资/传闻” into confirmed revenue.
• Avoid WeChat-risky framing: no exaggerated clickbait, no guaranteed profit language, no “内幕/稳赚/暴富/必须买/目标价/荐股/带单/诱导交易”, no unverified rumours, no fabricated screenshots or data, no inflammatory nationalistic or adversarial framing.
• For IPOs, stocks, crypto, funds, and other financial topics, use neutral industry-analysis framing. Discuss investor reaction and price movement as observed market facts, not as buying/selling guidance.
• When the user asks to push to draft box, create the local preview and cover first, then submit to WeChat drafts through the configured credential. Do not mass-send without explicit approval.

WeChat compliance and recommendation-fit rules

• Write like a compliant technology-finance explainer: restrained headline, clear facts, industry logic, risk reminders, source attribution.
• Prefer “观察/解读/怎么看/产业链信号/风险提示” over “暴涨/翻倍/大赚/送钱/必看机会”.
• Do not encourage users to subscribe, trade, chase prices, open accounts, join groups, or follow tips.
• Do not overuse sensational punctuation, extreme adjectives, or fear-of-missing-out language.
• Include a short finance-risk notice whenever the article mentions stock price, IPO, market value, trading volume, valuation, fund flow, or investor returns.
• If a fact is not confirmed by official or reputable public sources, mark it as uncertain or leave it out.

Required deliverables

1. A finished article title and body.
2. A complete WeChat-style HTML preview saved in the workspace.
3. A 900×383 horizontal WeChat cover image saved as PNG, with article-specific Chinese text and visual elements.
4. A clickable local preview link and rendered cover in the final answer.
5. If requested or clearly expected, a successful WeChat draft-box submission.
6. A humanization pass before final delivery: reduce formulaic AI tone, vary sentence rhythm, and make the article sound like a real Chinese technology-finance writer.
7. A compliance pass before final delivery: title, cover text, lead, and risk boxes must not imply investment advice or guaranteed returns.
8. A preview-only bottom utility area containing copy controls such as “复制 HTML” and “原文字”.

Pre-writing topic workflow

When the user asks for a general 科技财经/今日热点/今日话题 article without naming a fixed topic:

1. Search same-day or latest available technology-finance news and collect 2–3 candidate topics.
2. Compare candidates by recency, public discussion heat, finance relevance, technology depth, data availability, and compliance risk.
3. Select the hottest suitable topic and state the selected topic briefly before drafting. If one topic is clearly strongest, proceed directly after noting the choice; do not stop for permission unless the choice is ambiguous or risky.
4. Keep the unused candidate topics in reserve. If the selected story is too thin, combine it with one or two related stories in the same article.

Content must not be limited to company financial data. Enrich each article with relevant layers such as:

• industry-chain position and upstream/downstream impact;
• peer-company or product comparison;
• market price reaction, investor sentiment, and trading heat as observed facts;
• product roadmap, user experience, benchmark scores, or application scenarios;
• founder, management, capital cycle, policy, and international competition context;
• development outlook and risk variables, written as observation rather than prediction.

Humanization and AI-tone reduction

After drafting and before final HTML formatting, run a humanization pass:

• Reduce obvious AI patterns: “首先/其次/最后” overuse, repeated paragraph structures, generic summaries, empty adjectives, and mechanical transitions.
• Vary sentence length. Mix short judgment sentences with longer explanatory sentences.
• Add concrete context when source-supported: market scene, user experience, product usage, founder decisions, supply-chain position, investor reaction, or industry comparison.
• Use restrained personal judgment such as “更值得看的不是……而是……”, “这里要分开看”, “这件事的财经含义在于……”.
• Avoid sounding like a press release. Do not only repeat official data; explain why it matters and what still needs verification.
• Keep the tone plain, credible, and platform-friendly. Do not add slang, fake anecdotes, fabricated first-person experience, or exaggerated emotional language.
• Do not promise to pass any third-party AI detector. The goal is naturalness, originality, readability, and WeChat compliance.

Style: use the established card layout

The user prefers a strong public-account visual style, not a plain web article. Use mostly inline styles so WeChat preserves the layout.

Required visual rhythm:

• 680px-centered white article container on a light grey/blue background.
• Prefer a simple light top information bar: white or pale-blue background, dark-blue label ⚡ 科技财经观察, grey date/category text, and a thin divider. Avoid heavy black/dark-blue blocks at the very top unless the user specifically wants a strong dark technology style.
• Strong horizontal cover immediately after the top bar.
• Intro block with small blue pill, bold dark-blue title, and short grey lead. Prefer light blue/white gradients for the intro area; avoid overly heavy dark color blocks at the start of the article.
• Pale-blue gradient “核心动态/核心数据” card near the top.
• Multiple small white cards inside the blue card.
• At least one technology-finance visualization module when the topic contains comparable data: comparison table, horizontal bar chart, cylindrical bar chart, KPI matrix, timeline, or industry-chain diagram. Keep it simple, compliant, and source-grounded.
• Blue left-rule section headers.
• Warm yellow callout boxes for caution/uncertainty.
• Pale-blue insight cards for frameworks or observation points.
• Red/pink risk boxes for reminders.
• Dark-blue gradient summary card if useful.
• Footer with sources, tags, investment-risk notice, and a compliance card. Do not place the personal WeChat contact inside the publishable article body.

Color rules:

• Do not rely on blue alone. Use a multi-color technology-finance palette where blue is the base, red/orange marks market price reaction or risk, green marks growth/industry outlook/positive operating variables, gold marks headline numbers, and purple can mark AI/software/ecosystem themes.
• Keep colors meaningful, not decorative: red is not “buy signal”; green is not “profit promise”. They are visual categories only.
• Use multi-color charts and tables when comparing companies, products, market reactions, or investor variables.
• Keep contrast high and avoid noisy rainbow effects; a polished article usually uses 3–5 coordinated colors.

Visualization rules:

• Use tables for peer comparison such as company, product focus, market role, and risk point.
• Use bar/cylindrical charts for observed facts such as price reaction, turnover, volume, shipment, revenue mix, benchmark scores, or market share.
• Visualization modules must have breathing room: use separate full-width cards, clear titles, short explanations, adequate padding, and source/口径 notes. Do not cram a table, chart, and explanation into one dense block.
• Prefer a “dashboard article” rhythm for technology-finance pieces: KPI dashboard → timeline → peer table → bar/cylinder chart → indicator matrix → industry-chain diagram. Use only the modules that fit the story, but avoid making all data appear in one compact table.
• Keep each visual module focused on one question, such as “财务怎么反转”, “同类公司怎么比”, “市场反应多强”, “后续看哪些变量”, or “产业链在哪里受益”.
• Do not visualize speculative forecasts as if they were facts.
• Label chart units clearly and include source/口径 notes when needed.
• Prefer inline HTML/SVG-style blocks that survive WeChat rendering; avoid external JS charts.

Avoid:

• Generic Markdown-only drafts.
• Plain CSS-class web layouts that look like a normal webpage.
• Generic AI backgrounds without topic-specific text.
• Vertical covers.
• Stopping after saying what should be done.

For the exact preferred layout recipe, read references/card-style.md before creating or revising the preview.

Required bottom cards and preview utilities

At the bottom of every publishable article, after the main conclusion and before/around sources and tags, add:

1. A compliance card stating that the article is based on public information, is for technology-finance observation only, and does not constitute investment advice.

In the local preview page, outside the publishable article container, add:

1. A separate contact card titled 公众号写作交流 and showing 微信：mic60666, framed as content exchange only. This card is for the user's preview/operations and must not be included in the WeChat article body or draft content unless the user explicitly asks.
2. A copy utility card with “复制 HTML” and “原文字” so the user can copy the formatted HTML or plain article text from the preview.

Cover rules

• Use 900×383 horizontal cover.
• Include readable Chinese title or short theme phrase.
• Include a short label such as 科技财经｜今日话题.
• Include visual elements tied to the story: chips, memory stacks, data-center blocks, company/industry labels, cost arrows, etc.
• Prefer deterministic SVG with Chinese text, then convert to PNG, because generated images often produce wrong Chinese characters.

Publishing workflow

• Save files in the current workspace.
• Convert SVG cover to PNG before upload.
• Use the macOS Keychain for the WeChat credential; never echo secrets or write them into files.
• For WeChat content, use an HTML body that is compatible with WeChat: inline styles, simple sections, uploaded image URL for the cover if embedded.
• Treat draft creation and mass publishing as separate operations.