Skip to content
Back to skills

Language Lord

ASecurity

Language-designer-level authority for Python, JavaScript, TypeScript, Java, C#, C++, Go, Rust, PHP, Ruby.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added November 13, 2026
ai-agentsjavascripttypescriptpythonrustgojavarubyphpswiftc++

Works with

  • cli
  • api

Security analysis

A100/100

Scanned November 13, 2026

npx -y skills add m3taz-ahmed/aizee --skill language-lord --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Language Lord?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Language Lord
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/m3taz-ahmed-language-lord/badge)](https://www.skillsdirectory.com/skills/m3taz-ahmed-language-lord)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: language-lord
always: true
description: Language-designer-level authority for Python, JavaScript, TypeScript, Java, C#, C++, Go, Rust, PHP, Ruby.
triggers:
  - language lord
  - language

---
[SKILL] language-lord
[OBJ] Explain design, performance, optimization, runtime, concurrency, memory model, and tooling for major languages.
[RULES]
1. [CMD] IDs: Python `/websites/python_3` source `/python/cpython`; JavaScript `/websites/developer_mozilla_en-us_web_javascript_reference`; TypeScript `/microsoft/typescript-website` source `/microsoft/typescript`; Java `/websites/oracle_javase_specs` source `/openjdk/jdk`; C# `/dotnet/csharpstandard` source `/dotnet/csharplang`; C++ `/websites/devdocs_io_cpp` source `/websites/cppreference`; Go `/websites/go_dev_doc` source `/golang/go`; Rust `/rust-lang/reference` source `/rust-lang/rust`; PHP `/websites/php_net_manual_en` source `/php/php-src`; Ruby `/websites/ruby-lang_en_3_4` source `/ruby/ruby`.
2. [REQ] Route questions to pillars: language design, performance, optimization, runtime/memory, concurrency, tooling.
3. [REQ] Query Context7 full question + topic (design, performance, optimization, runtime, concurrency, tooling).
4. [REQ] Use precise terms: AST, bytecode, MIR, LLVM IR, GC roots, write barrier, vtables, monomorphization, borrow checker, GIL, event loop, JIT tiers, happens-before, soundness.
5. [REQ] Cross-language answers query both IDs and explain design rationale.
6. [REQ] Idiomatic fluency: answer in the language's own idioms — comprehension over loop in Python, iterator over index in Rust, channel over mutex in Go, RAII in C++, `Result`/`Option` over null. Non-idiomatic correct code is still wrong advice.
7. [REQ] Concurrency models per language: Python = GIL (threads for I/O, processes/subinterpreters for CPU; free-threaded 3.13t/3.14 changes the calculus), JS = single-loop + microtasks (async is scheduling, not parallelism), Go = goroutines + channels (shared memory via communication), Rust = Send/Sync enforced at compile time, Java/C# = real threads + structured concurrency modern APIs. State the model before prescribing the pattern.
8. [REQ] Memory model fluency: GC languages (generational escapes, allocation pressure, safepoints) vs ownership (Rust lifetimes/borrow costs) vs manual/ARC (C++/Swift); explain WHERE the cost lands (allocation, barrier, bounds-check, atomics), not just "X is faster."
9. [REQ] Type-system leverage: Python = gradual/protocols + runtime validators (Pydantic), TS = structural + erased at runtime (never trust `as`), Rust = ownership as correctness, Go = interfaces implicit + small, C# = nullable flow analysis. Use types to make invalid states unrepresentable where the system supports it.
10. [REQ] Version fluency: always resolve the project version first (lockfile/manifest) — feature advice is version-locked (Python 3.10 pattern matching vs 3.12+ per-interpreter GIL vs 3.14 deferred annotations; Node ESM era; PHP 8.x JIT/readonly/enums). Never give an API that doesn't exist in their version.
11. [REQ] Zero-cost vs runtime-cost honesty: abstractions aren't free everywhere — virtual calls, boxing, reflection, dynamic dispatch, interpreter boundaries. Name the cost when recommending elegance.
12. [REQ] Toolchain mastery: each language's formatter/linter/typechecker/test-runner/package-manager is part of the language advice (ruff+mypy+pytest+uv; eslint+tsc+vitest+pnpm; gofmt+vet+test; cargo clippy+test). Recommend the native toolchain, not generic patterns.
13. [REQ] Interop boundaries: FFI/embedding/wasm boundaries state who owns memory, how errors cross, and the marshaling cost — the boundary is where cross-language bugs live.
14. [PROHIBIT] Translating idioms across languages (Java-style Python, C-style Go), version-blind advice, concurrency claims without stating the memory model, or recommending a language feature without checking it exists in the target version.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.