Agent skill

Cross Platform Tauri UI

Cross-platform UI styling for MarkerOn Tauri app (macOS WKWebView vs Windows WebView2).

Install Cross Platform Tauri UI

skills CLI

$ npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install ifer47/markeron cross-platform-tauri-ui --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/ifer47/markeron.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/cross-platform-tauri-ui .claude/skills/cross-platform-tauri-ui && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "cross-platform-tauri-ui" agent skill from https://github.com/ifer47/markeron/tree/master/.cursor/skills/cross-platform-tauri-ui into .claude/skills/cross-platform-tauri-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-tauri-ui", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/ifer47/markeron/tree/master/.cursor/skills/cross-platform-tauri-ui

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ifer47/markeron cross-platform-tauri-ui --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ifer47/markeron.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/cross-platform-tauri-ui .agents/skills/cross-platform-tauri-ui && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cross-platform-tauri-ui" agent skill from https://github.com/ifer47/markeron/tree/master/.cursor/skills/cross-platform-tauri-ui into .agents/skills/cross-platform-tauri-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-tauri-ui", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ifer47/markeron cross-platform-tauri-ui --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ifer47/markeron.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/cross-platform-tauri-ui .cursor/skills/cross-platform-tauri-ui && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cross-platform-tauri-ui" agent skill from https://github.com/ifer47/markeron/tree/master/.cursor/skills/cross-platform-tauri-ui into .cursor/skills/cross-platform-tauri-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-tauri-ui", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/ifer47/markeron.git --path .cursor/skills/cross-platform-tauri-ui

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ifer47/markeron cross-platform-tauri-ui --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ifer47/markeron.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/cross-platform-tauri-ui .gemini/skills/cross-platform-tauri-ui && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "cross-platform-tauri-ui" agent skill from https://github.com/ifer47/markeron/tree/master/.cursor/skills/cross-platform-tauri-ui into .gemini/skills/cross-platform-tauri-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-tauri-ui", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install ifer47/markeron cross-platform-tauri-ui

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ifer47/markeron.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/cross-platform-tauri-ui .github/skills/cross-platform-tauri-ui && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "cross-platform-tauri-ui" agent skill from https://github.com/ifer47/markeron/tree/master/.cursor/skills/cross-platform-tauri-ui into .github/skills/cross-platform-tauri-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-tauri-ui", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ifer47/markeron cross-platform-tauri-ui --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ifer47/markeron.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/cross-platform-tauri-ui .opencode/skills/cross-platform-tauri-ui && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cross-platform-tauri-ui" agent skill from https://github.com/ifer47/markeron/tree/master/.cursor/skills/cross-platform-tauri-ui into .opencode/skills/cross-platform-tauri-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-platform-tauri-ui", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: cross-platform-tauri-ui
GitHub stars: 1.2k
Token cost: ~2k tokens
SKILL.md length: 703 words
Files: 1
Skills in repo: 2
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Cross-platform UI styling for MarkerOn Tauri app (macOS WKWebView vs Windows WebView2).

