@hurshb50/setup-ubuntu 0.0.0 → 0.0.3

package/README.md

@@ -1,59 +1,17 @@
 # setup-ubuntu
 
-## Publishing
-
-The repo includes two GitHub Actions workflows.
-
-- `publish.yaml` checks, tests, builds, bumps the version, tags it, and stages the package on npm.
-- `release.yaml` publishes a GitHub release once the version is live.
-
-CI uses npm's OIDC trusted publishing and staged publishing. No npm token. Nothing goes live until you approve it with 2FA.
-
-## One-time setup
-
-1. Push the repo to GitHub. Run `gh auth login` first if needed.
-
-   ```bash
-   git init -b main
-   git add .
-   git commit -m "Initial commit"
-   gh repo create setup-ubuntu --public --source . --remote origin --push
-   ```
-
-2. Log in to npm.
-
-   ```bash
-   vp pm login
-   ```
+Sets up a fresh Ubuntu machine with a standard set of tools, configuration, and dotfiles.
 
-3. Publish the first version manually. npm cannot stage a new package.
-
-   ```bash
-   vp pm publish
-   ```
-
-   This publishes 0.0.0. Later releases go through CI.
-
-4. Allow GitHub Actions to publish. In the package settings on npmjs.com, add a GitHub Actions trusted publisher.
-
-   - Organization or user: `hurshb50`
-   - Repository: `setup-ubuntu`
-   - Workflow filename: `publish.yaml`
-   - Allowed actions: staged publishing only
-
-5. Optional: in package settings under Publishing access, set "Require two-factor authentication and disallow tokens". CI still works through OIDC.
-
-## Releasing a version
+## Installation
 
 ```bash
-gh workflow run publish.yaml -f bump=patch
+sudo apt update && sudo apt install -y curl ca-certificates
+curl -fsSL https://vite.plus | bash
+vpx @hurshb50/setup-ubuntu
 ```
 
-Use `minor` or `major` instead of `patch` when it fits. Then approve the staged package.
+## Publishing
 
-```bash
-vp pm stage list
-vp pm stage approve <stage-id>
-```
+Run the `publish.yaml` workflow from the Actions tab, choosing `patch`, `minor`, or `major` for the version bump. CI checks, tests, builds, bumps the version, tags it, and stages the package on npm. It uses OIDC trusted publishing, so no npm token is needed.
 
-You can also approve on npmjs.com under Staged Packages. The Release workflow creates the GitHub release on its weekly run. Run `gh workflow run release.yaml` to do it now.
+Nothing goes live until you approve the staged package on npmjs.com under Staged Packages. The `release.yaml` workflow creates the GitHub release once the version is live.

package/distribution/assets/.bashrc

