• Mar 12

The 10 commands running my creator business right now (How I turned Claude Code into a full creative team)

  • Noah Vincent
  • AI
  • 0 comments

In this Ark Letter, you'll discover: ↱ All 10 custom Claude Code commands I've built over the past 3 weeks, from content creation to system maintenance ↱ What each command actually does and why I built it, so you can find inspiration for your own workflows ↱ How small, specific commands compound into a fully systematized creator business over time

Three weeks ago, I installed Claude Code.
I watched a video about it combined to Obsidian and I instantly got obsessed with it.
Since then I've been truly committed to using it every single day.
And it completely shifted the way I work and approach my creator business.


If you're new here, Claude Code is an AI terminal that lives inside your file system.
It can read and write files, run commands, browse the web, connect to external tools, and most importantly, it can be given custom commands that you build yourself, called skills.
I made a full setup video if you want to see how I installed everything from scratch:
https://youtu.be/2mAGV7MQd04


Today, I just want to share every command I've built so far.
A real list, with a quick explanation of what each one does and why it exists.
Think of this as a window into what's actually possible when you start building.


1. /voicenotetoletter
I go for walks. I talk out loud, like I'm explaining an idea to a friend.
When I get back, I run this command. It connects to Tana (my capture app), fetches the latest voice note from my #newsletter supertag, and transforms it into a complete Ark Letter:
The full body, 5 subject line options, 5 preview text options, a key takeaways section, a blog article description, and the entire email formatted with a bold sentence opening every paragraph, exactly the way I write.
(That's actually how most of my emails were born)


2. /voicenotetodigest
Same voice note workflow, different output format.
The Ark Digest is my weekly newsletter, more curated, less essay-like, with a specific structure of sections. This command knows the difference. It fetches the same way, but produces the Digest layout instead of the Letter one.
One input. Two completely different publishable outputs.


3. /voicenotecleaner
Voice-to-text has a specific set of problems:
Comma splices, run-on sentences, false alternatives, fragments that made sense out loud but look broken on a screen.
After the first command generates a draft, this one does a second pass:
Cleans grammar errors from the transcription, simplifies overly complex sentences, fixes structure, and adds rhythm. It's my silent editor. I never send without running it.


4. /substacknotes
Every week, I need 21 Substack Notes and X posts ready to publish.
This command mines unused ideas sitting in my Tana capture layer and my latest newsletters, writes the notes in my voice in iterative batches of 3, pausing for my approval after each batch, and once everything is approved, schedules all 21 directly to my publishing slots across X, LinkedIn, and Threads via Typefully MCP.
One command. Three platforms. Zero copy-pasting
(Except for substack, I still need to manually upload those to my dedicated scheduling platform.


5. /ytmindmap
Before I script a YouTube video, I build the structure first.
This command runs an iterative interview: it asks me about the core idea, the target viewer, the key sections, the hook, the examples. Once it has enough, it generates a MindNode-compatible mindmap file I can open directly in my mind-mapping app, plus a full YouTube metadata file with title options, thumbnail concepts, a description, and tags.
Everything I need before I record a single word.


6. /ytarticle
Every YouTube video deserves a long-form article that can live on a blog and on my X profile.
I add the raw transcript to my vault, run this command, and it reads my previous articles for tone reference, then transforms the transcript into a polished piece with a proper intro, structured sections, embedded links, and a CTA conclusion, saved directly into the right video folder in my vault.
The video becomes a search-optimized article with zero additional writing effort.


7. /galaxytonewsletter
My second brain has 549 permanent notes, years of synthesized ideas, mental models, and frameworks.
This command lets me give it a topic, searches the entire Galaxy for every relevant permanent note, synthesizes them, and writes a full newsletter following my AIDA structure and writing style.
It's like asking my past self, every insight I've ever written down, to write for my future readers.
(It's actually a command I created inside a YouTube video as an example and that I don't use in my business, I prefer voice notes for authenticity, but I though it was still an interesting workflow to show you)


8. /newslettertotweets
Once a newsletter is published, this command reads it, extracts every big standalone idea, and creates individual note files, one per idea, with the right category, status, and source link, saved and ready to be scheduled inside my Obsidian base.
One piece of content becomes ten.
Zero extra writing.


9. /sessionlog
After every significant Claude Code session, this command writes a structured session log:
What was done, decisions made, problems encountered, next steps.
It sounds like a small thing. But it means Claude carries the memory of every session forward. The more we work together, the more context it has.
Every session compounds into something smarter.


10. /backup
My entire vault (549 Galaxy notes, all my newsletters, SOPs, templates, agents, scripts, everything) is a private GitHub repository.
This command commits and pushes the full vault to GitHub with a single word.
One snapshot, versioned, stored forever, accessible from any machine.
It's the simplest command I have.
And probably the one I run the most because Claude also created a daily script that push the vault everyday at 8pm without me having to do a single thing.


What I find most compelling about this list is the direction it's pointing toward.
Right now, I still copy-paste the final newsletter into my email platform.
I still manually upload articles to my blog.
There are still a few steps between the AI output and the published content.
But I'm working on closing that gap entirely.


I have a self-hosted server running.
Claude Code is connected to it.
I'm building integrations so that in the near future, Claude will be able to schedule social media content, push articles directly to my website, and send emails from my own server, all from a single conversation.
I talk to an agent. The agent executes. The content ships.
(And I only pay for my server subscription (8$/m) and Claude Code (20 $/m) instead of paying for all the different SaaS I'm currently using)


That's the version of this I'm building toward:
A creator business where the only things I do are think, learn, write, record my voice, and talk with an AI.
Pure creative work, and a system that handles the rest.
That's god-mode for a solo creator.
And it's closer than most people think.


If you want help building your own version of this:
A custom AI workflow designed around how you think, what you create, and how you want to spend your time, reply "claude" to this email.
I'll send you the details of my 1:1 coaching and we can see if it's the right fit.


Thanks for reading...
And welcome back to the Ark.
Noah.

0 comments

Sign upor login to leave a comment