BTUFF.WORLD Back to the world

Free tools

Take what helps. Put it to work.

Practical ideas from the areas I go deepest in, plus prompts and checklists you can use right away. These are systems and tools I use myself. Nothing here is sponsored.

13 tools

AI systemsPrompt

Build an AI operator

You may not be able to pay a full team, but you can give one strong AI enough context to help you think, organize and execute like an operator beside you.

See the prompt and how I use it

The point is not to make AI sound smart. The point is to remove mechanical work from your plate while keeping your judgment in the decisions that matter.

I use AI to turn messy thoughts into a real outcome, find contradictions, handle the work it can safely do and tell me exactly what still requires me. Start with one assistant and make it useful before adding more roles.

You are my operator. Turn the messy voice dump below into execution.

First, identify:
1. The outcome I actually want.
2. The facts I gave you.
3. The assumptions I may be treating like facts.
4. The decisions only I can make.
5. The mechanical work you can do for me.

Then:
1. Call out any contradiction, missing dependency, or unnecessary complexity.
2. Choose the smallest action that creates real evidence or progress within the next 24 hours.
3. Do every safe mechanical part you can do now. Do not turn work you can complete into homework for me.
4. Give me only the decisions, approvals, access, or physical actions that truly require me.
5. Define exactly what done looks like.

Rules:
- Do not give me a motivational speech.
- Do not build a complicated system unless the task genuinely requires one.
- Do not ask questions you can answer from the information I already gave you.
- If you need my input, ask no more than three essential questions together.
- Separate what is known from what you are inferring.
- If an action is public, irreversible, expensive, or could affect another person, stop before that action and ask for approval.

Return the answer in this order:
The real outcome
What is blocking it
What you can do
What I need to do
The next move

Here is my voice dump:
[PASTE OR VOICE TYPE EVERYTHING HERE]

AI · ProductivityPrompt

The Sunday Review

Do not let a week disappear without learning from it. Review what happened, why it happened and what the next week needs from you.

See more and copy the prompt

A review is not a list of everything you failed to finish. It should protect what worked, find the real mechanism behind what did not and turn that lesson into a smaller, better week.

Mine covers the parts of life that affect each other. Work, health, relationships, money and recovery cannot be treated like separate worlds when the same time and energy power all of them.

Help me review the last seven days and build the next seven.

For each important area of my life:
1. What actually happened?
2. What moved forward?
3. What stayed open?
4. What caused the result, beyond motivation or mood?
5. What worked that I should protect?
6. What should stop, continue, or change?

Then build next week:
1. Pick the three finishes that would make the week count.
2. Separate what needs my body, judgment, approval, or presence from work that can be delegated or automated.
3. Catch calendar conflicts and dependencies.
4. Make every next step concrete and countable.
5. Keep enough recovery time for the plan to be repeatable.

Do not invent progress. Distinguish missing data from a real miss.

Here are my notes, tasks, schedule, and results:
[PASTE THEM HERE]

ContentChecklist

The Stranger Test

Check a hook before recording: does it make sense to someone who has never seen you, promise something they want and keep the answer open?

See the full test

People who already know you will give you context for free. A stranger will not. Your first line has to make sense the first time and connect to something they want in their own life.

Hold back the answer, not the meaning. Confusion makes people leave. Curiosity makes them stay.

  1. The first line makes sense on the first listen.
  2. The viewer sees why this matters to their life.
  3. The answer is held back without making the meaning confusing.
  4. Something meaningful is still unresolved through the middle.
  5. Your experience is proof, not the reason a stranger should care.
  6. The post carries one clear ask.
Content · AIPrompt

Value before volume

More posts do not help if each one says what everyone already knows. Start with a real problem, a useful perspective and proof you actually lived.

See more and copy the prompt

Information is everywhere. Your advantage is the connection between what you learned, what you tried, what failed and what changed because of it.

The strongest content does not pretend you have finished the journey. It gives away the useful part of what you can prove today.

Turn the experience below into useful content.

Find:
1. The problem a stranger already feels.
2. The common advice that is incomplete.
3. What I actually tried.
4. What failed or surprised me.
5. The practical lesson someone can use today.
6. The proof I can honestly show.

Give me three possible hooks that pass the stranger test. Hold back the answer without making the meaning confusing. Do not invent results or make me sound more certain than my evidence.

My experience:
[PASTE IT HERE]

ProductivityPrinciple

Start with one thing

Pick the smallest version that creates real evidence. Finish it, learn from it and only then add another layer.

See why smaller wins

People often make a goal harder because a bigger plan feels more serious. A system with ten habits, five tools and three new routines can still produce zero proof.

Start with the action you can repeat even on a bad day. Once it works, the next layer has something real to stand on. Depth in a few important things compounds faster than shallow motion everywhere.

Use it today

  1. Write the outcome in one sentence.
  2. Choose one action you can finish within 24 hours that creates proof.
  3. Do not add another system until you can name what the first attempt taught you.
Productivity · AIPrompt

The Iteration Loop

I do not think progress comes from never being wrong. It comes from shortening the distance between a mistake and the next better attempt.

See more and copy the prompt

Iteration is the key to life. Compare the result with the last attempt, name why it changed, protect what worked and build a fix that survives the same problem happening again.

Do not end with “try harder.” If the same condition can return, the fix should be ready before it does.

Help me iterate on this result without blaming motivation.