Works in 3 steps: Different web engines (main cause) → Tailwind opacity modifiers are the trigger → Transparent overlay windows (macOS-only…
Styling Vue/CSS
SKILL.md covers Why Mac and Windows look…, Project convention: semantic…, Development workflow and Anti-patterns, plus 1 more section
Calls rg

What it does

Cross Platform Tauri UI is an agent skill from ifer47/markeron. Cross-platform UI styling for MarkerOn Tauri app (macOS WKWebView vs Windows WebView2). Use when styling Vue/CSS, fixing Mac/Windows visual differences, working on settings window, overlay panels, or Tailwind opacity issues on WebKit.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering CSS and styling. It works with Tauri, Tailwind CSS, macOS and Vue.js. The repository describes itself as: Lightweight (~1.5 MB) open-source screen annotation with click-through mode and keyboard-first shortcuts. For demos, teaching, meetings & screen recording. Windows, macOS. The licence is MIT.

When your agent uses it

Styling Vue/CSS
Fixing Mac/Windows visual differences
Working on settings window
Tailwind opacity issues on WebKit

Example prompts

“/cross-platform-tauri-ui”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Different web engines (main cause)
Tailwind opacity modifiers are the trigger
Transparent overlay windows (macOS-only extra issues)

What it can do on your machine

Read from SKILL.md and the folder at commit 2cd0ef1. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- rg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cross Platform Tauri UI loads about 2k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 703 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~65
When it runs · the whole SKILL.md, loaded when a task matches: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ifer47/markeron at commit 2cd0ef1, republished under its MIT licence (© ifer47). 703 words, ~1,961 tokens.

Download SKILL.mdSave it as .claude/skills/cross-platform-tauri-ui/SKILL.md (or your agent's skills folder).

name: cross-platform-tauri-ui
description: Cross-platform UI styling for MarkerOn Tauri app (macOS WKWebView vs Windows WebView2). Use when styling Vue/CSS, fixing Mac/Windows visual differences, working on settings window, overlay panels, or Tailwind opacity issues on WebKit.

Cross-Platform Tauri UI (MarkerOn)

Why Mac and Windows look different

1. Different web engines (main cause)

Platform	Engine	Used by
macOS	WKWebView (WebKit)	Tauri WRY
Windows	WebView2 (Chromium)	Tauri WRY

Same Tailwind class can produce different pixels. This is not a "Mac bug" in app logic — it is compositing / alpha blending behavior in WebKit vs Chromium.

2. Tailwind opacity modifiers are the trigger

Tailwind v4 generates classes like text-white/45 → color: rgb(255 255 255 / 45%).

On macOS WebKit these often fail in predictable ways:

Borders (border-white/5, /8): render as harsh white outlines
Text (text-white/20–/70): render paler than intended; low contrast on #1e1e20
Backgrounds (bg-white/4, /10): nearly transparent; active states disappear
Semantic colors with alpha (text-green-400/70, bg-accent/30): hue/saturation lost; green looks grey

Safe: solid colors — text-white, text-accent, bg-[#1e1e20], hex/rgb in inline styles.

3. Transparent overlay windows (macOS-only extra issues)

The drawing overlay is a transparent Tauri window. WKWebView additionally needs:

overlay-panel-surface (isolation, backface-visibility, contain:paint)
Explicit panel background on .overlay-panel (not relying on semi-transparent Tailwind bg)
Tauri: set_background_color for overlay; settings window uses macos.rs dark background + transparent title bar
Do not call Objective-C on WryWebView inner handle (crashes)

Project convention: semantic rgba classes

All cross-platform UI colors live in src/style.css as named classes with explicit rgba().

Settings window

Class	Purpose
`settings-text-brand/title/heading/label/value/muted/subtle/faint/dim/footer/body`	Typography
`settings-text-accent`, `settings-text-accent-link`	Links, accent text
`settings-status-success`	Green "up to date"
`settings-msg-success`, `settings-msg-error`	Toast messages
`settings-nav-item`, `settings-nav-item--active`	Sidebar tabs
`settings-toggle-on`, `settings-toggle-off`	Switches
`settings-card`, `settings-card-row`, `settings-card-desc`, `settings-card--active`	Cards
`settings-card--popover-host`	Card that hosts a dropdown/tooltip — overrides card `overflow`
`settings-btn-accent-outline`, `settings-btn-accent-primary`	About page buttons
`settings-row-hover`, `settings-row-hover-strong`	List row hover
`settings-locale-item`, `settings-locale-item--active`	Language dropdown
`settings-app-icon`	About logo container
`settings-progress-track`, `settings-progress-fill`	Update progress

Overlay panels (space panel, quick colors)

Class	Purpose
`overlay-panel`, `overlay-panel--compact`	Panel shell
`overlay-panel-surface`	WebKit corner bleed fix
`overlay-text-section/hint/label/body/secondary/separator/caption/key*`	Text
`overlay-tool-btn`, `overlay-tool-btn--active`	Tool buttons
`overlay-width-btn`, `overlay-width-btn--active`, `overlay-width-line*`	Stroke width
`ui-divider-h/v/b`, `ui-kbd`, `ui-select`, `ui-popover`, `ui-segment*`	Shared controls
`color-swatch-ring*`, `color-picker-ring`, `color-dot-ring`	Color UI

All platforms use the same rgba() values — do not add Mac-only text opacity overrides.

Show full SKILL.md (383 more words)Show less

Settings cards and popovers (overflow)

.settings-card uses overflow: hidden in style.css so rounded borders clip cleanly on macOS WebKit. That clips any child with position: absolute or fixed (dropdowns, tooltips) and sibling cards below can paint over the overflow.

Rules:

Any card that contains a dropdown, tooltip, or popover must also use settings-card--popover-host (overflow: visible).
While the popover is open, raise the host card above siblings (e.g. relative z-20 when open) so the menu is not covered by the next card.
Prefer Teleport to body for new floating UI if it must survive scroll containers (overflow-y-auto on tab content) — see GeneralTab.vue language select for the card-host pattern; Teleport is the more robust default for new work.

Before changing a shared container class (.settings-card, .overlay-panel, scroll wrappers), grep for floating children:

bash

rg "absolute|fixed|ui-popover|ui-tooltip|Teleport" src/components/settings/

Container CSS checklist — these on a parent often break popovers; re-test open state after adding any of them:

Property	Risk
`overflow: hidden` / `auto`	Clips absolute/fixed descendants
`transform`	New stacking context; z-index surprises
`contain: paint`	Clips overflow
`isolation: isolate`	Stacking context; siblings may cover popover

Manual QA after card/style refactors (both platforms, ~2 min):

Settings → 常规: language dropdown fully visible, can switch locale
Settings → 快捷键: info tooltip visible on hover
Scroll the tab if applicable; popover still usable

Development workflow

Adding new UI

Check if an existing semantic class fits.
If not, add one class (or modifier) in style.css with rgba().
Use the class in Vue — no text-white/XX or border-white/XX in templates.
For Help-tab-style scoped CSS, prefer rgba() in <style scoped> (already done in SettingsView.vue help section).

Fixing Mac-only reports

Confirm the component uses Tailwind opacity → migrate to semantic class.
If borders: use ui-divider-* or settings-card patterns.
Use explicit rgba() at the same values on all platforms — do not add Mac-only opacity bumps.
Verify Windows unchanged (rgba values match original Tailwind intent).

Pre-commit grep

bash

rg "border-white/|text-white/|bg-white/|from-accent/|to-accent/|bg-accent/|text-accent/|border-accent/|text-green-|bg-emerald-|text-red-.*/|bg-red-.*/" src/components

Zero hits in src/components is the target for new work.

Manual test matrix

Surface	macOS	Windows
Settings → 常规	Toggles, language dropdown open, labels	Same
Settings → 关于	Green status, nav highlight, card borders	Same
Space → settings panel	Text, borders, tool active state	Same
Right-click color panel	Caption text, swatch rings	Same

Anti-patterns

vue

<!-- BAD: WebKit opacity issues -->
<span class="text-white/45">Label</span>
<div class="border border-white/8 bg-white/4">

<!-- GOOD -->
<span class="settings-text-muted">Label</span>
<div class="settings-card">

vue

<!-- BAD: dropdown inside .settings-card without popover-host -->
<div class="settings-card">
  <div class="relative">
    <div class="absolute ...">...</div>
  </div>
</div>

<!-- GOOD: allow popover to escape card; raise z-index when open -->
<div class="settings-card settings-card--popover-host" :class="{ 'relative z-20': open }">
  ...
</div>

vue

<!-- BAD: status color with alpha -->
<span class="text-green-400/70">Up to date</span>

<!-- GOOD -->
<span class="settings-status-success">Up to date</span>

css

/* GOOD: new semantic token */
.settings-text-new-role {
  color: rgba(255, 255, 255, 0.55);
}

src/style.css — all semantic UI classes
src-tauri/src/macos.rs — settings window background & title bar
index.html — html.settings for settings route

Files

Just SKILL.md in .cursor/skills/cross-platform-tauri-ui of ifer47/markeron.

Open the folder on GitHubat commit 2cd0ef1

Compare with similar skills

Cross Platform Tauri UI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cross Platform Tauri UI compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cross Platform Tauri UI this skillifer47/markeron	1.2k	—	~2k	Automated safety check: Pass	MIT	yesterday
Vuetify Skilldlogue/vite-vuetify-ts-starter	181	1 repos	~1.9k	Automated safety check: Pass	MIT	6 days ago
Vue Componentsscalar/scalar	16k	—	~886	Automated safety check: Pass	MIT	today
Vue Component Developmentgdarko/laravel-vue-starter	145	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Rasengan Configrasengan-dev/rasenganjs	124	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Frontend Code ReviewProgrammerAnthony/Expert-Coding-Harness	235	—	~614	Automated safety check: Pass	MIT	5 mo ago

Similar skills

Vuetify Skilld
logue/vite-vuetify-ts-starter
Vue Material Component Framework. An agent skill from logue/vite-vuetify-ts-starter.
181 GitHub starsUsed in 1 repo~1.9k tokens
Frontend & DesignAuto-check passed
Vue Components
scalar/scalar
Build Vue 3 components with TypeScript and Tailwind using clean structure, composable logic, accessibility, and maintainable patterns.
16k GitHub stars~886 tokensUpdated today
Frontend & DesignAuto-check passed
Vue Component Development
gdarko/laravel-vue-starter
Activate when creating or modifying Vue 3 components, pages, layouts, stores, or services in the frontend.
145 GitHub stars~1.1k tokensUpdated 6 mo ago
Frontend & DesignAuto-check passed
Rasengan Config
rasengan-dev/rasenganjs
Project configuration and rendering mode patterns for Rasengan.js.
124 GitHub stars~1.1k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Frontend Code Review
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 用户需要审查前端代码（React/Vue/Next.js/TypeScript/Tailwind等）、检查代码质量、性能问题、可维护性、安全漏洞、最佳实践落地时。触发场景：前端代码评审、前端代码优化、React/Vue代码检查、TypeScript代码审查、前端性能优化、前端安全审计、前端代码规范检查。
235 GitHub stars~614 tokensUpdated 5 mo ago
Frontend & DesignAuto-check passed
Dokan Frontend Dev
getdokan/dokan
Add or modify Dokan frontend code (React, TypeScript, Vue, Tailwind).
288 GitHub stars~1.9k tokensUpdated today
Frontend & DesignAuto-check passed

Questions about Cross Platform Tauri UI

What does Cross Platform Tauri UI do?

Cross-platform UI styling for MarkerOn Tauri app (macOS WKWebView vs Windows WebView2). Cross Platform Tauri UI is an agent skill from ifer47/markeron. Cross-platform UI styling for MarkerOn Tauri app (macOS WKWebView vs Windows WebView2).

When should I use Cross Platform Tauri UI?

Cross Platform Tauri UI fits situations like: styling Vue/CSS; fixing Mac/Windows visual differences; working on settings window; tailwind opacity issues on WebKit.

How do I install Cross Platform Tauri UI in Claude Code?

Run `npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a claude-code`. Or copy the skill folder (.cursor/skills/cross-platform-tauri-ui in ifer47/markeron) into .claude/skills/cross-platform-tauri-ui in your project. Claude Code loads it when a task matches its description.

How do I install Cross Platform Tauri UI in Codex?

Run `npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a codex`. Or copy the skill folder (.cursor/skills/cross-platform-tauri-ui in ifer47/markeron) into .agents/skills/cross-platform-tauri-ui in your project. Codex loads it when a task matches its description.

Can I use Cross Platform Tauri UI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ifer47/markeron --skill cross-platform-tauri-ui -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-platform-tauri-ui, .gemini/skills/cross-platform-tauri-ui, .github/skills/cross-platform-tauri-ui and .opencode/skills/cross-platform-tauri-ui in your project.

What does Cross Platform Tauri UI need to run?

Going by SKILL.md and its folder, Cross Platform Tauri UI needs the command-line tools its instructions call (rg).

Does Cross Platform Tauri UI access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cross Platform Tauri UI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cross Platform Tauri UI use?

Cross Platform Tauri UI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cross Platform Tauri UI use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cross Platform Tauri UI?

Skills that share tags, products or a category with Cross Platform Tauri UI: Vuetify Skilld (logue/vite-vuetify-ts-starter, 181 stars), Vue Components (scalar/scalar, 16k stars), Vue Component Development (gdarko/laravel-vue-starter, 145 stars) and Rasengan Config (rasengan-dev/rasenganjs, 124 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cross Platform Tauri UI?

ifer47 (a GitHub user) maintains it in ifer47/markeron, which has 1,165 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.

Source: ifer47/markeron on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Cross Platform Tauri UI

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Cross-Platform Tauri UI (MarkerOn)

Why Mac and Windows look different

1. Different web engines (main cause)

2. Tailwind opacity modifiers are the trigger

3. Transparent overlay windows (macOS-only extra issues)

Project convention: semantic rgba classes

Settings window

Overlay panels (space panel, quick colors)

Settings cards and popovers (overflow)

Development workflow

Adding new UI

Fixing Mac-only reports

Pre-commit grep

Manual test matrix

Anti-patterns

Related files

Files

Compare with similar skills

Similar skills

Vuetify Skilld

Vue Components

Vue Component Development

Rasengan Config

Frontend Code Review

Dokan Frontend Dev

More from ifer47/markeron

Tauri Config Ipc

Related

Questions about Cross Platform Tauri UI