"I typed 'make it look good,' and what came back wasn't good at all... 💢"
It's not the AI's fault; it's your "way of giving instructions."
Have you ever experienced this while using AI?
- Realized you can only say "make it better"
- Thought of prompts from scratch every time, only to get generic replies
- Created Skills but found accuracy dropped when you wrote everything in SKILL.md
- Paying for AI tools but not confident you're getting a return on investment
By reading this article to the end, you will gain 40 professional-grade prompts selected from 500 tests, along with design principles for structuring Claude Code Skills reference documents to increase accuracy.
An article published by angel investor Mr. Khairallah is currently going viral with 3 million views.
Before we start, I have two requests:
- Save this article and set aside 20 minutes this week.
- Share it with colleagues or friends who use AI.
This time, I will break down the content into easy-to-understand Japanese and explain "why this structure improves quality" and "how to apply this structure to Claude Code Skills reference document design."
Original post here:
https://x.com/eng_khairallah1/status/2048334883198738761
Output is Completely Different Between One-Line Prompts and Structured Prompts

Khairallah says:
"Most prompt collections are generic. 'Write a blog post,' 'Summarize this text,' 'Explain this concept.' These are not prompts. They are wishes."
When you actually try it, the difference is clear.
For example, if you only enter "Write a blog post," the AI returns harmless generalities. The structure is vague, and it's not uncommon to spend 30 minutes fixing it.
On the other hand, using the P01 prompt introduced in this article specifies the audience, angle, structure, and rules, so the AI outputs a specific and practical article in one go. It's at a level that can be used as-is without editing.
Same AI. Same theme. The only difference is the structure of the prompt.
So, what goes into a professional-quality prompt? Let's look at the 6 elements common to all 40 prompts.
6 Elements of Prompt Design Common to All 40 Prompts

Khairallah tested over 500 prompts and kept 40. These 40 share six common components.
Most prompt failures are caused by missing one of these six.
■ 1. Role
This element tells the AI, "You are an expert in XX."
Look at P01. It starts by specifying, "You are a senior content strategist with experience writing for top-tier media." Without a role, the AI answers as a "jack-of-all-trades." With a role, it answers from that expert's perspective.
■ 2. Context
This element provides the situation, background, and constraints.
In the P12 decision matrix, it asks for "budget, timeline, team structure, and goals" as input. If the context is thin, the AI can only return generalities. The more it knows about your situation, the more the AI's response becomes tailored to you.
■ 3. Constraints
This element clarifies what NOT to do.
In P01, it specifically lists prohibitions like "No filler expressions," "No hedge words," and "Max 3 sentences per paragraph." Without constraints, AI tends to play it safe and become redundant. Sharp output only appears when it's told "don't do this."
■ 4. Format
This element specifies the structure of the output.
In the P11 SWOT analysis, it specifies the output structure in detail: "5 items per quadrant → Impact assessment → Strategic priorities → Actions for this week." If you don't specify the format, the AI decides the structure on its own, which may not always be what you want.
■ 5. Quality Standards
This element shows the line for "redo if it doesn't reach this level."
The line at the end of P01, "This article must be at a level that can be published as-is without editing," is exactly this. When you communicate quality standards, the AI adjusts its own output against those standards before returning it.
■ 6. Concrete Examples
This element shows samples or variations of the desired output.
In the P03 email creation, it requests two patterns: "Version A: Straight and assertive / Version B: Warm and collaborative." By showing examples, the AI understands what you consider "good output."
These 6 Elements Can Be Used Directly in Skills Reference Documents

Let's look at these 6 elements from another angle.
Claude Code has a mechanism called "Skills." It allows you to name frequently used work patterns and call them with a single command.
For example, typing /write-article writes an article. Typing /weekly-plan creates a weekly plan. You no longer need to rewrite the prompt from scratch every time.
If you want to study Claude Code Skills, check the following as well ⇩

