Skip to content

Instantly share code, notes, and snippets.

View mhmyu's full-sized avatar
🎯
🐜

yu mhmyu

🎯
🐜
View GitHub Profile
@mattezell
mattezell / README.md
Last active September 22, 2026 07:18
Install Antigravity 2.0 / Antigravity IDE on Linux from the official tarballs (user-local install, Ubuntu 24.04+ AppArmor handled)

Antigravity / Antigravity IDE — Linux tarball installer

Antigravity 2.0 and the Antigravity IDE currently ship for Linux as raw .tar.gz archives — no .deb, no .AppImage, no Flatpak, no installer. This gist is a small set of shell scripts that turn one of those extracted tarballs into a proper user-local install: a desktop launcher in your app menu, a CLI symlink on your $PATH, an icon, and (on Ubuntu 24.04+) a working Chromium sandbox via an AppArmor profile.

Status: community workaround. Replace with whatever Google ships

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

@eonist
eonist / Markdown-Instructions-for-AI--and-humans.md
Created April 30, 2025 16:29
Best Practice Guidelines for Prompt Markdown Instructions (.md Files)

Best Practice Guidelines for Prompt Markdown Instructions (.md Files)

When creating Markdown (.md) files to standardize prompt instructions or best practices, clarity, consistency, and structure are paramount. Below is a comprehensive guideline on how to structure these files and what to do-and avoid-when authoring them.


Key Principles

  • Clarity: Use Markdown to make prompts and instructions easy to read, both for humans and AI models[6][8].
  • Consistency: Stick to a single Markdown flavor (e.g., CommonMark, GitHub Flavored Markdown) throughout your project[5].
@berkorbay
berkorbay / github_desktop_ubuntu.md
Last active September 30, 2026 08:24
To install Github Desktop for Ubuntu

IMPORTANT

See the following links for further updates to Github Desktop for Ubuntu. These are official instructions. (also mentioned by fetwar on Nov 3, 2023)

For the sake of "maintaining the tradition" here is the updated version.

@jesugmz
jesugmz / Deploy-Next.js-static-to-GitLab-pages.md
Last active April 9, 2024 14:33
Deploy Next.js static to GitLab pages

Deploy Next.js static to GitLab pages

Create a basic GitLab CI config:

$ cat .gitlab-ci.yml
image: node

before_script:
 - npm install
@chris-sev
chris-sev / setup.sh
Last active August 13, 2026 08:41
Mac Setup
# how to run this thingy
# create a file on your mac called setup.sh
# run it from terminal with: sh setup.sh
# heavily inspired by https://twitter.com/damcclean
# https://github.com/damcclean/dotfiles/blob/master/install.sh
# faster dock hiding/showing (run in terminal)
# defaults write com.apple.dock autohide-delay -float 0; defaults write com.apple.dock autohide-time-modifier -int 0;killall Dock
@sandren
sandren / tailwind.md
Last active February 28, 2025 13:05
Tailwind CSS best practices

Tailwind CSS best practices

Utility classes

  1. When writing a string of multiple utility classes, always do so in an order with meaning. The "Concentric CSS" approach works well with utility classes (i.e,. 1. positioning/visibility 2. box model 3. borders 4. backgrounds 5. typography 6. other visual adjustments). Once you establish a familiar pattern of ordering, parsing through long strings of utility classes will become much, much faster so a little more effort up front goes a long way!

  2. Always use fewer utility classes when possible. For example, use mx-2 instead of ml-2 mr-2 and don't be afraid to use the simpler p-4 lg:pt-8 instead of the longer, more complicated pt-4 lg:pt-8 pr-4 pb-4 pl-4.

  3. Prefix all utility classes that will only apply at a certain breakpoint with that breakpoint's prefix. For example, use block lg:flex lg:flex-col lg:justify-center instead of block lg:flex flex-col justify-center to make it very clear that the flexbox utilities are only applicable at the

@qoomon
qoomon / conventional-commits-cheatsheet.md
Last active October 8, 2026 18:46
Conventional Commits Cheatsheet
@lightonphiri
lightonphiri / bash-install_google_fonts_on_ubuntu.md
Last active July 27, 2026 18:45
Install Google Fonts on Ubuntu

Install Google Fonts

Download desired fonts

https://fonts.google.com/?selection.family=Open+Sans

Install Google Fonts on Ubuntu

cd /usr/share/fonts
sudo mkdir googlefonts
cd googlefonts
sudo unzip -d . ~/Downloads/Open_Sans.zip

@YuMS
YuMS / update-git.sh
Created June 29, 2016 09:28
Update git to latest version on Ubuntu
#!/bin/bash
sudo add-apt-repository -y ppa:git-core/ppa
sudo apt-get update
sudo apt-get install git -y