en un clic
rune-langium
rune-langium contient 171 skills collectées depuis pradeepmouli, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
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
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.
Documentation site and generated agent skills for rune-langium APIs
Router skill for the rune-langium monorepo. Use it to choose the right package skill before working in core, cli, lsp-server, codegen, or visual-editor.
Router skill for the rune-langium monorepo. Use it to choose the right package skill before working in core, cli, lsp-server, codegen, or visual-editor.
dockview-react panel layout library. Use when building multi-panel IDE-style layouts, implementing dockable/floatable panels, persisting layout state, or debugging dockview. Triggers on DockviewReact, IDockviewPanelProps, DockviewApi, DockviewReadyEvent, addPanel, fromJSON, toJSON, onReady, components prop.
Create baseline documentation for the project, establishing context for all future specs.
Create a bug fix workflow with regression test and minimal documentation.
Validate and reorganize spec-kit artifacts with proper numbering and structure
Initiate a feature deprecation workflow with phased sunset process (warnings -> disabled -> removed).
Create a minor enhancement workflow with condensed single-document planning.
Create an emergency hotfix workflow with expedited process and mandatory post-mortem.
Incorporate documents into an existing or new workflow and advance stages intelligently
Sync linked issue status for after_implement hook.
Sync linked issue status for after_plan hook.
Sync linked issue status for after_specify hook.
Sync linked issue status for after_tasks hook.
Sync linked issue status for before_implement hook.
Sync linked issue status for before_plan hook.
Sync linked issue status for before_specify hook.
Sync linked issue status for before_tasks hook.
Modify an existing feature with impact analysis and backward compatibility tracking.
Convert development phases into individual GitHub issues for better tracking and collaboration.
Create a refactoring workflow with metrics tracking and behavior preservation validation.
Review completed implementation work and update task status.
Generate a deeply-reasoned, implementation-ready task breakdown for the current spec-kit feature using extended analysis.
Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.
Create baseline documentation for the project, establishing context for all future specs.
Create a bug fix workflow with regression test and minimal documentation.
Validate and reorganize spec-kit artifacts with proper numbering and structure
Initiate a feature deprecation workflow with phased sunset process (warnings -> disabled -> removed).
Create a minor enhancement workflow with condensed single-document planning.
Create an emergency hotfix workflow with expedited process and mandatory post-mortem.
Incorporate documents into an existing or new workflow and advance stages intelligently
Sync linked issue status for after_implement hook.