tech-preference-tracker

Recommends consistent technology stacks by tracking cumulative user preferences across projects.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill tech-preference-tracker-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-preference-tracker
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/tech-preference-tracker
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill tech-preference-tracker-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing a language, framework, or platform for every new project from scratch leads to inconsistent stacks and zero accumulated expertise. This Skill reads your cumulative tech preference matrix and recommends choices aligned with your prior projects, balancing performance, update ease, and learning-cost recovery. ## Core Features & Use Cases - Preference Matrix Lookup: Reads your tech matrix (languages, runtimes, frameworks, deploy targets, DB, state management, testing, lint) from a personal wiki entity file and matches new project requirements against it. - Drift Detection: Scans existing repositories (package.json, requirements.txt, pyproject.toml) to report which projects have drifted from your declared stack, then lets you fix the drift or update the matrix. - Matrix Updates: When you deliberately adopt a new technology, updates the preference matrix and logs the change with a one-line rationale. - Use Case: You ask "what stack should I use for this new project?" and receive a recommendation scored on performance, update ease, learning-cost recovery, ecosystem stability, and Korea-market fit—defaulting to your existing matrix when scores tie. ## Quick Start Ask the assistant to recommend a stack for your new project consistent with your previous projects, and it will audit your preference matrix and report any drift.

Frequently Asked Questions about tech-preference-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a tech stack consistent with my previous projects?

Maintain a preference matrix listing your default language, runtime, framework, deploy target, database, state management, testing, and lint tools. When starting a new project, match requirements against the matrix and keep the existing option unless a new candidate scores higher on performance and update ease.

How to detect tech stack drift across multiple repositories?

Scan each repository's package.json, requirements.txt, or pyproject.toml and compare the detected tools against your declared preference matrix. Produce a drift report listing mismatches per repo, then decide whether to fix the drift or update the matrix.

What criteria should I use to evaluate a new framework?

Score candidates on five axes: benchmark-based performance, update ease for a solo maintainer, learning-cost recovery across multiple projects, ecosystem stability over one year, and regional market fit such as local payment and auth compatibility.

When should I update my tech preference matrix instead of fixing drift?

Update the matrix only when you deliberately adopt a new technology after evaluation, not when a project accidentally diverges. Record the change with a one-line rationale so future recommendations reflect the intentional shift.

What are the limitations of preference-based stack recommendations?

A fixed matrix can block genuinely better new technologies if treated as a lock, so an explicit update path is required. It also depends on the matrix being accurate; stale or missing entries produce weak recommendations.