[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7340AGD786QSTEBHQKFFMK0":3,"skill-same:01M7340AGD786QSTEBHQKFFMK0":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7340AGD786QSTEBHQKFFMK0","phoenix-api-channels",null,"Phoenix controllers, JSON APIs, Channels, and Presence on the BEAM","julio211916\u002FTlantiCAD-Studio-V0.1-alpha","julio211916","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128201165?v=4","01M730ENY015MHFY82VKR6AGGR","José Carlos amador garcia","01M730ENYT83EWH6EXRHF9FTXV",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fphoenix-api-channels\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: phoenix-api-channels\ndescription: \"Phoenix controllers, JSON APIs, Channels, and Presence on the BEAM\"\nversion: 1.0.0\ncategory: toolchain\nauthor: Claude MPM Team\nlicense: MIT\nprogressive_disclosure:\n  entry_point:\n    summary: \"Phoenix REST\u002FJSON + Channels\u002FPresence on the BEAM with contexts, plugs, auth, and PubSub.\"\n    when_to_use:\n      - \"Building JSON APIs with Phoenix controllers and versioned routes\"\n      - \"Adding WebSocket\u002FChannels for chat, notifications, or collaborative features\"\n      - \"Needing Presence tracking, fan-out broadcasts, and PubSub-backed updates\"\n      - \"Integrating Ecto contexts for persistence and domain boundaries\"\n    quick_start:\n      - \"mix phx.new my_api --no-html --no-live && cd my_api\"\n      - \"mix deps.get && mix ecto.create\"\n      - \"Define contexts + schemas; add routes\u002Fcontrollers; wire `socket` + Channel modules\"\n      - \"Start server: mix phx.server (REST + WebSocket on http:\u002F\u002Flocalhost:4000)\"\n  token_estimate:\n    entry: 170\n    full: 5200\n---\n\n# Phoenix APIs, Channels, and Presence (Elixir\u002FBEAM)\n\nPhoenix excels at REST\u002FJSON APIs and WebSocket Channels with minimal boilerplate, leveraging the BEAM for fault tolerance, lightweight processes, and supervised PubSub\u002FPresence.\n\n**Core pillars**\n- Controllers for JSON APIs with plugs, pipelines, and versioning.\n- Contexts own data (Ecto schemas + queries) and expose a narrow API to controllers\u002Fchannels.\n- Channels + PubSub for fan-out real-time updates; Presence for tracking users\u002Fdevices.\n- Auth via plugs (session\u002Fcookie for browser, token\u002FBearer for APIs), with signed params.\n\n---\n\n## Project Setup\n\n```bash\nmix phx.new my_api --no-html --no-live\ncd my_api\nmix deps.get\nmix ecto.create\nmix phx.server\n```\n\nKey files:\n- `lib\u002Fmy_api_web\u002Fendpoint.ex` — plugs, sockets, instrumentation\n- `lib\u002Fmy_api_web\u002Frouter.ex` — pipelines, scopes, versioning, sockets\n- `lib\u002Fmy_api_web\u002Fcontrollers\u002F*` — REST\u002FJSON controllers\n- `lib\u002Fmy_api\u002F*` — contexts + Ecto schemas (ownership of data logic)\n- `lib\u002Fmy_api_web\u002Fchannels\u002F*` — Channel modules\n\n---\n\n## Routing and Pipelines\n\nSeparate browser vs API pipelines; version APIs with scopes.\n```elixir\ndefmodule MyApiWeb.Router do\n  use MyApiWeb, :router\n\n  pipeline :api do\n    plug :accepts, [\"json\"]\n    plug :fetch_session\n    plug :protect_from_forgery\n    plug MyApiWeb.Plugs.RequireAuth\n  end\n\n  scope \"\u002Fapi\", MyApiWeb do\n    pipe_through :api\n\n    scope \"\u002Fv1\", V1, as: :v1 do\n      resources \"\u002Fusers\", UserController, except: [:new, :edit]\n      post \"\u002Fsessions\", SessionController, :create\n    end\n  end\n\n  socket \"\u002Fsocket\", MyApiWeb.UserSocket,\n    websocket: [connect_info: [:peer_data, :x_headers]],\n    longpoll: false\nend\n```\n\n**Tips**\n- Keep pipelines short; push auth\u002Fguards into plugs.\n- Expose `socket \"\u002Fsocket\"` for Channels; restrict transports as needed.\n\n---\n\n## Controllers and Plugs\n\nControllers stay thin; contexts own the logic.\n```elixir\ndefmodule MyApiWeb.V1.UserController do\n  use MyApiWeb, :controller\n  alias MyApi.Accounts\n\n  action_fallback MyApiWeb.FallbackController\n\n  def index(conn, _params) do\n    users = Accounts.list_users()\n    render(conn, :index, users: users)\n  end\n\n  def create(conn, params) do\n    with {:ok, user} \u003C- Accounts.register_user(params) do\n      conn\n      |> put_status(:created)\n      |> put_resp_header(\"location\", ~p\\\"\u002Fapi\u002Fv1\u002Fusers\u002F#{user.id}\\\")\n      |> render(:show, user: user)\n    end\n  end\nend\n```\n\n**FallbackController** centralizes error translation (`{:error, :not_found}` → 404 JSON).\n\n**Plugs**\n- `RequireAuth` verifies bearer\u002Fsession tokens, sets `current_user`.\n- Use `plug :scrub_params`-style transforms in pipelines, not controllers.\n- Avoid heavy work in plugs; they run per-request.\n\n---\n\n## Contexts and Data (Ecto)\n\nContexts expose only what controllers\u002Fchannels need.\n```elixir\ndefmodule MyApi.Accounts do\n  import Ecto.Query, warn: false\n  alias MyApi.{Repo, Accounts.User}\n\n  def list_users, do: Repo.all(User)\n  def get_user!(id), do: Repo.get!(User, id)\n\n  def register_user(attrs) do\n    %User{}\n    |> User.registration_changeset(attrs)\n    |> Repo.insert()\n  end\nend\n```\n\n**Guidelines**\n- Keep schema modules free of controller knowledge.\n- Validate at the changeset; use `Ecto.Multi` for multi-step operations.\n- Prefer pagination helpers (`Scrivener`, `Flop`) for large lists.\n\n---\n\n## Channels, PubSub, and Presence\n\nChannel module example:\n```elixir\ndefmodule MyApiWeb.RoomChannel do\n  use Phoenix.Channel\n  alias Phoenix.Presence\n\n  def join(\"room:\" \u003C> room_id, _payload, socket) do\n    send(self(), :after_join)\n    {:ok, assign(socket, :room_id, room_id)}\n  end\n\n  def handle_info(:after_join, socket) do\n    Presence.track(socket, socket.assigns.user_id, %{online_at: System.system_time(:second)})\n    push(socket, \"presence_state\", Presence.list(socket))\n    {:noreply, socket}\n  end\n\n  def handle_in(\"message:new\", %{\"body\" => body}, socket) do\n    broadcast!(socket, \"message:new\", %{user_id: socket.assigns.user_id, body: body})\n    {:noreply, socket}\n  end\nend\n```\n\n**PubSub from contexts**\n```elixir\ndef create_order(attrs) do\n  with {:ok, order} \u003C- %Order{} |> Order.changeset(attrs) |> Repo.insert() do\n    Phoenix.PubSub.broadcast(MyApi.PubSub, \"orders\", {:order_created, order})\n    {:ok, order}\n  end\nend\n```\n\n**Best practices**\n- Authorize in `UserSocket.connect\u002F3` before joining topics.\n- Limit payload sizes; validate incoming events.\n- Use topic partitioning for tenancy (`\"tenant:\" \u003C> tenant_id \u003C> \":room:\" \u003C> room_id`).\n\n---\n\n## Authentication Patterns\n\n- **API tokens**: Accept `authorization: Bearer \u003Ctoken>`; verify in plug, assign `current_user`.\n- **Signed params**: `Phoenix.Token.sign\u002Fverify` for short-lived join params.\n- **Rate limiting**: Use plugs + ETS\u002FCachex or reverse proxy (NGINX\u002FCloudflare).\n- **CORS**: Configure in `Endpoint` with `cors_plug`.\n\n---\n\n## Testing\n\nUse generated helpers:\n```elixir\ndefmodule MyApiWeb.UserControllerTest do\n  use MyApiWeb.ConnCase, async: true\n\n  test \"lists users\", %{conn: conn} do\n    conn = get(conn, ~p\\\"\u002Fapi\u002Fv1\u002Fusers\\\")\n    assert json_response(conn, 200)[\"data\"] == []\n  end\nend\n```\n\nChannel tests:\n```elixir\ndefmodule MyApiWeb.RoomChannelTest do\n  use MyApiWeb.ChannelCase, async: true\n\n  test \"broadcasts messages\" do\n    {:ok, _, socket} = connect(MyApiWeb.UserSocket, %{\"token\" => \"abc\"})\n    {:ok, _, socket} = subscribe_and_join(socket, \"room:123\", %{})\n    ref = push(socket, \"message:new\", %{\"body\" => \"hi\"})\n    assert_reply ref, :ok\n    assert_broadcast \"message:new\", %{body: \"hi\"}\n  end\nend\n```\n\n**DataCase**: isolates DB per test; use fixtures\u002Ffactories for setup.\n\n---\n\n## Telemetry, Observability, and Ops\n\n- `:telemetry` events from endpoint, controller, channel, and Ecto queries; export via `OpentelemetryPhoenix` and `OpentelemetryEcto`.\n- Use `Plug.Telemetry` for request metrics; add logging metadata (request_id, user_id).\n- Releases: `MIX_ENV=prod mix release`; configure runtime in `config\u002Fruntime.exs`.\n- Clustering: `libcluster` + distributed PubSub for multi-node Presence.\n- Assetless APIs: disable unused watchers (esbuild\u002Ftailwind) for API-only apps.\n\n---\n\n## Common Pitfalls\n\n- Controllers doing queries directly instead of delegating to contexts.\n- Not authorizing in `UserSocket.connect\u002F3`, leading to topic exposure.\n- Missing `action_fallback` → inconsistent error shapes.\n- Forgetting to limit event payloads; large messages can overwhelm channels.\n- Leaving longpoll enabled when unused; disable to reduce surface area.\n\nPhoenix API + Channels shine when contexts own data, controllers stay thin, and Channels use PubSub\u002FPresence with strict authorization and telemetry. The BEAM handles concurrency and fault tolerance; focus on clear boundaries and real-time experiences.\n","# Phoenix APIs, Channels, and Presence (Elixir\u002FBEAM)\n\nPhoenix excels at REST\u002FJSON APIs and WebSocket Channels with minimal boilerplate, leveraging the BEAM for fault tolerance, lightweight processes, and supervised PubSub\u002FPresence.\n\n**Core pillars**\n- Controllers for JSON APIs with plugs, pipelines, and versioning.\n- Contexts own data (Ecto schemas + queries) and expose a narrow API to controllers\u002Fchannels.\n- Channels + PubSub for fan-out real-time updates; Presence for tracking users\u002Fdevices.\n- Auth via plugs (session\u002Fcookie for browser, token\u002FBearer for APIs), with signed params.\n\n---\n\n## Project Setup\n\n```bash\nmix phx.new my_api --no-html --no-live\ncd my_api\nmix deps.get\nmix ecto.create\nmix phx.server\n```\n\nKey files:\n- `lib\u002Fmy_api_web\u002Fendpoint.ex` — plugs, sockets, instrumentation\n- `lib\u002Fmy_api_web\u002Frouter.ex` — pipelines, scopes, versioning, sockets\n- `lib\u002Fmy_api_web\u002Fcontrollers\u002F*` — REST\u002FJSON controllers\n- `lib\u002Fmy_api\u002F*` — contexts + Ecto schemas (ownership of data logic)\n- `lib\u002Fmy_api_web\u002Fchannels\u002F*` — Channel modules\n\n---\n\n## Routing and Pipelines\n\nSeparate browser vs API pipelines; version APIs with scopes.\n```elixir\ndefmodule MyApiWeb.Router do\n  use MyApiWeb, :router\n\n  pipeline :api do\n    plug :accepts, [\"json\"]\n    plug :fetch_session\n    plug :protect_from_forgery\n    plug MyApiWeb.Plugs.RequireAuth\n  end\n\n  scope \"\u002Fapi\", MyApiWeb do\n    pipe_through :api\n\n    scope \"\u002Fv1\", V1, as: :v1 do\n      resources \"\u002Fusers\", UserController, except: [:new, :edit]\n      post \"\u002Fsessions\", SessionController, :create\n    end\n  end\n\n  socket \"\u002Fsocket\", MyApiWeb.UserSocket,\n    websocket: [connect_info: [:peer_data, :x_headers]],\n    longpoll: false\nend\n```\n\n**Tips**\n- Keep pipelines short; push auth\u002Fguards into plugs.\n- Expose `socket \"\u002Fsocket\"` for Channels; restrict transports as needed.\n\n---\n\n## Controllers and Plugs\n\nControllers stay thin; contexts own the logic.\n```elixir\ndefmodule MyApiWeb.V1.UserController do\n  use MyApiWeb, :controller\n  alias MyApi.Accounts\n\n  action_fallback MyApiWeb.FallbackController\n\n  def index(conn, _params) do\n    users = Accounts.list_users()\n    render(conn, :index, users: users)\n  end\n\n  def create(conn, params) do\n    with {:ok, user} \u003C- Accounts.register_user(params) do\n      conn\n      |> put_status(:created)\n      |> put_resp_header(\"location\", ~p\\\"\u002Fapi\u002Fv1\u002Fusers\u002F#{user.id}\\\")\n      |> render(:show, user: user)\n    end\n  end\nend\n```\n\n**FallbackController** centralizes error translation (`{:error, :not_found}` → 404 JSON).\n\n**Plugs**\n- `RequireAuth` verifies bearer\u002Fsession tokens, sets `current_user`.\n- Use `plug :scrub_params`-style transforms in pipelines, not controllers.\n- Avoid heavy work in plugs; they run per-request.\n\n---\n\n## Contexts and Data (Ecto)\n\nContexts expose only what controllers\u002Fchannels need.\n```elixir\ndefmodule MyApi.Accounts do\n  import Ecto.Query, warn: false\n  alias MyApi.{Repo, Accounts.User}\n\n  def list_users, do: Repo.all(User)\n  def get_user!(id), do: Repo.get!(User, id)\n\n  def register_user(attrs) do\n    %User{}\n    |> User.registration_changeset(attrs)\n    |> Repo.insert()\n  end\nend\n```\n\n**Guidelines**\n- Keep schema modules free of controller knowledge.\n- Validate at the changeset; use `Ecto.Multi` for multi-step operations.\n- Prefer pagination helpers (`Scrivener`, `Flop`) for large lists.\n\n---\n\n## Channels, PubSub, and Presence\n\nChannel module example:\n```elixir\ndefmodule MyApiWeb.RoomChannel do\n  use Phoenix.Channel\n  alias Phoenix.Presence\n\n  def join(\"room:\" \u003C> room_id, _payload, socket) do\n    send(self(), :after_join)\n    {:ok, assign(socket, :room_id, room_id)}\n  end\n\n  def handle_info(:after_join, socket) do\n    Presence.track(socket, socket.assigns.user_id, %{online_at: System.system_time(:second)})\n    push(socket, \"presence_state\", Presence.list(socket))\n    {:noreply, socket}\n  end\n\n  def handle_in(\"message:new\", %{\"body\" => body}, socket) do\n    broadcast!(socket, \"message:new\", %{user_id: socket.assigns.user_id, body: body})\n    {:noreply, socket}\n  end\nend\n```\n\n**PubSub from contexts**\n```elixir\ndef create_order(attrs) do\n  with {:ok, order} \u003C- %Order{} |> Order.changeset(attrs) |> Repo.insert() do\n    Phoenix.PubSub.broadcast(MyApi.PubSub, \"orders\", {:order_created, order})\n    {:ok, order}\n  end\nend\n```\n\n**Best practices**\n- Authorize in `UserSocket.connect\u002F3` before joining topics.\n- Limit payload sizes; validate incoming events.\n- Use topic partitioning for tenancy (`\"tenant:\" \u003C> tenant_id \u003C> \":room:\" \u003C> room_id`).\n\n---\n\n## Authentication Patterns\n\n- **API tokens**: Accept `authorization: Bearer \u003Ctoken>`; verify in plug, assign `current_user`.\n- **Signed params**: `Phoenix.Token.sign\u002Fverify` for short-lived join params.\n- **Rate limiting**: Use plugs + ETS\u002FCachex or reverse proxy (NGINX\u002FCloudflare).\n- **CORS**: Configure in `Endpoint` with `cors_plug`.\n\n---\n\n## Testing\n\nUse generated helpers:\n```elixir\ndefmodule MyApiWeb.UserControllerTest do\n  use MyApiWeb.ConnCase, async: true\n\n  test \"lists users\", %{conn: conn} do\n    conn = get(conn, ~p\\\"\u002Fapi\u002Fv1\u002Fusers\\\")\n    assert json_response(conn, 200)[\"data\"] == []\n  end\nend\n```\n\nChannel tests:\n```elixir\ndefmodule MyApiWeb.RoomChannelTest do\n  use MyApiWeb.ChannelCase, async: true\n\n  test \"broadcasts messages\" do\n    {:ok, _, socket} = connect(MyApiWeb.UserSocket, %{\"token\" => \"abc\"})\n    {:ok, _, socket} = subscribe_and_join(socket, \"room:123\", %{})\n    ref = push(socket, \"message:new\", %{\"body\" => \"hi\"})\n    assert_reply ref, :ok\n    assert_broadcast \"message:new\", %{body: \"hi\"}\n  end\nend\n```\n\n**DataCase**: isolates DB per test; use fixtures\u002Ffactories for setup.\n\n---\n\n## Telemetry, Observability, and Ops\n\n- `:telemetry` events from endpoint, controller, channel, and Ecto queries; export via `OpentelemetryPhoenix` and `OpentelemetryEcto`.\n- Use `Plug.Telemetry` for request metrics; add logging metadata (request_id, user_id).\n- Releases: `MIX_ENV=prod mix release`; configure runtime in `config\u002Fruntime.exs`.\n- Clustering: `libcluster` + distributed PubSub for multi-node Presence.\n- Assetless APIs: disable unused watchers (esbuild\u002Ftailwind) for API-only apps.\n\n---\n\n## Common Pitfalls\n\n- Controllers doing queries directly instead of delegating to contexts.\n- Not authorizing in `UserSocket.connect\u002F3`, leading to topic exposure.\n- Missing `action_fallback` → inconsistent error shapes.\n- Forgetting to limit event payloads; large messages can overwhelm channels.\n- Leaving longpoll enabled when unused; disable to reduce surface area.\n\nPhoenix API + Channels shine when contexts own data, controllers stay thin, and Channels use PubSub\u002FPresence with strict authorization and telemetry. The BEAM handles concurrency and fault tolerance; focus on clear boundaries and real-time experiences.\n",{"name":5,"author":24,"license":15,"version":25,"category":26,"description":7,"progressive_disclosure":27},"Claude MPM Team","1.0.0","toolchain",{"entry_point":28,"token_estimate":40},{"summary":29,"quick_start":30,"when_to_use":35},"Phoenix REST\u002FJSON + Channels\u002FPresence on the BEAM with contexts, plugs, auth, and PubSub.",[31,32,33,34],"mix phx.new my_api --no-html --no-live && cd my_api","mix deps.get && mix ecto.create","Define contexts + schemas; add routes\u002Fcontrollers; wire `socket` + Channel modules","Start server: mix phx.server (REST + WebSocket on http:\u002F\u002Flocalhost:4000)",[36,37,38,39],"Building JSON APIs with Phoenix controllers and versioned routes","Adding WebSocket\u002FChannels for chat, notifications, or collaborative features","Needing Presence tracking, fan-out broadcasts, and PubSub-backed updates","Integrating Ecto contexts for persistence and domain boundaries",{"full":41,"entry":42},5200,170,"main","590aa4fe05d1ec71a02ee9cc76c9a20508b5bcea","skills\u002Fju\u002Fskills\u002Fphoenix-api-channels","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha","https:\u002F\u002Fgithub.com\u002Fjulio211916","Estudiante de ing sistemas y psicologia","2026-05-22 04:43:54",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add julio211916\u002FTlantiCAD-Studio-V0.1-alpha --skill phoenix-api-channels",{"tool":56,"command":57},"bunx","bunx skills add julio211916\u002FTlantiCAD-Studio-V0.1-alpha --skill phoenix-api-channels",{"tool":59,"command":60},"pnpm","pnpm dlx skills add julio211916\u002FTlantiCAD-Studio-V0.1-alpha --skill phoenix-api-channels","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fphoenix-api-channels\u002FSKILL.md",true,[],[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M735PMP7K29TEC1BC5A3VJ3Z","simpy","Process-based discrete-event simulation framework in Python. Use this skill when building simulations of systems with processes, queues, resources, and time-based events such as manufacturing systems, service operations, network traffic, logistics, or any system where entities interact with shared resources over time.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fsimpy\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M735NX56AZHYMV3BQ8GYZ7J0","shopify-expert","Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflows.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fshopify-expert\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M735N9WTN69TVA2T5VS9W1CA","shap","Model interpretability and explainability using SHAP (SHapley Additive exPlanations). Use this skill when explaining machine learning model predictions, computing feature importance, generating SHAP plots (waterfall, beeswarm, bar, scatter, force, heatmap), debugging models, analyzing model bias or fairness, comparing models, or implementing explainable AI. Works with tree-based models (XGBoost, LightGBM, Random Forest), deep learning (TensorFlow, PyTorch), linear models, and any black-box model.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fshap\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M735N3VQ8R56TXFF16BMF19H","shadcn-ui","Deep expertise on shadcn\u002Fui component library including installation, customization, theming, and accessibility patterns. Use when building UI with shadcn\u002Fui components, integrating Radix UI primitives, configuring Tailwind CSS v4 themes, or implementing dark mode. Covers Next.js App Router, Pages Router, and Vite setups.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fshadcn-ui\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M735KH64KS6Z58H6BJWX89BV","seoul-subway-arrival","Look up Seoul real-time subway arrival information with the official Seoul Open Data API. Use when the user asks when a train arrives, which trains are approaching a station, or how crowded Seoul subway timing looks right now.","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fseoul-subway-arrival\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M735K7KAFBZNACQ66PMDQMQD","seo-optimization","Comprehensive 7-phase SEO optimization workflow covering technical SEO auditing, keyword research strategy, on-page optimization, content SEO and E-E-A-T, structured data implementation, link building, and AI search optimization. Use when auditing search engine visibility, diagnosing ranking issues, implementing schema markup, conducting keyword research, optimizing content for E-E-A-T signals, or adapting for AI-driven search (AI Overviews, SGE).","https:\u002F\u002Fgithub.com\u002Fjulio211916\u002FTlantiCAD-Studio-V0.1-alpha\u002Fblob\u002Fmain\u002Fskills\u002Fju\u002Fskills\u002Fseo-optimization\u002FSKILL.md",[],[]]