Hola. Soy Hiro del Laboratorio de Full Body Tracking.

検索

【【PR】お勧めフルトラはこれ!:
ViveTracker3.0×3
ViveUltimateTracker×3
PICOMotionTracker
記事中にアフィリエイトリンクを含む記事が一部ございます。運営費用に充てられます。

フルトラ研究所フルトラ研究所
サイトの利用規約を必ずご確認ください。PC利用がお勧めです。

*Este artículo fue creado utilizando entrada de voz con IA (Aqua Voice). Tenga en cuenta que puede haber algunas inconsistencias.

Hola. Soy Hiro del Laboratorio de Full Body Tracking.

Today I want to talk about building my own personal AI secretary with Claude Code.

The “where did that note go?” problem — everyone has it, right?

Scattered Notes Is a Problem Everyone Faces

Notes in Notion, iPhone Notes, LINE Keep, Google Keep — information is everywhere. No idea where you wrote what.

I was the same way for a long time.

Changing note apps doesn’t solve it. The problem isn’t the app — it’s the lack of a system to “turn what you wrote into something usable later.”

Why Claude Code Becomes a Secretary

What’s great about Claude Code is that it can directly read and write files.

Regular ChatGPT or Claude’s chat interface — conversations end as conversations. Ask it to organize and it will, but the result doesn’t automatically save to a file.

Claude Code is different. In my setup:

(1) I throw notes and thoughts via voice input

(2) Claude Code structures them into Markdown files

(3) Those files save to Obsidian

(4) Next time I start Claude Code, I can load past files

Claude Code handles everything from “organizing to saving” automatically.

Not just chatting and done — it remains as files. That’s the decisive difference.

The “Stop Hook” Is Quietly the Most Powerful

The most effective part of my system is actually the Stop Hook.

Claude Code has a feature to automatically run a script when a session ends. I use this to auto-save every session’s conversation content to Obsidian.

Without doing anything, everything I discussed with Claude Code gets recorded.

That’s why “what was that conversation about?” never happens. Search in Obsidian and everything comes up — when and what I discussed.

PostToolUse Hook for Automatic Quality Checks

Another thing I do is the PostToolUse Hook.

This script runs automatically every time Claude Code writes a file. In my case, I use it for article quality checks.

For example:

  • Is the first person “I” (not “me” or “my” in Japanese context — checking for consistent persona)
  • Does it follow the note article format
  • Does it start with “Hello.”

Rule violations trigger automatic warnings. Claude Code checks its own output. Filtered before human eyes see it.

Why Claude Code Over Other Tools?

The reason I chose Claude Code is simple: it can directly touch local files.

Obsidian files are all local Markdown. Everything completes on my own PC without going through cloud services.

The peace of mind of having data in your own hands. You can’t get that with cloud-based tools.

Resumen

Claude Code isn’t a chat AI — it’s an “AI that can handle files.” That’s why it can be a secretary.

My setup:

  • Input: voice input
  • Organize & save: Claude Code + Obsidian
  • Auto-record: Stop Hook (daily logs)
  • Quality control: PostToolUse Hook
  • Objectify: VOICEVOX read-aloud
  • Rediscovery: loading past notes

The “where did that note go?” problem can be solved with systems. Not willpower — automation.

¡Gracias por leer! ¡Síguenos en X y suscríbete a nuestro canal de YouTube!