agentleFS
haxsdhaxsd/haxsd-byok/.agents/skills/frontend/SKILL.md

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

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 1 new projectWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

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.
  • DevNewbie1826Skill

    programming

    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

  • wewpellex21Skill

    backend

    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-aiSkill

    data

    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-aiSkill

    domain

    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

  • AnthropicSkill

    architecture

    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

  • 0xSeroSkill

    security

    Also in 9 projects that use this

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
  1. Very specific:

    Treat the Rust management server as the single HTTP origin for the desktop UI.

    line 12
  2. Very specific:

    Keep the /__byok-api__/ namespace reserved for this boundary:

    line 14
  3. Distinctive:

    Use Tauri commands only for native desktop capabilities such as opening Terminal, tray integration, or operating-system actions.

    line 22
  4. Distinctive:

    Keep Provider, Model, Call, Usage, and persisted settings state outside presentation components.

    line 26
  5. Very specific:

    Keep App.tsx as the route composition root.

    line 29
  6. Very specific:

    Keep the main scroll viewport full-height and position: relative.

    line 36
  7. Very specific:

    Keep the menu Card fixed and reserve it with the content area's margin-left.

    line 38
  8. Distinctive:

    Do not use child or section padding to create external spacing.

    line 39
  9. Distinctive:

    Use a vertical flex layout with these invariants:

    line 40
  10. Distinctive:

    Keep Header and Footer outside the scroll viewport.

    line 44
  11. Distinctive:

    Keep macOS traffic-light space and the top fixed drag strip free of interactive controls.

    line 46
  12. Distinctive:

    Avoid decorative brand text and explanatory copy when it does not help the user perform an action or interpret state.

    line 47
  13. Very specific:

    Write component styles in SCSS and source every font-size from src/styles/_typography.scss.

    line 51
  14. Very specific:

    Use base for normal UI text and ordinary titles, including title bars, panels, cards, and section headings.

    line 52
  15. Very specific:

    Use xs only for secondary information.

    line 53
  16. Very specific:

    Use components/layout/VirtualPage.tsx for vertically scrolling page content.

    line 58
  17. Very specific:

    Use components/virtual/VirtualList.tsx for data collections and menus that can grow.

    line 59
  18. Very specific:

    Treat ScrollArea as the low-level primitive owned by the virtual scrolling implementation.

    line 60
  19. Very specific:

    Use the global scroll-shadow-top and scroll-shadow-bottom masks for scroll-edge shadows.

    line 61
  20. Very specific:

    Do not use document scrolling, native page overflow: auto, or nested vertical scroll containers.

    line 63
  21. Very specific:

    Ensure every flex/grid ancestor of a virtual viewport has min-height: 0 and the viewport has an explicit bounded height.

    line 64
  22. Very specific:

    Use HashRouter for Tauri compatibility.

    line 68
  23. Very specific:

    Keep / as the statistics dashboard and expose every primary page through the persistent menu in the shared AppLayout.

    line 69
  24. Very specific:

    Use top-level routes for primary pages: /, /providers, /models, /calls, and /settings.

    line 70
  25. Distinctive:

    Do not create separate Home and Settings shells or add a Home-switching control.

    line 71
  26. Distinctive:

    Keep route content independent of the window Header and Footer.

    line 72
  27. Very specific:

    Use ECharts through components/charts/EChart.tsx.

    line 76
  28. Distinctive:

    Keep chart components declarative: accept domain data and construct an option without fetching or persisting data.

    line 78
  29. Distinctive:

    Verify that Header and Footer remain fixed, only the virtual content viewport scrolls, settings navigation remains reachable at minimum …

    line 90

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 from tauri://localhost or expose a second frontend origin.
  • Make every frontend management request relative to /__byok-api__/api. Do not discover, inject, persist, or pass an apiOrigin, 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 frontendDist through 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 localhost resolving 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.tsx as 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 titleless Card. 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-top on 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, and overflow: hidden.
  • 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-size from src/styles/_typography.scss; never hardcode a font size in SCSS, React styles, or chart options.
  • Use base for normal UI text and ordinary titles, including title bars, panels, cards, and section headings. Do not increase a font merely because its element is h1 or h2.
  • Use xs only for secondary information. Reserve lg for 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.tsx for vertically scrolling page content.
  • Use components/virtual/VirtualList.tsx for data collections and menus that can grow.
  • Treat ScrollArea as the low-level primitive owned by the virtual scrolling implementation. Do not import ScrollArea directly in pages or layouts.
  • Use the global scroll-shadow-top and scroll-shadow-bottom masks for scroll-edge shadows. When a scroll content inset reserves an absolute overlay, source the top shadow distance from the same CSS variable as its padding-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: 0 and the viewport has an explicit bounded height.

Routing and pages

  • Use HashRouter for Tauri compatibility.
  • Keep / as the statistics dashboard and expose every primary page through the persistent menu in the shared AppLayout.
  • 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 ResizeObserver resize 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-bundle

Verify 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.