@@ -0,0 +1,147 @@
+function is_interactive() {
+    [[ $- == *i* ]]
+}
+
+function check_command() {
+    command -v "$1" &> /dev/null
+}
+
+function path_exists() {
+    if [ -e "$1" ]; then
+        return 0
+    else
+        return 1
+    fi
+}
+
+function is_posix() {
+    shopt -oq posix
+}
+
+function print_error() {
+    local RED='\033[0;31m'
+    local NC='\033[0m'
+    echo -e "\n${RED} $1 ${NC}"
+    echo -e "\n${RED} Run the setup script to fix this.${NC}"
+}
+
+function path() {
+    export PATH="$HOME/.local/bin:$PATH"
+}
+
+function setup_history() {
+    shopt -s histappend
+    shopt -s checkwinsize
+}
+
+function completion() {
+    if is_posix; then
+        return
+    fi
+
+    USER_COMPLETION_PATH="/usr/share/bash-completion/bash_completion"
+
+    if path_exists "${USER_COMPLETION_PATH}"; then
+        . "${USER_COMPLETION_PATH}"
+    fi
+}
+
+function terminal_view() {
+    if ! check_command "oh-my-posh"; then
+        print_error "'oh-my-posh' is not installed"
+        return 1
+    fi
+
+    eval "$(oh-my-posh init bash --config $HOME/.config/oh-my-posh/oh-my-posh.toml)"
+}
+
+function smart_change_directory() {
+    if ! check_command "zoxide"; then
+        print_error "'zoxide' is not installed"
+        return 1
+    fi
+
+    eval "$(zoxide init bash --cmd cd)"
+}
+
+function list_directory_alias() {
+    alias ls="ls -lAh --color=auto"
+}
+
+function custom_bash_rc() {
+    CUSTOM_BASH_RC_PATH="${HOME}/custom.bashrc"
+
+    if ! path_exists "${CUSTOM_BASH_RC_PATH}"; then
+        return
+    fi
+
+    source "${CUSTOM_BASH_RC_PATH}"
+}
+
+function disable_legacy() {
+    stty -ixon
+}
+
+function swap_capslock_and_esc() {
+    gsettings set org.gnome.desktop.input-sources xkb-options "['caps:swapescape']"
+}
+
+function load_auto_suggestion() {
+    BLE_PATH="$HOME/.local/share/blesh/ble.sh"
+
+    if ! path_exists "$BLE_PATH"; then
+        print_error "'ble.sh' is not installed"
+        return 1
+    fi
+
+    source "$BLE_PATH" --attach=none
+}
+
+function start_auto_suggestion() {
+    if ! check_command "ble-attach"; then
+        print_error "ble-attach is not installed"
+        return 1
+    fi
+
+    ble-attach
+    clear
+}
+
+function fuzzy_finder() {
+    if ! check_command "fzf"; then
+        print_error "'fzf' is not installed"
+        return 1
+    fi
+
+    FZF_KEY_BINDINGS="/usr/share/doc/fzf/examples/key-bindings.bash"
+    FZF_COMPLETION="/usr/share/bash-completion/completions/fzf"
+
+    if path_exists "$FZF_KEY_BINDINGS"; then
+        source "$FZF_KEY_BINDINGS"
+    fi
+
+    if path_exists "$FZF_COMPLETION"; then
+        source "$FZF_COMPLETION"
+    fi
+}
+
+function run() {
+    if ! is_interactive; then
+        return
+    fi
+
+    path
+    load_auto_suggestion
+    setup_history
+    completion
+    terminal_view
+    smart_change_directory
+    list_directory_alias
+    custom_bash_rc
+    disable_legacy
+    swap_capslock_and_esc
+    fuzzy_finder
+    start_auto_suggestion
+}
+
+run

package/distribution/assets/.blerc

@@ -0,0 +1,22 @@
+bleopt highlight_syntax=
+bleopt highlight_filename=
+bleopt highlight_variable=
+
+ble-face -s auto_complete fg=245
+
+ble-bind -m auto_complete -f 'C-RET' 'auto_complete/insert'
+
+set -o vi
+
+function blerc/vim-mode-hook {
+    bleopt keymap_vi_mode_show=
+    ble-bind -m vi_nmap --cursor 2
+    ble-bind -m vi_imap --cursor 6
+    ble-bind -m vi_imap -f 'C-p' 'history-search backward:ignore-case'
+    ble-bind -m vi_imap -f 'C-n' 'history-search forward:ignore-case'
+    ble-bind -m vi_nmap -f 'C-p' 'history-search backward:ignore-case'
+    ble-bind -m vi_nmap -f 'C-n' 'history-search forward:ignore-case'
+}
+
+blehook/eval-after-load keymap_vi blerc/vim-mode-hook
+bleopt prompt_command_changes_layout=1

package/distribution/assets/AGENTS.md

