All of these diagrams are dynamically rendered during html display by Github, the images generated from text inside the Github-Flavored Markdown. None are static images. Mermaid support was released for Github on 2022-02-14
Pros & Cons:
Notes:
B-->C[fa:fa-ban forbidden], hyperlink and tooltips) are supported by Github.
| created | 2026-04-12 |
|---|---|
| did | did:repo:53936a6c815841cab48caa0ac46e37364a197e86 |
| github | https://gist.github.com/ChristopherA/151aefa6a6bde1ce4fa6b1182656cebe |
| purpose | Agent reference for wikilinks and named edges in plain-markdown knowledge graphs |
| copyright | ©2026 by @ChristopherA, licensed under CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/) |
| summary | How wikilinks and named edge predicates work in a plain-markdown knowledge graph. Covers syntax, YAML vs body predicates, node types (atomic and compound), annotated predicates, vocabulary curation (folksonomy vs ontology), classification predicates (conforms_to:: over is_a::) and predicate conflation, naming sovereignty across collaborating systems, and agent traversal patterns. |
Last Updated: 2024-02-06
Git worktrees allow you to check out multiple branches simultaneously in separate directories, while sharing a single .git metadata store.
THere are some best practices, useful Git aliases, and shell functions for efficiently managing Git worktrees. It covers:
A single prompt (~1400 tokens), placed in a project's .claude/CLAUDE.md, can bootstrap a Claude Code instance into a self-improving system — one that captures learnings, extracts patterns, evolves its own configuration, and gets meaningfully better at helping its user with each session.
No pre-built infrastructure required. No user-level config. No hooks, skills, templates, or elaborate folder hierarchies. Just a seed and the affordances Claude Code already provides.
Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.
If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.
- did:
did:repo:08dc488d960ef5087f62016240bd0636b6d5cb34/blob/main/0-Setup-macOS-Machine.md- github:
https://gist.github.com/ChristopherA/647e8ae63fbfd9c5792b75c5d56c9764- updated: 2026-05-07 by Christopher Allen <ChristopherA@LifeWithAlacrity.com>
Important
Superseded as of 2026-05. This gist's bootstrap script ran on a fresh Mac to create the daily-driver account, enable SSH, and toggle the firewall. Current practice creates both accounts during macOS Setup Assistant + System Settings (no script needed) and drives the rest from a remote Claude Code session over SSH. The gist remains as historical Open Integrity provenance — the inception commit is still valid as a trust anchor — but 1-setup-from-admin.sh should not be run on new machines.
Current path: see the provisioning runbook (Phase U + Phase 0 + Phase 1 + Phase 2) and the `mach
Abstract: This guide provides best practices for writing clear, maintainable, and robust Zsh scripts. Aimed at helping developers transition from Bash to Zsh, particularly on macOS, this guide offers practical advice and examples for creating standardized and efficient scripts.
Copyright This text of this guide is Copyright ©️2024 by Christopher Allen, and is shared under spdx:CC-BY-SA-4.0 open-source license. All the example code is relenquished to the public domain under spx:CC0-1.0.
Tags: #zsh #scripting #cli #opinionated
Draft, 2026-05-01.
Christopher Allen <ChristopherA@LifeWithAlacrity.com
(VERY rought draft, still a work-in-progress)
Authentication and signing keys serve different purposes, especially on platforms like GitHub where code integrity and access control are crucial. Here's a comparison based on their functions and best practices: