language-selection
Skill0 starsChanged 41 days agoMITView on GitHub
Use when choosing a programming language or app stack, comparing Go, Rust, Zig or other languages, starting a new app whose stack is undecided, or proposing a language migration for an existing app. Do not use for routine changes within an established stack.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- annatchijova/SKILLStheir own version, first seen Jul 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- annatchijova/SKILLS★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- afkSkill
- apple-contactsSkill
- apple-devSkill
- apple-notesSkill
- apple-photosSkill
- bug-huntSkill
- catch-upSkill
- cherriSkill
- chrome-controlSkill
- claude-sessionsSkill
- coordinatorSkill
- discountsSkill
- forge-skillSkill
- groupmeSkill
- herdr-crewSkill
- iconsSkill
- imsgSkill
- laterSkill
- mac-controlSkill
- nix-mechanicsSkill
- notion-cliSkill
- posthogSkill
- quotaSkill
- redditSkill
- rustSkill
- scoutSkill
- semverSkill
- social-contentSkill
- spotifySkill
- travelSkill
- validate-ideaSkill
- verdictSkill
- web-reconSkill
- whatsappSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Existing or new?: Keep an existing app's language unless a measured performance or concrete integration benefit justifies changing it.
- Distinctive: line 27
Narrow the defaults: Use the table below as a starting point, subordinate to hard constraints.
- Distinctive: line 29
Prove uncertainty: When two candidates differ materially, spike the difficult library, target deployment and resource budget.
- Distinctive: line 51
Use the declared machine tools for common work and a pinned project development environment for specialist compilers or different versions.
- Very specific: line 61
Read Go references for the relevant tool or language.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Language selection
Choose for the product's workload, platform, reliability and maintenance. An AI author's ability to write an unfamiliar language removes personal syntax familiarity as a constraint; it does not remove integration or operational cost.
Gates, in order
- Existing or new? Keep an existing app's language unless a measured performance or concrete integration benefit justifies changing it. For a performance migration, set an end-to-end target, profile representative inputs and prefer replacing a hot component before a whole-app rewrite.
- Hard constraints. Identify platform APIs, required libraries, hosting, signing, persistence and distribution. Consult the applicable deployment policy. A favorite language does not justify new hosting. Treat an unspecified host as unresolved before committing to a deployment plan.
- Resource targets. State relevant startup, peak memory, throughput or latency targets. Separate CPU/allocation work from network/database/model waits. New apps may choose Rust prospectively for tight resource budgets or useful type/ownership guarantees; an existing incident is not required.
- Narrow the defaults. Use the table below as a starting point, subordinate to hard constraints. Do not force one language across every layer.
- Prove uncertainty. When two candidates differ materially, spike the difficult library, target deployment and resource budget. Record the chosen language, runner-up and reason in the project's AGENTS.md. Explain the recommendation during design; do not reopen a settled choice on every edit.
| Workload | First candidate | Switch when |
| Native Apple UI or Apple-bound integration | Swift | A measured/shared core justifies an additional language |
| Browser UI, extensions, thin API in an established web stack | TypeScript | A supported alternative has a specific integration or resource advantage |
| Ordinary portable service, sync tool, CLI or daemon | Go | Hosting/libraries or stronger ownership/invariant/resource requirements favor another language |
| Demanding native core, parser, tight memory/latency budget | Rust | Required interop, libraries or a measured spike favor a different implementation |
| ML/data libraries or Python-centric runtime integration | Python | The actual bottleneck and dependency path support moving a component |
| Specialized C-facing library or explicit allocator control | Evaluate Zig against Rust | Lifetime correctness, compiler/editor compatibility and the target build are proven |
| JVM/.NET/BEAM, shared mobile UI, scientific/GPU kernel requirements | Evaluate the matching ecosystem | A concrete platform/library/product need earns the extra runtime or toolchain |
A compile/typecheck pass is useful evidence, not proof of correct product behavior. Verify external-input validation, tests, lint, realistic resource behavior, packaging and the installed app. Do not promise a universal language speed ranking or better AI coding success without measurements.
Toolchains
Use the declared machine tools for common work and a pinned project development environment for specialist compilers or different versions. Keep builds reproducible and package installation declarative where the environment requires it. A compiler's availability does not authorize changing the app's language.
For Go, use repository just verbs first; otherwise check formatting,
go vet ./..., go test ./..., go test -race ./... on supported targets,
and build/run the binary. Add representative benchmarks and native fuzzing when
useful. Inspect dependencies with govulncheck; the race detector only covers
executed paths. Disable automatic SDK/editor-tool downloads when Nix owns them.
Read Go references for the relevant tool or language.
For Rust work, use the rust skill if available.
Credits: official language and platform documentation (constraints and tool checks); Go's compatibility, GC and race-detector guides (maintenance and runtime tradeoffs); Rust and Zig references (ownership and allocator choices).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.