Configuring Horizon
coollabsio/coolify
A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.
Celeriant codebase architecture, crate responsibilities, and how they fit together.
Install Understanding Celeriant Structure
$ npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install celeriant/celeriant-db understanding-celeriant-structure --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/understanding-celeriant-structure .claude/skills/understanding-celeriant-structure && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "understanding-celeriant-structure" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/understanding-celeriant-structure into .claude/skills/understanding-celeriant-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understanding-celeriant-structure", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/understanding-celeriant-structureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install celeriant/celeriant-db understanding-celeriant-structure --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/understanding-celeriant-structure .agents/skills/understanding-celeriant-structure && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "understanding-celeriant-structure" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/understanding-celeriant-structure into .agents/skills/understanding-celeriant-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understanding-celeriant-structure", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install celeriant/celeriant-db understanding-celeriant-structure --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/understanding-celeriant-structure .cursor/skills/understanding-celeriant-structure && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "understanding-celeriant-structure" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/understanding-celeriant-structure into .cursor/skills/understanding-celeriant-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understanding-celeriant-structure", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/celeriant/celeriant-db.git --path .claude/skills/understanding-celeriant-structure--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install celeriant/celeriant-db understanding-celeriant-structure --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/understanding-celeriant-structure .gemini/skills/understanding-celeriant-structure && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "understanding-celeriant-structure" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/understanding-celeriant-structure into .gemini/skills/understanding-celeriant-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understanding-celeriant-structure", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install celeriant/celeriant-db understanding-celeriant-structureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/understanding-celeriant-structure .github/skills/understanding-celeriant-structure && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "understanding-celeriant-structure" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/understanding-celeriant-structure into .github/skills/understanding-celeriant-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understanding-celeriant-structure", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install celeriant/celeriant-db understanding-celeriant-structure --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/understanding-celeriant-structure .opencode/skills/understanding-celeriant-structure && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "understanding-celeriant-structure" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/understanding-celeriant-structure into .opencode/skills/understanding-celeriant-structure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "understanding-celeriant-structure", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
understanding-celeriant-structure- GitHub stars
- 114
- Token cost
- ~803 tokens
- SKILL.md length
- 321 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Celeriant codebase architecture, crate responsibilities, and how they fit together.
- Works in 8 steps: Binary: celeriant (server),… → Runtime: celeriant_runtimes (glommio… → Shard: celeriant_shard (WAL… → …
- Navigating the codebase
- SKILL.md covers Layers (top to bottom), Thread-Per-Core, Write Path and Read Path, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Understanding Celeriant Structure is an agent skill from celeriant/celeriant-db. Celeriant codebase architecture, crate responsibilities, and how they fit together. Use when navigating the codebase, understanding what a crate does, or figuring out where to make changes.
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs. The repository describes itself as: Fast, distributed per-aggregate event log with strict ordering and optimistic concurrency control. The licence is Apache-2.0.
When your agent uses it
- Navigating the codebase
- Understanding what a crate does
- Figuring out where to make changes
Example prompts
- “/understanding-celeriant-structure”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Binary: celeriant (server), celeriant_cli (CLI/TUI)
- Runtime: celeriant_runtimes (glommio orchestration, shard routing, inter-shard channels), celeriant_sidecar (tokio bridge for S3)
- Shard: celeriant_shard (WAL orchestrator, fsync batching, validation), celeriant_watch (subscriptions)
- Storage: celeriant_memcache (caches, queues), celeriant_rotating_log (log files, bloom filters), celeriant_disk (DMA I/O)
- Core: celeriant_wal (data types, no I/O), celeriant_wire (serialization, CRC, framing), celeriant_msg (request/response types)
- Infra: celeriant_crypto (RSA, API key hashing, PKI), celeriant_ktls (kernel TLS offload), celeriant_distributed (replication, leader…
- Clients: celeriant_client_tokio (application clients), celeriant_client_glommio (server-to-server replication)
- Examples: celeriant_demo, celeriant_reference (reference implementations mirroring .NET client examples)
What it can do on your machine
Read from SKILL.md and the folder at commit d071a6d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Understanding Celeriant Structure loads about 803 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 321 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from celeriant/celeriant-db at commit d071a6d, republished under its Apache-2.0 licence (© celeriant). 321 words, ~803 tokens.
Download SKILL.mdSave it as
.claude/skills/understanding-celeriant-structure/SKILL.md (or your agent's skills folder).- name
- understanding-celeriant-structure
- description
- Celeriant codebase architecture, crate responsibilities, and how they fit together. Use when navigating the codebase, understanding what a crate does, or figuring out where to make changes.
Celeriant Project Structure
Fast, distributed write-ahead log for event sourcing. Thread-per-core (glommio/io_uring). Two-node cluster with S3 for coordination and backup replication.
Layers (top to bottom)
- Binary:
celeriant(server),celeriant_cli(CLI/TUI) - Runtime:
celeriant_runtimes(glommio orchestration, shard routing, inter-shard channels),celeriant_sidecar(tokio bridge for S3) - Shard:
celeriant_shard(WAL orchestrator, fsync batching, validation),celeriant_watch(subscriptions) - Storage:
celeriant_memcache(caches, queues),celeriant_rotating_log(log files, bloom filters),celeriant_disk(DMA I/O) - Core:
celeriant_wal(data types, no I/O),celeriant_wire(serialization, CRC, framing),celeriant_msg(request/response types) - Infra:
celeriant_crypto(RSA, API key hashing, PKI),celeriant_ktls(kernel TLS offload),celeriant_distributed(replication, leader election, S3 catchup) - Clients:
celeriant_client_tokio(application clients),celeriant_client_glommio(server-to-server replication) - Examples:
celeriant_demo,celeriant_reference(reference implementations mirroring .NET client examples)
Thread-Per-Core
One glommio executor per CPU core. Each shard owns aggregates via routing (aggregate_id % num_shards by default, configurable to org_id or aggregate_type_id). No locks on the hot path. Rc<RefCell<_>> for per-shard state. The only Arc types crossing shard boundaries are immutable-after-creation or atomic booleans.
Shard 0 handles all cluster coordination: lease management, heartbeats, kick processing.
S3/HTTP runs in a separate tokio sidecar runtime. io_uring and tokio are incompatible in the same thread.
Write Path
- Validation (OCC, idempotency, allow_create, schema validation)
- Queue to
pending_append_queue - Fsync batching via Coordinator (amortises across concurrent writers)
- Replication (sync to follower or S3 fallback)
- Commit positions, broadcast watch events, ACK to client
Read Path
- Check recent write cache (filtered by
visible_wal_seq) - Reverse scan via
ReverseMetablockScanner - Bloom filter skips entire log segments
- Metablock-level filters (timestamps, batch indices, event type bloom)
- Fetch datablocks (inline if <= 512 bytes, otherwise from disk)
- Event-level filters
File Layout
log_N.wal (preallocated, up to 1GB)
[Header 4096KB] [Metablocks 1024B each, growing down ->] [Free space] [<- Datablocks variable, growing up] [Header 4096KB]Rotates when metablocks and datablocks meet. Dual headers for crash recovery. File does not grow. Can shrink via compaction.
Where to Find Things
Every crate has a README.md. Some also have ARCHITECTURE.md for deeper design details (celeriant_wire, celeriant_wal, celeriant_crypto, celeriant_client_tokio, celeriant_msg). System-wide invariants are in docs/invariants.md.
© celeriant, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/understanding-celeriant-structure of celeriant/celeriant-db.
Open the folder on GitHubat commit d071a6d
Compare with similar skills
Understanding Celeriant Structure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Understanding Celeriant Structure this skillceleriant/celeriant-db | 114 | — | ~803 | Automated safety check: Pass | Apache-2.0 | |
| Configuring Horizoncoollabsio/coolify | 63k | 4 repos | ~898 | Automated safety check: Pass | MIT | |
| Nestjs Best Practicesrolling-scopes/rsschool-app | 10k | 6 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Sub2API AdminWei-Shaw/sub2api | 43k | 1 repos | ~717 | Automated safety check: Pass | LGPL-3.0 | |
| Firecrawl Build Onboardingfirecrawl/firecrawl | 190k | 1 repos | ~1.4k | Automated safety check: Notes | ISC | |
| Obsidian BasesAtmosphere/atmosphere | 3.8k | 22 repos | ~3.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Nestjs Best Practices
rolling-scopes/rsschool-app
NestJS best practices and architecture patterns for building production-ready applications.
Sub2API Admin
Wei-Shaw/sub2api
Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.
Firecrawl Build Onboarding
firecrawl/firecrawl
Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.
Obsidian Bases
Atmosphere/atmosphere
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.
Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
More from celeriant/celeriant-db
All 13 skills in this repoError Handling
celeriant/celeriant-db
Error handling patterns in Celeriant. An agent skill from celeriant/celeriant-db.
Testing
celeriant/celeriant-db
How to write and run tests in Celeriant. An agent skill from celeriant/celeriant-db.
Extract A Type
celeriant/celeriant-db
Refactor a named Rust type or its surrounding code with an agreed scope.
Client Server Protocol
celeriant/celeriant-db
Celeriant's client-server protocol invariants, network behavior, failure modes, and shard routing.
Database Architecture
celeriant/celeriant-db
Core architecture invariants for Celeriant. An agent skill from celeriant/celeriant-db.
Glommio Locking Patterns
celeriant/celeriant-db
Locking patterns for Glommio's single-threaded async executors.
Related
Categories
Questions about Understanding Celeriant Structure
What does Understanding Celeriant Structure do?
Celeriant codebase architecture, crate responsibilities, and how they fit together. Understanding Celeriant Structure is an agent skill from celeriant/celeriant-db. Celeriant codebase architecture, crate responsibilities, and how they fit together.
When should I use Understanding Celeriant Structure?
Understanding Celeriant Structure fits situations like: navigating the codebase; understanding what a crate does; figuring out where to make changes.
How do I install Understanding Celeriant Structure in Claude Code?
Run `npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a claude-code`. Or copy the skill folder (.claude/skills/understanding-celeriant-structure in celeriant/celeriant-db) into .claude/skills/understanding-celeriant-structure in your project. Claude Code loads it when a task matches its description.
How do I install Understanding Celeriant Structure in Codex?
Run `npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a codex`. Or copy the skill folder (.claude/skills/understanding-celeriant-structure in celeriant/celeriant-db) into .agents/skills/understanding-celeriant-structure in your project. Codex loads it when a task matches its description.
Can I use Understanding Celeriant Structure in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add celeriant/celeriant-db --skill understanding-celeriant-structure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/understanding-celeriant-structure, .gemini/skills/understanding-celeriant-structure, .github/skills/understanding-celeriant-structure and .opencode/skills/understanding-celeriant-structure in your project.
What does Understanding Celeriant Structure need to run?
SKILL.md names no scripts, command-line tools or credentials: Understanding Celeriant Structure is instructions for the agent only.
Does Understanding Celeriant Structure access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Understanding Celeriant Structure safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Understanding Celeriant Structure use?
Understanding Celeriant Structure is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Understanding Celeriant Structure use?
About 803 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Understanding Celeriant Structure?
Skills that share tags, products or a category with Understanding Celeriant Structure: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 43k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Understanding Celeriant Structure?
celeriant (a GitHub organization) maintains it in celeriant/celeriant-db, which has 114 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 28, 2026.
Source: celeriant/celeriant-db on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.