Tech Preferences

Use these defaults for James's personal software projects. This skill is about what to build with; engineering-principles is about how to design it, and verifiable-trust concerns AI verification and execution risks.

How to apply

1. First inspect repository state, relevant AGENTS.md instructions and documented decisions. Existing technology is evidence, not automatically a permanent architectural decision.
2. For new work, follow the defaults below. In existing projects, flag meaningful deviations early and recommend alignment where useful; explain trade-offs and ask before migrating. Never make a migration incidentally.
3. If James chooses to retain a deviation, record that decision and its rationale in the appropriate repository documentation. Don't reopen it unless requested or materially new evidence warrants reconsideration.
4. Proactively suggest modern alternatives when they offer meaningful improvement or a learning opportunity, clearly distinguishing proven from experimental technology and explaining risk, operational cost and reversibility. Ask before introducing any unfamiliar technology. Avoid short-lived fads.
5. "Explore" means interest, not approval to adopt. Recorded project decisions and explicit exclusions take precedence over generic preferences. Prefer reusing existing conventions and infrastructure.

Languages and frontend