YouMind
登入

Automating 100-Yen Note Sales with Claude Code: A Full Prompt Guide

@take_ai_mkt
日語2026年9月25日
117K
123
5
0
321

TL;DR

This guide details a workflow for automating the creation of low-priced digital articles using Claude Code. It emphasizes establishing a 'CLAUDE.md' rulebook and implementing a monthly feedback loop where sales data informs future content generation to improve conversion rates.

Before heading out, type just one line into your computer.

That's all you do.

When you return at night and open the folder, five new articles are waiting. Repeat this for four weeks, and you'll have twenty.

So far, this automation loop worked perfectly.

But the moment I opened the twentieth article, I realized something.

The quality of the first article and the twentieth was exactly the same.

Sales were around 70,000 yen at that point.

There was no improvement, nor any degradation. The common traits of selling articles and non-selling articles were never fed back into the next piece.

AI writes according to instructions. As long as the instructions don't change, the twentieth article is written with the same prompt as the first. It seems obvious in hindsight.

Just arranging departments doesn't make a company. A company that doesn't learn produces nothing but its first draft, no matter how many times it tries.

In this article, I will lay out the entire process of delegating 100-yen note creation to Claude Code. On top of that, I will add the "fifth department" that most people miss at the end.

This is where things start changing from article twenty-one onward.

"500,000 Yen/Month" Takes the Form of Multiplication

First, let's unpack the numbers.

Paid notes can be priced starting at 100 yen.

500,000 yen ÷ 100 yen = 5,000 purchases.

If you think "I can't get 5,000 people," you've already lost. But this 5,000 isn't necessarily unique people.

If one person buys an average of five articles, you only need 1,000 people. If you have 150 articles, each article needs to reach about seven people per month.

One article reaches seven people a month.

At this level, even plain procedural guides enter the search results. Going viral or having thousands of followers appears nowhere in this equation.

And what you should really look at in this formula is the structure itself.

Revenue = Number of Articles × Purchases Per Person

The left side, "Number of Articles," can be increased by workload. That's why you can delegate it to AI.

The tricky part is the right side. Purchases per person don't automatically rise just because you increase volume.

The department responsible for this is the one we'll add in the second half of the article.

For those who want to know the full picture of achieving results with side hustles alongside this article 🎁

Currently, via official LINE, for 0 yen:

"Shokupan-style AI × Fastest Affiliate Strategy: Top 5 Bonuses"

食パン on X — cover

is being given away 🎁

Since this was originally planned as paid content,

distribution will close once capacity is reached.

Please grab it along with this article while you can.

▼▼▼

【▶︎▶︎▶︎Receive the 5 Bonuses】

Now, let's get to the main topic!

What Changes When You Hand Over a Folder

The decisive difference between Claude Code and chat-based Q&A AI is that you can entrust it with an entire computer folder.

Three capabilities emerge:

• You can make it read all articles in the folder at once.

• You can generate five drafts simultaneously instead of one by one.

• If you place a file containing "our rules," it reads that before starting every task.

The third point is what makes it a "company."

Place a single file named CLAUDE.md inside the folder containing your articles.

Whatever is written there remains a permanent premise going forward.

You no longer need to explain things to new hires every time. It's like distributing employee handbooks.

Preparation is short: create one folder for articles and simply type claude there.

Let's start by creating that one file.

———————

【Copy-Paste Prompt】

Save the following content as a file named CLAUDE.md.

【About This Company】

Product: 100-yen paid note articles

Reader: Someone who wants to finish this procedure today. Zero prior knowledge.

Length per article: 3,000–5,000 characters

Tone: Polite (desu/masu). Short assertions. Replace jargon with plain language on first use.

【Article Structure】

  1. The situation where the reader is currently stuck (within 150 chars)
  2. Overview. How many steps to completion?
  3. Steps for each phase. Include screen names and button locations.
  4. Common pitfalls and solutions.
  5. How to confirm completion.

【Paywall Position】

Place immediately after Step 2 of the structure.

Keep free portion to 20-30% of total.

