agentmods.dev

naming-conventions

File, directory, component, type, variable, and function naming rules for Rill’s web frontend.

In plain words
What is it for?
Use them when adding or renaming TypeScript, JavaScript, Svelte, directory, interface, type, variable, and function files or symbols.
Why use it?
They prevent inconsistent names that make files harder to find and code harder to understand.

Cursor rule for Cursor

2.9k 4d ago A scan 0 tokens original Apache-2.0
View the source file rilldata/rill
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/rilldata/rill/naming-conventions
Clone the repo
git clone --depth 1 https://github.com/rilldata/rill

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 503 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.00503
Opus 5 $0.00000 $0.00251
Sonnet 5 $0.00000 $0.00101
Haiku 4.5 $0.00000 $0.00050

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

Security

Grade A, and why

naming-conventions 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/naming-conventions.mdc · 78 lines

What it actually says

Naming Conventions

File Naming Rules

TypeScript/JavaScript Files

  • Use kebab-case for all TypeScript and JavaScript files
  • Examples: user-management.ts, environment-variables.ts, project-status.ts

Svelte Component Files

  • Use PascalCase for Svelte component files
  • Examples: ProjectCard.svelte, UserManagement.svelte, EnvironmentVariables.svelte
  • Exception: Use kebab-case for layout files (e.g., +layout.svelte, +page.svelte)

Directory Naming

  • Use kebab-case for all directories
  • Examples: user-management/, environment-variables/, project-status/

Component Naming Rules

Svelte Components

  • Use PascalCase for component names in Svelte files
  • Examples: <ProjectCard />, <UserManagement />, <EnvironmentVariables />
  • Match the component name to the file name

TypeScript Interfaces/Types

  • Use PascalCase for interfaces and types
  • Examples: ProjectPermissions, UserManagement, EnvironmentVariable

Variable and Function Naming

Variables

  • Use camelCase for variables and constants
  • Examples: projectPermissions, environmentVariables, userManagement

Functions

  • Use camelCase for function names
  • Use descriptive verbs: getProjectPermissions(), updateEnvironmentVariables(), validateUserInput()

Constants

  • Use UPPER_SNAKE_CASE for true constants
  • Examples: MAX_FILE_SIZE, DEFAULT_TIMEOUT, API_BASE_URL

Special Cases

Test Files

  • Use the same naming as the source file with .spec suffix

Configuration Files

  • Use kebab-case for configuration files
  • Examples: tailwind.config.ts, vite.config.ts, svelte.config.js
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 · 78 lines · 0 tokens per session scan A ea2869dc5973

Subscribe to this mod's changes

naming-conventions is a cursor rule published in the GitHub repository rilldata/rill (2,853 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 503 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.

DocumentsFrontendLanguagescsvdatavizduckdbparquetparquet-toolssveltekit
Related

Other cursor rules, from other repositories

svelte

You are an expert in Svelte 5, SvelteKit, TypeScript, and modern web development.

humanspeak/svelte-markdown · 0 tokens

testing

Comprehensive Testing Best Practices for Svelte 5 + vitest-browser-svelte.

spences10/sveltest · 0 tokens

cli

The cli is written in TypeScript and uses Node.js. It is hosted in ./cli directory. This directory also contains the vscode extension to interact with the flapi server.

DataZooDE/flapi · 109 tokens

global

ALWAYS follow this rule.

davis7dotsh/river · 188 tokens

sveltekit-spa

You are an expert SvelteKit engineer. Follow these rules ALWAYS when generating or editing code.

wesselgrift/sveltekit-spa · 3,474 tokens

code-organization

Code and file organization standards.

raw-labs/mxcp · 107 tokens