@fredlackey/devutils 0.0.18 → 0.0.19

package/README.md

@@ -1,182 +1,64 @@
 # DevUtils CLI
 
-> **Early Development (v0.0.1)** — This project is currently a proof of concept. Core functionality is being built and tested. You're welcome to:
-> - Use it as-is and provide feedback
-> - Participate in development
-> - Watch for future releases (v0.1.0 for beta, v1.0.0 for stable)
-> - [Reach out](#contact) with questions or suggestions
+> **Rebuild in Progress (v0.0.19)** — This project is being restructured from the ground up. The previous version (v0.0.18) tried to do too much too fast. The new approach is config-driven, user-driven, and machine-aware. If you're looking for the old code, it's been preserved in the `_rebuild/` directory.
 
-Stop wasting hours setting up new machines. One command, any platform, ready to code.
+## What Happened
 
-## The Problem
+The original DevUtils CLI was built as a rigid, opinionated toolkit. It assumed a specific workflow, shipped dozens of global scripts, and tried to be everything to everyone out of the gate. After real-world usage and feedback, it became clear that this approach wouldn't hold up. It was too prescriptive, too fragile across environments, and too hard for users to adapt to their own needs.
 
-Every developer knows the pain:
-- New laptop? Spend a day installing tools and configuring dotfiles
-- Switch between work and personal projects? Juggle SSH keys and git configs
-- Help a teammate set up their environment? Walk them through 50 different steps
-- Work on macOS at home, Linux in prod? Remember two sets of commands
+## What's Changing
 
-## The Solution
+The new version takes a fundamentally different approach:
 
-```bash
-npm install -g @fredlackey/devutils
-dev setup
-```
-
-That's it. DevUtils CLI detects your operating system and installs everything you need. Your configuration travels with you.
-
-## Installation
-
-### If You Have Node.js Installed
-
-If you already have Node.js 18+ on your machine, install DevUtils CLI as a global npm package:
-
-```bash
-npm install -g @fredlackey/devutils
-```
-
-### Fresh Machine (No Node.js)
-
-For a fresh machine without Node.js, run the bootstrap script. It installs everything you need: build tools, nvm, Node.js LTS, and DevUtils CLI.
-
-**macOS:**
-```bash
-bash -c "$(curl -LsS https://raw.github.com/fredlackey/devutils-cli/main/setup.sh)"
-```
-
-**Ubuntu / Debian / Raspberry Pi OS:**
-```bash
-bash -c "$(wget -qO - https://raw.github.com/fredlackey/devutils-cli/main/setup.sh)"
-```
-
-**Amazon Linux / RHEL / Fedora:**
-```bash
-bash -c "$(curl -LsS https://raw.github.com/fredlackey/devutils-cli/main/setup.sh)"
-```
-
-The script is interactive by default. For automated/CI environments, add `--no-prompt`:
-
-```bash
-bash -c "$(curl -LsS https://raw.github.com/fredlackey/devutils-cli/main/setup.sh)" -- --no-prompt
-```
+### Config-Based, Not Opinion-Based
 
-## Quick Start
+Instead of shipping a fixed set of behaviors, DevUtils will be driven by user configuration. You tell it what matters to you, and it adapts.
 
-```bash
-# Install essential tools (git, ssh, gpg, etc.)
-dev setup
+### User Onboarding
 
-# Set up your developer profile
-dev configure
+The first run walks you through a lightweight onboarding process. It learns who you are, what tools you care about, and how your machine is set up. No assumptions.
 
-# Install your favorite tools
-dev install vscode
-dev install docker
-dev install node
-```
+### Machine-Aware Profiles
 
-## Key Features
+Configuration is scoped to the machine you're on. A laptop, a server, and a VM can each have their own rules without conflicting.
 
-### Cross-Platform Package Installation
+### Rule-Based Behavior
 
-Forget whether it's `brew install`, `apt-get install`, or `choco install`. Just run:
-
-```bash
-dev install docker
-dev install node
-dev install vscode
-```
+Users define rules for folders, tools, and workflows. DevUtils enforces those rules rather than imposing its own. For example:
+- "This folder always uses this git identity"
+- "This machine should have these tools installed"
+- "Run these checks when I open a new terminal"
 
-DevUtils CLI figures out the right command for macOS, Ubuntu, Raspberry Pi OS, Amazon Linux, Windows, or Git Bash.
-
-### Git Identity Management
-
-Manage multiple git identities for work, personal, and client projects:
-
-```bash
-# Create identities with SSH and GPG keys
-dev identity add work --email you@company.com
-dev identity add personal --email you@gmail.com
-
-# Link identities to folders - commits automatically use the right credentials
-dev identity link work ~/work
-dev identity link personal ~/personal https://github.com/yourusername
-```
+### Temporary Workspace
 
-Clone with any URL format. DevUtils CLI routes it through the correct SSH key automatically.
+DevUtils sets up a managed workspace inside the user's home directory for staging, caching, and intermediate state. Nothing touches system-level paths unless you ask for it.
 
-### Smart .gitignore Management
+## Installation
 
 ```bash
-dev ignore node      # Add Node.js patterns
-dev ignore macos     # Add .DS_Store and friends
-dev ignore vscode    # Add .vscode/ patterns
-```
-
-Patterns are managed in sections—run it twice and it won't duplicate.
-
-### Portable Configuration
-
-Your `~/.devutils` file stores your preferences:
-
-```json
-{
-  "user": {
-    "name": "Jane Developer",
-    "email": "jane@example.com"
-  },
-  "identities": {
-    "work": { "email": "jane@company.com", "sshKey": "~/.ssh/id_ed25519_work" },
-    "personal": { "email": "jane@gmail.com", "sshKey": "~/.ssh/id_ed25519_personal" }
-  }
-}
+npm install -g @fredlackey/devutils
 ```
 
-Copy this file to a new machine and run `dev identity sync` to regenerate all your SSH configs.
-
-## Supported Platforms
-
-| Platform | Package Manager |
-|----------|-----------------|
-| macOS | Homebrew |
-| Ubuntu | APT / Snap |
-| Raspberry Pi OS | APT / Snap |
-| Amazon Linux | DNF / YUM |
-| Windows | Chocolatey / winget |
-| Git Bash | Manual / Portable |
+> The CLI is published but actively being rebuilt. Expect breaking changes until v0.1.0.
 
-## Available Commands
+## Previous Version
 
-| Command | Description |
-|---------|-------------|
-| `dev setup` | Install essential development tools |
-| `dev configure` | Set up your developer profile |
-| `dev install <tool>` | Install a tool (cross-platform) |
-| `dev identity add` | Create a new git identity with keys |
-| `dev identity link` | Link an identity to a folder or remote |
-| `dev identity unlink` | Remove a folder link |
-| `dev ignore <tech>` | Add .gitignore patterns |
-| `dev status` | Show current configuration |
+The v0.0.18 codebase (commands, scripts, installers, utilities) has been moved to `_rebuild/` and is preserved for reference. Useful patterns and utilities will be pulled forward into the new architecture as needed.
 
-## Why DevUtils CLI?
+## Roadmap
 
-- **Zero memorization** — Same commands on every platform
-- **Identity isolation** — Never accidentally commit with the wrong email again
-- **Reproducible setups** — New machine? `dev setup && dev identity sync`
-- **No lock-in** — Standard tools, standard configs. Uninstall anytime
-
-## Contributing
-
-Contributions welcome! Feel free to open issues or submit pull requests.
+- [ ] User onboarding flow
+- [ ] Config file schema (`~/.devutils/config.json`)
+- [ ] Machine profile detection and storage
+- [ ] Rule engine for folder and tool behaviors
+- [ ] Migrate useful scripts and installers from `_rebuild/`
 
 ## Contact
 
-Questions, suggestions, or just want to chat about the project?
-
 **Fred Lackey**
-- Email: [fred.lackey@gmail.com](mailto:fred.lackey@gmail.com)
-- Website: [fredlackey.com](https://fredlackey.com)
-- GitHub: [@FredLackey](https://github.com/FredLackey)
+- Email: [fred.lackey@gmail.com](mailto:fred.lackey@gmail.com)  
+- Website: [fredlackey.com](https://fredlackey.com)  
+- GitHub: [@FredLackey](https://github.com/FredLackey)  
 
 ## License
 

package/package.json

@@ -1,91 +1,14 @@
 {
   "name": "@fredlackey/devutils",
-  "version": "0.0.18",
-  "description": "A globally-installable Node.js CLI toolkit for bootstrapping and configuring development environments across any machine.",
+  "version": "0.0.19",
+  "description": "A config-driven CLI toolkit for bootstrapping and managing development environments across any machine.",
   "main": "src/index.js",
   "bin": {
-    "dev": "./bin/dev.js",
-    "afk": "./src/scripts/afk.js",
-    "backup-all": "./src/scripts/backup-all.js",
-    "backup-source": "./src/scripts/backup-source.js",
-    "brewd": "./src/scripts/brewd.js",
-    "brewi": "./src/scripts/brewi.js",
-    "brewr": "./src/scripts/brewr.js",
-    "brews": "./src/scripts/brews.js",
-    "brewu": "./src/scripts/brewu.js",
-    "c": "./src/scripts/c.js",
-    "ccurl": "./src/scripts/ccurl.js",
-    "certbot-crontab-init": "./src/scripts/certbot-crontab-init.js",
-    "certbot-init": "./src/scripts/certbot-init.js",
-    "ch": "./src/scripts/ch.js",
-    "claude-danger": "./src/scripts/claude-danger.js",
-    "clean-dev": "./src/scripts/clean-dev.js",
-    "clear-dns-cache": "./src/scripts/clear-dns-cache.js",
-    "clone": "./src/scripts/clone.js",
-    "code-all": "./src/scripts/code-all.js",
-    "count": "./src/scripts/count.js",
-    "count-files": "./src/scripts/count-files.js",
-    "count-folders": "./src/scripts/count-folders.js",
-    "d": "./src/scripts/d.js",
-    "datauri": "./src/scripts/datauri.js",
-    "delete-files": "./src/scripts/delete-files.js",
-    "docker-clean": "./src/scripts/docker-clean.js",
-    "dp": "./src/scripts/dp.js",
-    "e": "./src/scripts/e.js",
-    "empty-trash": "./src/scripts/empty-trash.js",
-    "evm": "./src/scripts/evm.js",
-    "fetch-github-repos": "./src/scripts/fetch-github-repos.js",
-    "get-channel": "./src/scripts/get-channel.js",
-    "get-course": "./src/scripts/get-course.js",
-    "get-dependencies": "./src/scripts/get-dependencies.js",
-    "get-folder": "./src/scripts/get-folder.js",
-    "get-tunes": "./src/scripts/get-tunes.js",
-    "get-video": "./src/scripts/get-video.js",
-    "git-backup": "./src/scripts/git-backup.js",
-    "git-clone": "./src/scripts/git-clone.js",
-    "git-pup": "./src/scripts/git-pup.js",
-    "git-push": "./src/scripts/git-push.js",
-    "h": "./src/scripts/h.js",
-    "hide-desktop-icons": "./src/scripts/hide-desktop-icons.js",
-    "hide-hidden-files": "./src/scripts/hide-hidden-files.js",
-    "install-dependencies-from": "./src/scripts/install-dependencies-from.js",
-    "ips": "./src/scripts/ips.js",
-    "iso": "./src/scripts/iso.js",
-    "killni": "./src/scripts/killni.js",
-    "ll": "./src/scripts/ll.js",
-    "local-ip": "./src/scripts/local-ip.js",
-    "m": "./src/scripts/m.js",
-    "map": "./src/scripts/map.js",
-    "mkd": "./src/scripts/mkd.js",
-    "ncu-update-all": "./src/scripts/ncu-update-all.js",
-    "nginx-init": "./src/scripts/nginx-init.js",
-    "npmi": "./src/scripts/npmi.js",
-    "o": "./src/scripts/o.js",
-    "org-by-date": "./src/scripts/org-by-date.js",
-    "p": "./src/scripts/p.js",
-    "packages": "./src/scripts/packages.js",
-    "path": "./src/scripts/path.js",
-    "ports": "./src/scripts/ports.js",
-    "q": "./src/scripts/q.js",
-    "refresh-files": "./src/scripts/refresh-files.js",
-    "remove-smaller-files": "./src/scripts/remove-smaller-files.js",
-    "rename-files-with-date": "./src/scripts/rename-files-with-date.js",
-    "resize-image": "./src/scripts/resize-image.js",
-    "rm-safe": "./src/scripts/rm-safe.js",
-    "s": "./src/scripts/s.js",
-    "set-git-public": "./src/scripts/set-git-public.js",
-    "show-desktop-icons": "./src/scripts/show-desktop-icons.js",
-    "show-hidden-files": "./src/scripts/show-hidden-files.js",
-    "tpa": "./src/scripts/tpa.js",
-    "tpo": "./src/scripts/tpo.js",
-    "u": "./src/scripts/u.js",
-    "vpush": "./src/scripts/vpush.js",
-    "y": "./src/scripts/y.js"
+    "dev": "./bin/dev.js"
   },
   "files": [
     "bin/",
-    "src/",
-    "files/"
+    "src/"
   ],
   "scripts": {
     "test": "echo \"Error: no test specified\" && exit 1"
@@ -95,7 +18,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/FredLackey/devutils-cli.git"
+    "url": "git+ssh://git@github.com/FredLackey/devutils-cli.git"
   },
   "keywords": [],
   "author": {

package/bin/dev.js

@@ -1,16 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * @fileoverview Main entry point for the `dev` CLI command.
- * This file handles tab completion detection and delegates to the CLI module.
- */
-
-// Handle tab completion before loading the full CLI
-// This allows for fast completion responses
-if (process.env.COMP_LINE) {
-  require('../src/completion').handleCompletion();
-  process.exit(0);
-}
-
-// Normal CLI execution
-require('../src/cli').run();

package/files/claude/.claude/commands/setup-context.md

@@ -1,3 +0,0 @@
-Read the following files for context:
-- README.md
-- CLAUDE.md

package/files/monorepos/_archive/README.md

@@ -1,36 +0,0 @@
-# Archive
-
-**DO NOT READ OR MODIFY CONTENTS OF THIS FOLDER.**
-
-## Purpose
-
-This folder is a **failsafe backup**—a last resort for code and resources that may need to be referenced in rare circumstances. Think of it as a "soft delete" before permanent removal.
-
-## Critical Warnings
-
-- **Nothing in this folder should be trusted as correct**
-- Contents are outdated, deprecated, or potentially broken
-- Code here has been replaced by better implementations elsewhere
-- Documentation may be inaccurate or misleading
-
-## AI Instructions
-
-**This folder must be ignored by all AI processes:**
-- Do NOT read files from this folder
-- Do NOT reference code or patterns found here
-- Do NOT modify or update any contents
-- Do NOT use this folder as a source of truth for anything
-
-## What Belongs Here
-
-- Deprecated code kept only as an emergency reference
-- Old implementations preserved before deletion
-- Retired features that might need forensic review
-- Anything we're not ready to permanently delete
-
-## Guidelines
-
-- Date items when archiving (use folder names like `YYYYMMDD/`)
-- Include a brief note explaining why the item was archived
-- Never actively maintain or improve archived code
-- Periodically review and permanently delete obsolete items

package/files/monorepos/_legacy/README.md

@@ -1,36 +0,0 @@
-# Legacy
-
-**CONTENTS SHOULD NOT BE TRUSTED. USE WITH CAUTION.**
-
-## Purpose
-
-This folder contains **previous attempts** at building the same concepts, packages, or even the entire project. Think of it as the "last version" or "last attempt" before the current rebuild.
-
-We keep this code for reference, but if we're rebuilding, it's for a reason:
-
-- **A)** We learned enough about the problem and now want to do it properly
-- **B)** We failed completely and need to start over, but want to remember our mistakes
-
-This folder is one step better than `/_archive`—we may occasionally refer to it—but it still should not be treated as a source of truth.
-
-## AI Instructions
-
-**Approach this folder with skepticism:**
-- Do NOT trust patterns or implementations found here
-- Do NOT copy code from this folder without explicit instruction
-- Do NOT use this as a reference for "how things should work"
-- Contents represent what we're moving *away from*, not toward
-
-## What Belongs Here
-
-- Previous iterations of the current project
-- Failed attempts preserved for learning
-- Old architectures we've outgrown
-- Code that "worked" but wasn't good enough
-
-## Guidelines
-
-- Note why the previous attempt was abandoned
-- Reference only when specifically trying to avoid past mistakes
-- Never improve or maintain legacy code—build new instead
-- Move to `/_archive` once the new implementation is stable and proven

package/files/monorepos/ai-docs/README.md

@@ -1,33 +0,0 @@
-# AI Docs
-
-This folder contains documentation **created by AI, for AI**.
-
-## Purpose
-
-A persistent knowledge base that preserves AI research, discoveries, and insights so they don't have to be repeated. When AI investigates a concept, researches a technique, or works through a problem, the findings are documented here for future reference.
-
-This eliminates redundant research and discovery processes across sessions.
-
-## Usage
-
-- AI writes documentation here after research or discovery work
-- AI reads from this folder to recall prior findings
-- Humans may reference content but it's optimized for AI consumption
-- Treat as a "memory" that persists between AI sessions
-
-## What Belongs Here
-
-- Research findings and conclusions
-- Technology evaluations and comparisons
-- Best practices and implementation patterns
-- Convention documentation and standards
-- Schema definitions
-- Brainstorming outcomes and design decisions
-- Concept explanations and technical deep-dives
-
-## Guidelines
-
-- Write in clear, structured formats AI can easily parse
-- Include context about why research was performed
-- Update documents as understanding evolves
-- Prefer comprehensive detail over brevity

package/files/monorepos/apps/README.md

@@ -1,24 +0,0 @@
-# Apps
-
-This folder contains the main applications for the project.
-
-## Purpose
-
-Each application in this folder represents a distinct, deployable unit—whether it's a frontend, backend API, admin tool, or other service. Applications are organized as separate subdirectories, each with their own dependencies and configuration.
-
-## Structure
-
-```
-apps/
-├── [app-name]-ui-[framework]/    # Frontend applications
-├── [app-name]-api-[framework]/   # Backend API services
-├── [app-name]-admin-[framework]/ # Admin tools
-└── ...
-```
-
-## Guidelines
-
-- Each application should be independently runnable
-- Applications may depend on shared code from `/packages`
-- Keep application-specific code within its subdirectory
-- Use consistent naming: `[project]-[type]-[framework]`

package/files/monorepos/docs/README.md

@@ -1,40 +0,0 @@
-# Docs
-
-This folder contains documentation **created by humans, for humans**.
-
-## Purpose
-
-The counterpart to `/ai-docs`—this folder holds documentation intended for human authors and human readers. Content here should be accessible, verbose enough for clarity, and written so that a junior developer or project manager can understand it.
-
-AI may assist with editing, formatting, or refining language, but the content is fundamentally human-focused.
-
-## Audience
-
-- Junior developers onboarding to the project
-- Project managers needing business context
-- Team members referencing technical decisions
-- External contributors or stakeholders
-
-## What Belongs Here
-
-- Architecture decision records (ADRs)
-- Setup and installation guides
-- API documentation and usage examples
-- Business logic explanations
-- Deployment and operations guides
-- Contributing guidelines
-- Project overviews and roadmaps
-
-## Guidelines
-
-- Write for clarity over brevity
-- Assume the reader may not have full context
-- Explain the "why" alongside the "what"
-- Use plain language; avoid unnecessary jargon
-- Include examples where helpful
-
-## What Does NOT Belong Here
-
-- AI-generated research or discovery docs (use `/ai-docs`)
-- Exploratory research materials (use `/research`)
-- Auto-generated API docs (keep with the relevant app)

package/files/monorepos/packages/README.md

@@ -1,25 +0,0 @@
-# Packages
-
-This folder contains shared libraries and utilities used across applications.
-
-## Purpose
-
-Packages are reusable code modules that provide common functionality to multiple applications in the monorepo. This promotes code reuse, consistency, and maintainability across the project.
-
-## Structure
-
-```
-packages/
-├── [project]-utils/     # Utility functions and helpers
-├── [project]-types/     # Shared type definitions
-├── [project]-config/    # Shared configuration
-└── ...
-```
-
-## Guidelines
-
-- Packages should be framework-agnostic when possible
-- Each package should have a single, well-defined responsibility
-- Packages are imported by applications in `/apps`
-- Keep packages small and focused
-- Document public APIs within each package

package/files/monorepos/research/README.md

@@ -1,29 +0,0 @@
-# Research
-
-This folder is a **workspace for reference artifacts**—often excluded from version control.
-
-## Purpose
-
-A staging area where developers can pull in external artifacts, code samples, documentation, or even entire repos from other sources. This keeps useful reference material close at hand without polluting the actual codebase.
-
-The goal: work within a single IDE while having access to everything you need.
-
-## Git Status
-
-This folder is **typically excluded from the repository** (added to `.gitignore`). Contents are meant to be temporary and local to each developer's environment. Don't assume anything here will persist or be shared.
-
-## What Belongs Here
-
-- Cloned repos for reference
-- Code samples from external sources
-- API documentation downloads
-- Third-party library source code
-- Screenshots, PDFs, or other reference materials
-- Anything useful for development that doesn't belong in the repo
-
-## Guidelines
-
-- Treat this folder as ephemeral and personal
-- Don't rely on contents being available to others
-- Clean up periodically—this isn't long-term storage
-- If findings are valuable, document them in `/ai-docs` or `/docs`

package/files/monorepos/scripts/README.md

@@ -1,24 +0,0 @@
-# Scripts
-
-This folder contains development, build, and operational scripts.
-
-## Purpose
-
-Utility scripts that automate common tasks across the monorepo. These scripts help with development workflows, builds, deployments, and maintenance operations.
-
-## What Belongs Here
-
-- Build and compilation scripts
-- Development environment setup
-- Database migration helpers
-- Deployment automation
-- Code generation tools
-- Maintenance and cleanup utilities
-
-## Guidelines
-
-- Make scripts executable (`chmod +x`)
-- Include usage comments at the top of each script
-- Use consistent naming conventions
-- Document any required environment variables
-- Keep scripts idempotent when possible