Posts
All the articles I've posted.
-
When department-specific Claude Code sessions don't follow instructions — putting CLAUDE.md in the actual working folder
While running multiple Claude Code sessions split by role in one project, the frontend session kept using git commands. Moving the instructions from the 'department folder' to the 'actual working folder' fixed it.
-
Two Traps I Hit While Adding Kakao and Google Login to Supabase
id_token audience validation failures and missing redirect URIs. Both are traps that rarely show up in the official docs, so I'm recording how I ran into them and solved them myself.
-
What is Deno? — The Runtime I Met in Supabase Edge Functions
While building a solo app, I touched Supabase Edge Functions and ran into Deno for the first time. Here's what I found out about what Deno is, how it differs from Node.js, and why Supabase chose Deno in the first place.
-
How System Prompts Differ from User Messages — Persona Consistency and Forcing JSON Output
A question I ran into while experimenting with personas in the Claude API: how is a system prompt actually different from just writing 'please do X' in a user message? I worked through this in terms of consistency, security, and output enforcement.