> For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt.

# Naming

Let the containing directory supply context, then name the operation or value precisely.

<standard id="naming-conventions">

## Conventions

<why>

### Why

`packs/manifest.ts` is easier to navigate than a repeated pack prefix. A name such as `findGitCommit` tells a caller more than a vague `resolve` helper.

| Kind                                  | Convention                          | Example                      |
| ------------------------------------- | ----------------------------------- | ---------------------------- |
| Files and directories                 | kebab-case                          | `sources/local/directory.ts` |
| Functions and values                  | camelCase                           | `readManifest`, `manifest`   |
| Types                                 | PascalCase                          | `ReadManifestParams`         |
| Booleans and predicates               | `is`, `has`, `can`, `should`        | `isInstalled`                |
| Stable constants and literal catalogs | SCREAMING_SNAKE_CASE                | `MAX_PACK_BYTES`             |
| Schemas and clients                   | camelCase                           | `packSchema`                 |
| Generic parameters                    | Whole words in SCREAMING_SNAKE_CASE | `CONTENT`, `SOURCE_KIND`     |

</why>

<rules>

### Rules

<rule id="apply-the-table-s-casing-conventions-to-newly-authored-declarations">

- <level>MUST</level> apply the table's casing conventions to newly authored declarations. <enforcement>\[review]</enforcement>

</rule>

<rule id="choose-operation-verbs-for-functions-and-domain-nouns-for">

- <level>MUST</level> choose operation verbs for functions and domain nouns for values. <enforcement>\[review]</enforcement>

</rule>

<rule id="spell-out-generic-parameter-names-rather-than-using-single">

- <level>MUST</level> spell out generic parameter names rather than using single letters. <enforcement>\[review]</enforcement>

</rule>

<rule id="put-related-literals-in-an-as-const-catalog-and">

- <level>MUST</level> put related literals in an `as const` catalog and derive its union type. <enforcement>\[review]</enforcement>

</rule>

<rule id="collect-related-fields-beneath-a-meaningful-domain-object-instead">

- <level>SHOULD</level> collect related fields beneath a meaningful domain object instead of repeating the same prefix. <enforcement>\[review]</enforcement>

</rule>

<rule id="retain-filenames-imposed-by-tooling-or-established-conventions-such">

- <level>MAY</level> retain filenames imposed by tooling or established conventions, such as `README.md`, `AGENTS.md`, and `LICENSE`. <enforcement>\[review]</enforcement>

</rule>

</rules>

<examples>

</examples>

<enforcement>

\[review]

Configured lint checks cover their supported naming rules. Review checks operation verbs, domain meaning, and the remaining casing conventions.

</enforcement>

</standard>

## Enforcement

Configured lint checks cover their supported naming rules. Review checks operation verbs, domain meaning, and the remaining casing conventions.