<?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: kanta13jp1</title>
    <description>The latest articles on DEV Community by kanta13jp1 (@kanta13jp1).</description>
    <link>https://dev.to/kanta13jp1</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F801579%2F93001d32-b560-4f80-9b6e-732e7ee424d2.jpg</url>
      <title>DEV Community: kanta13jp1</title>
      <link>https://dev.to/kanta13jp1</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kanta13jp1"/>
    <language>en</language>
    <item>
      <title>How I Automated CS, Bug Fixes, and Competitor Monitoring with Claude Code Schedule</title>
      <dc:creator>kanta13jp1</dc:creator>
      <pubDate>Fri, 10 Apr 2026 18:49:45 +0000</pubDate>
      <link>https://dev.to/kanta13jp1/how-i-automated-cs-bug-fixes-and-competitor-monitoring-with-claude-code-schedule-18a6</link>
      <guid>https://dev.to/kanta13jp1/how-i-automated-cs-bug-fixes-and-competitor-monitoring-with-claude-code-schedule-18a6</guid>
      <description>&lt;h3&gt;
  
  
  The Problem
&lt;/h3&gt;

&lt;p&gt;I run a personal SaaS called "Jibun Corp" (自分株式会社) — an AI-integrated life management platform built with Flutter Web + Supabase. As a solo developer, I was drowning in:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Support ticket responses&lt;/li&gt;
&lt;li&gt;Bug reports and fixes&lt;/li&gt;
&lt;li&gt;Competitor monitoring across 14 products&lt;/li&gt;
&lt;li&gt;Daily reports and metrics tracking&lt;/li&gt;
&lt;li&gt;Blog post writing&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The Solution: Claude Code Schedule
&lt;/h3&gt;

&lt;p&gt;Claude Code recently added a "Schedule" feature. It runs tasks on a cron-like schedule, entirely in Anthropic's cloud. No server, no PC required, no API costs beyond the Pro plan.&lt;/p&gt;

&lt;h3&gt;
  
  
  My 9 Automated Tasks
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Task&lt;/th&gt;
&lt;th&gt;Frequency&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;daily-report&lt;/td&gt;
&lt;td&gt;Daily 9 AM&lt;/td&gt;
&lt;td&gt;Fetches metrics → generates report → posts to X&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;cs-check&lt;/td&gt;
&lt;td&gt;Hourly&lt;/td&gt;
&lt;td&gt;Reads tickets → replies via FAQ or fixes bugs → escalates complex ones&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;weekly-sns-draft&lt;/td&gt;
&lt;td&gt;Weekly Mon&lt;/td&gt;
&lt;td&gt;Summarizes week → drafts social posts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;daily-development&lt;/td&gt;
&lt;td&gt;Daily 10 AM&lt;/td&gt;
&lt;td&gt;Pushes roadmap tasks forward&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;pr-auto-review&lt;/td&gt;
&lt;td&gt;Every 3h&lt;/td&gt;
&lt;td&gt;Reviews open PRs for security, performance, logic&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;competitor-monitoring&lt;/td&gt;
&lt;td&gt;Daily 7 AM&lt;/td&gt;
&lt;td&gt;Checks 14 competitors' websites and news&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;infra-health-check&lt;/td&gt;
&lt;td&gt;Every 30 min&lt;/td&gt;
&lt;td&gt;Verifies DB connectivity and table availability&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;dependency-audit&lt;/td&gt;
&lt;td&gt;Weekly Mon&lt;/td&gt;
&lt;td&gt;Checks for vulnerable packages&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;blog-draft&lt;/td&gt;
&lt;td&gt;Daily 8 AM&lt;/td&gt;
&lt;td&gt;Generates technical blog drafts&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Architecture
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;CLAUDE.md (task definitions)
    ↓
Claude Code Schedule (cron trigger)
    ↓
WebFetch → Supabase Edge Functions (thin API layer)
    ↓
Supabase PostgreSQL (data persistence)
    ↓
GitHub push → Firebase auto-deploy
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Key Learnings
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Edge Functions as thin APIs&lt;/strong&gt;: Schedule can only use WebFetch (HTTP), so create minimal Edge Functions that expose your data.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;RLS matters&lt;/strong&gt;: Schedule runs as &lt;code&gt;service_role&lt;/code&gt;, so set up RLS policies accordingly.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Log everything&lt;/strong&gt;: Created a &lt;code&gt;schedule_task_runs&lt;/code&gt; table to track execution status, viewable from the admin dashboard.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Cost
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Claude Pro plan: $20/month (already paying for development)&lt;/li&gt;
&lt;li&gt;Additional API cost: $0&lt;/li&gt;
&lt;li&gt;Server cost: $0&lt;/li&gt;
&lt;li&gt;Total automation cost: $0&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Conclusion
&lt;/h3&gt;

&lt;p&gt;Claude Code Schedule turns CLAUDE.md into a living operations manual. Write what you want done, set a schedule, and walk away.&lt;/p&gt;




&lt;p&gt;URL: &lt;a href="https://my-web-app-b67f4.web.app/" rel="noopener noreferrer"&gt;https://my-web-app-b67f4.web.app/&lt;/a&gt;&lt;br&gt;
GitHub: &lt;a href="https://github.com/kanta13jp1/my_web_app" rel="noopener noreferrer"&gt;https://github.com/kanta13jp1/my_web_app&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  flutter #supabase #claudecode #automation #buildinpublic
&lt;/h1&gt;

</description>
      <category>flutter</category>
      <category>supabase</category>
      <category>claudecode</category>
      <category>automation</category>
    </item>
  </channel>
</rss>
