40 lines you can use right now, no install
You can paste these lines into the Claude app, Claude on the web, or the Claude Code terminal. The /command names on the left are just labels — typing one into a chat window does nothing. In Claude Code, saving a file under ~/.claude/commands/ turns it into a real slash command. Tap a corner on the right to find skills that do it on their own.
Added daily
A few more useful lines every morning.
Clean up the data below: merge duplicate rows, make date, number and name formatting consistent, and flag any cells that are empty or look wrong. Give me the cleaned table plus a list of every change you made:
Review the UI described or coded below for accessibility issues: colour contrast, keyboard-only operation, focus order, screen reader labels and heading structure, and touch target size. List the problems from most to least severe, with a one-line fix for each:
Turn the notes below into a postmortem document with these sections: (1) one-line summary, (2) timeline of events, (3) what went well, (4) what went wrong, (5) root cause (kept separate from surface symptoms), (6) action items with owner and due-date columns. Keep it blameless — focus on systems and process, not people:
Suggest a color palette for the product/brand below. Give HEX codes for primary, secondary, accent, background, and text colors, one line of reasoning per color, and state whether each text-on-background pair passes WCAG AA contrast. Include a dark-mode variant too:
Turn the commit list and changes below into user-facing release notes. Group them under 'New / Improved / Fixed / Heads-up', keep each item to one plain-English line, and end with a one-sentence summary of this release:
Write the UI copy for the screen described below: button labels, helper text, error messages, and empty-state text. Give 3 options for each in three tones (concise, friendly, formal) and show the character count. Here's the screen:
Turn the requirements below into user stories my dev team can ticket right away. Split them into "As a <role>, I want <goal> so that <benefit>" statements, and give each one 3-5 testable acceptance criteria plus any edge cases people usually forget. Requirements:
Read the code or endpoint details below and write an API reference document. For each endpoint, cover the method and path, request parameters (type, required or not, description), a request example, a successful response example, and common error codes with their meanings, using tables and code blocks. Don't guess at anything you can't infer — mark it as "needs confirmation":
Build a budget for the goal and constraints below. Lay out estimated costs line by line in a table (item, unit cost, quantity, subtotal, basis for the estimate), then show the total and a contingency amount separately. Point out which lines could be trimmed, which shouldn't be, and any cost items I've likely forgotten:
Design a survey for the goal below. Keep it to about 10 questions mixing scale, multiple-choice and open-ended items, and avoid leading or double-barreled questions. Next to each question, note in one line what it measures, then suggest how to analyze the responses. Survey goal and target respondents:
Give me the terminal command for the task below. Start with one ready-to-run command, then explain what each flag does and how to preview it safely or undo it if I run it by mistake. My environment (OS/shell) and what I want to do:
Turn the notes below into a handover document someone can pick up on day one. Organize it as: responsibilities / current status / where files and accounts live / recurring deadlines / gotchas / who to ask. Mix short tables with bullets, and list anything still missing under "Needs confirmation" at the end. Notes:
Write alt text for the image below. One sentence, under 125 characters, focused on what a screen reader user needs for context — don't start with "image of" or "photo of". If it's purely decorative and alt should be empty, say so instead. Image or description:
Write a reply that politely declines the request below. Open with genuine thanks, give the reason in one short sentence, and close by offering an alternative or a future opening. Keep it to 5-7 sentences so it doesn't read like an excuse:
Below is my from-memory explanation of something I just learned. Read it and respond in three parts: 1) what I got right, 2) what's wrong or muddled, with the correct version, 3) key concepts I left out entirely and should study next. End with a one-line verdict on how well I understand it:
Act as my interviewer. Based on the role and my background below, ask one question at a time; after each of my answers, give brief feedback on what worked, what didn't, and a stronger sample answer, then move on. Ask 7 questions total, getting harder as we go:
Write a GitHub README.md in Markdown for the project described below: one-line intro, key features, installation, usage examples with code blocks, environment variables, folder structure, and license. Mark anything you don't have enough info for with [ ]:
Suggest the 3 best chart types for the data below. For each one, explain what message it highlights and how to set the axes, sorting, and colors, then pick your top recommendation. Data:
Write a one-page cover letter based on the job posting and my background below. Tie each requirement in the posting to a real experience of mine with specific numbers and examples, and skip generic filler phrases. Posting and background:
Using the table structure below, write a SQL query that returns exactly what I describe. After the query, explain each clause in one line and flag anything that could get slow on large data. Table structure and desired result:
Build a week-by-week study plan that gets me to the goal below within the time I have. Give it as a table with what to cover each week, which resources to use, when to review, and how to test whether it actually stuck. End with the most common reasons this kind of plan fails. My goal and the time I can spend per day:
Sort the task list below by importance and urgency into four groups: ① do now ② schedule for later ③ delegate ④ drop. Add one short line explaining why each task landed in that group, then pick the 3 things I should start with today:
Walk me through the code below in the order it actually executes. For each function, say what it takes in and what it returns, and point out where the data gets transformed. Flag anything a first-time reader would likely misread, then close with a 3–4 line summary of the overall structure:
Read the content below and pull out the 8 questions readers are most likely to ask, then write them up as a FAQ (question - answer). Keep each answer to 2-3 sentences based only on what's actually in the text, and mark anything the text doesn't cover as "needs confirmation":
Write unit tests for the code below. Group them into happy path, edge cases, and error handling, and add a one-line comment saying what each test verifies. Pick a test framework that fits the code, and flag anything that's hard to test along with why:
Write a Conventional Commits style message for the changes below: a summary line under 50 characters, then 2-3 lines explaining why. If these changes should be split into separate commits, suggest how:
Build an agenda for the meeting described below. For each item give a time box, the decision that must be made, and who needs to be in the room. Flag any items that can be dropped if we run short on time:
Turn the content below into a presentation deck. For each slide give me a title, at most 3 bullet points, and a short speaker script. Aim for about 8 slides:
Write a decision memo for the situation below. Cover: what needs to be decided, each option with its rationale and cost, whether the decision is reversible, your recommendation and why, and a deadline if I delay. Here's the situation:
Turn the content below into a clean comparison table. Choose sensible column headers yourself and put '-' where information is missing. After the table, add 2-3 lines pointing out the key differences:
Come up with 10 name options for the following. Give a one-line rationale for each and flag any awkward pronunciations or connotations. At the end, pick your top 3 and explain why:
Write a regular expression for the requirement below. Break the pattern into parts and explain what each part does, then list sample strings that match and strings that don't. Here's what I need to match:
Using the goal and deadline below, build a backwards timeline starting from the due date. Give me a table with the main phases, how long each one needs, and the date each must be finished by, and flag the steps most likely to slip. Here are the details:
Write an Excel/Google Sheets formula for the calculation I need. Give me one ready-to-paste formula, a breakdown of what each part does, and how to handle blank cells or error values. Here are my columns and the result I want:
Pull out every technical term and acronym in the text below and turn them into a glossary. Format each entry as: term — one plain-English definition — what it means in this specific text, with the most important ones first. Text:
Draft a reply to the email below. First sum up in one line what the sender is actually asking for, then give me a complete, ready-to-send reply in two versions: one formal, one short and friendly. At the end, flag anything I need to confirm or any missing information. Email:
Translate the text below into natural, native-sounding English (or another language if I name one). Don't translate word for word — rewrite it the way a native speaker would say it, while keeping the original tone and level of formality. Where the meaning could go more than one way, list the alternatives underneath. Text:
Turn the raw meeting notes below into clean minutes. Split them into Decisions, Open Issues, and Action Items (with owner and due date), and flag anything unclear as "needs confirmation":
Here's an error message and the related code. Explain in plain language what's causing it, list the most likely fixes in order of probability, then show the corrected code:
Explain blockchain simply enough for a ten-year-old
Summarize the text below in three lines, key points only:
Make the strongest possible case for a four-day work week
Push back hard on my claim that remote work is always better
Lay out the pros and cons of iPhone vs Galaxy in one table
Walk me through starting a YouTube channel, step by step
Make a packing checklist for an overseas trip, including easy-to-forget items
Give me a business proposal email template I can fill in
Give me three concrete examples of a 'hook' in marketing
Explain how a rate hike affects the economy using an everyday analogy
Tell me honestly where the following is weak:
Make this Instagram caption more compelling, with specific edits:
Cut the length of this passage sharply without losing meaning:
Expand this note on 'why exercise matters' into a full piece
Rewrite this contract clause in plain language:
Rewrite this refund notice in a friendlier tone:
Throw out ten content ideas for a cafe's Instagram
Draft the outline for onboarding training material first
Find counterexamples to the claim that pricier always means better
Point out the hidden assumptions in 'just cut the price and it sells'
I'm evaluating a startup idea — ask me the questions I should be asking
Compare Notion, Obsidian and Evernote in a table by criteria
Lay out the risks and mitigations for running my first offline event
Answer as a marketer with ten years' experience would about this copy:
Revenue keeps falling — ask 'why' five times to find the root cause
Rewrite this email in a formal, courteous register:
Mark the claims in this text that need fact-checking:
I want to start a blog — put the immediate actions in priority order
This sentence reads awkwardly — rewrite it naturally:
Turn these meeting notes into key bullet points:
I want to launch an online course — turn it into an executable plan
Give me five opening lines that force people to keep reading about dieting
Polish this blog post so it reads like a person wrote it, not an AI:
Fix only the spelling, typos and grammar below — leave the content as is:
Write our product launch as one punchy sentence
Score the following out of ten and explain the score:
Rewrite this so my 70-year-old parents would understand it:
Explain compound interest through a story and real examples
Turn this material into question-and-answer flashcards:
I want to ask for a raise — script what I should say