Use specific procedure names in paid section headings.

【Prohibited】

Paragraphs ending in generalities.

Sentences ending in "It is important..." without subsequent actionable steps.

Asserting specs you aren't sure about. Mark uncertain parts with 【To Confirm】.

【Trends of Selling Articles】

(Leave blank here. HR Department will fill this in later.)

———————

After pasting, rewrite only the "Reader" and "Prohibited" sections in your own words.

Changing these two spots alone drastically alters the output.

The last blank field is fine for now.

This is where the fifth department will reside.

Run the First Cycle with Three Departments

Start with Planning.

The heaviest lift for 100-yen notes wasn't writing, but finding topics.

Moreover, if you don't specify direction, AI tends to list flashy, competitive themes.

So, provide detailed conditions.

———————

【Copy-Paste Prompt】

Generate 30 sellable themes for 100-yen note articles.

【Conditions】

Limit to situations involving "procedures," "forms," "applications," or "settings" in work/life.

Prioritize areas where searchers exist but complete explanations are missing.

Prioritize themes where the same person gets stuck again in six months or next year.

Exclude money-making, investment, and romance topics.

Exclude issues solvable by reading official help docs for one minute.

【Output Format per Theme】

  1. Theme Name
  2. Three likely search queries
  3. Who is stuck and in what scenario
  4. What to show for free vs. what to put behind paywall

After generating 30, keep only those where #4 "paid procedures" are concrete actions, narrowing down to the top 10.

Write one line explaining why each was chosen.

———————

The final instruction "narrow down and explain why" is key.

If handed 30 raw ideas, you'll stall deciding where to start.

The output looks something like this:

• List of attachments and filling guide for application forms touched once a year.

• Minimum initial setup for a tool assigned with zero handover.

• Procedure for someone creating internal forms for the first time.

All are plain, lacking flashiness.

But plain procedures often lack consolidated explanations anywhere online.

People buy 100-yen notes not for inspiration, but to finish a task today.

Next, run Writing and Inspection together.

———————

【Copy-Paste Prompt】

Write body text for the top 5 themes from planning, strictly following the structure in CLAUDE.md.

One file per theme. Filename = Theme Name.

Create all 5 at once. No intermediate checks needed.

Mark paywall location with "--- Paid Section Starts Here ---".

Include actual screen names, button names, and input examples in every step.

Add 【To Confirm】 for any unverifiable specs.

After finishing 5 drafts, re-read the entire folder and fix these 4 points:

  1. Duplication: Delete or replace paragraphs nearly identical to other articles.
  2. Empty sentences: List all instances ending in "important" without next-step action.
  3. Endings: Fix places where the same sentence ending repeats 3+ times.
  4. 【To Confirm】: List these per article. Do NOT auto-correct to assertions; humans will verify.

Finally, output a table showing "Free Word Count / Total Word Count / Ratio" for each of the 5 articles.

———————

The final table lets you see the paywall position numerically, not visually.

If the free portion exceeds 40%, readers leave satisfied without buying.

Is it within 20-30%?

Check this every time.

This completes the first cycle.

Inventory: 5 articles.

The Real Reason You Stall at Article 20

Four weeks yields 20 articles.

Returning to the opening story: Article 1 and Article 20 had identical quality.

The reason is simple:

Sales data was never fed back into the system.

With 20 articles, clear winners and losers emerge.

There must be a reason. Maybe topic selection, maybe paywall placement.

That info exists in the note dashboard.

But it's not in CLAUDE.md.

So Article 21 is written with the same instructions as Article 1.

This is where automation breaks.

The system isn't flawed; it has an exit but no entry.

Remember the multiplication formula's right side?

Purchases per person didn't rise with volume.

The material to raise them exists only within selling articles.

Thus, one department is missing.

Fifth Department | HR Returns Results to Employee Handbook

The task is simple: feed sales data to AI and have it update CLAUDE.md.

One prep step:

Export a list of sales per article from the note dashboard and drop it in the folder.

Filename can be sales.csv or sales.txt.

