Use D3.js v7 to show complex data and draw documentation diagrams (charts, trees, networks, heatmaps, boxes-and-arrows flows), with the d3 MCP server for the API reference and d3-svg for static SVG files. Use it whenever you are asked for a chart, graph, plot, diagram or visualization, or touch D3 code.
Andrei Merlescu
Computer Engineer. ex Warner Bros Games, Oracle and Cisco. Neurodivergent. Former Orphan.
Skills
andreimerlescu/skills
npx skilld add andreimerlescu/skills --allUse for ANY date or time calculation or date-handling code in Rust or Go. Covers date arithmetic ("today + 90 days", "first monday of january 2026 + 3 weeks", "last wednesday + 5 days", "every 2 weeks after <date>"), day counts, business days, month/year boundaries, time zones and DST, and the Gregorian, Julian, Hebrew, Hijri and Chinese calendars. Includes a verified calculator script (scripts/datecalc.py), tested chrono and Go time recipes, and golden test data. Load it before writing or debugging date code, and whenever you are unsure what a date API does.
Mandatory rules for any task that generates, inspects, imports, exports, trusts, rotates or uses OpenPGP keys with GnuPG 2 (gpg, gpgv, gpg-agent, gpgconf), including encrypting, decrypting, signing and verifying in scripts, CI, or agent-driven shell sessions.
Mandatory Go documentation and code-comment discipline for DeepSeek V4 and other local coding agents. Produces useful GoDoc and IDE hovers, complete parameter and behavioral contracts, realistic usage examples, explanatory implementation comments, and verified repository-relative file:line usage references maintained as generated documentation.
Mandatory production-grade Go discipline for every task that writes, edits, reviews, tests, debugs, documents, benchmarks or operates Go code, go.mod, go.sum or Go CI. Enforces explicit ownership of shared state, race freedom, bounded goroutines, honest verification with real command output, and Go 1.27.1+ compatibility. Tuned for local agents such as DeepSeek V4.
Clarify vague or underspecified requests through rigorous, iterative questioning before implementation. Use when the user says "grill me", asks to eliminate ambiguity, wants a requirements interview, or a consequential project decision is unclear. Inspect existing context first; ask targeted follow-ups until scope is approved; revise the repository's AGENTS.md with user-confirmed, reusable instructions and iterate on that file until the user is satisfied. Never guess material requirements.
Mandatory senior-level Rust engineering standard for every Rust implementation, review, refactor, FFI, or Cargo task. Prevents pointer-through-channel slop, unsynchronized shared maps, unbounded concurrency, dropped task errors, fabricated passing tests, unchecked unsafe code, and incomplete implementations. Enforces idiomatic ownership, bounded workers, real tests, rustdoc, security, and independently verifiable delivery. Load for ALL Rust work.
Mandatory security-conscious engineering for every task that writes, edits, reviews, configures, builds, packages or ships code, scripts, Dockerfiles, CI, config or docs, and especially any task where the agent is handed, discovers or reads a credential, API key, token, password, private key, certificate, connection string, sample .env, or personal data. Forces the agent to classify sensitive material before touching it, keep secrets out of source, binaries, flag defaults, embeds, logs, tests, commits and chat, and to prove it with a scan. Language-agnostic with Go-specific rules; pairs with go-engineering-standards.
Senior-level secrets handling for software that consumes or manages secrets in 1Password, Keeper, Bitwarden Secrets Manager, AWS Secrets Manager, OCI Vault, GCP Secret Manager, Azure Key Vault, HashiCorp Vault, Infisical, Doppler, or Akeyless. Use when writing, reviewing, testing, or operating code, CI/CD, or infrastructure that creates, reads, updates, deletes, rotates, injects, or logs around secrets, in Go, Rust, PHP, C#, Java, Swift, Python, TypeScript, C++, or C.
Load when you notice yourself saying you are stressed, overwhelmed, confused, frustrated, stuck, thrashing or going in circles; when you keep writing "wait", "no -", "actually" or re-deriving the same fact; when you have edited the same code 3+ times for one problem, are trying numbers or constants at random, or have reasoned for a long time without running a tool; or when the user asks why you are stressed or stuck. Gives a short protocol for breaking the loop by handing the unknown to a tool, a test or another skill (dates and times go to date-time-helper).
Curated skills from @andreimerlescu. Checked GitHub just now