Skip to content
View RepoEnjoyer's full-sized avatar
🎯
Focusing
🎯
Focusing
1 follower · 1 following
  • Toronto

Achievements

Achievement: Pull SharkAchievement: YOLOAchievement: Quickdraw

Achievements

Achievement: Pull SharkAchievement: YOLOAchievement: Quickdraw

Block or report RepoEnjoyer

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
RepoEnjoyer/README.md

Daily commits ↗   /   Selected work   /   The AI Guide   /   Working principles   /   All repositories ↗

RepoEnjoyer and Terry Davis reaching toward a glowing HolyC spark

THE SPARK   ·   HolyC, Terry Davis, and the curiosity to build your own world.

RepoEnjoyer. Build with curiosity. Think in systems. Open source, privacy tools, and practical AI.


Curiosity runs deep.

I'm RepoEnjoyer. I build tools that make hidden behavior easier to inspect: what a package does during installation, what a repository accidentally reveals, and what a graphics layer needs to stay small and predictable.

My work spans developer tooling, privacy, native graphics, and practical AI education. I use AI throughout the build process, with a particular interest in the decisions that still need human judgment: scope, architecture, failure modes, and whether the result is useful.

I like a good abstraction. I like knowing what it hides even more.


Built to go deeper

01 / InstallGlass

What actually happens during npm install?

An instrumented Docker sandbox that observes installation behavior and produces reviewable evidence: file activity, child processes, network destinations, and native artifacts.

PACKAGE BEHAVIOR   ·   NODE.JS / DOCKER / STRACE

02 / LeakFence

Your source code can reveal more than secrets.

A local scanner for credentials, identity leaks, Git author details, and document metadata. Findings explain the problem without echoing the sensitive value.

PRIVACY ENGINEERING   ·   NODE.JS / CLI / SARIF

03 / OverlayKit

A small window into a running system.

A header-only C++20 toolkit for transparent Win32 overlays and performance HUDs. DirectX 11 rendering, a renderer-neutral draw list, and explicit resource ownership.

NATIVE GRAPHICS   ·   C++20 / WIN32 / DIRECTX 11

04 / RepoMend

The repository is part of the product.

A deterministic repository doctor for Git state, dependency health, workflow risks, privacy, and documentation. Readable findings with a useful next action.

DEVELOPER EXPERIENCE   ·   TYPESCRIPT / GIT / CI

The playbook is open.

The Practical AI Guide. From a better question to a working project. 17 chapters, 5 hands-on labs, reusable templates.

The Practical AI Guide is where I organize the methods behind the work: prompting, coding agents, local models, context engineering, evaluation, and the distance between a prototype and something people can use.

Start reading ↗   ·   Explore the labs   ·   Use the templates

For a different kind of machine, there's HolyC Handbook: a source-first guide to programming inside TempleOS, from the language model to memory, graphics, and small runnable programs.


How I think about software

  • Make behavior inspectable. A finding should explain what happened and where to look next.
  • Design the failure path. Limits, partial results, and recovery belong in the design.
  • Keep control close to the user. Prefer local processing and reversible changes when the problem allows them.
  • Write down the reasoning. Good documentation preserves the decisions, not just the commands.
A few other directions worth exploring
Project The question behind it
FormMint Can 3D asset inspection happen in a private browser workspace?
CreatorDock Can a creative workflow stay useful without accounts or a backend?
DirChord What changed between two folders, and how can we verify it?
VoxLocal How much can speech tools do with voices already on the device?

Stay curious. Build something that matters.

Explore a repository. Read the design decisions. Try to break an assumption.

Popular repositories Loading

  1. LeakFence LeakFence Public

    A privacy-first scanner that catches personal information, credentials, Git identity leaks, and hidden document metadata before your code becomes public.

    JavaScript 1

  2. AI-Guide AI-Guide Public

    A clear, practical guide to prompting, vibe coding, AI tools, local models, automation, media, safety, and shipping useful projects.

    1

  3. Grimwick Grimwick Public

    A Skeleton Rogue like game Next.js / Tailwind project

    TypeScript

  4. Voice-Synthesizer Voice-Synthesizer Public

    Full Functional Voice-Synthesizer unlimited use on local device.

  5. Vox-Local Vox-Local Public

    A free, private browser-based voice synthesizer.

    JavaScript

  6. DirChord DirChord Public

    DirChord is a local-first tool that creates deterministic folder manifests and compares modpacks, asset bundles, backups, and project folders without uploading their contents.

    TypeScript