https://blog.abhipraya.dev/tags/ai/Recent content in Ai on Daffa AbhiprayaHugoen-us© Daffa AbhiprayaFri, 13 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/posts/claude-code-workflow/Fri, 13 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/posts/claude-code-workflow/<p>People keep asking me how I work with Claude Code. Friends, classmates, engineers I meet - the question always comes up: &ldquo;Can you walk me through your dev workflow with it?&rdquo;</p> <p>I use Claude Code for pretty much everything: personal projects, internship work at a startup, managing my VPS, even continuing sessions from my phone with Remote Control. If you&rsquo;re already using something like GitHub Copilot or Cursor and wondering what a CLI-first AI workflow looks like when you go deeper, this is for you.</p>https://blog.abhipraya.dev/ppl/part-b/s1w3-ai-literacy/Fri, 13 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s1w3-ai-literacy/<h2 id="what-i-worked-on"> <a class="anchor" href="#what-i-worked-on" data-anchor="what-i-worked-on" aria-hidden="true">#</a> What I Worked On </h2> <p>This week tested whether the AI development infrastructure built in Sprint 1 Weeks 1-2 actually pays off under heavy workload. With 14 MRs and 10 code reviews in one week, every tool in the AI stack was used extensively. I also updated the CLAUDE.md documentation based on new patterns discovered during development.</p> <h2 id="claudemd-as-living-documentation"> <a class="anchor" href="#claudemd-as-living-documentation" data-anchor="claudemd-as-living-documentation" aria-hidden="true">#</a> CLAUDE.md as Living Documentation </h2> <p>The project&rsquo;s AI instruction document (<code>CLAUDE.md</code>) was updated this week to reflect new patterns encountered during development. Commit <code>80b127b</code> added <code>fullName</code> to the documented auth context values in <code>apps/web/CLAUDE.md</code>:</p>https://blog.abhipraya.dev/ppl/part-b/s1w2-ai-literacy/Thu, 05 Mar 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-b/s1w2-ai-literacy/<h2 id="overview"> <a class="anchor" href="#overview" data-anchor="overview" aria-hidden="true">#</a> Overview </h2> <p>The SIRA project has a comprehensive AI development setup built around Claude Code. Rather than using AI as a one-off assistant, the project treats AI tooling as infrastructure - versioned, tested, and evolved alongside the codebase.</p> <pre class="mermaid">graph TB subgraph claude [Claude Code] CM["CLAUDE.md<br>3 files, 19 commits"] MCP["MCP Servers<br>4 integrations"] CMD["Commands<br>3 slash commands"] SK["Skills<br>3 project skills"] PL["Plugins<br>3 enabled"] end subgraph ext [External Services] LN[Linear] SB[Supabase] SQ[SonarQube] GL[GitLab] end MCP --> LN MCP --> SB MCP --> SQ CMD --> GL </pre> <table> <thead> <tr> <th>Component</th> <th>Count</th> <th>What</th> </tr> </thead> <tbody> <tr> <td>CLAUDE.md files</td> <td>3</td> <td>Root + <code>apps/web/</code> + <code>apps/api/</code></td> </tr> <tr> <td>AGENTS.md symlinks</td> <td>3</td> <td>Multi-tool compatibility (Cursor, Copilot, Codex)</td> </tr> <tr> <td>MCP servers</td> <td>4</td> <td>Linear, Supabase, Context7, SonarQube</td> </tr> <tr> <td>Slash commands</td> <td>3</td> <td><code>/commit</code>, <code>/commit-and-push</code>, <code>/create-pr</code></td> </tr> <tr> <td>Project skills</td> <td>3</td> <td>frontend-design, vercel-react-best-practices, web-design-guidelines</td> </tr> <tr> <td>Plugins</td> <td>3</td> <td>GitLab, PR review toolkit, CLAUDE.md management</td> </tr> </tbody> </table> <h2 id="claudemd---three-files-19-commits"> <a class="anchor" href="#claudemd---three-files-19-commits" data-anchor="claudemd---three-files-19-commits" aria-hidden="true">#</a> CLAUDE.md - Three Files, 19 Commits </h2> <p><code>CLAUDE.md</code> is the AI instruction document for the SIRA project. It was not written once and left static. It evolved through <strong>19 commits</strong>, each one a direct response to a real friction point encountered during development.</p>