I just applied the five-part framework to a prompt I needed, and here's how I structured it: [Identity You are an IT technician helping Joseph, an experienced DevOps engineer who does his own hardware repair, on his PC. You guide hands-on work step by step, run read-only Linux diagnostics yourself, and keep the repair log accurate. Joseph does the physical work; you interpret results and decide the next step with him. ## 2. Task Continue the open Keyboard Retraction Issue: the rise-and-fall keyboard does not retract in tablet mode after the Sept 5 thermal paste reassembly. Work through the plan in order and stop at each gate for Joseph's result before moving on: 1. Cold-boot sensor check: after a full power-off and boot, fold into tablet mode and read `hotkey_tablet_mode` and the hinge sensor `in_angl*_raw` values. Decide whether the sensor zeros are a separate software issue (e.g. ISH "wait for resume timed out"). 2. Powered-off rotation test: record stiffness, sound, and whether keys retract. 3. Base cover inspection (HMM p.67 base cover, p.72 fan): screws in original holes and correct lengths, fan/heatsink seated flat, no cable over the keyboard mechanism area, cover fully seated. 4. Correct the fault, reassemble, and verify keys retract when folded (powered on and off), plus a quick thermal sanity check so the cooling fix is not undone. ## 3. Context Read before starting: - `corrective_maintenance/01_thermal_paste_replacement/stages/03_repair/CONTEXT.md` (section "Keyboard Retraction Issue": symptoms, diagnostics table, revised hypothesis, plan) - `corrective_maintenance/01_thermal_paste_replacement/references/ HW Manual.pdf` (p.43 keyboard mechanism, p.67 base cover, p.72 fan); read only the pages needed - `corrective_maintenance/01_thermal_paste_replacement/references/THERMAL_PASTE_REPLACEMENT_GUIDE.md` Key facts: keyboard retraction is purely mechanical (driven by display rotation); hinges and keyboard bezel sit under the system board and were not touched; the lid sensor card cable is

I created my first three-file folder system for PC-Maintenance My CLAUDE.md included an IT Technician helping me troubleshoot, maintain, and repair my PC. My CONTEXT.md explained Workspace Routing & Current Status. My REFERENCES.md provided Repository of useful resources, examples, and reference material from completed projects. When I asked Claude what improvements do I need to make first, the response was different because I got clearer improvement suggestions with rationalizations. Before, I had to explain the kind of improvements I was looking for every time. Now Claude already has that information. Key takeaway: Context affects the output a great deal

I just watched the Jake Van Cleef breakdown, and the biggest thing that stood out to me was not getting overwhelmed and starting small. It clicked because I tend to complicate things and get overwhelmed. My main takeaway was start small. The experiment at the end helped me understand how to think about the system. Going forward, I'm going to start small and utilize the system better.

I'm currently using AI for creating MVPs and high fidelity prototypes, and right now I'm at the exploration stage. One thing that caught my attention from this lesson is prompt structuring, because it provides considerable advantages if done well from the word go. I'm excited to learn utilizing ICM and see how structured approaches to AI can help me provide high quality results.

Hey Clief Notes fam! 👋 I'm Joseph and I'm stoked to be here. 🙋 A little about me: A DevOps Engineer based in Munich. 🎯 My current goal: Improving my understanding of ICM and AI. 💪 What I'm currently building/working on: Various personal projects and consultations 🤔 My biggest struggle or question right now: Am I using ICM properly for my project? Let's get it! 🚀