<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: 吴冲</title>
    <description>The latest articles on DEV Community by 吴冲 (@vito1993).</description>
    <link>https://dev.to/vito1993</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4000649%2F296fd1fe-9f59-4b73-bee6-096a315d24ca.png</url>
      <title>DEV Community: 吴冲</title>
      <link>https://dev.to/vito1993</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vito1993"/>
    <language>en</language>
    <item>
      <title>How to Create Cursor Project Rules with .mdc Files</title>
      <dc:creator>吴冲</dc:creator>
      <pubDate>Thu, 25 Jun 2026 13:30:45 +0000</pubDate>
      <link>https://dev.to/vito1993/how-to-create-cursor-project-rules-with-mdc-files-5cd2</link>
      <guid>https://dev.to/vito1993/how-to-create-cursor-project-rules-with-mdc-files-5cd2</guid>
      <description>&lt;p&gt;Cursor project rules work best when they are small, scoped and easy to maintain. Instead of keeping every instruction in one large file, split your rules into focused &lt;code&gt;.mdc&lt;/code&gt; files.&lt;/p&gt;

&lt;h2&gt;
  
  
  Suggested structure
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;project/
  .cursor/
    rules/
      project-overview.mdc
      code-style.mdc
      framework-rules.mdc
      testing.mdc
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Example &lt;code&gt;.mdc&lt;/code&gt; rule
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="nn"&gt;---&lt;/span&gt;
&lt;span class="na"&gt;description&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;React&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;component&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;conventions"&lt;/span&gt;
&lt;span class="na"&gt;globs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;**/*.tsx"&lt;/span&gt;
&lt;span class="na"&gt;alwaysApply&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;
&lt;span class="nn"&gt;---&lt;/span&gt;

&lt;span class="p"&gt;-&lt;/span&gt; Use functional components.
&lt;span class="p"&gt;-&lt;/span&gt; Define explicit TypeScript props.
&lt;span class="p"&gt;-&lt;/span&gt; Keep components focused and testable.
&lt;span class="p"&gt;-&lt;/span&gt; Prefer accessible HTML before custom abstractions.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  When to use globs
&lt;/h2&gt;

&lt;p&gt;Use globs when a rule only applies to a subset of the project:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;globs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;**/*.tsx"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;globs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;src/**/*.{ts,tsx}"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;globs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="s"&gt;app/**"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  When to use AGENTS.md
&lt;/h2&gt;

&lt;p&gt;Use &lt;code&gt;AGENTS.md&lt;/code&gt; when you want a simpler markdown instruction file that can be read by coding agents and does not need MDC frontmatter.&lt;/p&gt;

&lt;h2&gt;
  
  
  Free generator
&lt;/h2&gt;

&lt;p&gt;I made a free generator that creates &lt;code&gt;.cursor/rules/*.mdc&lt;/code&gt;, &lt;code&gt;AGENTS.md&lt;/code&gt; and legacy &lt;code&gt;.cursorrules&lt;/code&gt; output:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.cursorgenerator.dev/" rel="noopener noreferrer"&gt;https://www.cursorgenerator.dev/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cursor</category>
      <category>ai</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How to Check If a Page Is Ready for AI Search Visibility</title>
      <dc:creator>吴冲</dc:creator>
      <pubDate>Wed, 24 Jun 2026 13:17:39 +0000</pubDate>
      <link>https://dev.to/vito1993/how-to-check-if-a-page-is-ready-for-ai-search-visibility-39i</link>
      <guid>https://dev.to/vito1993/how-to-check-if-a-page-is-ready-for-ai-search-visibility-39i</guid>
      <description>&lt;p&gt;AI search is changing how people discover content. A page can rank in traditional search and still be hard for AI answer engines to extract, summarize or cite.&lt;/p&gt;

&lt;p&gt;Here is the practical checklist I use before calling a page AI-search friendly.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Start with a direct answer
&lt;/h2&gt;

&lt;p&gt;The page should answer the main question in the first few paragraphs. A good answer block is clear, factual and easy to quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Use a clean heading structure
&lt;/h2&gt;

&lt;p&gt;Use one H1, then organize the page with descriptive H2 and H3 sections. Avoid vague headings like "Introduction" or "More details" when a specific question would be clearer.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Add visible Q&amp;amp;A content
&lt;/h2&gt;

&lt;p&gt;FAQ content can help when it matches real user questions. The important part is that the questions and answers must be visible on the page, not only hidden in JSON-LD.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Use schema that matches the content
&lt;/h2&gt;

&lt;p&gt;Useful schema types include FAQPage, Article, Product, LocalBusiness and BreadcrumbList. The markup should reflect what users can actually see on the page.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Show trust and freshness signals
&lt;/h2&gt;

&lt;p&gt;Add author, publisher, published date and updated date where appropriate. This is especially important for guides, comparisons and advice content.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Keep the content crawlable
&lt;/h2&gt;

&lt;p&gt;If important text only appears after client-side rendering or user interaction, search engines and AI answer systems may miss it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Free checklist tool
&lt;/h2&gt;

&lt;p&gt;I made a free AEO Checker that scans a URL for these issues and returns a score with fix suggestions:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.aeotools.dev/aeo-checker" rel="noopener noreferrer"&gt;https://www.aeotools.dev/aeo-checker&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There is also a JSON-LD generator for FAQPage, Article, Product, LocalBusiness and BreadcrumbList:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.aeotools.dev/schema-generator" rel="noopener noreferrer"&gt;https://www.aeotools.dev/schema-generator&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>seo</category>
      <category>webdev</category>
      <category>marketing</category>
    </item>
  </channel>
</rss>
