TARGET_DATE: Date in YYYY-MM-DD format
Example: 2026-02-02

TARGET_DATE = Date extracted from prompt parameters
Format: YYYY-MM-DD
Example: 2026-02-02

Read the latest 7 articles from content/blog/daily-tech-news-*.mdx
Extract reported: project names, company names, event keywords
Establish a deduplication list

Search Strategy (by priority):
1. site:techcrunch.com AI {date}
2. site:theverge.com artificial intelligence {date}
3. "OpenAI" OR "Anthropic" OR "Google AI" announcement {date}
4. "LLM" OR "GPT" OR "Claude" release {date}
5. machine learning breakthrough research {date}

Search Strategy:
1. site:github.blog {date}
2. "open source" major release {date}
3. GitHub "stars" trending repository {date}

Search Strategy:
1. site:reactjs.org OR site:vuejs.org blog {date}
2. "React" OR "Vue" OR "Next.js" OR "Svelte" release {date}
3. frontend framework update {date}
4. JavaScript TypeScript major update {date}

Search Strategy:
1. site:kubernetes.io blog {date}
2. "Rust" OR "Go" programming release {date}
3. "Docker" OR "Kubernetes" announcement {date}
4. cloud infrastructure AWS Azure GCP {date}

Search Strategy:
1. site:crunchbase.com funding {date}
2. tech startup Series A B C funding {date}
3. developer tools company announcement {date}

Search Strategy:
1. site:juejin.cn trending {date}
2. site:infoq.cn {date}
3. site:segmentfault.com headline {date}

1. Core Fact Extraction:
   - WHO: Involved companies/individuals/projects
   - WHAT: What exactly happened
   - WHEN: Exact time
   - WHERE: Location/platform of occurrence
   - WHY: Why it matters

2. Multi-source Verification (at least 2 independent sources):
   - Source A report → Retrieve original text using WebFetch
   - Source B verification → Search for the same event using WebSearch
   - Compare whether core facts are consistent

3. Confidence Marking:
   ✓ Verified (confirmed by 2+ sources)
   ? Pending verification (only single source)
   ⚠️ Controversial (conflicts between sources)

WebFetch extracts key points:
1. Core argument of the article
2. Key data and facts
3. Expert quotes and comments
4. Technical details and implementation methods
5. Practical impact on developers

Kubernetes 1.33 natively supports Sidecar
- Scope of Impact: 24/25 (Global K8s users)
- Practicality: 23/25 (Directly changes deployment methods)
- Novelty: 18/20 (First official release)
- Information Depth: 14/15 (With technical implementation details)
- Authority: 15/15 (Official release)
= Total Score: 94/100 ⭐⭐⭐⭐⭐

❌ Clickbait Detection:
- Title contains "shocking", "blockbuster", "exposed" but no substantive content
- Severe mismatch between title and body keywords
- Excessive exclamation marks and question marks

❌ Low-quality Content Filtering:
- General tech news irrelevant to developers
- Vague reports with no specific information (e.g., "AI continues to develop")
- Duplicate events reported in the last 7 days
- Unverifiable news from a single source

❌ Content Deduplication:
- For multiple reports on the same event, only retain the one with the most comprehensive information
- Priority: Official sources > Professional media > General media

undefined

---

---
title: Daily Tech News - {TARGET_DATE converted to Chinese format}
description: {Summary of the day's news highlights, 50-100 words, highlighting Top 3. Add "Today, a total of N important technical news items verified by multiple sources are included." at the end.}
date: {TARGET_DATE}
---

---

□ All news items have source links
□ Top 3 news items have in-depth analysis
□ Importance scoring markers are complete
□ No duplicate content
□ No obvious factual errors
□ MDX Security Check (must confirm item by item):
  □ No bare < symbols in the body (except in code blocks), replaced with &lt;
  □ All code block language identifiers are Shiki-supported languages (use text if unsure)
  □ No bare {} curly braces in the body (except in code blocks)
□ Chinese expression is smooth

git add content/blog/daily-tech-news-{date}.mdx
git commit -m "docs: add daily tech news for {date}"

❌ Excessive emotional words: shocking, blockbuster, exposed, earth-shattering, subversive
❌ Over-exaggeration: strongest in history, completely change, completely crush
❌ Vague expressions: a certain company, allegedly, may, might
❌ No substantive content: AI continues to develop, technology is advancing
❌ Title-content mismatch: title says major breakthrough, content is just a small update

❌ Users affected by versions <1.123.17    → Error: Unexpected character `1`
✅ Users affected by versions &lt;1.123.17

❌ When x < 10               → Error: Unexpected character `1`
✅ When x &lt; 10

❌ Array<string>              → Error: Parsed as JSX
✅ `Array<string>`            → Wrap with inline code
✅ Array&lt;string&gt;         → Or use HTML entity

text, plaintext, txt, bash, shell, sh, javascript, js, typescript, ts,
python, py, json, yaml, yml, html, css, sql, go, rust, java, c, cpp,
markdown, md, diff, toml, xml, graphql, docker, dockerfile, ini, csv

❌ ```td        → Shiki does not support this language, use ```text instead
❌ ```nushell   → Shiki does not support this language, use ```shell or ```text instead
❌ ```hcl       → Use ```text instead

❌ Format: {Name}    → Error: Name is not defined
✅ Format: \{Name\}  → Escape
✅ Format: `{Name}`  → Wrap with inline code