frontend
Skill33 starsChanged 34 days agoMITView on GitHub
Implement and review the Cursor BYOK React/Tauri desktop frontend. Use for changes under apps/desktop involving routing, page layout, window chrome, settings UI, scrolling, virtualization, charts, themes, or frontend component architecture.
53 other projects use a version of this; 0 new projects in the last 4 weeks, against 1 the 4 before.
Adopted by
Cooling: 0 new projects took it in the last 4 weeks, 0× the 4 weeks before.thin data
Most recently taken up by
- nomorehappypath/nomorehappypaththeir own version, first seen Nov 15, 2026
- theopenco/llmgatewaytheir own version, first seen Nov 15, 2026
- speakeasy-api/gramtheir own version, first seen Nov 13, 2026
- Mazalucas/El-DT-Lightweight-Armytheir own version, first seen Nov 13, 2026
- notque/vexjoy-agenttheir own version, first seen Nov 10, 2026
- lucas-moraes/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use programming, backend and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DevNewbie1826Skillprogramming
MUST USE for work on Python, Rust, TypeScript, JavaScript, or Go source files and project manifests, and whenever a test or spec file is written, reshaped, reviewed, or deleted. Triggers: write or edit code; add, change, or delete a test; test authoring gate; junk tests; new project; Go HTTP service (gin lane); Bubble Tea TUI; CJK IME; Connect-Go RPC; sqlc or pgx; branded IDs; exhaustive matching; unsafe Rust; Miri; oversized file; refactoring; logging, log levels, structured logging, or observability; arena, allocator, bumpalo, const fn, const generics, compile-time programming, zero-allocation APIs, bitfields, repr, scope guards, errdefer-style cleanup, Zig-like patterns, zero-copy parsing, packed data, or FFI; Rust public API design or macros.
Also in 3 projects that use this
wewpellex21Skillbackend
Servers, routes, APIs, and backend architecture. Activated when Claude creates server-side code, API routes, or Express/Fastify/Next.js API handlers.
Also in 9 projects that use this
launch52-aiSkilldata
Generate data layer code (Freezed DTOs, repository implementations, data sources) from feature specifications or API references. Creates the bridge between domain entities and external data sources. Use after /domain to implement the data layer.
Also in 4 projects that use this
launch52-aiSkilldomain
Generate domain layer code (entities, enums, repository interfaces) from feature specifications. Creates pure Dart business logic with no external dependencies. Use after /feature-init to fill in the domain layer.
Also in 3 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 8 projects that use this
0xSeroSkillsecurity
Also in 9 projects that use this
Other versions53 projects use a version of this.
Word for word · 1
- leookun/cursor-byok★ 3.2k100% same
Edited · 0
None found.
Wrote their own version · 52
- langwatch/langwatch★ 5ksame name
- atopile/atopile★ 4ksame name
- theopenco/llmgateway★ 1.7ksame name
- notque/vexjoy-agent★ 450same name
- notque/claude-code-toolkit★ 448same name
- AlexPEClub/ai-coding-starter-kit★ 382same name
- OyadotAI/oya-browser★ 349same name
- speakeasy-api/gram★ 278same name
- ThePrimeagen/skills★ 234same name
- kid-sid/claude-spellbook★ 190same name
42 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cursor-prefix-stabilitySkill
- database-schemaSkill
- floating-uiSkill
- i18nSkill
- model-selectionSkill
- releaseSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
29 rules. 0 are common, 11 are distinctive, and 18 are very specific to this project.
0
Common
Most of the 46 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
18
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Treat the Rust management server as the single HTTP origin for the desktop UI.
- Very specific: line 14
Keep the /__byok-api__/ namespace reserved for this boundary:
- Distinctive: line 22
Use Tauri commands only for native desktop capabilities such as opening Terminal, tray integration, or operating-system actions.
- Distinctive: line 26
Keep Provider, Model, Call, Usage, and persisted settings state outside presentation components.
- Very specific: line 29
Keep App.tsx as the route composition root.
- Very specific: line 36
Keep the main scroll viewport full-height and position: relative.
- Very specific: line 38
Keep the menu Card fixed and reserve it with the content area's margin-left.
- Distinctive: line 39
Do not use child or section padding to create external spacing.
- Distinctive: line 40
Use a vertical flex layout with these invariants:
- Distinctive: line 44
Keep Header and Footer outside the scroll viewport.
- Distinctive: line 46
Keep macOS traffic-light space and the top fixed drag strip free of interactive controls.
- Distinctive: line 47
Avoid decorative brand text and explanatory copy when it does not help the user perform an action or interpret state.
- Very specific: line 51
Write component styles in SCSS and source every font-size from src/styles/_typography.scss.
- Very specific: line 52
Use base for normal UI text and ordinary titles, including title bars, panels, cards, and section headings.
- Very specific: line 53
Use xs only for secondary information.
- Very specific: line 58
Use components/layout/VirtualPage.tsx for vertically scrolling page content.
- Very specific: line 59
Use components/virtual/VirtualList.tsx for data collections and menus that can grow.
- Very specific: line 60
Treat ScrollArea as the low-level primitive owned by the virtual scrolling implementation.
- Very specific: line 61
Use the global scroll-shadow-top and scroll-shadow-bottom masks for scroll-edge shadows.
- Very specific: line 63
Do not use document scrolling, native page overflow: auto, or nested vertical scroll containers.
- Very specific: line 64
Ensure every flex/grid ancestor of a virtual viewport has min-height: 0 and the viewport has an explicit bounded height.
- Very specific: line 68
Use HashRouter for Tauri compatibility.
- Very specific: line 69
Keep / as the statistics dashboard and expose every primary page through the persistent menu in the shared AppLayout.
- Very specific: line 70
Use top-level routes for primary pages: /, /providers, /models, /calls, and /settings.
- Distinctive: line 71
Do not create separate Home and Settings shells or add a Home-switching control.
- Distinctive: line 72
Keep route content independent of the window Header and Footer.
- Very specific: line 76
Use ECharts through components/charts/EChart.tsx.
- Distinctive: line 78
Keep chart components declarative: accept domain data and construct an option without fetching or persisting data.
- Distinctive: line 90
Verify that Header and Footer remain fixed, only the virtual content viewport scrolls, settings navigation remains reachable at minimum …
“Common” is measured: kept by at least 6 in 10 of the 46 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cursor BYOK Frontend
Build on the components and theme system already present in apps/desktop. Preserve the Tauri HTTP boundary; frontend management features call /__byok-api__/api and never add IPC business APIs.
Desktop HTTP communication
- Treat the Rust management server as the single HTTP origin for the desktop UI. The main WebView and browser-opened detail pages must use
http://127.0.0.1:<dynamic-port>/__byok-api__/; do not load the main UI fromtauri://localhostor expose a second frontend origin. - Make every frontend management request relative to
/__byok-api__/api. Do not discover, inject, persist, or pass anapiOrigin, and do not construct management URLs from a fixed port. - Keep the
/__byok-api__/namespace reserved for this boundary:/__byok-api__/api/*is handled locally by the Rust management API.- Other
/__byok-api__/*paths are frontend documents, assets, modules, and development resources.
- In production, serve the frontend embedded by Tauri's
frontendDistthrough the Rust server. Reuse Tauri's asset resolver rather than bundling or copying a second set of frontend resources. - In development, let the Rust server reverse-proxy non-API
/__byok-api__/*requests to Vite. Preserve the request path and query string. Do not configure Vite to proxy management API requests back to Rust. - Configure Vite's base path as
/__byok-api__/so generated assets, module imports, and development client URLs stay under the reserved namespace. - Bind the development Vite server to an explicit loopback address compatible with the Rust proxy target; do not rely on
localhostresolving to the same IP family. - Open external detail pages with their normal loopback HTTP URL and hash route. Because the page and API are same-origin, do not add Tauri URL workarounds, API-origin query parameters, or CORS-dependent browser flows.
- Use Tauri commands only for native desktop capabilities such as opening Terminal, tray integration, or operating-system actions. Do not create IPC mirrors for HTTP business APIs.
Component boundaries
- Keep Provider, Model, Call, Usage, and persisted settings state outside presentation components.
- Let components receive business snapshots and dispatch actions. Local React state is allowed for transient UI behavior such as focus, open state, drag state, and input drafts.
- Split pages, layouts, charts, forms, and reusable controls into focused components. Do not collect an entire feature set in
App.tsx. - Keep
App.tsxas the route composition root.
Page layout
- Build every full-height page with
components/layout/PageLayout.tsx; do not hand-roll page shells with grid rows. - Put page-level commands and controls such as create, import, export, filtering, sorting, and view options in the shared page action region through
PageActions. Keep only operations that target one concrete list item, such as edit and delete, inside that item's row. Do not add duplicate action bars or panel-header controls inside page content. - Never render a title region above a data table or flat data list. Use the page title for context, keep column labels in the table header, place page-level controls in
PageActions, and wrap the table in a titlelessCard. A hierarchy label that identifies parent data in a grouped parent-child view is not a table title. - Keep the main scroll viewport full-height and
position: relative; place the page title and action region absolutely over it. - Reserve the absolute title/action region with
padding-topon the scroll content, never by shortening or offsetting the scroll viewport itself. - Keep the menu Card fixed and reserve it with the content area's
margin-left; do not place Header, menu, and content in a flow grid. - Do not use child or section padding to create external spacing. Use flex/grid gaps between siblings and margins or fixed offsets at container boundaries; the scroll-content top padding is reserved only for its absolute title/action overlay.
- Use a vertical flex layout with these invariants:
- Header:
flex: 0 0 auto. - Footer:
flex: 0 0 auto. - Content:
flex: 1 1 auto,min-height: 0, andoverflow: hidden.
- Header:
- Keep Header and Footer outside the scroll viewport. They must never grow or shrink with content.
- Apply macOS, Windows, and Linux window-corner safe-area variables only to edge chrome that can enter native rounded corners.
- Keep macOS traffic-light space and the top fixed drag strip free of interactive controls.
- Avoid decorative brand text and explanatory copy when it does not help the user perform an action or interpret state.
Typography
- Write component styles in SCSS and source every
font-sizefromsrc/styles/_typography.scss; never hardcode a font size in SCSS, React styles, or chart options. - Use
basefor normal UI text and ordinary titles, including title bars, panels, cards, and section headings. Do not increase a font merely because its element ish1orh2. - Use
xsonly for secondary information. Reservelgfor an explicitly oversized display title; do not use it for routine headings. - Audit all typography-token usages after changing the scale, not only raw numeric font sizes.
Scrolling and virtualization
- Use
components/layout/VirtualPage.tsxfor vertically scrolling page content. - Use
components/virtual/VirtualList.tsxfor data collections and menus that can grow. - Treat
ScrollAreaas the low-level primitive owned by the virtual scrolling implementation. Do not importScrollAreadirectly in pages or layouts. - Use the global
scroll-shadow-topandscroll-shadow-bottommasks for scroll-edge shadows. When a scroll content inset reserves an absolute overlay, source the top shadow distance from the same CSS variable as itspadding-top. - Model non-list pages as a short sequence of measurable top-level virtual sections.
- Do not use document scrolling, native page
overflow: auto, or nested vertical scroll containers. - Ensure every flex/grid ancestor of a virtual viewport has
min-height: 0and the viewport has an explicit bounded height.
Routing and pages
- Use
HashRouterfor Tauri compatibility. - Keep
/as the statistics dashboard and expose every primary page through the persistent menu in the sharedAppLayout. - Use top-level routes for primary pages:
/,/providers,/models,/calls, and/settings. - Do not create separate Home and Settings shells or add a Home-switching control.
- Keep route content independent of the window Header and Footer.
Charts
- Use ECharts through
components/charts/EChart.tsx. - Register only required ECharts Core charts, components, and renderers.
- Keep chart components declarative: accept domain data and construct an option without fetching or persisting data.
- Let
ResizeObserverresize the chart with its layout container and dispose the instance on unmount.
Validation
Run from apps/desktop:
npm run check
npm run tauri:build -- --debug --no-bundleVerify that Header and Footer remain fixed, only the virtual content viewport scrolls, settings navigation remains reachable at minimum window size, and macOS controls stay outside rounded-corner and traffic-light unsafe regions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