@@ -0,0 +1,58 @@
+# Voice
+
+Default to one to three sentences. Answer, then stop. No opening praise and no
+closing summary of what you just wrote.
+
+Lead with the answer. The first sentence answers the question or states what
+changed. Detail I cannot infer comes after it, and only if it earns its place.
+
+Scale length to the task, not to your effort. One file changed gets two
+sentences. A tradeoff I must weigh can run a few short paragraphs. If a reply
+needs more than a screenful, say why in line one. Otherwise revise it shorter.
+
+Prose first. Bullets are for genuinely parallel items, not for chopping sentences
+into pieces.
+
+Plain words. Cut hedging, preamble, adverbs, and openers like "it is important to
+note". Delve, resolve, crucial, robust, seamless, leverage, showcase, testament,
+landscape, and underscore are banned. So is any non-technical word you would not
+say out loud. No em dashes, and no parentheses for asides. Sentence case headings.
+Bold at most one phrase per reply.
+
+Write the point once. No "not just X, but Y", no padding a list to three, and no
+bullet whose lead-in restates its own line.
+
+Terse means fewer sentences, not denser ones. Keep the articles and the verbs.
+
+Keep one idea per sentence, most of them under 15 words. Split anything past 20.
+
+# Formatting
+
+Blank line between every paragraph, heading, list, and code block. A paragraph
+break is a full blank line, not just a wrap to the next line.
+
+Never let two prose paragraphs run together, and never butt a heading against the
+text above it. The whitespace is part of the answer, not decoration.
+
+# Explanation
+
+Show the code. Quote the lines that do the thing you are explaining, trimmed to
+the ones that matter. Describing what code does is not explaining it. The lines
+do that.
+
+Draw a diagram when the answer is a flow, a sequence, or a state machine. Keep it
+under ten nodes and taller than it is wide.
+
+Snippets, diagrams, and before-and-after pairs do not count against the length
+budget.
+
+# Delegation
+
+Do the work in this thread by default. Spawn a subagent for reads that cost more
+than they return: codebase search, online research, docs and changelog lookups,
+log and CI triage, enumerating call sites, mapping an unfamiliar repo, and
+summarizing a large diff.
+
+Brief it like it has no history, because it does not. "Look into the auth flow"
+fails; "Find where a session token is validated in src/ and return the file, the
+function, and whether expiry is checked" works.

package/distribution/assets/fonts/comic-code/ComicCodeLigatures-Bold.otf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fae108ae1f7e47ffc3a5f5b63e5b3055a5dbdd44ac6cd36ae3f228beae6fd2fb
+size 92016

package/distribution/assets/fonts/comic-code/ComicCodeLigatures-BoldItalic.otf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d382359a98fb8695633bfa34d4c668b2326d329ccda0d1d85e652398031b2eac
+size 92188

package/distribution/assets/fonts/comic-code/ComicCodeLigatures-Italic.otf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:406035ccf5b2ffeb3951a54d09b2601250032b82f949b812a13b056b8ca5fb97
+size 95120

package/distribution/assets/fonts/comic-code/ComicCodeLigatures-Medium.otf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0416c5043eb3288176fe3daa4765c1bf5033b7f7d491cbc0caa727f55d27d00d
+size 94056

package/distribution/assets/fonts/comic-code/ComicCodeLigatures-MediumItalic.otf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a5e27ddce66bffc208be5dc3363ce3c58902de0cb50327decacde2d08508f88
+size 95256

package/distribution/assets/fonts/comic-code/ComicCodeLigatures-Regular.otf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ad4c5bd48a4fed1d95cdaa538c6caf7b6f65706197d03a62cb644cc7f128624
+size 93004

package/distribution/assets/fonts/nerd-fonts-symbols/symbols-nerd-font-mono-regular.otf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:442da90baae7fc1a497245b148564857e89b72e95ebacfa943381cf2b0d3b0c8
+size 6060664

package/distribution/assets/fonts/nerd-fonts-symbols/symbols-nerd-font-regular.otf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d19edb42e101b16b0c5bc121d6943b88d87357db34f0acce6e458942eaa6b2d3
+size 5525104

package/distribution/assets/oh-my-posh.toml

