<?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 肖益成 (@yichengxiao).</description>
    <link>https://dev.to/yichengxiao</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%2F4165843%2F692039bc-617b-42c6-aa94-3378ae94df02.png</url>
      <title>DEV Community: 肖益成</title>
      <link>https://dev.to/yichengxiao</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yichengxiao"/>
    <language>en</language>
    <item>
      <title>How I structured an AI academic assistant for students: the Verla AI workflow</title>
      <dc:creator>肖益成</dc:creator>
      <pubDate>Tue, 06 Oct 2026 08:35:16 +0000</pubDate>
      <link>https://dev.to/yichengxiao/how-i-structured-an-ai-academic-assistant-for-students-the-verla-ai-workflow-1i2b</link>
      <guid>https://dev.to/yichengxiao/how-i-structured-an-ai-academic-assistant-for-students-the-verla-ai-workflow-1i2b</guid>
      <description>&lt;p&gt;Building study tools has taught me one thing: students don't need another chatbot. They need a workflow that takes them from an assignment prompt to a finished, reviewable draft.&lt;/p&gt;

&lt;p&gt;That's the idea behind &lt;a href="https://verla.io" rel="noopener noreferrer"&gt;Verla AI&lt;/a&gt;, an AI academic assistant I've been working on for university and college students. Here's how the pieces fit together.&lt;/p&gt;

&lt;h2&gt;
  
  
  The workflow
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Draft with context.&lt;/strong&gt; Instead of dumping a generic essay, Verla's AI essay writer works from the assignment requirements and academic context you provide — essay type, topic, sources you're working from — so the first draft is structured around the actual task.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Support every assignment type.&lt;/strong&gt; Beyond essays, the same workflow covers research papers, literature reviews, lab reports, case studies, presentations, and coding or data-analysis assignments.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Review before you submit.&lt;/strong&gt; Two tools handle this side: an AI detector that flags AI-generated content in a draft, and an AI humanizer that reworks AI-assisted text for readability, sentence flow, and natural expression while keeping the original meaning.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why detection and humanizing matter
&lt;/h2&gt;

&lt;p&gt;Most students already use AI somewhere in their process. The problem isn't using it — it's submitting text that reads like a machine wrote it, with no opportunity to review what's actually going out. Pairing generation with a detector and a humanizer closes that loop: generate, check, refine, then own the result.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;I'm iterating on the research side (source organization for longer papers) and the presentation maker. If you're a student or you build for education, I'd genuinely like feedback: what does your current essay/thesis workflow look like, and where does it break down?&lt;/p&gt;

&lt;p&gt;Verla is web-based and subscription-based, starting at $2.99: &lt;a href="https://verla.io" rel="noopener noreferrer"&gt;verla.io&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>studytips</category>
    </item>
  </channel>
</rss>