UTokyo ClaudeCode Lab
@ClaudeCode_UT
·

Article
[90% Don't Know] "20 Skills to Give AI Expertise" Saved by 20,000 People
"How many times do I have to explain the same thing to the AI... !😩"
"I taught it so much yesterday, why is it back to zero today..."
This isn't the AI's fault; it's your own "way of teaching AI."...
4
109
1.1K
The structure of the "reference documents" determines the output quality of these Skills.
A common failure pattern is stuffing rules, examples, and background information all into one file called SKILL.md. While understandable, this gives the AI too much information to process at once, dropping accuracy.
The correct way is to split information into files by purpose and only load the necessary files when needed.
Anthropic's official Skills template also recommends this separation structure.
1skill-name/2 SKILL.md → Always loaded. Role and basic rules only (recommended under 500 lines)3 references/ → Loaded depending on the task. Knowledge, constraints, quality standards4 scripts/ → Executable code. Repetitive processing or data conversion5 assets/ → Output templates or icons
Only the name and description of SKILL.md are loaded initially. Keep SKILL.md thin and separate detailed information into references/ with links. This is the officially recommended design.
And how to structure the content of the reference files? You can use the 6 elements from earlier directly.
■ Role → Define "You are XX" in SKILL.md
■ Context → Place company/reader info in audience.md or company-context.md
■ Constraints → Consolidate "what not to do" in writing-rules.md or risk-criteria.md
■ Format → Define output structure in format-templates.md
■ Quality Standards → Specify pass/fail criteria in quality-checklist.md
■ Concrete Examples → Accumulate past success stories in good-examples.md
From here on, please read the category-specific prompts from two perspectives.
First, as "prompts you can copy and paste directly." Second, as "patterns for designing Skills reference documents."
At the end of each category, I've included a specific example of what it looks like to turn those prompts into Skills reference documents.
Now, here are all 40 prompts in 6 categories.
Note: For the technical series P21-28, only titles are introduced as they are for engineers.
Writing & Content Creation (10 Prompts)

All 10 prompts in this category incorporate "Role" and "Quality Standards." By making the AI act as an expert and telling it the standard it must reach, the AI's output changes from a "draft" to a "finished product ready for use."
Writing prompts can be applied not only to articles and emails but also to daily business reports and presentation materials.
■ 01. Expert Article Writer
For writing blog or note articles. The key is to decide the angle and structure first.
1You are a senior content strategist with experience writing for top-tier media.23Write an article of [word count] characters about [topic].45Audience: [Audience attributes and knowledge level]6Angle: [Your unique perspective. Differentiation points from other articles on the same theme]78Structure:9- Hook: Start with a bold claim or surprising fact. No generic introductions.10- Problem Statement: Why the common view on this topic is wrong or incomplete.11- Framework: Develop the argument into 3-5 sections. Clear headings for each.12- Evidence: At least one specific example, case study, or data point per section.13- Action: End with 3 specific actions the reader can take "this week."1415Rules:16- Max 3 sentences per paragraph.17- No filler expressions ("What's important is," "In today's world," etc.).18- No hedge words ("might," "perhaps," "seems like," etc.).19- All claims must be specific. No ambiguity.20- Bold the most important sentence in each section.2122This article must be at a level that can be published as-is without editing.
■ 02. Thread Design
For writing X (Twitter) threads. A configuration designed from hook to closing.
1Write an X thread about [topic].23Thread Structure:4- Tweet 1: Hook. Bold claim, surprising statistic, or contrarian view. Stop the scroll in 2 seconds.5- Tweets 2-3: Problem statement. Why many people get this wrong.6- Tweets 4-10: Framework. Numbered steps, techniques, or insights. One per tweet. Each tweet should stand alone but flow as a whole.7- Tweets 11-12: Real-world examples or case studies where the framework works.8- Final Tweet: 1 specific action + Call to Action.910Rules:11- Max 280 characters per tweet.12- No meaningless emojis.13- No preambles like "To explain a bit" or "The point is." Start each tweet with the content.14- Feel like learning from a sharp friend, not a textbook.1516Total: 12-15 tweets.
■ 03. Email Creation
1Write an email for this situation: [Describe situation, recipient, and purpose in detail]23Tone: [Professional/Casual/Straight/Diplomatic]45Rules:6- Subject Line: Specific and action-oriented (No "Quick question" or "Follow-up").7- Opening: Get to the point in the first sentence. No pleasantries needed.8- Body: Max 3 short paragraphs. Each paragraph has only one role.9- Closing: Clear next action or request. Don't let the recipient wonder what to do.10- Overall: Under 150 words.1112Create 2 versions:13Version A: [Tone 1. e.g., Straight and assertive]14Version B: [Tone 2. e.g., Warm and collaborative]

■ 04. Content Expansion
When you want to expand one article into 5 formats (SNS, newsletter, video, etc.).
1Expand this content into 5 formats.23<Original Content>4[Paste article, post, transcript, etc.]5</Original Content>67To Create:81. X Thread (12 tweets, max 280 chars each)92. LinkedIn Post (200-300 words, professional but not too stiff)103. Newsletter Intro (100 words, teaser for the full text)114. 3 SNS Posts (each independent, highlighting different insights)125. Short Video Script (60 seconds, conversational, intended for talking to camera)1314Rules:15- Each format must feel natural to its platform. No copy-paste feel.16- Maintain core claims and key insights across all formats.17- Adjust tone by platform: X = punchy and straight, LinkedIn = professional and thoughtful, Newsletter = personal and exclusive.
■ 05. Copywriting Transformation
When you want to turn your text into professional copy. Includes explanations of changes.
1Rewrite this text into more persuasive copy.23<Original Text>4[Paste text]5</Original Text>67Apply these copywriting principles:8- Lead with benefits, not features.9- Use specific numbers instead of vague expressions.10- Anticipate and address objections before they arise.11- Create urgency without being manipulative.12- End with a clear, low-hurdle call to action.1314After showing the rewritten version, explain the 3 most impactful changes and why they work psychologically.
■ 06. Blog Post Outline Design
When you want to solidify the structure before writing.
1Create a detailed outline for a blog post about [topic].23Target Audience: [Who]4Goal: [What the reader should be able to do after reading]5Target Word Count: [Word count]67For each section:8- Heading (Attractive and specific. Not generic)9- 2-3 sentence summary10- Data points, examples, or arguments needed for this section11- Transition to the next section1213Also include:14- 3 alternative heading ideas (ranked by predicted CTR)15- Meta description (max 160 characters)16- 5 internal/external link candidates

■ 07. Storytelling Transformation
When you want to turn data or facts into a narrative. Also for presentation or report intros.
1Transform this dry factual information into a compelling narrative.23<Facts>4[Paste facts, data, or technical content]5</Facts>67Rules:8- Don't start with definitions; start with a specific scene, person, or moment.9- Weave facts into a story arc: Setup → Tension → Resolution.10- Use analogies to make complex concepts intuitive.11- Include one "Aha!" moment that changes the reader's understanding.12- End with a takeaway linked to the reader's life.1314Facts remain accurate. Change the delivery, not the content.
■ 08. Headline Generator
When struggling with titles or headings.
1Create 20 headline ideas for this content: [Content summary]23Categories:4- Curiosity-driven: 5 (impossible not to click)5- Benefit-driven: 5 (value clear at a glance)6- Contrarian: 5 (shakes the reader's common sense)7- Number-driven: 5 (uses specific quantities or periods)89For each headline:10- Rate predicted CTR from 1-10 and explain why.1112Rank the overall TOP 3 with reasons.

■ 09. Case Study Creation
For creating implementation or success stories.
1Summarize the following facts into a case study.23Client: [Name/Industry]4Challenge: [What they were struggling with]5Solution: [What was implemented]6Results: [Measurable outcomes]78Structure:91. Challenge (2 paragraphs. Make the reader feel the pain)102. Approach (3-4 paragraphs. Specific steps. No generalities)113. Results (1-2 paragraphs. Specific numbers, Before/After comparison)124. Lesson (1 paragraph. Learning applicable to the reader)135. Pull Quote (One sentence the client would actually say based on results)1415Rules:16- Use present tense for a sense of realism.17- Include at least 3 specific numbers.18- Pull quotes should be real words, not marketing copy.
■ 10. Style Replication
When you want to write in a specific style. Extracts patterns from 3 samples.
1Analyze 3 writing samples by the same author.23<Sample 1>[Paste]</Sample 1>4<Sample 2>[Paste]</Sample 2>5<Sample 3>[Paste]</Sample 3>67Identify:8- Sentence length patterns (Short/Mixed/Long)9- Vocabulary level (Simple/Technical/Mixed)10- Tone (Formal/Casual/Authoritative/Conversational)11- Structural quirks (Paragraph length, heading use, bullet point patterns)12- Repeated phrases or patterns13- Things consistently avoided1415After analysis, write a 300-word piece about [New Topic] perfectly replicating this author's style. It must be believable as written by the original author.
★ Turning this category into Skills reference documents...

The writing prompts P01-P10 are particularly rich in "Constraints" and "Quality Standards." These can be directly transferred to Skills reference documents.
1.claude/skills/content-writer/2 SKILL.md ← Role definition only3 references/4 writing-rules.md ← Constraints. No fillers, max 3 sentences per paragraph5 audience.md ← Context. Reader attributes and knowledge level6 format-templates.md ← Format. Structure for articles, emails, threads7 quality-checklist.md ← Quality Standards. Conditions for publication level
The content of writing-rules.md would look like this:
1## Constraints2- Max 3 sentences per paragraph.3- No filler expressions ("What's important is," "In today's world," etc.).4- No hedge words ("might," "perhaps," etc.).5- Claims must be specific. No ambiguity.67## Quality Standards8- Must be at a level that can be published as-is without editing.9- Bold the most important sentence in each section.
The "Rules" and "Quality Standards" from the P01 prompt become the content of the reference file. By writing only the role in SKILL.md and separating detailed rules into reference files, the same quality is maintained whether you're writing an article or an email.
Analysis & Strategy (10 Prompts)

Why do some AI analysis requests yield useful answers while others don't?
The answer is simple. In these prompts, "Context" and "Format" are thoroughly specified. The P12 decision matrix asks for budget, timeline, team, and goals, and forces the output into a "5 criteria x weighting x score" table format. The higher the resolution of the context, the more the AI avoids generalities and provides answers suited to your situation.
■ 11. SWOT Analysis
For organizing strategies for new businesses or projects. Includes priority ranking by impact.
1Perform a comprehensive SWOT analysis for [Company/Product/Strategy].23For each quadrant (Strengths, Weaknesses, Opportunities, Threats):4- List 5 specific items (not generalities, specific to this situation).5- Each item: 1-sentence explanation of why it fits this quadrant.6- Impact of each item: High/Medium/Low.78Additionally:9- #1 Strategic priority based on this analysis (1 sentence).10- Maximum risk if this priority is ignored (1 sentence).11- First action to take this week (1 specific, actionable step).
■ 12. Decision Matrix
1Need to decide between these options: [List 2-4 options]23Background: [Budget, timeline, team structure, goals]45Create a decision matrix:61. Identify the 5 most important criteria for this decision (ask if unclear).72. Weight each criterion by importance (total 100%).83. Score each option against each criterion from 1-10.94. Calculate weighted scores.105. Present in a formatted table.1112Then, a 2-paragraph recommendation:13- Clearly state which option to choose and why.14- Acknowledge the strongest argument for the runner-up.15- Identify one condition that would change the recommendation.
■ 13. Root Cause Analysis
To find the real cause of a problem. Digs from surface to root using "5 Whys."
1Problem faced: [Describe problem and symptoms]23Perform a root cause analysis:41. Dig deeper with "Why?" 5 consecutive times (5 Whys). Each time to a deeper layer.52. At each level, identify if it's a symptom or a root cause.63. At the deepest level, identify the true root cause.74. Propose 3 solutions: one for the surface symptom, one for the intermediate cause, and one for the root cause.85. Recommend which solution to execute and why.910Do not take my initial problem definition at face value. The real problem is often different from what I described.

■ 14. Market Opportunity Analysis
To assess the potential of a new idea.
1Analyze the market opportunity for [Product/Service Idea].23Evaluation Items:41. Demand: Who wants it? How many? Evidence of demand?52. Competition: Who else provides it? At what price? Where are they weak?63. Timing: Why now? Why was it impossible before but possible now?74. Barriers to Entry: What prevents competitors from copying in 6 months?85. Unit Economics: Cost to provide per customer vs. billable amount.910Each section: Be as specific as possible with numbers. Clearly state uncertainties.1112Finally, provide a GO / Cautious GO / NO GO judgment with confidence level (High/Medium/Low).
■ 15. Meeting Strategy
Before important sales calls or client meetings. Prepare even for expected Q&A.
1I have a meeting about [Topic] with [Person. Role, relationship, what they value].23Goal for this meeting: [What you want to achieve]45Preparation:61. Opening statement (2 sentences. Set the right frame for the conversation).72. 3 key points that must be conveyed (in order of priority).83. 3 questions to ask (in order of importance).94. 3 expected objections and responses to each.105. Ideal closing (summarize agreement and next actions).116. Walk-away line: What is the minimum acceptable result?
■ 16. Pricing Design
When deciding prices for products or services. Includes 3-tier configuration and psychological basis.
1Help me design pricing for [Product/Service].23Background:4- What it does: [Description]5- Who it's for: [Target customer]6- Cost to provide: [Cost]7- Competitor pricing: [If known]8- Value provided: [What the customer gets. Time saved, revenue increase, problem solved]910Design the pricing structure:111. 3 Tiers (Entry/Main/Premium). Names reflecting value, not size.122. What's included in each tier and the reason for the boundaries.133. Psychological basis for each price point.144. Which tier most customers should land on and how to guide them there.155. Analysis of One-time vs. Subscription. Which is appropriate and why?1617Present in a formatted comparison table.
■ 17. Competitor Analysis
To find competitor weaknesses. Strips them bare across 5 axes and finds differentiation points.
1Perform a competitor analysis of [Competitor Name/URL].23Analysis:41. Positioning: What is the core message? Who is the target? What emotion are they selling?52. Product: What do they actually provide? Distinction between core features and added value.63. Pricing: How do they charge? Content of each tier? Where is the profit margin?74. Content: What topics do they post? Frequency? Most reactive format?85. Weaknesses: Where are they vulnerable? What are customers dissatisfied with? What are they NOT doing?910Finally: End with "3 things I would do differently if competing directly with [Competitor Name]."
■ 18. OKR Design
For setting structural goals for teams or individuals.
1Create OKRs for [Team/Individual/Company] for [Period].23Background: [Current status. Where you are, where you want to be, available resources]45For each Objective (propose 3):6- Objective: Ambitious but achievable. Qualitative. Inspiring.7- 3-4 Key Results: Specific, measurable, time-bound.8- For each Key Result: Current baseline, target, measurement method.9- Confidence level of achievement (1-10).1011Flag any contradictions between Key Results.
■ 19. Risk Assessment
To identify risks in advance for new measures or projects.
1I am about to execute [Measure/Decision/Project].23Perform a risk assessment:41. List the 7 most likely risks.52. For each risk:6 - Probability: High/Medium/Low7 - Impact if it occurs: High/Medium/Low8 - Early warning signs (how to notice this risk is materializing)9 - Prevention (what can be done to prevent occurrence)10 - Contingency plan (what to do if it occurs)113. Plot all risks on a 2x2 matrix (Probability vs. Impact).124. Identify TOP 3 risks to monitor actively.1314Do not be optimistic. I want to hear risks I haven't thought of, not "it'll be fine."

■ 20. Retrospective Facilitator
For structured project retrospectives.
1Facilitate a retrospective for this project/period: [Explain what happened]23Structure:41. What went well (5 specific items with evidence).52. What didn't go well (5 specific items with root causes).63. Lessons learned (3 lessons that will change how we work in the future).74. What to change next (3 specific, actionable changes. No vague intentions).85. What to stop (2 things to intentionally stop doing).910Rules:11- Be specific. "Communication was bad" is meaningless. "The product team wasn't told about the price change until 2 days before launch, forcing a rush on marketing materials" is meaningful.12- Include specific preventive actions for all identified problems.
★ Turning this category into Skills reference documents...

Analysis and strategy prompts have particularly precise "Format" specifications. Saving these formats as reference files allows you to call the same analysis framework repeatedly.
1.claude/skills/decision-support/2 SKILL.md ← Role. "Business Analyst"3 references/4 frameworks.md ← Format. Templates for SWOT/Decision Matrix/5 Whys5 company-context.md ← Context. Company budget/goals/team structure6 risk-criteria.md ← Constraints. "No optimism," "State uncertainties"
The content of frameworks.md would look like this:
1## Decision Matrix21. Identify 5 criteria32. Weight each (total 100%)43. Score options 1-1054. Calculate weighted scores65. Identify one condition that would change the recommendation78## Root Cause Analysis91. Dig deeper with "Why?" 5 times102. Propose solutions at 3 levels: Surface/Intermediate/Root113. Do not take problem definitions at face value
Technical (8 Prompts - Titles Only)
P21-P28 cover code reviews, API design, etc., for engineers. See the original article for full text.
**■ 21. Architecture Advisor
■ 22. Code Review
■ 23. Debug Diagnosis
■ 24. API Design
■ 25. Database Schema Design
■ 26. Test Case Creation
■ 27. Documentation Creation
■ 28. Refactoring Plan**
Work Productivity (4 Prompts)

The P29 weekly plan prompt has a section for "Things to intentionally skip." It asks for a "not-to-do list" rather than just a to-do list. This is the core design philosophy of this category.
■ 29. Weekly Planner
For Monday mornings. Decide what "not to do" by working backward from quarterly goals.
1Quarterly Goals: [List]2Last Week's Results: [Brief summary]3This Week's Commitments: [Meetings, deadlines, obligations]45Create a weekly plan:61. TOP 3 Priorities (most important for quarterly goals).72. Schedule (meetings and deadlines by day).83. Buffer Tasks (important but flexible).94. Things to intentionally skip (what not to do this week and why).

■ 30. Learning Accelerator
1I want to learn [Topic/Skill].23Current Level: [Beginner/Intermediate/Advanced]4Available Time: [Hours per week]5Learning Style: [Practical/Theoretical/Mixed]6Goal: [What you want to be able to do after learning]78Create a learning plan:91. Prerequisites: What to know first (be honest if basics are lacking).102. Core Concepts: 5-7 key ideas to understand, in order.113. Projects: One hands-on project per concept to learn by doing.124. Resources: Only one best resource per concept (not 10 choices).135. Milestones: How to judge if a concept is truly understood (specific tests).146. Timeline: Realistic weekly plan based on available time.1516Don't pad the plan. If it can be learned in 3 weeks, don't stretch it to 8.
■ 31. Negotiation Preparation
Before salary negotiations or deals. Design everything from concession order to walk-away lines.
1Negotiating with [Who] about [What].23Background: [Relationship, history, power balance]4Ideal Outcome: [Best case]5Acceptable Outcome: [Minimum acceptable]6Predicted Opponent Position: [What they likely want]78Preparation:91. Initial position and its basis.102. 3 concessions to offer (from smallest to largest).113. 3 things to ask for in return for each concession.124. 3 likely objections and responses to each.135. 2 creative options that increase value for both (expand the pie).146. Walk-away line and specific words to exit gracefully.
■ 32. Habit Designer
When you want to start a new habit.
1I want to build this habit: [Describe habit]23Current Routine: [What a typical day looks like]4Past Attempts: [What you tried before and why it failed]56Design a habit implementation plan:71. Smallest version (2-minute starter version).82. Trigger: Which existing habit or event to attach it to.93. Environment Design: Physical changes to make the habit easier.104. Reward: Immediate positive feedback to reinforce the habit.115. Tracking Method: How to measure consistency.126. Failure Protocol: What to do if you miss a day (because you will).137. Gradual Expansion: How the 2-minute version grows over 4 weeks.1415Be realistic. A small habit that lasts is better than a perfect routine discarded in a week.
Data Analysis & Research (3 Prompts)

If you ask AI to "summarize" data, it returns a superficial summary. These prompts are different. P33 specifies the format: "State the conclusion in plain language first, then attach supporting numbers."
■ 33. Data Analysis
For sales data or survey results. Even tells you "possibilities of being misled."
1Analyze this data.23<Data>4[Paste CSV, table, numbers, survey results, etc.]5</Data>67Provide:81. Summary statistics (key numbers at a glance).92. 3 most important patterns or trends.103. 2 surprising findings not immediately visible.114. 1 aspect where this data could be misleading (common misunderstandings).125. 3 questions this data raises that require additional data.1314Audience: [Who reads this and their technical level]15State the conclusion in plain language first, then attach supporting numbers.
■ 34. Survey Analysis
■ 35. Research Synthesis
Communication (5 Prompts)

1-on-1s with bosses, feedback to subordinates, apologies to clients. In this category, the use of "Role" is unique. Instead of giving yourself a role, you have the AI assume the recipient's position.
■ 36. Preparing for Difficult Conversations
■ 37. Feedback Design

■ 38. Presentation Design
■ 39. Apology Design
■ 40. Elevator Pitch
Prompt Collections are an Entrance, Not a Destination

You now have 40 prompts. How you use them will change the results significantly.
Khairallah suggests 4 steps:
- Save them.
- Use 5 this week.
- Save the prompts that worked well.
- Expand by 2-3 each week.
As you save more prompts, you'll see the next step: managing them as "Skills" in Claude Code. Skills are definitions of reusable business patterns. Anyone who can structure their work can create them.
▼ Read this for an introduction to Claude Code Skills ▼

UTokyo ClaudeCode Lab
@ClaudeCode_UT
·

Article
[Complete Edition] Guide to Making AI Learn Your Work with Claude Code Skills
"I'm worried if I can use AI because I have zero programming knowledge..."
"The black terminal screen is scary..."
"But I'm afraid of being left behind by the AI trend !😱"
Even in that state, Claude Code...
1
87
825
Summary
- The 40 prompts are "designed instructions," not "wishes."
- Professional prompts have 6 elements: Role, Context, Constraints, Format, Quality Standards, Examples.
- These elements can be used for Claude Code Skills reference documents.
- Separate info into
references/instead of stuffingSKILL.md. - Covers 5 business categories: Writing, Thinking, Planning, Researching, Speaking.

UTokyo Claude Code Lab is an account run by a team of current UTokyo students. We share practical information for business operations. Follow us for free Skills, design patterns, and translated AI techniques.
Official LINE for limited info: https://lin.ee/quYxNMc





