Instructions file GitHub Copilot
Copilot instructions for emporix/md-module-template, covering emporix frontend — agent rules index, project, directory map, generic rules (from frontend-ai-rules) and project-specific rules.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering core conventions, technology stack, file naming, imports (order) and code style.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering api & service layer, structure & location, configuration, types and error handling.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering extension module template, overrides (this project wins over global rules), host integration, standalone local development and project config (vite.config.ts).
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering git workflow, branches, commits, before commit and merging to master.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering internationalization (i18n), setup, usage in components, key conventions and pluralization and formatting.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering module federation, vite config, entry point, provider hierarchy and local dev.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering performance, memoization, code splitting, data fetching and lists and rendering.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering primereact, menus and general.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering testing, framework, helper tests, component tests and run.
Instructions file GitHub Copilot
Instructions for emporix/md-module-template, covering ui components, structure, example: presentational dialog, example: container with local ui state + confirmation and example: section component props.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: