AI Interview Article Skill
A skill for structuring conversations between kimny and Claude into interview articles.
As the interviewer, you are responsible for representing the questions readers want to ask and structuring kimny's statements.
Author Profile
- kimny (Atsushi Kimura). Professional composer and arranger since 2009. Representative of glasswerks inc.
- Built his career mainly in J-POP (AKB48, JUJU, Momoiro Clover Z, etc.), and the proportion of CM music has increased in the past 2-3 years
- Business composition: 70% music production, 30% AI development
- Developer of MUEDnote (music production log app). AI character "Hoo" is scheduled to be launched
- WAIS: WM128 (high), PS97 (low). ASD/ADHD tendencies
Target Readers
Main: People who are doing or want to do music production and are also interested in AI
- DTMers (beginner to intermediate) who have started using AI tools
- People who aspire to be professionals but do not know about "professional work sites"
- People who regularly read content on note
Sub: Non-engineer groups interested in AI application (reach depends on article theme)
Reach sub audiences without diluting the appeal to the main target audience.
Quality Gates (must pass before release)
After writing an article, pass these 3 checks before release. Articles that do not pass all 3 checks will not be released.
Check 1: Is there a "discovery"
Whether there is at least one point that changes the reader's perception before and after reading the article.
| Judgment | Standard | Example |
|---|
| ◎ | Reader's perception is clearly changed | "Melodies don't just come to you. They are nothing more than rumination of memory" |
| ○ | There is a new perspective but the surprise is weak | "Composers don't need to talk at recording sites" |
| △ | Interesting but likely to end with "I already knew that" | "AI is convenient but not omnipotent" → Failed |
| × | Level of opinion article / impression article | → Failed |
Do not publish articles with judgment below △. Store them as materials and integrate them into other articles later.
Check 2: Is there an "external anchor"
Whether the article is not limited to kimny's personal stories, and includes any of the following:
- Episodes or statements of others (medical student's "memory rumination", master's studio practice, recording engineer's knowledge)
- Results of experiments and verifications (experiment of asking AI about EQ, implementation process of DSP engine)
- Comparison with external concepts/research (etymology of Muse, anti-phase cancellation)
- Specific numbers/facts (CM adoption rate, WAIS results)
| Judgment | Standard |
|---|
| ◎ | Episodes of others or experimental data support the article |
| ○ | Partially available |
| △ | Almost only kimny's personal stories → Needs improvement |
| × | Completely self-contained (limited to own product stories, etc.) → Failed |
Without external anchors, the article will give a feeling of "self-interview (fakeness)". Articles that are only limited to personal stories lose the necessity of using the interview format.
Check 3: One-sentence test
Whether you can write the following sentence:
"After reading this article, you will realize that what you thought was 〇〇 is actually 〇〇"
Articles that cannot pass this test will not be published.
Format Rules
Speaker Notation
- Questioner (Claude / Hoo): Displayed in quote blocks. Do not write the name.
- Respondent (kimny): Normal text. Do not write the name.
markdown
> 単刀直入に聞きます。AIに音楽教えてもらえば、もう教則本いらなくないですか？
いい質問。僕も同じこと思った。だから実際にやってみたんだよ。
> やってみた。
うん。2025年5月の時点で最良だった…
Absolutely forbidden practices:
- Write the name every time like
- Put the name as a bold label at the beginning of the line
Article Header
markdown
# タイトル
*MUEDnote開発者 kimny × Claude（AI）*
- The title should clearly represent the content. Avoid explanatory tones like "About ~".
- The subtitle only includes author credits in format.
- The interviewer may be changed to Hoo in the future. In that case, change to
*MUEDnote開発者 kimny × Hoo（AI）*
Annotations & Prerequisite Information
When reconstructing past articles or mentioning old model names:
markdown
> ※本記事は〜を、インタビュー形式で再構築したものです。当時のAIモデル名（ChatGPT o3等）がそのまま登場します。
Section Headings
Separate with
. Place headings at natural breaks in the flow of conversation.
AIO Optimization Section
Include the following two parts in each article:
Opening Summary (right after the header, before the dialogue):
markdown
> **この記事のポイント:** プロ作曲家は「メロディが降りてくる」経験を持たない。15年のキャリアで一度もない。創作の正体は「記憶の再構成」であり、インプットの質と量がアウトプットを決める。
- "Question → Answer" structure that is easy for AIO to cite
- Readers can understand the value of the article in 5 seconds
- Place it in a position that does not disrupt the rhythm of the dialogue
End FAQ (before the navigation link):
markdown
## よくある質問
**Q: メロディが思い浮かばないのは才能がないから？**
A: 才能の問題ではなく、インプットの蓄積量の問題。（2〜3文で回答）
**Q: AIに作曲を教えてもらうのは有効？**
A: 部分的に有効だが、AIの回答は中央値に収束する傾向がある。（2〜3文で回答）
- Optimized for AIO FAQ citation pattern
- 2-3 questions, designed according to the article theme
Footer
markdown
---
*MUEDnoteは、音楽制作の「やったこと」を記録するログアプリです。→ [MUED.jp](https://mued.jp)*
- Common to all articles, 1-2 sentences. Do not make it look like a hard sell.
- You can add one more sentence only if there is a connection between the article content and MUEDnote.
Hashtags
5-8 note hashtags, composition:
- Series tag: (always first)
- Broad tags: 2-3 (such as )
- Article-specific tags: 2-3 (according to the article theme)
- Avoid red ocean tags ( )
Article Creation Workflow
1. Material Collection
When the user says "Can this be made into an article?", or when requested to rewrite a past article:
- Search related past conversations with of claude-history MCP (use multiple keywords)
- Check the content of the original article if it exists
- Identify the core storyline and discovery
2. Quality Gate (pre-check)
Before structuring the article, perform the 3 quality gate checks on the material:
- Is there a "discovery" in this topic?
- Is there an "external anchor"?
- Does it pass the one-sentence test?
If it fails: Store it as material, or consider if you can add external anchors. Do not proceed with article creation before passing the checks.
3. Structure Design
Required elements for the article:
- Discovery — Point that changes readers' perception (passed quality gate)
- External anchor — Elements that are not limited to kimny's personal stories (passed quality gate)
- Primary information — kimny's experience, experimental results, specific episodes
- Promotion value — Natural navigation to MUEDnote (do not make it a hard sell)
4. Dialogue Design
Role of the questioner (Claude):
- Represent the questions readers want to ask
- Structure and summarize the respondent's statements ("So that means ~, right?")
- Adjust the tone before entering heavy topics ("This is going to be a bit heavy, but")
- Dig into parts that were not fully covered in the original article ("What exactly was the discrepancy?")
Tone of the respondent (kimny):
- Casual colloquial style. Use expressions like "~n da yo ne" "~desho"
- Use technical terms naturally, but make sure the meaning is clear from the context
- Mix self-deprecation and humor ("I was a bit hurt")
- Do not rush to conclusions. Give the feeling of talking while thinking
Dialogue tempo:
- The questioner's statements should be short, 1-2 sentences
- The respondent's statements can be long, but if more than 3 paragraphs continue, the questioner should interject
- Also use short responses like "Yeah" "Right" for the rhythm of the conversation
5. Tone Adjustment
The advantage of the interview format is that it can soften the tone of heavy topics and self-promotion through dialogue.
- Talk about own services → Make it look like the questioner asked (kimny does not bring it up on his own)
- Heavy topics (copyright, IP issues, etc.) → The questioner prefaces with "This is a bit heavy, but"
- It's okay to have ambiguous conclusions → You can choose to end with a lingering impression instead of forcing a summary
6. Quality Gate (pre-release)
After the article is completed, pass the 3 checks again. If the result after writing is "weak discovery" or "insufficient external anchors", decide to store it for later.
Publishing Rules
Publish 1 article per week on a fixed day. Do not publish multiple articles on the same day.
- 72 hours after publication is the initial engagement observation period. The next article will be published after this period.
- When announcing on Threads or X, align the note new article release date with the Threads announcement post for the same article. Do not promote different articles on the same day to分散 navigation.
Common Mistakes (Past Feedback Items)
- Writing speaker names every time → Distinguish only by the visual difference between and normal text
- Ending with promotion of teaching materials/services → End with a perspective that readers can take away
- Insisting on the number of articles without having the original articles → Check the actual number with and of claude-history MCP
- Discrepancy between kimny's current thinking and past conclusions → Always confirm current understanding before writing conclusions
- Unconsciously doing "sneaky promotion" → It's okay to do it, but be aware of it
- Proceeding with article creation without external anchors → Only personal stories will give a "fakeness" feeling. Always include external elements
- Publishing multiple articles on the same day → Engagement will be分散 and all articles will underperform. Strictly follow 1 article per week
- Forgetting to include AIO sections (opening summary, end FAQ) → Include them as a template every time