Edapt HSBR Works

Created by Hisham Basheer (HSBR)

Prompt Engineering
Back
Task Basic Prompt Before Response RACE Prompt After Response Comparison Reflection HSBR Note

Task 4: Prompt Engineering — RACE Framework Before & After Analysis

See how reframing the same question with RACE improves quality, depth, and actionability.

RACE
How can I become a better freelance web developer?

AI Response (Before — Summary)

1
5 Key Areas
  • Strengthen technical foundation
  • Build a strong portfolio
  • Master client communication
  • Improve business systems
  • Keep learning & evolving
2
Limitations
  • High-level and generic
  • Not tailored to Laravel/HSBR context
  • Action steps not time-bound
Role: You are a professional career coach and productivity strategist for freelance web developers.
Action: Create a personalized productivity plan.
Context: I’m a PHP/Laravel full-stack developer (HSBR Enterprise), working from home with multiple projects. I struggle with focus and time management.
Expectation: Give a realistic daily routine, focus techniques, digital tool recommendations, and steps to build a company.

AI Response (After — Summary)

Personalized
A
Daily Routine (7AM–11PM)
  • Deep work block (8–10AM), comms/admin, learning block, HSBR internal work
  • Evening review + optional writing
  • Weekly reset on Sundays
B
Focus & Tools
  • Pomodoro 50/10, time-blocking, task-batching, 2-minute rule
  • Notion/ClickUp, Clockify, GitHub Projects, Slack/Discord, Forest
  • Company path: Foundation → Systemize → Productize → Grow → Brand & Scale

Before vs After

Scroll on mobile
Dimension Before (Basic) After (RACE)
Clarity Generic advice Clear role, action, context, expectations
Personalization Low High — Laravel + HSBR specific
Depth High-level concepts Detailed routine + tools + company path
Actionability Broad suggestions Time-boxed steps, weekly reset, concrete stack
Outcome Useful but generic Copy-paste plan you can run tomorrow

Reflection (Answered)

  • How did the response change? From general roadmap → personalized, time-boxed plan.
  • Biggest difference? Context — including Laravel, HSBR, and focus issues.
  • Confidence using RACE? 9/10 — will use for important prompts.
  • More actionable? Yes — routine, focus methods, tools, and company steps.
Insight Repeatable System
HSBR Note — Summary:

Using the RACE format turned a broad question into a concrete plan tailored to my Laravel freelancing context. The Context and Expectation sections drove the biggest gains in clarity and actionability.

Takeaway: Discipline beats motivation — systems build success. RACE is now part of my standard prompt checklist.