meridian: Skill for Claude Code

.claude/skills/meridian-ui/SKILL.md

meridian-ui is a skill for Claude Code from Meridiona/meridian. It costs 44 tokens per session (1,543 once invoked), scanned C, original, MIT.

Development guidance for the Meridian dashboard, a Next.js interface exported as static files and displayed inside a Tauri desktop app's tray window. The interface calls Rust code through Tauri instead of using a web server or API routes.

In plain words
What is it for?
Use it to develop, build, type-check, test, and debug the dashboard with React, TypeScript, Tailwind CSS, Next.js, Tauri, and the Bun test runner.
Why use it?
It prevents debugging and build mistakes caused by treating the dashboard like a normal server-backed Next.js site. It explains the project's required tools, structure, and runtime limits.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

This is Meridiona/meridian's own configuration. It tells Claude Code how to work on meridian itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything meridian configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Meridiona/meridian. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Meridiona/meridian/main/.claude/skills/meridian-ui/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Meridiona/meridian

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for meridian-ui

README.md
[![agentmods](https://agentmods.dev/badge/skills/meridiona/meridian/meridian-ui/github.svg)](https://agentmods.dev/skills/meridiona/meridian/meridian-ui)
Your own site
<a href="https://agentmods.dev/skills/meridiona/meridian/meridian-ui"><img src="https://agentmods.dev/badge/skills/meridiona/meridian/meridian-ui/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for meridian-ui

Your own site · 80×15
<a href="https://agentmods.dev/skills/meridiona/meridian/meridian-ui"><img src="https://agentmods.dev/badge/skills/meridiona/meridian/meridian-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,543 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.01543
Opus 5 $0.00022 $0.00772
Sonnet 5 $0.00009 $0.00309
Haiku 4.5 $0.00004 $0.00154

Measured 11d ago against content hash bf50652b3477, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade C, and why

meridian-ui scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

produces an `Invalid distDirRoot` panic; `rm -rf .next` from `ui/` clears it.
.claude/skills/meridian-ui/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Meridian UI Skill

The dashboard is a Next.js static export (output: 'export'ui/out) that runs inside the Tauri tray webview. There is no Node server at runtime and there are no /api route handlers - ui/app/api/ does not exist, and better-sqlite3 is not a dependency of ui/. Everything that used to be a route handler is now Rust reached over Tauri invoke.

If you are looking for the old route-handler / @/lib/db / @/lib/category-colors world, it was removed in the Next fold. See CLAUDE.md → "Dashboard → Tauri fold".

Stack

  • Next.js 16 (App Router), React 19
  • TypeScript - strict, no any without a justifying comment
  • Tailwind CSS 4 - utility classes, no CSS modules
  • bun:test - test runner for ui/__tests__/

Dev & Build

cd ui

npm run dev        # dev server on :3939 (turbopack; NODE_ENV is unset deliberately)
npm run build      # production build + copies the tray popover into out/
npm run typecheck  # tsc --noEmit
bun test           # dashboard tests

Two things worth knowing before you debug either:

  • Never run next dev with NODE_ENV set - that is why the script is env -u NODE_ENV next dev. A stale .next after a branch or config switch produces an Invalid distDirRoot panic; rm -rf .next from ui/ clears it.
  • The popover works under tauri dev too. tauri.conf.json's beforeDevCommand runs node scripts/sync-popover.mjs dev, which copies tray/src/ into ui/public/popover/, and next dev serves public/ at the root - so /popover/index.html resolves. The build does the same into out/popover/. If it 404s, the sync step did not run: start the tray with npm run tauri dev from tray/ rather than starting next dev by hand.

Reaching data: the bridge, never fetch

All data crosses to Rust through ui/lib/bridge.ts:

import { load, mutate, subscribe } from '@/lib/bridge'

const today = await load<TodayResponse>('/today', 'get_today')        // read
await mutate('/settings', 'save_settings', body, 'PATCH')             // write
const stop = subscribe<Health>('/health', 'get_health', 'health', cb) // live stream

Read the full file on GitHub · 148 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 148 lines · 44 tokens per session scan C bf50652b3477

Subscribe to this mod's changes

meridian-ui is a skill published in the GitHub repository Meridiona/meridian (336 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 1,543 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

bug-fix

Regression-first workflow for fixing a defect whose cause is known. Reproduce the confirmed defect, fix the root cause minimally, protect it with a regression test, and verify. If the root cause is still unknown, use the debugging skill first.

thixpin/pitway · 52 tokens

diagnosing-bugs

Diagnose bugs with a reproducible red signal, minimized case, ranked hypotheses, and regression test.

MoonTzai/folderbridge-mcp · 25 tokens

systematic-debugging

Systematic debugging approach for errors, test failures, and unexpected behavior. Use when encountering bugs, test failures, errors, or when debugging is needed. Prevents common anti-patterns like random fixes, skipping root cause analysis, and thrashing.

shrwnsan/vibekit-claude-plugins · 54 tokens

diagnose

A structured troubleshooting workflow for complex software bugs. TDD here means test-driven development; this skill defines the diagnosis phase, including gathering bug details, forming several possible causes, and checking them.

morodomi/dev-crew · 42 tokens

build-test

Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.

nexu-io/open-design · 31 tokens

bug-fixing

Fix defects in the Composio SDK repository with focused reproduction, root-cause analysis, regression tests, and narrow verification. Use when the user reports a bug, failing test, CI regression, runtime defect, or incorrect SDK behavior. Do not use for new feature design or broad refactors.

ComposioHQ/composio · 63 tokens