Opportunities: Wiki Knowledge Applicable to Tech Explainer Video Workflow — Incremental Pass, 2026-08-18
Scope: TechResearch/Figma_Design_System_Workflows/figma_use_cases.md (new 2026-08-11, not covered by the 2026-08-09 pass) checked against Projects/tech-explainer-video-workflow.md, whose "Diagram polish + animation" pipeline stage already names Figma as the tool that imports Eraser's SVG output, applies branding, builds 16:9/9:16 frames, and uses Smart Animate for motion.
figma_use_cases.md's accessibility-audit and component-brief material is new leverage for the video workflow's diagram/UI-explainer content specifically, not just general Figma skill
The existing tech-explainer-video-workflow.md treats Figma purely as an animation/branding step for architecture diagrams. figma_use_cases.md (new this window) documents three additional Figma capabilities the video workflow doesn't currently use but could, for a specific content category: any explainer video that walks through a UI or product feature (e.g., a course platform screen, a SaaS dashboard) rather than a pure architecture diagram.
- Dev Mode inspection (§1) — reading exact spacing/token values and generated code snippets directly off a component — is a fast way to produce accurate on-screen annotations ("this spacing is
space/md, this color issurface/primary") for any video walking through a UI implementation, without hand-measuring or guessing values from a screenshot. - Accessibility audits in Figma (§3) — contrast-checker plugins, touch-target-size checks, tab-order verification — are a ready-made content format, not just a design QA step: a short explainer video demonstrating "here's how to audit a Figma design for WCAG compliance before it ships" is a concrete, demoable, senior/staff-level topic that fits directly into the existing pipeline (screen capture of the Figma canvas + plugin output, no new tooling required) and lines up with Mihir's stated content themes (RAG, agentic systems, AWS) by adding a design-systems-adjacent engineering topic that's genuinely differentiated from typical dev-content channels.
- Design token audits (§4) — cross-referencing Figma variables against a codebase's actual token file to catch drift — is a scriptable, demoable artifact (an "applies AI/automation to create business value" example the note itself calls out) that could become its own short video: build a token-drift checker on screen, narrate the logic, ship the repo link. This is the same "watch me build it" format
content-as-infrastructure-and-removing-setup-friction.mdalready recommends for RAG/LangGraph content, applied to a design-systems topic instead.