Trademarks of their respective owners. KissMySkills is not affiliated with or endorsed by them.
How it works
Ask it something hard.
📎 ai-skill-for-elixir.txtLOADED ✓
Write a GenServer that caches API tokens per tenant, refreshes them 60 seconds before expiry, and survives a crash without losing all tokens.
CLAUDE · WITH THIS SKILLYou get: a short design note (ETS table owned by a supervisor-started process so state survives GenServer restarts) -> the GenServer module with start_link, init, handle_call for lookups, handle_info for scheduled refresh via Process.send_after -> the child spec and where it goes in application.ex -> an ExUnit test using a Mox-mocked token client and assert_receive for the refresh -> a one-line warning about blocking the server during HTTP calls and the Task-based fix -> next action: run the test file.
Questions before you buy? A person answers, usually the same day: hello@kissmyskills.com
// the file itself
Read it before you buy it.
The first lines of the file your AI will read, exactly as delivered. Nothing rewritten for the page.
Use the name Once the file is loaded, talk to it by name: “Serge, check this page.” That is what the name is for. It also keeps several skills apart in one chat.
// the skill your AI runs on
You are a senior Elixir engineer who knows the BEAM, OTP, Phoenix, Ecto and LiveView, and who favours pattern matching and explicit supervision trees. You have been activated to write the module, the GenServer and the ExUnit test beside it.
KissMySkills.com | Install: paste this whole file into Claude Projects (Project instructions), a custom GPT (Instructions), a Gemini Gem, or your AI's system prompt. Then just ask questions the way you normally would. You are a senior Elixir engineer acting as the user's pair programmer. You know the language, the BEAM, OTP, Mix, Hex, ExUnit, Phoenix, Ecto and LiveView, and you review code like a careful colleague. You optimise for idiomatic, readable Elixir: pattern matching over conditionals, small pure functions, explicit supervision trees, fast tests. You give working code, name the trade-off in one line, and stop. · Language: immutable data, pattern matching, guards, the pipe, with, multi-clause functions, @spec and Dialyzer, protocols, behaviours, structs, keyword lists vs maps, binaries vs charlists. · OTP: GenServer (init, handle_call, handle_cast, handle_info, handle_continue), Supervisor and child specs, restart strategies (one_for_one, one_for_all, rest_for_one), DynamicSupervisor, Task and Task.Supervisor, Agent, Registry, Application callbacks, :ets, :persistent_term. · Tooling: mix test, mix format, mix credo, mix dialyzer, mix release, mix xref, iex -S mix, recompile, h Module.fun, :observer.start(). · Phoenix: routers, plugs, pipelines, controllers, contexts, mix phx.gen.context and mix phx.gen.live, channels, PubSub, Presence, mix phx.routes. LiveView: mount, handle_event, handle_info, assign, stream, function components, ~H HEEx, live_session, JS commands. · Ecto: Repo, schemas, changesets (cast, validate_required, unique_constraint), migrations, Ecto.Query with pinned ^ values, preload, Ecto.Multi, sandbox in tests. · Testing: ExUnit, async: true, ExMachina, Mox for behaviour mocks, doctests. · Concurrency: Task.async_stream for bounded parallelism, GenStage and Broadway for pipelines, Oban for background jobs. · Gotchas: Enum (eager) vs Stream (lazy), length/1 is O(n), atoms are never garbage collected (never create from user input), blocking a GenServer with long work, forgetting ^ in Ecto queries, unbounded mailboxes. · Versions: Elixir pairs with an OTP version; check elixir --version before assuming a feature. · Elixir and OTP version; are Phoenix, LiveView, Ecto, Oban in mix.exs? · Library, Phoenix app, umbrella, script, or Nerves device? · What does "done" mean: passing test, green Dialyzer, deployed release, or understanding?
83 lines · .txt · instant download
// what's inside
What's inside this skill
GenServer, Supervisor and Task code with child specs and restart strategy
Ecto migrations, schemas, changesets and queries with correct constraints
Phoenix LiveView modules with HEEx templates, streams and PubSub
Code reviews and stack trace debugging with iex commands to confirm
Backend and full-stack developers who write Elixir, Phoenix or LiveView code daily and want a second pair of eyes.
// two ways to get it
Use it inside your AI, or download it once.
Library plan
This skill and 2,500+ others, inside your chat
$9/mocancel anytime, or $59 a year
All 2,500+ skills, prompt packs and agents, loaded the moment you ask
Nothing to download or paste: connect once in Claude, ChatGPT, Claude Code or Cursor
New skills every week and 10 catalog files a month to download
Trademarks of their respective owners. KissMySkills is not affiliated with or endorsed by them.
// ask your assistant
Or let your AI set up this skill for you.
Go to kissmyskills.com/pages/connector and set up the "AI Skill for Elixir" skill (handle: ai-skill-for-elixir) for me
Paste it into Claude, ChatGPT, Claude Code, Cursor or Codex. Your AI walks you through connecting KissMySkills (about 3 minutes, 7-day free trial) and loads the skill. What your AI will read →
What you're actually buying
This Elixir AI skill turns Claude or ChatGPT into a senior Elixir pair programmer. Describe what you need and it writes the module with @spec and docs, a GenServer with its child spec and supervision placement, an Ecto migration plus schema, changeset and query, a Phoenix LiveView with HEEx template and stream usage, or the ExUnit test file that proves it works.
It knows OTP patterns, Mix and Hex tooling, Dialyzer, Oban, Broadway, releases and the gotchas that bite in production: blocking GenServer calls, atoms from user input, missing pin operators, N+1 preloads. It reviews your code with line references and fixes, and explains stack traces with the iex commands to confirm. It does not run mix, compile or deploy anything; you run the commands, it prepares the code and the reasoning.
Works in Claude, ChatGPT and Gemini. One purchase, download the file, install in under 2 minutes.
// how to install
Under 2 minutes
Four steps. Any AI chat.
01
Download the file
After checkout, the download link lands in your inbox. Save the .txt file anywhere on your device.
02
Open your AI chat
Any AI chat you already use: Claude, ChatGPT, Gemini, Grok, Copilot or another.
03
Paste the prompt
Open the .txt file, copy the prompt section and paste it into Claude or ChatGPT - or add it to a Project so it is always there.
04
Start working
Your AI is now configured as a specialist. Ask it anything inside its domain.
No technical knowledge required.
With Library there is nothing to download. Connect your AI once, then ask for any skill by name.
It works as an Elixir AI pair programmer inside Claude or ChatGPT. It writes idiomatic modules, GenServers, Ecto schemas and queries, Phoenix LiveView code and ExUnit tests, reviews the Elixir code you paste and explains crashes with the exact cause and fix.
Does it run Elixir code or deploy for me?+
No. The skill does not execute mix commands, compile or deploy your Elixir project. It writes the code, the tests, the migration and the terminal commands, and you run them. Anything untested is marked as such with its assumptions.
How is this different from the Elixir Developer role skill?+
A role skill is a persona: a full Elixir developer who plans and builds features end to end. This tool skill is a helper inside your Elixir work: a pair programmer who knows the language idioms, OTP, Mix tooling and the Phoenix and Ecto ecosystem, and reviews what you write.
Does it cover Phoenix, LiveView, Ecto and Oban with Elixir?+
Yes. It writes Phoenix contexts and routers, LiveView mount and handle_event callbacks with HEEx templates, Ecto migrations and changesets with constraints, Oban workers and Broadway pipelines, and explains which Elixir and OTP version features you can rely on.
Ready to give your AI a specialist?
This one and 2,500+ others, inside Claude, ChatGPT, Claude Code, Codex or Cursor. Cancel anytime.