solidjs-pages

solidjs-pages is a cursor rule for Cursor from golid-ai/golid. It costs 0 tokens per session (1,051 once invoked), scanned A, original, MIT.

A set of rules for building page interfaces with SolidJS, a JavaScript framework for reactive web interfaces. It covers route switching, modal dialogs, authentication gates, and page titles.

In plain words
What is it for?
It guides list-detail modals, destructive-action dialogs, authenticated pages, route layouts, and document titles in SolidJS applications.
Why use it?
It gives developers consistent patterns for reactive page behavior and avoids specific mistakes such as nested display conditions, browser confirmation dialogs, and unsafe reactive titles.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It guides list-detail modals, destructive-action dialogs, authenticated pages, route layouts, and document titles in SolidJS applications.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/golid-ai/golid/solidjs-pages
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/golid-ai/golid

Made for: Cursor.

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 solidjs-pages

README.md
[![agentmods](https://agentmods.dev/badge/rules/golid-ai/golid/solidjs-pages/github.svg)](https://agentmods.dev/rules/golid-ai/golid/solidjs-pages)
Your own site
<a href="https://agentmods.dev/rules/golid-ai/golid/solidjs-pages"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/solidjs-pages/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 solidjs-pages

Your own site · 80×15
<a href="https://agentmods.dev/rules/golid-ai/golid/solidjs-pages"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/solidjs-pages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,051 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.01051
Opus 5.5 $0.00000 $0.00420
Sonnet 5.5 $0.00000 $0.00210
Haiku 4.5 $0.00000 $0.00105

Measured 2mo ago against content hash 83bb73b3bab0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

solidjs-pages scanned grade A with 0 findings 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 2mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/solidjs-pages.mdc · 124 lines

How it starts

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

SolidJS Page Patterns

Thesis: Route UI uses flat Switch/Match, signal modals, and auth gates — never nested Show or early returns.

Signal-Driven Modals

Detail views within list pages use a signal, not a sub-route:

const [activeItem, setActiveItem] = createSignal<Item | null>(null);
// Open: setActiveItem(item)
// Close: setActiveItem(null)

<Show when={activeItem()}>
  {(item) => <DetailModal item={item()} onClose={() => setActiveItem(null)} />}
</Show>

Destructive Actions

Never window.confirm(). Always use DestructiveModal:

const [deleteTarget, setDeleteTarget] = createSignal(false);
// ...
<DestructiveModal
  open={deleteTarget()}
  onOpenChange={(open) => {
    if (!open) setDeleteTarget(false);
  }}
  onConfirm={handleDelete}
  title="Delete item?"
  message="This action cannot be undone."
  confirmText="Delete"
/>;

Page Titles

Never put reactive expressions directly inside <Title>. The @solidjs/meta <Title> component creates an internal computation to track children. During route transitions, this computation is re-evaluated outside the component's reactive root, causing "computations created outside createRoot" warnings.

// BAD — reactive ternary inside <Title> leaks during route transition
<Title>{userType() === "admin" ? "Manage Items" : "Items"} | My App</Title>

// GOOD — pre-compute as a memo, pass resolved string (static strings are fine when no reactive expression is needed)
const pageTitle = createMemo(() =>
  `${userType() === "admin" ? "Manage Items" : "Items"} | My App`
);
// ...
<Title>{pageTitle()}</Title>

Auth & Routing

  • Add every new private route to PRIVATE_ROUTES in frontend/src/lib/constants.ts.
  • Do not early-return from route components before reactive setup. Put auth/access redirects in an effect and gate JSX with <Show> so async auth.user updates can re-render the page.
createEffect(
  on(
    () => auth.user?.type,
    (type) => {
      if (type && type !== "admin") navigate("/dashboard", { replace: true });
    },
  ),
);

return (
  <Show when={auth.user?.type === "admin"} fallback={<Spinner />}>
    <AdminPageContent />
  </Show>
);

Read the full file on GitHub · 124 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. 2mo ago First seen · 124 lines · 0 tokens per session scan A 83bb73b3bab0

Subscribe to this mod's changes

solidjs-pages is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,051 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.