القائمة
Documentation site and generated agent skills for rune-langium APIs
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review a production UX checkout harness run against the deployed Studio (daikonic). Use after `pnpm --filter @rune-langium/studio run test:prod-ux` (or test:prod-smoke) completes, when the user asks to review/triage a prod checkout run, or when a nightly prod-ux artifact needs auditing. Consumes report/run-manifest.json + screenshots + traces and produces a severity-ranked UX review with per-journey verdicts.
Documentation site and generated agent skills for rune-langium APIs Use when: Validating a single `.rosetta` file or snippet in memory.
Documentation site and generated agent skills for rune-langium APIs Use when: Embedding a Rune DSL language server in a web application via WebSocket.
Documentation site and generated agent skills for rune-langium APIs Use when: Rendering two or more `RuneTypeGraph` components simultaneously (different....
Runtime <ZodForm> renderer for Zod v4 schemas Use when: You need form rendering in storybook, playgrounds, or low-traffic admin UIs —.... Also: zod, zod-v4, react, forms, form-generation, react-hook-form, schema-driven, dynamic-forms, form-renderer, hookform-resolver, zod-form-renderer.
Vite plugin for zod-to-form — transforms ?z2f imports into generated form components and optionally replaces <ZodForm> JSX call sites with generated components at build time Use when: You want `import SignupForm from './signup.schema?z2f'` to Just Work in a.... Also: vite, vite-plugin, zod, zod-v4, codegen, forms, form-generation, schema-driven, react-hook-form, build-plugin, jsx-transform.
| description | Documentation site and generated agent skills for rune-langium APIs |
| name | rune-langium-codegen |
Documentation site and generated agent skills for rune-langium APIs
Spec 021 Phase 2's subpath restructure ("CLEAN FLIP") splits this package's public API by direction — nothing in it is genuinely shared between the two, so the main barrel exports nothing:
@rune-langium/codegen/export — the outbound (Rune → target-language)
surface: generate(), generatePreviewSchemas(), every emitter
contract/option type, TARGET_DESCRIPTORS, etc.@rune-langium/codegen/import — the inbound (source → Rune) surface:
importModel(), SourceModel/ConstraintIR types, the CLI's
runImport, and import diagnostics.@rune-langium/codegen/rosetta — UNCHANGED: the shared, browser-safe
.rosetta render-core consumed by both directions (the outbound
emitters render Rune AST to .rosetta text; the inbound importer
renders its built AST-shaped nodes the same way).Import from the subpath that matches what you need; do not add exports
here unless a symbol is genuinely used by both /export and /import
(as of this restructure, nothing is — /rosetta already covers the one
case that legitimately spans both directions).