slate

Project rules for using Electrik Slate 3.x components in Laravel Blade templates. They define naming, layout, theming, form, and overlay conventions.

In plain words
What is it for?
Use them while building or reviewing Slate components, Tailwind themes, Alpine overlays, Livewire forms, and toast notifications.
Why use it?
They give the coding agent consistent boundaries when editing Slate-based interfaces. This helps prevent unsupported syntax and inconsistent styling.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/electrikhq/slate/slate
Clone the repo
git clone --depth 1 https://github.com/electrikhq/slate

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 236 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00236
Opus 5 $0.00000 $0.00118
Sonnet 5 $0.00000 $0.00047
Haiku 4.5 $0.00000 $0.00024

Measured 2d ago against content hash 2b4f298c25e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

slate 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 2d 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/slate.mdc · 19 lines

What it actually says

Electrik Slate

When building UI in this project with electrik/slate:

  • Use <x-slate::*> anonymous Blade components only — no React/Vue/shadcn copies.
  • Prefer progressive props: label, description, errorMessage.
  • Do not nest the same Slate component inside itself.
  • Do not put @if inside <x-slate::*> opening tags.
  • Prefer logical properties (start/end) for spacing and positioning.
  • Theme with --slate-* OKLCH tokens; import vendor/electrik/slate/resources/css/slate.css after Tailwind v4.
  • Interactive overlays need Alpine; mount <x-slate::toaster /> once for toasts (slate-toast events).
  • Read docs from https://slate.electrik.dev/llms.txt or *.md component URLs before inventing APIs.
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. 2d ago First seen · 19 lines · 0 tokens per session scan A 2b4f298c25e4

Subscribe to this mod's changes

slate is a cursor rule published in the GitHub repository electrikhq/slate (25 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 236 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.