Idea detail
gs_01_why_reqlan
reqlan rq/marketing_and_media/tutorials.rq:202
block
Summary
Audience: developers or knowledge workers who already talk to LLMs about their project and feel context drift.
Outcome: viewer can explain reqlan in one sentence and knows where install / docs live.
Runtime: 4 – 5 min.
Demo: cold open on a fresh machine or reset profile. Folder `reqlan-tutorials-demo` does not exist yet — or an empty folder with only `README.md`. No `.rq` files. reqlan extension not installed ( or disabled ) until the install beat.
Related: mission_statement llm_first inspiration installation_event installation extension_installation
Attributes
| Key | Value |
|---|---|
| example | ```rq // Contrast slide only — not typed live in this episode // Left panel: chat paste (prose blob) // Right panel: the same intent as three named ideas login must reject empty passwords session expires after inactivity audit_log records failed attempts ``` |
| script | SCR: Dark title card: reqlan wordmark + "Get started · 01 · Why requirements as code". Brand palette. VO: If you work with language models on real projects, you already write requirements — you just write them into the chat window, over and over. SCR: Split screen. Left: a bloated chat paste — one long paragraph mixing login, sessions, and audit rules. Right: three short named lines from the example. VO: reqlan is a small language for turning that intent into a graph of named ideas — so you, your teammates, and your tools can find, link, and reuse them instead of retyping. SCR: Brief montage (no narration overlap): VS Code with a `.rq` file, reqlan activity bar icon, Ideas Summary graph with a handful of nodes. VO: The day-one job is simple: name the idea, write the prose, point at related work. You can see it here — a file of names, and lines that connect them. SCR: Show a sticky note or chat bubble: "Isn't this just another notes app?" Cut to the named-ideas side of the contrast — three handles you can reference by name. VO: Notes apps store paragraphs. reqlan stores handles. You do not need a schema on day one — you need names your tools can search and link. SCR: Browser: Visual Studio Marketplace page for the reqlan extension — or Open VSX equivalent. Click Install. Switch to VS Code: Extensions view confirms install. File → Open Folder → create or select `reqlan-tutorials-demo`. VO: Install the reqlan extension from the Marketplace or Open VSX. Open a folder — even an empty one — so the editor has a workspace root. SCR: Onboarding webview appears: "Thanks for installing". Pause on docs / marketplace links in the welcome body. Do not create a base yet. VO: On first launch you get a short welcome screen. Keep those links handy. Creating a base — the `.reqlan` marker — comes after you have written a few ideas. SCR: End card: CTA row — Install · Docs · next episode "Your first idea". VO: Next: write your first idea in under a minute. |
| slides | { id title transition fade background brand-dark kicker Get started · 01 heading Why requirements as code asset logo notes If you work with language models on real projects, you already write requirements — you just write them into the chat window, over and over. }, { id problem transition fade background brand-panel heading Context drift is familiar body You paste the same intent into chat again and again. notes Every new thread starts from scratch unless you rebuild context by hand. }, { id contrast transition none background brand-contrast heading Chat dump vs named ideas body Left: bloated prose paste. Right: three named ideas. code_lang rq code login must reject empty passwords / session expires after inactivity / audit_log records failed attempts notes reqlan turns that intent into a graph of named ideas — requirements as code. }, { id loop transition fade background brand-panel heading Name, prose, neighbours asset montage-ide body Editor language support · activity bar neighbourhood · optional graph map. notes Day one is name the idea, write the prose, point at related work. }, { id misconception transition none background brand-contrast heading Not another notes app body Notes store paragraphs. reqlan stores handles you can link and search. notes You do not need a schema on day one — you need names your tools can reuse. }, { id install transition slide background brand-panel heading Install the extension body Marketplace or Open VSX → Install → Open Folder. notes Open a workspace folder even if it is empty. The welcome webview appears on first launch. }, { id onboarding transition fade background brand-panel heading Welcome, not base yet body Keep docs and marketplace links from the onboarding page. notes Creating a base with .reqlan comes after you have written a few ideas. }, { id end transition fade background brand-dark heading Your first idea is next body Install · Docs · then write your first idea. fragments Next: Your first idea asset logo notes Next: write your first idea in under a minute. } |
Ancestor context
No ancestor chain recorded.
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| None | |||
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| ideaset_member | get_started_series | reqlan rq/marketing_and_media/tutorials.rq | — |
| ideaset_member | slide_decks | reqlan rq/marketing_and_media/tutorials.rq | — |
| Kind | Idea | Path | Snippet |
|---|---|---|---|
| references | extension_installation | extension_installation | |
| references | inspiration | inspiration | |
| references | installation | installation | |
| references | installation_event | installation_event | |
| references | llm_first | llm_first | |
| references | mission_statement | mission_statement |
Initialising graph…