@@ -0,0 +1,61 @@
+console_title_template = '{{ .Folder }}'
+version = 3
+final_space = true
+
+[[blocks]]
+type = 'prompt'
+alignment = 'left'
+newline = true
+
+[[blocks.segments]]
+style = 'diamond'
+template = ' {{ .Path }} '
+foreground = '#000000'
+background = 'blue'
+type = 'path'
+
+[blocks.segments.properties]
+folder_icon = '󰉕 '
+folder_separator_icon = ' / '
+home_icon = ' '
+max_depth = 2
+style = 'agnoster_short'
+
+[[blocks.segments]]
+style = 'plain'
+template = ' {{ if or (.Working.Changed) (.Staging.Changed)  }}{{ .HEAD }}  {{ else }}{{ .HEAD }}{{ end }}'
+foreground = 'yellow'
+background = 'transparent'
+type = 'git'
+
+[blocks.segments.properties]
+branch_icon = ''
+fetch_status = true
+
+[[blocks]]
+type = 'prompt'
+alignment = 'right'
+overflow = 'hidden'
+
+[[blocks.segments]]
+style = 'plain'
+template = ' {{ .FormattedMs }}  '
+foreground = '#000000'
+background = 'lightRed'
+type = 'executiontime'
+
+[blocks.segments.properties]
+always_enabled = true
+style = 'roundrock'
+
+[[blocks]]
+type = 'prompt'
+alignment = 'left'
+newline = true
+
+[[blocks.segments]]
+style = 'plain'
+template = ' '
+foreground = 'green'
+background = 'transparent'
+type = 'text'

package/distribution/assets/skills/design/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: design
+description: Push an architecture forward. Interview me, fan out on widely varying designs, then build the API shape together.
+disable-model-invocation: true
+---
+
+# Design
+
+Turn a vague architectural idea into one API shape we agree on.
+
+Produce the API shape, not the implementation: types, function signatures, classes with their fields and methods. No function bodies, no pseudocode, no queries. If a decision depends on how something would be built, say so in prose and let me decide.
+
+## Phase 1. Interview
+
+Interview me before designing anything.
+
+Ask me about the decisions the design has to make.
+
+Some decisions depend on others. Ask the unblocked ones now and leave the rest for a later round.
+
+When a question lands better as an example than as prose, add one: a short snippet of a caller using each option, a sketch of the types, or a diagram of the flow. Keep it small and illustrative. This is not meant to represent the final design.
+
+One option per line, each labeled, never run together in a paragraph. Assume I have not read the code you are asking about: name each option by what it does, and quote the signature, variable, or line it turns on, so I can judge it without opening the file.
+
+Put every unblocked question in one round, numbered, each with your recommended answer and whatever example it needs. Then stop and wait for mine.
+
+Do not ask me for facts. Look them up, then ask me only what needs my judgement.
+
+Move on when the remaining questions can only be answered by trying designs. That is Phase 2.
+
+## Phase 2. Ideation
+
+Spawn three or four subagents at once. They all solve the same problem, and each one takes a different approach.
+
+Send them different starting material. At least one starts from the code as it is today, and at least one ignores the current code and designs as if the problem were new.
+
+Each subagent returns:
+
+- The API shape: types, signatures, classes with fields and methods.
+- An example of a caller using it.
+- A short paragraph on what the API handles for the caller.
+- The rules a caller must follow, and how it fails.
+- What this approach makes worse.
+
+Read what comes back before Phase 3. Throw away any design that does not address the problem, and spawn a replacement with a different approach until you have three or four that do. Merge any two that describe the same shape, or re-run one with different starting material. If all of them match, either the domain forces that shape or the starting material was too alike. Tell me which you think it is.
+
+## Phase 3. Choose together
+
+Present all the designs.
+
+For each design, show how a caller would use it: a code snippet or a diagram, whichever fits better.
+
+Then ask me for my feedback: what I like, what I do not like, and whether to run another round of Ideation or move on to Phase 4. Do not pick a winner.
+
+## Phase 4. Converge
+
+Build one API shape from the parts I chose. It has to read as one design, not several stuck together. When two parts conflict, pick one and tell me why.
+
+Show it to me, then refine it from my feedback until I say it is done.
+
+Then output the same things the subagents returned, and explain why you chose each part. Say how much of the code we already have has to change.

package/distribution/assets/skills/teach/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: teach
+description: Teach me a concept from the ground up, assuming no prior knowledge and no context.
+disable-model-invocation: true
+---
+
+# Teach
+
+Any concept, in one sitting, from the ground up.
+
+## Before you start
+
+Assume I know nothing about this and have no context. Do not ask what I already know.
+
+Define every term the first time it appears, including ones that seem basic. Say what problem the concept solves and what it replaces.
+
+Do not refer to anything I have not been shown. No other files, no earlier conversations, no shared setup.
+
+Start at the beginning. Teach the first idea, then add one step at a time.
+
+## The lesson
+
+Each section depends on the ones before it. Use a term only after you have defined it.
+
+Concrete before abstract. Show a case that works before you name the rule that explains it.
+
+One new idea at a time. If a sentence asks me to hold two at once, split it.
+
+Grow one running example. Do not hop between unrelated ones.
+
+## Ending
+
+Close with what this now lets me do or understand, in two sentences.
+
+Then the sources. Links to the pages you actually read, local paths for anything in this repo. Never invent a link, and if you did not read a source, say so.

