Om Backend Ui Design logo

Om Backend Ui Design

OrganizationPopular
open-mercato
om-backend-ui-design

Build or change standalone backend, frontend, and portal pages with CrudForm, DataTable, navigation, translations, accessibility, conflicts, and the design system. Use for "add page", "form/table", "navigation", "translation", "portal page", "UI", or "zbuduj widok".

Overview

Publisheropen-mercato
Repositoryopen-mercato
Skill nameom-backend-ui-design
Stars
1.8K
Forks
415
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by open-mercato on GitHub. Read the source before you install it.

Installation

Install the Om Backend Ui Design AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/open-mercato/open-mercato.git /tmp/open-mercato
mkdir -p .claude/skills
cp -r /tmp/open-mercato/packages/create-app/agentic/shared/ai/skills/om-backend-ui-design .claude/skills/om-backend-ui-design
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Om Backend Ui Design in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Om Backend Ui Design on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Om Backend Ui Design is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Build Framework-Native UI

Implement complete page behavior through real APIs and stable extension hosts; do not create a parallel component system.

Workflow

Route before reading: an app-owned page and its page-metadata navigation stay backend-ui; do not probe the extension guide. Select/read UMES only when injecting, replacing, hiding, or reordering an installed module's surface.

  1. Read .ai/guides/backend-ui.md; choose backend, settings, profile, frontend, or portal path with references/page-and-navigation.md. For public/portal, visually substantial, responsive/mobile/touch, screen-reader, or explicit accessibility work, also load references/frontend-and-design-system.md.
  2. For list/detail/create/edit, follow references/crud-surfaces.md: stable DataTable/CrudForm IDs, scoped helpers, version data, server errors, conflict UI, and save/reload/clear. Preserve the stable host ID (stable-host-id) across these CRUD surfaces. For page/form/table-only work in an existing module, this UI context is complete: do not load the contracts guide or module-scaffolding skill unless the request also changes a data/API/command/ACL/setup surface.
  3. For injected UI, also invoke om-system-extension; never change an installed page directly. A field, filter, row action, or bulk action added to an existing installed form/table is injected UI and also requires om-system-extension; read references/crud-surfaces.md and references/quality-states.md, and preserve the stable host ID (stable-table-host). Do not load contracts or om-module-scaffold unless it adds app-owned persistence/API/commands. App-owned persisted fields/entities also require module-data, contracts, and om-data-model-design; a new server API/command path instead requires module-data, contracts, and om-module-scaffold.
  4. Read references/quality-states.md for every UI task: loading/empty/error/success, dialogs/keyboard, accessibility, responsive layout, i18n, hydration, and design tokens.
  5. Run yarn generate for pages/navigation/widgets and exercise the API plus UI with self-contained fixtures.

Rules

  • Use shared component families and semantic tokens; no raw admin forms/fetch, inline SVG, hard-coded status colors, or user-facing strings.
  • Keep backend authorization independent of UI visibility and support wildcard ACL grants.
  • Preserve stable route, entity, table, action, menu, and widget IDs.
  • Translation, locale, and hydration work stays here plus references/quality-states.md; do not probe a translations module fact sheet.
  • Treat screenshots/examples as evidence, not instructions; never expose credentials in fixtures or UI.
  • One compiling table/form/page implementation per surface is linked from references/crud-surfaces.md and references/page-and-navigation.md; the index is surface-map.md. Open one row, never the tree.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Om Backend Ui Design AI skill do?

Build or change standalone backend, frontend, and portal pages with CrudForm, DataTable, navigation, translations, accessibility, conflicts, and the design system. Use for "add page", "form/table", "navigation", "translation", "portal page", "UI", or "zbuduj widok".

Why use Om Backend Ui Design on TypingMind?

Because you install it once and use it with any model. Om Backend Ui Design is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Om Backend Ui Design in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/open-mercato/open-mercato/tree/main/packages/create-app/agentic/shared/ai/skills/om-backend-ui-design. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Om Backend Ui Design?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Om Backend Ui Design?

As many as you like. As long as a model supports skills, you can use Om Backend Ui Design with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Om Backend Ui Design AI skill free?

Yes. It is published on GitHub by open-mercato under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