# Step 1: Scan 65 top front-end information sources

You need to search for the following 65 latest technology-related topics for front-end developers and organizations (within the past 7 days):

## 🏢 Institutional Accounts (17)

@reactjs, @vuejs, @angular, @sveltejs, @nextjs, @vercel, @remix_run, @astrodotbuild, @vite_js, @webpack, @tailwindcss, @typescript, @nodejs, @denoland, @bunjavascript, @stackblitz, @codesandbox

## 👤 Personal Accounts (48)

@dan_abramov, @sebmarkbage, @acdlite, @sophiebits, @youyuxi, @patak_dev, @antfu7, @shuding_, @rauchg, @leeerob, @shadcn, @t3dotgg, @kentcdodds, @ryanflorence, @mjackson, @remix_run, @wesbos, @addyosmani, @paul_irish, @jaffathecake, @argyleink, @Una, @chriscoyier, @sarah_edo, @cassidoo, @housecor, @getify, @BrendanEich, @slicknet, @cramforce, @mathias, @ericwbailey, @mmatuzo, @heydonworks, @steveworkman, @jensimmons, @rachelandrew, @smashingmag, @csswizardry, @mgechev, @samccone, @_developit, @Rich_Harris, @trueadm, @sebmck, @jamiebuilds, @left_pad, @devongovett

## Scanning Method

Use Google Search to search for technical content related to these accounts, employing an optimized search strategy:

**First Batch: Core Front-End Experts** (Priority search, highest quality)

- Accounts: @dan_abramov, @youyuxi, @rauchg, @leeerob, @shadcn, @t3dotgg, @kentcdodds, @addyosmani, @jaffathecake

- Search format: `@dan_abramov OR @youyuxi OR @rauchg OR @leeerob OR @shadcn OR @t3dotgg OR @kentcdodds OR @addyosmani OR @jaffathecake tool library framework performance optimization tutorial`

- Time range: freshness="week"

- category="general" (Using the general category will yield the best results)

**Second Batch: Official Framework Accounts**

- Account: @reactjs, @vuejs, @nextjs, @vercel, @sveltejs, @remix_run, @astrodotbuild, @vite_js, @tailwindcss, @typescript

- Search format: `@reactjs OR @vuejs OR @nextjs OR @vercel OR @sveltejs OR @remix_run OR @astrodotbuild OR @vite_js OR @tailwindcss OR @typescript release update feature`

- Time range: freshness="week"

- category="general"

**Third batch: Other front-end experts**

- Accounts: @antfu7, @shuding_, @wesbos, @paul_irish, @argyleink, @Una, @chriscoyier, @cassidoo, @Rich_Harris

- Search format: `@antfu7 OR @shuding_ OR @wesbos OR @paul_irish OR @argyleink OR @Una OR @chriscoyier OR @cassidoo OR @Rich_Harris tip best practice pattern`

- Time range: freshness="week"

- category="general"

**Batch 4: Tools and Runtimes**

- Account: @nodejs, @denoland, @bunjavascript, @webpack, @stackblitz, @codesandbox

- Search format: `@nodejs OR @denoland OR @bunjavascript OR @webpack OR @stackblitz OR @codesandbox performance release`

- Time range: freshness="week"

- category="general"

**Fifth Batch: Accessibility and CSS Experts**

- Accounts: @ericwbailey, @mmatuzo, @heydonworks, @csswizardry, @smashingmag

- Search format: `@ericwbailey OR @mmatuzo OR @heydonworks OR @csswizardry OR @smashingmag accessibility pattern`

- Time range: freshness="week"

- category="general"

## Key Points

- **Do not** use `excludeDomains` or `includeDomains`; let Google sort naturally.

- **Do not** limit the search to specific websites; let the algorithm return the most relevant results.

**Key Point:** Use precise keyword combinations to naturally rank high for high-quality technical articles.

- **Strategy:** Search in batches to ensure coverage of all sources, with each batch using slightly different keywords to match different types of content.

Continue with step two.

# Step 2: Intelligent Filtering and Classification

Filter the search results to find content that meets the following criteria:

## ✅ Retention Criteria (Priority Order)

1. **In-depth technical articles** (highest priority)

- Original articles on my personal technical blog

- Official documentation and changelog

- Tutorials for technical platforms (Dev.to, Medium, CSS-Tricks, etc.)

