Big-endian file naming as semantic binding
Pro scans all 5 files and shows the line behind each finding
Scanned 10/6/2026
npx -y skills add SimHacker/moollm --skill naming --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Naming?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/simhacker-naming)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: naming
description: Big-endian file naming as semantic binding
license: MIT
tier: 1
allowed-tools: []
related: [room, character, yaml-jazz, k-lines]
tags: [moollm, naming, filesystem, semantic, convention]
---
# Naming Skill
> *"The filesystem is a semantic network."*
This skill wraps [kernel/NAMING.yml](../../kernel/NAMING.yml).
## Core Pattern
```
TYPE-VARIANT.ext
```
| Part | Meaning | Examples |
|------|---------|----------|
| TYPE | Category/role | `cat`, `staff`, `ROOM` |
| VARIANT | Specific instance | `terpie`, `marieke` |
| ext | File type | `.yml`, `.md` |
## Examples
```
pub/
├── ROOM.yml # Type only — the pub itself
├── cat-terpie.yml # Type-variant
├── cat-stroopwafel.yml
├── staff-marieke.yml
└── menu-strains.yml # Menu type, strains variant
```
## Sorting Advantage
```bash
ls *.yml | sort
# cat-stroopwafel.yml
# cat-terpie.yml
# menu-strains.yml
# ROOM.yml
# staff-marieke.yml
```
Categories cluster. Finding "all cats" → `cat-*.yml`
## Special Filenames
| Name | Purpose |
|------|---------|
| `ROOM.yml` | Room definition |
| `CHARACTER.yml` | Character definition |
| `SKILL.md` | Skill specification |
| `README.md` | Human landing page |
| `INDEX.yml` | Registry |
## Canonical Forms
See [kernel/NAMING.yml](../../kernel/NAMING.yml) for:
- Full naming rules
- Big-endian rationale
- Minsky K-line connection
## Dovetails With
### Kernel
- [kernel/NAMING.yml](../../kernel/NAMING.yml) — definitive reference
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!