Documentation

Two things live in here.

The tools. One page per tool: what it does, what it does not do, how to run it, and where it breaks.

The GitHub standards. The files a repository is expected to publish, what each one is for, and the community profile score GitHub currently gives every repository here.

Tools

planciaOne board for the tasks your coding agents have open, and a spoken daily recap.

claude-codex-bridgeMoves a live coding session between Claude Code and Codex, in both directions.

scribaLocal transcription that separates speakers and remembers them next time.

radaA queue for heavy jobs launched by parallel coding sessions on one machine.

moloA local queue for yt-dlp on Mac, Windows and Android.

varoA Claude Code plugin for shipping static sites and auditing the live one.

arganoRebuilds the index of a video file that was never finalised.

vestaVirtual try-on running locally on Apple Silicon.

snapchat-memories-to-photosA Snapchat export into Apple Photos, with dates and places kept.

wedding-invite-starter-kitA one page wedding invite you host yourself, with a local visual editor.

parancoOne macOS app that holds Full Disk Access, so scripts and interpreters never need to.

capitaneriaA status line for each tool in the control-plane suite: reachable, running, and on what commit.

paratiaFiles an agent cannot read, enforced by the harness instead of a line in a prompt.

portoThe landing page and installer for the control-plane suite.

placaWho wins Gran Hermano Argentina, from the vote shares Telefe already publishes.

japepoMasterChef Celebrity Paraguay, forecast and scored gala by gala, in Spanish and Guaraní.

vesuvius-ladderFinds papyrus surfaces published twice under different names.

man5-surfacesTraced surface area on a scroll with no published segments, checked two independent ways.

GitHub standards

Overview and scorecardWhat every repository publishes, and the score GitHub gives it today.

The README standardStructure, and the rule about stating limits.

LicensingMIT and GPL-3.0, and where the pattern breaks.

Contributing and conductWhen a single maintainer actually needs these files.

Security policyPrivate reporting, and who currently has a policy.

Releases and versionsHow a release is cut here.

Where these pages come from

The data behind these pages, licences, topics, push dates and community profile scores, is pulled from the GitHub API by node scripts/sync-repos.mjs and committed.