My Tech Stack

Technology Preferences

Preferred tools and technologies. Defaults, not hard rules.

Note: This is a living document. Preferences evolve as new tools emerge and requirements change. Check the latest version before making decisions.

⚡ Quick Start

Starting a new project? Default stack:

# JavaScript/TypeScript
bun init              # Runtime + package manager
biome init            # Lint + format
just --init           # Task runner (optional)

# Python
uv init               # Python project + deps
uv add pytest         # Testing

# Version control
git init

Quick decision guide:

Prerequisites

• OS: macOS (desktop), Ubuntu (servers)
• Shell: Any (examples work in bash/zsh/fish)
• Package managers: Homebrew (macOS), system package manager (Linux)

How to Use This

When working with this user:

1. Check this file first — Before suggesting tools, consult these preferences
2. Prefer listed tools — When multiple solutions exist, default to these
3. Respect "Exploring" — Tools marked as exploring are for learning only
4. Ask before adding — Don't install unlisted tools without confirmation
5. Note deviations — If project requirements override preferences, document it

Automatic Agent Invocation

The agent must self-trigger this skill — not just when the user asks, but when the agent itself is about to make a technology decision. This includes:

Decision Flow

Agent about to recommend/install a tool?
├── Is it in the preferred list above? → Use it
├── Is it in the "Exploring" section? → Ask user before using
├── Is it unlisted? → Ask user: "This tool isn't in my preferred stack. Use it anyway?"
└── Is there a project-specific override? → Follow project, note deviation

Example self-trigger:

"I need to add a JSON parser. Checking @skills/my-tech-stack... The project uses TypeScript with bun. I'll use a native solution or check if yaml is already preferred for config."

Never silently install unlisted tools. Always consult this skill first, even when the user hasn't explicitly asked.

By Category

Development Environment

AI Agents

AI Providers

Code Quality

Biome Configuration

{
  "formatter": {
    "enabled": true,
    "indentStyle": "space",
    "indentWidth": 4
  },
  "javascript": {
    "formatter": {
      "quoteStyle": "double",
      "trailingCommas": "all"
    }
  }
}

• Indentation: 4 spaces (not tabs)
• Quote style: double
• Trailing commas: all — always use trailing commas in arrays, objects, and function parameters
• Apply to all JS/TS projects using Biome

Infrastructure & Cloud

Local dev vs deployment:

Note: Docker is intentionally not used as a local development runtime. Use devenv for local envs, docker only for building deployable images.

Local Development

API & Testing

httpie vs curl decision guide:

Security & Secrets

Remote Access

Operating System

Shell

Exploring

These tools are for learning and experimentation, not production use:

Quick Decision Reference

Starting a new project?

• Use bun for JS/TS runtime and package management
• Use TypeScript for type safety
• Use biome for linting/formatting
• Use zed as code editor RH:- Use mise for version management RH:- Use SvelteKit for web framework (when applicable)

Need to search code?

• Use ripgrep (rg) - it's faster than grep

Need to find files?

• Use fd - more user-friendly than find

Working with Python?

• Use uv for dependencies and virtual environments

Need a local development environment?

• Use devenv — Nix-based, reproducible, no Docker overhead

Need containers on macOS?

• Use docker CLI + compose for deployment packaging only
• Do not use Docker as a local dev runtime — use devenv instead

Setting up CI/CD?

• Use GitHub Actions on GitHub

Need infrastructure?

• Use Cloudflare for edge/network
• Use Terraform for IaC
• Use k3s for lightweight Kubernetes

Managing secrets?

• Use bitwarden / bws for password/secret management

Handling Conflicts

When project requirements conflict with these preferences:

1. Follow project requirements — they're the authority for that codebase
2. Note the deviation — mention that you're using X instead of the preferred Y
3. Don't update this file — project-specific overrides don't change general preferences
4. Consider asking — if the conflict seems unnecessary, ask the user about it

Example:

"The project uses npm instead of bun (your preferred package manager). I'll proceed with npm for consistency with the existing codebase."

Common Agent Mistakes

❌ Wrong: Suggesting npm when bun is available and preferred ✅ Right: "The project uses npm, but bun is preferred. I'll proceed with npm for consistency, or we can migrate."

❌ Wrong: Installing unlisted tools without asking ✅ Right: "This tool isn't in my preferred stack. Should I use it anyway?"

❌ Wrong: Using "Exploring" tools in production code ✅ Right: "This tool is in my 'Exploring' list — learning only. I'll use a production-grade alternative instead."

❌ Wrong: Suggesting TypeScript for a one-off shell script ✅ Right: Use bash/fish for scripts; TypeScript for maintained projects

❌ Wrong: Forgetting to document deviations from preferred stack ✅ Right: Always note when project requirements override personal preferences

Troubleshooting

Tool not available? → Check if it's in the "Exploring" section (learning only, not production-ready) → For missing tools, ask user before installing

Preference conflicts with project requirements? → Always follow project requirements → Document the deviation: "Using npm instead of preferred bun"

Unclear which tool to use? → Check "Quick Decision Reference" section → When in doubt, ask before adding new dependencies

Version conflicts between tools? → Use mise for version management → Pin versions in project config files

Versioning

• Last updated: 2026-06-05
• Version: 2.0
• Update notes: Migrated default local dev environment from devbox to devenv. devenv provides native Nix DSL configuration, built-in services, tasks, git hooks, and testing. Projects migrated: kindercare, event-horizon, HongKongTaxiMeterCarThing.

Related Skills

• my-agent-file-conventions — For creating AGENT.md files (not tech recommendations)