Skip to content

Instantly share code, notes, and snippets.

View ultralightspeed's full-sized avatar

jojo ultralightspeed

  • USA
  • 01:06 (UTC -04:00)
View GitHub Profile
@iamhenry
iamhenry / technical decision-making assistant.md
Last active May 24, 2025 12:04
technical decision-making assistant

technical decision-making assistant

You are a technical decision-making assistant designed to help beginner software developers choose between libraries, tools, packages, or technologies based on their current project, stack, and skill level.

🎯 Your Objective:

Help the user make an informed, beginner-friendly, and context-aware technical decision. Ensure the recommendation is compatible with the user’s constraints and justified with clear, relevant reasoning.


🔍 PHASE 1: Dynamic Clarification

@iamhenry
iamhenry / Avoid Local Optima Prompt.md
Last active May 24, 2025 12:04
Avoid Local Optima Prompt

Avoid Local Optima Prompt

Where to use it

  • Use when introducing a new task, feature, or bug report

Purpose

  • explore alternatives
  • analyze trade-offs
  • justify decisions
  • recursive reflection
@iamhenry
iamhenry / System Architecture Design Assistant.md
Last active May 24, 2025 12:04
System Architecture Design Assistant

System Architecture Design Assistant

Use when refining and defining requirements. Input is a rough idea or user stories, and this prompt helps you define the rest.

You're an expert system architect specializing in translating business requirements into technically sound system designs. Your goal is to help the user build a clear architectural foundation for their project based on first principles.

Core Thinking Methodologies

@iamhenry
iamhenry / System Architecture Document Template.md
Last active May 24, 2025 12:03
System Architecture Document Template (Project Planning)

1. Overview

Purpose

[Provide a brief description of the system, its objectives, and its intended users.]


2. System Context Diagram

[Provide a high-level diagram illustrating how the entire system interacts with external entities, such as APIs, databases, and user interfaces.]

Description

Feature Development Conventions

This document outlines our conventions for implementing features using a clean architecture approach with TypeScript, React, and Zod. The pattern described here promotes maintainability, scalability, and testability.

Feature Structure

Features should be organized in a dedicated feature folder with the following structure:

src/features/[feature-name]/
@pmarreck
pmarreck / comparison-of-shells.md
Last active March 16, 2026 14:25
Comparison of Bash, Elvish, NuShell, Murex, es-shell, fish, xonsh, PowerShell, Oil and Ion shells

Comparison of Bash, Elvish, NuShell, Murex, es-shell, fish, xonsh, PowerShell, Oils (Oil/OSH/YSH) and Ion shells

(Originally generated by ChatGPT and reviewed/edited by Claude; now corrected/expanded based on reader feedback. YMMV.)

(generated by chatgpt 4o and reviewed/edited by claude 3.5 sonnet, YMMV)

| Feature | Bash | Elvish | NuShell | Murex | es-shell | Fish | Xonsh | PowerShell | Oil

@espresso3389
espresso3389 / wsl2-rootless-docker.md
Last active January 23, 2026 06:27
WSL2 configuration for developing using rootless docker

NOTE: WORK IN PROGRESS

WSL2 configuration for developing using rootless docker

This document assumes Windows Insider Preview Dev.

Install Ubuntu 22.04

Installing Ubuntu 22.04.1 LTS from Microsoft Store.

@s-a-c
s-a-c / starship.nix
Created August 11, 2022 16:07
Nix file to generate complete, mostly default, starship.toml, including equivalent of <format = "$all">
programs.starship = {
enable = true;
settings = {
# "$schema" = "https://starship.rs/config-schema.json";
add_newline = true;
command_timeout = 500;
continuation_prompt = "[∙](bright-black) ";
format = "[](0x9A348E)$username$hostname$localip$shlvl$singularity$kubernetes[](fg:0x9A348E bg:0xDA627D)$directory$vcsh[](fg:0xDA627D bg:0xFCA17D)$git_branch$git_commit$git_state$git_metrics$git_status$hg_branch[](fg:0x86BBD8 bg:0x06969A)$docker_context$package$buf[](fg:0xFCA17D bg:0x86BBD8)$c$cmake$cobol$container$daml$dart$deno$dotnet$elixir$elm$erlang$golang$haskell$helm$java$julia$kotlin$lua$nim$nodejs$ocaml$perl$php$pulumi$purescript$python$rlang$red$ruby$rust$scala$swift$terraform$vlang$vagrant$zig$nix_shell$conda$spack$memory_usage$aws$gcloud$openstack$azure$env_var$crystal$custom$sudo$cmd_duration$line_break$jobs$battery[](fg:0x06969A bg:0x33658A)$time$status$shell$character";
right_format = "";
scan_timeout = 30;

How to setup AWS lambda function to talk to the internet and VPC

I'm going to walk you through the steps for setting up a AWS Lambda to talk to the internet and a VPC. Let's dive in.

So it might be really unintuitive at first but lambda functions have three states.

  1. No VPC, where it can talk openly to the web, but can't talk to any of your AWS services.
  2. VPC, the default setting where the lambda function can talk to your AWS services but can't talk to the web.
  3. VPC with NAT, The best of both worlds, AWS services and web.