package/distribution/assets/zed/keymap.json

@@ -0,0 +1,123 @@
+[
+    {
+        "context": "Editor",
+        "bindings": {
+            "d ]": null,
+            "d [": null,
+            "g shift-k": null,
+            "ctrl-f": null
+        }
+    },
+    {
+        "context": "Editor",
+        "bindings": {
+            "ctrl-w v": null,
+            "ctrl-w s": null,
+            "ctrl-w q": null,
+            "ctrl-w a": null,
+            "ctrl-w o": null
+        }
+    },
+    {
+        "bindings": {
+            "ctrl-h": "workspace::ActivatePaneLeft",
+            "ctrl-j": "workspace::ActivatePaneDown",
+            "ctrl-k": "workspace::ActivatePaneUp",
+            "ctrl-l": "workspace::ActivatePaneRight"
+        }
+    },
+    {
+        "context": "VimControl && !menu",
+        "bindings": {
+            "ctrl-w h": null,
+            "ctrl-w j": null,
+            "ctrl-w k": null,
+            "ctrl-w l": null
+        }
+    },
+    {
+        "context": "Workspace",
+        "bindings": {
+            "ctrl-s": null,
+            "ctrl-shift-w": null,
+            "ctrl-shift-t": null,
+            "ctrl-?": null,
+            "ctrl-~": null,
+            "ctrl-shift-e": null,
+            "ctrl-shift-g": null,
+            "ctrl-shift-f": null,
+            "ctrl-shift-o": null,
+            "ctrl-b": null,
+            "ctrl-alt-b": null
+        }
+    },
+    {
+        "context": "FileFinder || (FileFinder > Picker > Editor)",
+        "bindings": {
+            "ctrl-p": null
+        }
+    },
+    {
+        "context": "AgentPanel",
+        "bindings": {
+            "ctrl-n": null
+        }
+    },
+    {
+        "context": "Terminal",
+        "bindings": {
+            "ctrl-p": ["terminal::SendKeystroke", "ctrl-p"],
+            "ctrl-n": ["terminal::SendKeystroke", "ctrl-n"]
+        }
+    },
+    {
+        "context": "GitPanel",
+        "bindings": {
+            "p": "git::Push",
+            "l": "git::Pull",
+            "b": "git::Switch",
+            "c": "git::Commit",
+            "m": "git::GenerateCommitMessage",
+            "ctrl-j": "git_panel::FocusEditor",
+            "ctrl-k": "git_panel::FocusChanges"
+        }
+    },
+    {
+        "context": "ThreadsSidebar",
+        "bindings": {
+            "/": null
+        }
+    },
+    {
+        "context": "ThreadsSidebar > Editor",
+        "bindings": {
+            "ctrl-j": "menu::Cancel",
+            "ctrl-k": "menu::Cancel",
+            "ctrl-h": "menu::Cancel",
+            "ctrl-l": "menu::Cancel",
+            "j": "menu::Cancel",
+            "k": "menu::Cancel",
+            "h": "menu::Cancel",
+            "l": "menu::Cancel"
+        }
+    },
+    {
+        "context": "CommitEditor > Editor",
+        "bindings": {
+            "m": "git::GenerateCommitMessage",
+            "ctrl-k": "git_panel::FocusChanges"
+        }
+    },
+    {
+        "context": "GitPanel > Editor",
+        "bindings": {
+            "ctrl-k": "git_panel::FocusChanges"
+        }
+    },
+    {
+        "context": "vim_mode == visual && !menu",
+        "bindings": {
+            "shift-s": "vim::PushAddSurrounds"
+        }
+    }
+]