Code reference detail
showcases.test.ts
site/src/content/showcases.test.ts
| Idea | Status | Tags | Summary | Katz |
|---|---|---|---|---|
| broken_links_showcase | done | diagnostics, refactor, cli, ci | Flagship. Links that break loudly. Someone renames a file. Show the diagnostic, the quick-fix menu, and the rewritten refs. Then the same issue from ["../core_analysis/check.rq".check] ( `reqlan check`, exit 1 ) and that command as a CI step so a merge cannot land rot. This is the argument against a wiki. Domain: refactor safety, any stack. | 0.190 |
| showcase_module | done | Showcases are standardised and typed in TS content objects. Types live in ["../../site/src/content/showcases/types.ts"]. Each showcase is its own file under ["../../site/src/content/showcases"]. ["../../site/src/content/showcases/index.ts"] composes them in [showcase_set] order. Each showcase file carries rq: comment references to its showcase idea and to the product ideas it demonstrates. Short version ( list card ): id, title, summary, tags, mechanism badge. Long version ( detail page ): full blocks array including payoff. Exist as a list page and as a full page per slug. Routes: `/showcase/` and `/showcase/[slug]/` — static export. Block kinds needed beyond today's code | features union: callout — the one-sentence point of the page exchange — query + response, terminal-styled diagnostic — editor-style error with quick-fixes diagram — visually distinct from code; never language- " rq " caption / mechanism fields on the showcase object Copy stays minimal and show-don ' t-tell, aligned with site copy rules. | 0.057 | |
| site | the / site folder contains a static Next. js App Router landing page for reqlan. should align with [brand] Copy modules: [copy] Document head: [meta_tags] | 0.040 | ||
| story_codebase_showcase | done | story, traceability, delivery | Flagship. A story that ships with the code. Write the feature as one idea. Bind source with @ implementation. Bind proof with @ tests. Point back with rq: comments. Click on that name returns the bound files — not a ticket outside the repo. Domain: product delivery. One worked name across every block per [one_worked_example_per_page]. Payoff is click output per [every_showcase_ends_in_a_payoff] and ["../cli/click.rq".click]. Uses [development_core.code_comment_references] and [development_core.testing]. Demonstrates [sub_file_binding] and [bidirectional_comment_links]. | 0.046 |
Reference labels
"../../site/src/content/showcases.test.ts", "../../site/src/content/showcases.test.ts:broken-links shows reqlan check as a CI gate", "../../site/src/content/showcases.test.ts:gives each showcase its own file with rq comment references", "../../site/src/content/showcases.test.ts:story-codebase binds a story to source and tests", ../../site/src/content/showcases.test.ts, ../../site/src/content/showcases.test.ts:broken-links shows reqlan check as a CI gate, ../../site/src/content/showcases.test.ts:gives each showcase its own file with rq comment references, ../../site/src/content/showcases.test.ts:story-codebase binds a story to source and tests