Skip to content

Instantly share code, notes, and snippets.

View bossjones's full-sized avatar
💭
Learning every damn thing I can

Malcolm Jones (bossjones/Tony Dark) bossjones

💭
Learning every damn thing I can
View GitHub Profile
@bossjones
bossjones / post_devin.sh
Last active June 5, 2025 00:44
post_devin.sh
# change password first before homebrew commands run.
sudo passwd ubuntu
# setup everything for neovim
mkdir -p ~/.local/src || true
mkdir -p ~/.local/bin || true
mkdir -p ~/.local/share || true
# SOURCE: https://rtx.pub/install.sh
@bossjones
bossjones / migration.txt
Created May 23, 2025 14:27
migration.txt
Key Achievements
- ✅ New modular structure with dedicated AI, CLI, monitoring, and storage modules
- ✅ Backward compatibility preserved - existing code continues to work with deprecation warnings
- ✅ All tests passing - no functionality broken during migration
- ✅ Deprecation system working - clear migration path for future phases
- ✅ Health check system - automated validation script for future phases
Next Steps
@bossjones
bossjones / get_imgUrls.js
Created May 22, 2025 03:50
get_imgUrls.js
// This script collects the URLs of all images with the class 'bbImage' on the page. SS
const imageUrls = Array.from(document.querySelectorAll('img.bbImage')).map(img => img.src);
console.log(imageUrls);
@bossjones
bossjones / links.txt
Created May 21, 2025 22:01
mcp_remote_and_git_mcp_for_repo_context.md
@bossjones
bossjones / brew_install_ansible.txt
Created May 21, 2025 20:48
brew_install_ansible.txt
~/dev/netdata-org
❯ brew install ansible
==> Auto-updating Homebrew...
Adjust how often this is run with HOMEBREW_AUTO_UPDATE_SECS or disable with
HOMEBREW_NO_AUTO_UPDATE. Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).
==> Downloading https://ghcr.io/v2/homebrew/portable-ruby/portable-ruby/blobs/sha256:fd162df7a06190ee800a9e6afd28f4466d33548821a480ba043cd927b44d60f7
############################################################################################################################################################################################################# 100.0%
==> Pouring portable-ruby-3.4.4.arm64_big_sur.bottle.tar.gz
==> Auto-updated Homebrew!
==> Updated Homebrew from 1399d2e98a to 1cfc303969.
@bossjones
bossjones / so_audit.sh
Last active May 16, 2025 23:54
so_audit.sh
sudo du -sch /etc /opt/so/conf /opt/so/saltstack /opt/so/log /opt/so/state /etc/docker /etc/sysctl.d /nsm/backup /opt/so/custom /opt/so/rules
BACKUP_DATE=$(date +%Y%m%d)
sudo tar czpf /tmp/so_backup_$BACKUP_DATE.tar.gz \
/opt/so \
/etc/docker/daemon.json \
/etc/sysctl.d/99-reserved-ports.conf \
/etc/soversion \
#!/bin/bash
# Enhanced script to collect information needed for configuring Netdata monitoring
# for Proxmox VE, ZFS pools, and S.M.A.R.T. on a Proxmox 8.4 host
# Check if script is run as root
if [ "$(id -u)" -ne 0 ]; then
echo "This script must be run as root" >&2
exit 1
fi

Okay, let's break down prompt_library.py into a more modular structure within the promptlib directory.

The core idea is to separate concerns:

  1. Data Structures (Types): Definitions of how cursor rules look.
  2. Constants: Configuration like paths and patterns.
  3. Core Rule Logic: Functions for reading, parsing, and generating rule files.
  4. MCP Endpoints: Separate files for Resources, Prompts, and Tools.
  5. Complex Workflows: Isolate the multi-phase workflow logic.
  6. Server Setup: Initialize the FastMCP server and register all endpoints.

BMad's Best Practices Cursor Custom Agents and Rules Generator

BMad Version: 3.1 (March 30, 2025) Cursor Version: 0.48+

Note from BMad: This repo has become much more successful than I originally envisioned, and I want to thank everyone for the feedback, support, contributions, and also feedback on the youtube channel. I now realize that many are using what I originally thought would be just a way to document some best practices around cursor rules and a simple rule that helps generate the rules - all with the intent of creating a separate updated workflow repo and set of documentation. But this has evolved.

With that in mind, going forward after this correction update - any major changes will follow a versioning standard, and upgrade paths or instructions to migrate if you are already using a prior version of rules or workflows whenever there is a significant potentially breaking change - although I will try to avoid that somehow depending on what comes with Cursor updates or workflow improvements. Keep