Loading...
Loading...
Apply James's technology choices and exclusions when selecting stacks, building software, adding dependencies, reviewing architecture or considering migrations. Flag meaningful deviations early, ask before unfamiliar technology, and respect recorded decisions.
npx skill4agent add jamespegg/skills tech-preferencesengineering-principlesverifiable-trustAGENTS.md| Classification | Guidance |
|---|---|
| Prefer | Go for new backends, CLIs and developer tools. Go standard library first; small focused libraries when useful. |
| Prefer | React + TypeScript + Vite for frontends, npm as package manager, ESLint and Prettier. Zustand for shared state. |
| Accept | Tailwind CSS; choose component, routing, query, form and validation libraries case by case. No mandated design system. |
| Strongly avoid | Next.js unless there is an exceptionally strong, concrete reason over React + Vite. Ask before introducing. |
| Avoid | Redux, Java, C#/.NET, PHP and heavyweight enterprise frameworks unless explicitly required. |
| Scripting | Just as task runner. Only tiny development glue in Bash; no substantial Bash scripts. Go for reusable tools. Python mainly for machine learning, not general scripting. |
| Explore | Microfrontends and Module Federation, not defaults. |
| Quality | Responsive and accessible UI, proportional to project maturity. |
sqlcimplementtddtesting