Members

IdeaFileStatusSummaryKatz
code_comment_referencesreqlan rq/development/core.rqcode comments should include reference to their respective rq references.0.054
current_link_iconsreqlan rq/development/core.rqSlugs are defined on each link in ["../phonebook.json"]: - `site` → mdi / web - `vsc` → simple-icons / visualstudiocode - `openvsx` → simple-icons / vscodium ( proxy; no Open VSX slug in Simple Icons ) - `github` → simple-icons / github - `discord` → simple-icons / discord - `github-sponsors` → simple-icons / githubsponsors - `email` → mdi / email-outline - `sticker-form` → mdi / sticker-emoji Package entries under `packages` all use simple-icons / npm: - `language`, `analytical`, `cli`0.057
hierarchy_of_requirementsreqlan rq/development/core.rquser request trumps the ["../../reqlan rq"] requirements, and ["../../reqlan rq"] trump the current implementation.0.045
iconify_stackreqlan rq/development/core.rqIcons use Iconify offline — bundled at build time, not fetched from a CDN at runtime. Icon data comes from npm packages listed under the `icons` key in ["../phonebook.json"] per [phonebook_reqs.phonebook_icons].0.080
modulurisationreqlan rq/development/core.rqfiles should be small0.040
phonebook_icon_keysreqlan rq/development/core.rqdoneper [phonebook_reqs.phonebook_icons] A phonebook link or package can omit `icon`. If `icon` is present, it is an object with `set` and `name`. Set ids and lookup URLs are canonical in ["../phonebook.json"]. icons. Use each set's `search` URL to find replacement slugs when a name changes or an icon is removed upstream. Typed helpers live in [phonebook_script]: `formatPhonebookIconKey`, `getPhonebookIconSearchUrl`.0.048
pnpmreqlan rq/development/core.rqMust use pnpm for all js package management across the monorepo ( packages, extension, site ).0.045
pnpm_valreqlan rq/development/core.rqdoneRoot `pnpm run val` chains `check`, then `test`, then `build` ( ["../../package.json"] ). Use for local / ingestion validation ( ["../ingest/ingest.rq"._file] ).0.046
rust_mindsetreqlan rq/development/core.rq- code should be complete - nulls should be safe and deliberate - fallbacks should be used sparingly - incomplete code should be marked as such - comments should describe final desired state of the code, not the current state; they should be timeless. - tests should be local0.100
scopereqlan rq/development/core.rqthese requirements describe the actual development of the reqlan language and tooling itself0.040
stackreqlan rq/development/core.rq- Requirements are documented with reqlan in the ["../../reqlan rq"] folder. - Language grammar truth is ["../../reqlan rq/language/syntax.rq"]; the default editor LSP is Rust ( `reqlan-lsp` ). - Langium in `@reqlan/language` remains a dual-parser oracle and the transitional `node` engine fallback. - VS Code extension host is in ["../../packages/extension"]; open-buffer features run in `crates/reqlan-lsp`. - vscode webviews are implemented with svelte - Extension build pipeline is documented in ["./build.rq"]0.045
succinctreqlan rq/development/core.rqmaximised meaning to character ratio.0.040
testingreqlan rq/development/core.rqtests should have comment references to the requirements they serve to test. per ["../extension/language/comment-references/functional-code-comment-references.rq"]0.061