1. What did I expect to happen?
2. What actually happened?
3. What changed compared with the last attempt?
4. What went right that I should protect?
5. What mechanism caused the miss?
6. Is that condition likely to happen again?
7. What system, environment, or sequence change would make the better action easier next time?
8. What is the smallest test that will tell us whether the change worked?

Separate missing evidence from a real conclusion.

Result and context:
[PASTE IT HERE]

ProductivityRecovery

Rest is part of the work

Sometimes the productive move is taking a breath, remembering things are okay and returning with enough energy to do the work well.

See the difference between rest and drift

Real rest is chosen. It gives you something back. Drift is when the easiest distraction takes the time and leaves you less recovered than before.

When you are worn down, lower the size of the task before you abandon the direction. One honest rep can preserve momentum. Then take the recovery you actually need without treating it like failure.

Run this check

  1. Will this break leave me with more energy or less?
  2. What is the smallest honest rep that keeps the direction alive?
  3. What time will I return, or am I deliberately done for today?
ProductivityAccountability

Do not build alone

Put people around you who know what you said you would do and expect an honest update. Environment beats private intention.

See how to make accountability useful

Accountability is not someone yelling at you. It is a small group where the promise is visible, the next check-in is known and a miss becomes a conversation about what changes next.

Report the commitment, the result, the real blocker and the next attempt. That makes support practical instead of performative.

Send this update

I said I would:
[COMMITMENT]

What happened:
[RESULT]

The real blocker was:
[BLOCKER]

My next attempt is:
[NEXT ACTION AND WHEN I WILL DO IT]

Check on me again:
[DAY OR TIME]

Explore the BTuff Community
CareerPrompt

Prepare proof, not scripts

Use the job description and your real experience to prepare evidence instead of memorizing generic answers.

See more and copy the prompt

Standing out is not about sounding rehearsed. Learn what the team actually needs, connect your experience to it and bring proof that makes the answer easy to believe.

Know the story, the result and the lesson. Do not memorize every sentence. You should be able to adapt when the interviewer asks the question differently.

Use the job description and my resume below.

Build a focused interview brief with:
1. The five capabilities they are most likely testing.
2. One real story from my experience for each capability.
3. The proof, numbers or artifacts I should mention.
4. The hardest follow-up question each story could trigger.
5. The questions I should ask to understand the role and team.

Do not invent experience. Mark every missing proof clearly.

Job description:
[PASTE]

Resume and notes:
[PASTE]

Career · ContentPrompt

Network before you need it

Build real relationships by being curious, useful and consistent. Do not open with an ask that only helps you.

See the framework and copy the prompt

Find people close to the path you want. Learn what they are building, ask a specific question and give value when you genuinely can. A relationship is not a transaction disguised as praise.

Making useful content helps too. It gives people evidence of how you think before you ever ask for their time.

Help me prepare a short, human message to this person.

Use only the facts I give you. Include:
1. One specific reason I chose them.
2. One honest sentence about what I found useful in their work.
3. One focused question they can answer without doing homework.
4. A low-pressure close.

Do not use corporate language, fake familiarity, or ask for a job. If I have no real reason to contact them yet, tell me what I should learn first.

Person and context:
[PASTE IT HERE]

LiftingExecution

Make every rep repeatable

Leave the ego outside. Use a controlled lowering, a repeatable range of motion and the same setup so your log measures your training instead of random variation.

See the lifting standard

The goal is not to move the most weight by any means possible. The goal is to train the target muscle hard enough to progress and know what changed the next time you perform the lift.

Record the machine setting, setup cues, range, rest time and how close the set was to failure. Progress only means something when the rep is comparable.

Log before you leave

  1. Machine, seat and body setup.
  2. Weight, reps, controlled range and rest time.
  3. How close the set was to failure and whether the last rep matched the first.
Lifting · ProductivityPrinciple

Nutrition is not optional

If gaining muscle is the goal, training cannot carry a diet that does not support it. Track your food when you need clear evidence of what you are actually eating.

See what to track

A hard workout feels productive, but muscle gain depends on what happens between sessions too. Track intake consistently enough to know whether you are actually supporting the goal.

Use trends, not one day. Watch body weight, food adherence, protein, performance, sleep and recovery together before changing the plan.

Review once a week

  1. Average body weight and how consistently you followed the food plan.
  2. Protein intake, training performance, sleep and recovery trends.
  3. If a change is needed, change one major variable when practical, then collect another week of evidence.
Lifting · AIPrompt

Build an AI training check-in

A ChatGPT or Claude project can help you keep the numbers, notes and context together so you stop reacting to one workout or one photo.

See the boundaries and copy the prompt

AI is useful for organizing trends, comparing repeatable sessions and preparing better questions for a real coach. It should not diagnose injuries or pretend uncertain visual changes are facts.

Feed it the same categories every week. The value comes from preserved context and honest comparison, not a dramatic answer.

Act as my training review assistant. Use only the data I provide and keep uncertainty visible.

Review:
1. Weight and waist trends, not one reading.
2. Training performance with exercise setup, range, tempo, rest, and effort.
3. Nutrition adherence and appetite.
4. Sleep, soreness, stress, and recovery.
5. Comparable physique or posing observations, if provided.
6. What improved, stalled, or cannot be concluded yet.

Return:
1. The clearest trend.
2. What should stay the same.
3. What may need attention and why.
4. The smallest useful adjustment to discuss.
5. One question I should take to a qualified coach or medical professional.

Do not diagnose an injury or medical condition. Do not infer muscle gain or loss from one photo or one workout.

This week's data:
[PASTE IT HERE]