saftacatalinmihai

Lcars — Development skill for Claude Code

Development community

A Star Trek console for your journal: one SQLite file, a C server, a web console and a walkable 3D ship.

How to install Lcars

This entry records only its repository, not the path inside it, so there is no exact command to give. Open saftacatalinmihai/lcars and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Lcars does

A Star Trek console for your journal: one SQLite file, a C server, a web console and a walkable 3D ship.

Alternatives in Development

North Star Metric — Define North Star Metric and input metrics constellation 7.8k ★
Om Weekly — Weekly synthesis — cross-session review of vault activity, North Star alignment, patterns, uncaptured wins, an 4.6k ★
Google Ads Meta Ads MCP — Google Ads MCP server + Meta Ads MCP (Facebook Ads MCP) + GA4 + Search Console in one hosted remote MCP for Cl 3.2k ★

README

LCARS

![The 3D deck's main bridge, from the aft rail](docs/bridge.webp)

[![C/C++ CI](https://github.com/saftacatalinmihai/lcars/actions/workflows/c-cpp.yml/badge.svg)](https://github.com/saftacatalinmihai/lcars/actions/workflows/c-cpp.yml)

A Star Trek console for your journal: one SQLite file, a small HTTP server in C, and the web console and 3D deck it serves, for one person on a box of their own.

**Try it in the browser, nothing installed:** [the demo](https://public.mihai-safta.dev/lcars-demo/index.html) (it runs on made-up entries in your browser, and saves nothing to a server).

Built by a crew of Claude Code engineers run by an AI first officer: the rules they work to are [CLAUDE.md](CLAUDE.md), their roles [crew/](crew/), their seat and deploys [scripts/engineer.py](scripts/engineer.py). How it was made: [the blog post](https://blog.mihaisafta.com/posts/lcars_journal/).

Run it

Download the tarball for your machine from the [Releases](../../releases) page, `lcars-X.Y.Z-linux-x86_64.tar.gz` or `lcars-X.Y.Z-linux-arm64.tar.gz`, and `SHA256SUMS` beside it, then:

sha256sum --check --ignore-missing SHA256SUMS
tar xzf lcars-X.Y.Z-linux-x86_64.tar.gz && cd lcars-X.Y.Z-linux-x86_64
./lcars init ~/lcars-data     # a data directory, a password, lcars.env; prints the URL and login
./lcars --data ~/lcars-data   # open http://127.0.0.1:8080/ui/ and log in

`lcars` is one static binary: the server, the web console and the deck inside it, and the CLI (`lcars-cli` beside it is a link to it). The tarball also holds the crew's `scripts/` and `crew/`, this README and the licences. `lcars init` never overwrites anything: run it again and it says what it left alone. A new journal starts empty; you make kinds as you go, by typing them on an entry.

**The user manual** starts at [site/manual/pages/00-start.md](site/manual/pages/00-start.md); a running LCARS serves it at `/manual` (the help's foot links it too).