- README and documentation for the GitHub repository

2. **Utilities and Libraries**

- Newly released or updated front-end tools, libraries, and frameworks

- Includes usage instructions and code examples

3. **Development Techniques and Best Practices**

- Code techniques that can be applied directly

- Performance optimization methods

- Architectural Design Patterns

4. **Official Update**

- Framework version update notes

- API Change Documentation

- Migration Guide

5. **High-quality tweets** (as a supplement)

- Retained only if the tweet contains a full technical description or a link to a high-quality article.

- The tweet itself is rich in content, including code examples or detailed explanations.

## ❌ Filtration Standards

- Tweets that are purely social in nature (likes, retweets, simple comments)

- Non-technical content such as personal life, recruitment, and conference promotion.

- Content that is too basic or too niche

- Duplicate or similar information

- News and information content (unless it contains technical details)

- Video and podcast links (text content preferred)

- Marketing-oriented product promotion

## 📊 Classification System

The filtered content is divided into the following categories:

1. **🛠️ Tools & Libraries**: New tools, library updates, and useful plugins.

2. **⚡ Performance Optimization**: Performance enhancement techniques and optimization solutions

3. **💡 Development Skills**: Coding Techniques and Best Practices

4. **🎨 UI/UX**: Interface development, animation, and styling techniques

5. **Architecture and Patterns:** Architectural design and design patterns

6. **🔧 Workflow**: Development process and toolchain optimization

7. **📱 Cross-platform:** Mobile and desktop development

8. **New Features**: New features in frameworks/browsers

9. **♿ Accessibility**: Best Practices for Web Accessibility

## 🎯 Content Quality Assessment

Preferred choice:

- Articles with complete code examples

- Content with descriptions of practical application scenarios

- Articles containing performance data or comparative tests

- Official documentation and authoritative sources

- In-depth sharing from a developer's personal blog

Continue with step three.

# Step 3: Generate Weekly Report Document

Based on the filtered and categorized content, generate a structured front-end development weekly report:

## 📝 Weekly Report Structure

```markdown

# This week's X most informative articles on front-end development ([date range])

## 1. **[Title - Focusing on Practical Value]**

**Summary:** The core issues or themes discussed in the article.

**Recommendation Reason**: A single sentence explains "why it's worth reading," unlike a summary (which states "what it is," while the recommendation reason states "why").

**Article Link:** https://example.com/article-url

---

[Repeat the above format]

```

## ✍️ Writing Requirements

1. **Article Title Translation**:

- **The English article title must be translated into Chinese.**

- Keep the original link unchanged

- Title format: Use Chinese titles directly, do not use Markdown link format.

Example: How to optimize React performance

2. **Article Link Format** (Important):

- **The complete URL address must be displayed directly.**

- **Do not use Markdown link formats such as [citation](url) or [text](url).**

- Format: **Article Link**: https://example.com/article-url

- Correct example: **Article link**: https://shadcnstudio.com/blog/how-to-optimize-shadcn-performance

- Example of an error: **Article link**: [citation](https://example.com) or [click here](https://example.com)

3. **Concise and clear:** Each piece of content should be limited to 100-200 words.

4. **Emphasis on Practicality:** Emphasize how to apply the technology and what problems it solves.

5. **Preserve the original link:**

- If it's a technical article, use the article URL.

- If it's a tweet, use the tweet URL.

- Ensure the link is accessible

6. **Chinese Expressions:** Use clear Chinese; retain English for technical terms.

7. **Publication Time Format:** Use the YYYY-MM-DD format (e.g., 2026-04-09), and do not include the specific time.

## 📊 Content Presentation Principles

1. **Prioritize displaying technical articles:** If there are both articles and tweets on the same topic, articles will be displayed first.

2. **Maintain diversity:** Ensure coverage of different types of content (tools, tutorials, documentation, etc.)

3. **Focus on practicality:** Each piece of content should have clear application value.

4. **Provide context:** Briefly explain why this content is worth paying attention to.

## 🚫 Formatting Requirements

**Do not include the following:**

- Do not add a "This Week's Trends" section.

- Do not add "Generation Time" information.

- Do not add any summary or closing content.

- Keep your weekly report clean and concise, containing only a list of selected articles.

Generate a complete weekly report document.