What problem does it solve? Turning open-source release news into social media image cards often produces shallow README summaries or unsupported performance claims. This Skill converts a verified fact base about an open-source technology event into a structured, traceable storyboard where every mechanism, architecture detail, and performance number is bound to a source. ## Core Features & Use Cases - Evidence-bound narrative planning: Organizes pages along a problem → mechanism/architecture → evidence → boundary arc, with every content block carrying source references. - Structured JSON output: Emits a strict card_plan array with page kinds, roles, content blocks, and semantic visual intent, without HTML, CSS, or hardcoded styling. - Degradation and boundary rules: Downgrades to a general event card when mechanism evidence is missing, and refuses performance comparisons without verifiable benchmarks. - Use Case: Given a fact base about a new open-source database release with architecture changes and benchmark results, produce a 4-6 page storyboard covering the technical problem, the mechanism change, cited evidence, applicability limits, and follow-up signals. ## Quick Start Classify the event as open_source_technology, then ask the AI to generate a technical storyboard from the confirmed fact base with source-bound mechanism and evidence pages.
