10 Epic (Free!) Apps That Should Be Built Into macOS

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: 10 Epic (Free!) Apps That Should Be Built Into macOS
- URL: https://www.youtube.com/watch?v=jaFTv7uWBn0
- Topic: Creative Automation
- My current learning frame: Audit one day of Mac use, identify three recurring points of friction, and test a file, automation, or productivity utility whose scope matches each problem.
- Why this matters: New playlist item from Mostly Mac; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "When you're buying into the Apple Macintosh ecosystem, whether it's for your MacBook Air, Studio, or an iMac, you're also gaining access to one of the most vibrant and creative software communities on the planet. From expensive top-tier..."
- 2:45 / Evidence 2: "whether it's just from one folder on the internal SSD to another, or onto your iCloud Drive, an external drive, or on a network. The sidebar navigation makes moving between folders and drives, whether local or online, an..."
- 4:17 / Evidence 3: "designed to be keyboard first. Once you master these simple navigation shortcuts, you'll be pinging around your operating system like a hacker, shifting files faster than a politician's intern. The app is configurable in all the right ways,..."
- 7:02 / Evidence 4: "terminal sessions alongside each other. But actually, the reason I use it is I configure it so it doesn't look like a scene from the 1983 film WarGames. >> Game time elapsed: 31 hours, 12 minutes, 15 seconds."
- 8:45 / Evidence 5: "combinations are already spoken for. Hyperkey fixes that issue with one simple idea. It turns your Caps Lock key into a modifier that works alongside command, control, option, and shift. So, for instance, if you wanted, you could..."
- 10:30 / Evidence 6: "to rule them all. In all, you will find 49 different features in For Saint. Everything from clipboard managers to system monitors. In fact, several of the features of apps I've already mentioned, such as Amphetamine, can be..."
- 12:56 / Evidence 7: "have a heap of cool content planned for this channel, with upcoming looks at more awesome apps, both open source and commercial, along with guides and roundups for all things Mac related. So, if you haven't already, do..."

Video-aware target:
- Prompt lane: Creative automation
- Mechanism to extract: Extract the creative production loop, especially where the human keeps taste, selection, and final judgment.
- Artifact to produce: A creative production board with source inputs, prompt recipe, selection criteria, edit pass, and taste-review checkpoints.
- Artifact must include: brief; source inputs; generation recipe; selection criteria; edit/review checkpoint

Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Extract the creative production loop, especially where the human keeps taste, selection, and final judgment. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A creative production board with source inputs, prompt recipe, selection criteria, edit pass, and taste-review checkpoints.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Brief -> Source material -> Generation -> Selection -> Edit -> Taste review -> Reusable recipe
   - answers to these source questions: What asset is being produced? | What inputs and tools drive it? | Where does human taste intervene?
   - 3 concrete examples that apply the video idea to real agentic work, such as Claude-generated video campaign; image-to-site workflow; voice or video editing loop
   - 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: mistaking novelty for quality; no source/brief discipline; shipping generated media without taste review
   - a checklist for the next real workflow, focused on: brief, inputs, generation, selection, critique
   - one practical exercise with a clear done signal: Build one reusable creative recipe and define what would make the result rejectable.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.

Quality bar:
- Make this specific to "10 Epic (Free!) Apps That Should Be Built Into macOS", not a generic Creative Automation essay.
- Anchor each creative step to transcript evidence about inputs, model/tool choices, iteration, editing, or critique.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic content advice; tool hype; creative output without selection criteria.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.