Teach the tool
how you work.
Stop explaining the same task from scratch. Save a small set of instructions that captures your standards, then test it on a new example.
Smart is not the same as informed.
A model can draw on broad general knowledge. That does not mean it knows what matters in your classroom, your small business, your project, or your life. It does not know your audience, your definition of done, the things you never want it to assume, or the way you want it to speak to you.
Saved instructions guide the assistant when the app supplies them; editing a Markdown file does not itself retrain the underlying model. Supplying that context is part of the work. You provide the purpose, taste, context, and boundaries. The LLM brings speed, breadth, and detailed execution.
There are two kinds of instructions
The day-one syllabus
Standing instructions a compatible tool loads for a project or workspace: what this work is, who it serves, the stack or tools, quality standards, and non-negotiable guardrails.
Use it when the instruction should shape almost every interaction.The focused playbook
A self-contained procedure for a repeatable job: create a lesson plan, review a pull request, make a slide deck, turn a report into a visual, or prepare a client update.
Use it when you want a particular kind of work done well.The exact filename changes between tools. You may encounter names such as CLAUDE.md, AGENTS.md, or another project rule file. Do not get hung up on the label. The idea is similar, but each app has its own supported filenames, search locations, and rules for which instructions take precedence. Ask the assistant to check its documentation and confirm which file it actually loaded.
Build the foundation first
Think of durable context as the syllabus you hand someone on their first day. It should be short enough to stay useful, but clear enough to prevent the same questions and mistakes from happening again.
"Help me write a short project instruction file for this work. Ask me only the questions you need about the audience, the outcome, my working style, privacy boundaries, and what I consider done. Then give me a Markdown draft I can edit before we use it."
Skills are where improvement compounds
Start with a saved, reusable playbook for one task. You can paste it into an ordinary chat, or package it as a skill when the app supports that format. When you notice a task coming up for the third or fourth time, stop and ask: what did I have to explain again? That is the beginning of a skill.
Identity and objective
Define the role, operating baseline, and the result this skill is responsible for.
Inputs and outputs
Say what the skill needs and what a good finished result looks like.
Guardrails
List the privacy limits, actions needing approval, and when to ask for help.
Workflow
Give the repeatable sequence - including when to use a tool or show work for review.
Examples
Show one or two examples of the kind of answer or artifact you actually want.
Use the same method for a learning activity.
Fictional brief: upper-primary learners comparing one half with two quarters, 15 minutes, paper and pencils. A reusable instruction could be: “Give one clear objective, a short demonstration, a learner activity, an adaptation, and an exit question. Use only the supplied materials. Ask if the age band or objective is missing. Leave the final content check to the educator.”
An illustrative activity: use two sheets of paper of the same size. Fold one into two equal parts and the other into four. Shade one half and two quarters, compare the areas, then explain why they match. Exit question: “How many quarters cover one half?” Expected answer: two. The educator checks the explanation, accessibility, and fit with their curriculum before use.
Test the playbook on a different objective. Reusable instructions should preserve the structure without copying the fractions activity into an unrelated lesson.
A portable skill template
Markdown is plain text with lightweight formatting: # for a heading, - for a bullet. The reusable instructions below are the body of a skill. Apps that support the Agent Skills format also expect a SKILL.md file with name and description metadata. Your assistant can package this draft for the tool you use.
# Skill: [name / purpose] ## Identity and objective - Role, baseline, and core mission. ## Input and output - What I will provide. - What a finished result must look like. ## Guardrails - Never do ... - Do not guess about ... - Stop and ask when ... ## Workflow 1. First step. 2. Review point. 3. Final check. ## Examples Input: ... Output: ...
Start with a real repeat
Your first skill does not need to be impressive. It needs to be useful. A teacher could make a skill for turning a learning objective into a classroom activity. A small business owner might make one for product descriptions in their voice. A manager might make one for turning rough notes into a clear update.
"We have done this task several times. Review the way I corrected you and the final results I approved. Draft a small reusable skill that captures the goal, inputs, workflow, output format, and things you should never assume. Keep it practical and show me the draft before using it."
A product-description skill.
Input: the product name, verified materials, dimensions, price, and one example in your voice. Output: a description of no more than 60 words and three factual bullets. Rule: never invent a benefit, certification, or delivery date. If a required detail is missing, ask for it.
When moving that skill to another app, check its trigger, available tools, file paths, and permissions. Test it with the same sample product. Portable instructions help; identical behavior is not guaranteed.
You are still in the loop
Good context and tested instructions can improve consistency. They do not make it infallible or give it authority you did not intend. Keep the decisions that carry consequences: what is shared, what is changed, what is true, and what represents you. The better your instructions get, the more room you have for that kind of judgment.
Turn one good result into a reusable playbook
This small business example is deliberately complete enough to test. The same pattern works for a classroom activity or a staff update.
Your starting information
Fictional product: Cedar desk tray Verified material: untreated cedar Dimensions: 20 × 12 × 3 cm Price: $18 Delivery time and certifications: not supplied
Create a reusable product-description playbook. Inputs: verified product name, material, dimensions, price, and desired tone. Output: one description of no more than 60 words plus three factual bullets. Use a warm, plain style. Do not invent benefits, certifications, delivery promises, or sustainability claims. Ask if a required input is missing. Apply the playbook to the fictional cedar tray above, then show me the reusable instructions separately.
Check the expected result
Illustrative answer · check your own result first
- One suitable description: “Cedar desk tray, made from untreated cedar. Measures 20 × 12 × 3 cm. Price: $18.” Three factual bullets can list the material, dimensions, and price.
- It must not call the tray certified, waterproof, sustainably sourced, or available for next-day delivery: none of those facts were supplied.
- Try the playbook with a second product missing its dimensions. It should ask or clearly mark the gap, not reuse the cedar tray's size.
You are ready to move on when…
- I saved the instructions separately from the example output.
- I tried a new example and checked for invented details.
Keep the playbook. Try it again.
You have chosen a task, practiced review, set up your assistant, and captured a repeatable standard. Try it on new information before adding complexity.
Optional next step: go further →Revisit assistant setup →Return to the learning path →