As long as article names and purchase counts are listed, it's enough.

Then, run this once a month.

———————

【Copy-Paste Prompt】

Read the sales data and all article bodies in the folder.

【1. Classification】

List the top 3 and bottom 3 articles by purchase count.

【2. Gap Analysis】

Compare top vs. bottom on these 6 points:

• Theme type (Procedure/Form/Application/Setting)

• Specificity of reader's pain point

• Free portion word count ratio

• Presence of specific procedure names in paid headings

• Number of steps

• Presence of links to next articles at the end

Report only differences verified in actual text, not guesses.

If no difference found, state "No Difference."

【3. Update Employee Handbook】

From the differences found in #2, append ONLY those reproducible in the next article to the 【Trends of Selling Articles】 section in CLAUDE.md.

If contradictions exist with current rules, report them before rewriting.

【4. Redesign User Flow】

Add 1-2 lines linking to relevant top-performing articles at the end of the bottom 3.

Selection criteria: Not "similar articles," but "what the user will struggle with next after finishing this procedure."

Finally, report changes made to CLAUDE.md in under 3 lines.

———————

The power lies in Step 3.

By conditioning on "reproducible in the next article," you prevent vague advice like "be empathetic" from cluttering the handbook.

Step 4 addresses the right side of the multiplication.

Send traffic from non-selling articles to selling ones.

For readers, their next hurdle is anticipated.

Running this monthly means Article 21 onward is written with different instructions.

It's no longer the same company as Article 1.

True automation begins here.

One Job You Cannot Delegate

Let's draw a clear line.

Almost all writing tasks can be delegated.

But one thing cannot.

Visually verifying items marked 【To Confirm】.

AI excels at writing procedures "plausibly."

Screen names or button positions may slightly deviate from reality.

Even for 100 yen, if a paid procedure differs from reality, that article won't be bought again.

The loss outweighs the few dozen yen profit.

That's why inspection prompts forbid auto-correcting 【To Confirm】 to assertions.

Human job: Open the list and check actual screens.

Takes minutes per article.

Another point:

Sales don't start the day after posting.

Search indexing takes time.

Initially, inventory grows while numbers stay flat.

Most quit here.

The system isn't broken; the left side of the multiplication is just still small.

Round Two Is Where It Counts

Here is the sequence:

Day 1: Create article folder, place CLAUDE.md. Rewrite "Reader" and "Prohibited" in your own words.

Day 2: Run Planning, narrow themes to 10.

Day 3: Run Writing & Inspection, produce 5 drafts.

Day 4: Visually verify 【To Confirm】 lists.

Day 5: Upload 5 articles to note, set paywalls.

Inventory: 5 articles.

Left side of multiplication = "5".

One month later, run HR Department once.

Many stop here, repeating the same week. Volume increases, but per-article metrics stagnate.

Feed reasons for success back into the employee handbook.

Company quality never exceeds handbook quality.

And the handbook doesn't grow unless it reads sales data.

For those who want to know the full picture of achieving results with side hustles alongside this article 🎁

Currently, via official LINE, for 0 yen:

"Shokupan-style AI × Fastest Affiliate Strategy: Top 5 Bonuses"

食パン - inline image

is being given away 🎁

Since this was originally planned as paid content,

distribution will close once capacity is reached.

Please grab it along with this article while you can.

▼▼▼

【▶︎▶︎▶︎Receive the 5 Bonuses】

Now, let's get to the main topic!

二次創作

使用 YouMind 創作爆款文章

收集素材、拆解爆點、生成視覺資產、撰寫內容,並在一個 AI 工作空間裡完成分發。

了解 YouMind
寫給創作者

把你的 Markdown 變成乾淨的 𝕏 文章

圖片上傳、表格、程式碼區塊,往 𝕏 上手動重排太痛苦。YouMind 把整篇 Markdown 一鍵轉成乾淨、可直接發佈的 𝕏 文章草稿。

試試 Markdown 轉 𝕏

更多可拆解樣本

近期爆款文章

探索更多爆款文章