module: "MODULE 2" category: "DIGITAL FTES: ENGINEERING" title: "Context Is the Missing Layer — Links, Images, and Emphasis Complete Your Spec" description: "A specification that only describes requirements leaves AI blind to live documentation, visual context, and priority signals. Links, images, and emphasis are the finishing layer that makes specs machine-optimized." cta_hook: "Bold means must. Italic means recommended. AI reads the difference." warning_banner: "Vague link text like 'click here' removes destination context — AI cannot infer what the link contains and may ignore it entirely when generating code." the_3_rules: title: "Links = Live Truth" description: "A Markdown link to documentation gives AI access to ground truth — it fetches the actual API reference instead of relying on potentially outdated training data." fix: "Fix → Documentation Anchors" title: "Alt Text = Hidden Context" description: "AI often reads Markdown as plain text, not rendered HTML. Descriptive alt text ensures AI understands what an image shows even when the image itself cannot be processed." fix: "Fix → Descriptive Alt Text" title: "Emphasis = Priority Signal" description: "Bold signals non-negotiable requirements. Italic signals optional guidance. AI interprets emphasis semantically — it's not decoration, it's a constraint level." fix: "Fix → Semantic Emphasis" what_this_fixes: flow: step1: "Bare Requirements" step2: "Links + Images + Emphasis" step3: "Contextualized Spec" result: "Machine-Optimized Output" quote: "Links give AI eyes into the real world. Images give it spatial understanding. Emphasis tells it what cannot be compromised. Together, they complete the specification." short_hook: "Contextualize. Don't just describe."
A great specification doesn't just describe—it contextualizes. This lesson teaches you how to enrich your Markdown documents with links to external resources, embedded images for visual clarity, and text emphasis to highlight critical constraints. You will learn to use "alt text" as a hidden context layer for AI and master the use of bold and italic markers to communicate priority, ensuring your specifications are both human-readable and machine-optimized for high-quality outcomes.
Example: Read the Python documentation for help.
[!CAUTION] Never use vague link text like "click here" or "link". Descriptive text like "requests library documentation" helps both humans and AI understand the destination context.
Images help readers understand UI, data flows, and architecture.
[!TIP] Link vs Image:
- [text](url) = Take me there (clickable link)
-  = Show it here (embedded image)
Markdown provides two levels of emphasis: bold (strong) and italic (light).
Example: User passwords must be hashed. API keys should never be committed to version control.
Install Python 3.9+
Run: python tracker.py