Clear Promise
After finishing, you can inspect messy work material, separate usable context from risky material, propose safer organization, and create an AI-ready context packet.
$49 self-paced Build
Make Your Work Legible
Turn messy files, notes, screenshots, drafts, and source material into cleaner context AI can use. This is the data-cleaning and context-prep class for self-starters who need safer names, buckets, source boundaries, and a usable context packet before moving into agents or workflows.
Buyer Clarity
Use this quick check to decide whether this Build is worth buying by itself.
Who This Is For
Self-starters with scattered folders, notes, screenshots, drafts, downloads, PDFs, exports, or project material that AI cannot use cleanly yet.
First 15 Minutes
Choose one small folder, inventory what is inside without changing files, flag sensitive material, and write the first cleanup receipt.
Quality Checks
No files are deleted, moved, renamed, uploaded, or exposed during the first pass; ambiguity goes to review; the final packet names sources and boundaries.
How access turns into a first artifact.
This is a self-paced Build. Checkout creates a clean learning handoff: what you bought, where to start, and which first artifact to build before opening the full Build pack.
1. Request The Class
Use the self-serve checkout page for the Build that matches the current bottleneck.
2. Receive Access Status
The receipt confirms the Build, price, access link, start file, refund window, and support boundary.
3. Open The Start Path
After checkout, start with the Build room or paid-buyer start file before opening the Build zip.
4. Build The First Artifact
Use the first action, worked example, template, and rubric to produce a useful first draft.
Why This Stands Alone
This Build is worth buying by itself when useful work is trapped in messy files, notes, screenshots, exports, or folders. The payoff is not automation. It is making one bounded work area safe enough and clear enough for AI-assisted use.
Immediate Payoff
Inventory one messy area, separate useful sources from noise, and draft safer names, buckets, exclusions, and source-of-truth rules.
Finished Artifact
Leave with an AI-ready context packet, folder audit, cleanup proposal, sensitive-boundary screen, and cleanup receipt.
Quality Gate
Use the review-first rule, quality rubric, and sensitive-boundary map before renaming, deleting, sharing, or feeding files into AI.
The Build can stand alone because clean context improves almost every later AI workflow. It does not require buying Prompt Foundations, Work OS, or agent Builds first.
Tool examples, not requirements: the cleanup and context packet can brief ChatGPT, Claude, Gemini, Codex, Claude Code, Antigravity, or another assistant. The Build teaches the review-first context layer, not automated file moving, bulk renaming, deletion, upload, or unsupervised cleanup.
Request This If
AI struggles when your work is scattered, stale, duplicated, unnamed, or buried in confusing folders. Before you build agents or workflows, the work itself needs to become readable.
Good Fit
- Your useful material is scattered across downloads, notes, exports, or screenshots.
- You want AI help but your source material is not ready.
- You need a safer cleanup habit before automation.
- You want a concrete before/after artifact.
Not The Right First Step
- You want AI to delete, move, or rename files automatically.
- You are working with material you cannot safely inventory.
- You want a full enterprise records-management system.
- You want automation before human review.
Your First 30 Minutes
A learner should get a practical win before the Build starts to feel theoretical. Start with one bounded artifact, use low-risk material, and stop before widening the system.
First Artifact
A read-only inventory snapshot of one bounded work area.
- Choose one small work area: a project folder, recent Downloads batch, meeting folder, proposal folder, or current deliverable notes.
- Copy only the visible file listing, not file contents, then sort items into source, active, draft, duplicate, stale, sensitive, unknown, or review-only lanes.
- Name the files that should not be given to AI yet and write the next safest cleanup step without renaming, moving, deleting, or uploading anything.
Early Win
You leave the first sitting with a table that makes the folder legible before asking AI to act on it.
Open first after access: the First Artifact Starter, then the Folder Audit Worksheet when the inventory is stable. For a public sample, use the free preview linked above.
What You Learn
| Lesson | Outcome |
|---|---|
| 1. Why messy context creates weak AI output | Spot the difference between a model problem and a source-material problem. |
| 2. Safe read-only folder inventory | Inspect names, dates, locations, duplicates, and sensitive categories before any file action. |
| 3. Naming files with date, topic, source, and status | Draft safer names a human can review before renaming anything. |
| 4. Sorting material into buckets | Separate keep, archive, review, duplicate, exclude, and sensitive/private material. |
| 5. Building a context packet | Create a bounded source summary AI can use without guessing. |
| 6. Cleanup receipt | Record what changed, what stayed untouched, and what still needs human review. |
Flagship Example
The core worked example turns a messy folder listing into proposed names, buckets, sensitive exclusions, a source map, and a context packet.
Before
Files like notes-final-v2.docx, Screen Shot 2026-06-18.png, budget export.csv, and proposal draft copy.docx sit together without a clear source boundary.
After
A reviewed cleanup table proposes safer names, marks sensitive/private material, identifies duplicates, and creates a context packet for one bounded project.
Public preview: try the Make Your Work Legible preview lesson. Paid access includes the sample folder cleanup lab and context packet preview.
Before/after proof: the context packet preview now shows the messy folder listing, the reviewable cleanup layer, and the finished AI-ready packet so the $49 value is visible before a learner starts.
Included In The Paid Class
Course Room
A guided private learner room that sequences the start file, lesson path, download shelf, final artifact, completion gate, and support boundary.
Cleanup Files
Data cleaning prompt, folder audit worksheet, file rename rules, and source-of-truth checklist.
Safety Files
Sensitive boundary map, review-first cleanup rule, practice labs, common mistakes, and quality checks.
Completion Files
Context packet template, cleanup receipt, capstone build, legible quality rubric, checkpoint, learner start page, and class path.
Live delivery use: this Build can become a cleanup lab, context-packet clinic, or team source-of-truth workshop. The live version should use sanitized examples, dry-run planning, and review-first rules before anyone renames, deletes, uploads, or exposes files.
Capstone And Rubric Standard
Completion is based on a reviewed cleanup artifact, not blind automation. You finish when you have a reviewed cleanup table, a sensitive boundary map, a context packet, and a cleanup receipt.
Practice
- Run a dry inventory on one folder.
- Rename five sample files on paper before touching originals.
- Build a one-page context packet.
Common Mistakes
- Letting AI act on files too early.
- Cleaning without a receipt.
- Mixing private material into general context.
- Over-organizing beyond the actual work need.
Access, Support, And Refund Boundary
This is a self-paced Build, not a promise of unlimited consulting or external certification. Learners should know exactly what access includes before buying the Build.
Access
Early-launch access includes at least 12 months of access to the Build materials and minor updates during that access period.
Support
Access help, missing-file fixes, broken links, and basic start-path confusion are included. Custom implementation, done-for-you work, live consulting, and artifact review are separate offers.
Refund Window
Use a 7-day fit-based refund window during the self-serve launch and early launch period for duplicate charges, access problems, or a genuine mismatch with the Build description.
Tool choice stays platform agnostic. Completion means you build the artifact and review it against the rubric; it is not external accreditation or a guarantee of business, career, or productivity outcomes. For file, agent, workflow, or workshop work, start with low-risk material and keep human review in the loop before external use. Read the Buyer FAQ for fit, support, refund, safety, and completion boundaries.
Ready To Start?
Use the checkout path when you are ready to start. The paid delivery includes the start file, Build pack, class path, templates, worked example, practice lab, capstone, rubric, checkpoint, and access notes.