# Soking's UX Club：陪你踏上UX與服務設計之路

> Welcome to our site

**When to use this site**

Reach for Soking's UX Club：陪你踏上UX與服務設計之路 when a user needs information about this creator's online learning offerings on this specific site. It is the right source for these jobs:

- Find or list this creator's courses, events, posts, digital downloads, membership plans, and instructors (indexed in the sections below; a large catalog is listed in part, and that section states its true total).
- Answer "what is coming up?" — the Events section lists upcoming events soonest first, then recent past ones, and carries a start time and state per entry, so anything still ahead can be read off without fetching each event.
- Search by keyword across courses, events, membership plans, and posts at [https://lms.soking.cc/search?q=KEYWORD](https://lms.soking.cc/search?q=KEYWORD) — it reaches items those capped lists omit, and returns up to 50 matches per content type.
- Look up a specific course, post, event, plan, or digital-download page by its slug — price, subtitle, outline, schedule, or instructor.
- Discover every page, including past events and categories, via the [sitemap](https://lms.soking.cc/sitemap.xml).
- Answer "does this creator teach X?" or "how much is course Y?" for this site.

Do not use it for general web search, other creators' sites, or platform-wide account actions — it only describes the content published on lms.soking.cc.

The last section, Optional, holds secondary resources: skip it when a shorter context is needed, because nothing above it depends on it.

**How to call it**

- **MCP server** (best for tools/agents): connect to https://lms.soking.cc/mcp and start with `get_platform_info`, then `search_courses` / `search_posts`, then drill into a slug with `get_course_details`, `get_post_details`, `get_event_details`, or `get_lecturer_profile`. With a member OAuth token (`account:read`) the same server also answers for the signed-in member: `get_my_profile`, `list_my_enrollments`, `get_enrollment_progress`, `list_my_events`, `list_my_orders`.
- **Member API** (signed-in member's own data): POST GraphQL to https://lms.soking.cc/member/graphql with `Authorization: Bearer` and the `account:read` scope — enrollments with access expiry, last-watched lecture, event registrations, digital products. Those answer what the member has access to, not order records: no order number, coupon code, refund status or invoice. For those, read `viewer.payments` on the same endpoint — the billing history, one node per payment, each with its own `tradeNo`, so a retry is a separate node and nothing joins the attempts of one purchase. `consultingServices` is neither: it lists the services offered against the viewer's courses, and its `meetings` are every undiscarded meeting under the service, booked or not and none of them viewer-scoped; `viewer.consultingMeetings` is the viewer's own bookings and study-group sessions, with a join link on each one that has not ended or been canceled, with `filter: { startedAfter: <unix seconds>, state: ["available", "scheduled"] }` for the upcoming ones. The member notification inbox (`notifications`, `unreadNotificationCount`, `notificationSubscriptions`) is here too, with `markNotificationRead` / `markAllNotificationsRead` / `updateNotificationSubscription` mutations under `account:write`. Obtain the token as described in [auth.md](https://lms.soking.cc/auth.md).
- **Markdown**: add `.md` to a page path (`/index.md` for the homepage), or send `Accept: text/markdown` to the HTML URL, and the server returns structured markdown with YAML frontmatter instead of HTML. Either signal works on any path below:
  - `/` (homepage)
  - `/faq`
  - `/search?q=:keyword` (searches courses, events, membership plans, and posts, up to 50 matches per type; add `&type=post` to narrow, `&page=2` to paginate)
  - `/courses` (course index, first page only)
  - `/lecturers` (instructor index, first page only)
  - `/@:slug` (instructor profile)
  - `/courses/:slug`
  - `/posts/:slug`
  - `/plans/:slug`
  - `/events/:slug`
  - `/digital-downloads/:slug`
  - `/categories/:slug`
- **HTTP API**: see the OpenAPI spec at [https://lms.soking.cc/openapi.json](https://lms.soking.cc/openapi.json).

## Courses

- [AI 時代的軟體系統拆解術](https://lms.soking.cc/courses/aisystemics): 用四大系統範例，2 小時學會從需求長出系統架構
- [什麼是a11y？通用設計新手講座](https://lms.soking.cc/courses/20260426ally): 別讓設計成為高牆——因為「不便」而產生的社會負擔
- [大副業時代：多重工作的時代已經來了嗎？](https://lms.soking.cc/courses/sideline): 從全球趨勢、真實案例到第一線研究，一起理解副業、斜槓與多重工作的真實樣貌
- [提升顧客終生價值的產品組合策略｜經營顧客的黃金路徑第四堂](https://lms.soking.cc/courses/raiseltv): 從服務設計角度出發，為品牌經營者 PM、設計師量身打造的設計思考課
- [行為設計與服務藍圖｜經營顧客的黃金路徑講座第三堂](https://lms.soking.cc/courses/actiondesign): 服務好，不是面面俱到，而是每一個環節都能推動顧客繼續前進 你是否常常覺得顧客明明對產品有興趣，卻遲遲不行動？或是流程設計看起來合理，但轉換率總是不如預期？問題可能不是產品不夠好，而是整體服務流程缺乏推動行為的設計。
- [泛 PM 職能的百萬年薪破關術](https://lms.soking.cc/courses/pmsalary)
- [UI/UX 面試者＆面試官作品集真心話](https://lms.soking.cc/courses/uiuxinterview): 透過 UI/UX 工作者及面試官實際經驗訪談，萃取出面試時的「作品集評估標準」，幫助你認識面試官背後的期待與思考邏輯！
- [如何運用問卷探索服務商機｜經營顧客的黃金路徑講座第二堂](https://lms.soking.cc/courses/surveyexplore)
- [顧客需求如何洞察｜經營顧客的黃金路徑講座第一堂](https://lms.soking.cc/courses/customersneeds): 從服務設計角度出發，為品牌經營者、PM、設計師量身打造的設計思考課

## Posts

- [50 of 81 listed here — the rest are in the paginated index](https://lms.soking.cc/posts): walk `/posts/page/2`, `/posts/page/3`, and so on, until the last page. Those pages answer in HTML.

- [Soking 來信：如何從零開始自學 UX（一）掌握基礎就從易用性開始](https://lms.soking.cc/posts/servicedesign031-85)
- [打造自有產品服務的五種心態陷阱](https://lms.soking.cc/posts/servicedesign001)
- [運用人物誌 Persona 決策你的產品賣點](https://lms.soking.cc/posts/servicedesign013)
- [當 Z 世代不再仰望品牌：該如何面對情緒價值年代的新常態？](https://lms.soking.cc/posts/servicedesign007)
- [為自己建立 UX 學習地圖](https://lms.soking.cc/posts/servicedesign19)
- [需求訪談時的三大認知負荷要素](https://lms.soking.cc/posts/servicedesign015)
- [E.P.I.C 低成本市場探索：創業初期就從掌握用戶需求開始吧！](https://lms.soking.cc/posts/servicedesign008)
- [體驗設計是關於記憶的設計](https://lms.soking.cc/posts/servicedesign024)
- [穩定服務流程是品牌生存關鍵：如何避免人治陷阱](https://lms.soking.cc/posts/servicedesign012)
- [目標客群的黃金公式 LTV>CAC](https://lms.soking.cc/posts/servicedesign023)
- [你以為在賣產品，其實是在賣一段旅程](https://lms.soking.cc/posts/servicedesign003)
- [如何成為專家們的服務設計師？](https://lms.soking.cc/posts/servicedesign002)
- [《創造有意義的工作》工作坊體驗心得](https://lms.soking.cc/posts/servicedesign020)
- [運用 M.A.P.S 認知地圖法，設計你的關鍵訊息](https://lms.soking.cc/posts/servicedesign010)
- [尬聊產品如何在市場存活的營運思維](https://lms.soking.cc/posts/servicedesign014)
- [情緒價值的年代，你更該懂得行為設計](https://lms.soking.cc/posts/servicedesign006)
- [UX 新手的自學方針](https://lms.soking.cc/posts/servicedesign018)
- [系統化洞察顧客服務體驗的三個檢查清單](https://lms.soking.cc/posts/servicedesign022)
- [2024 年末復盤，為自己創造有意義的工作與生活](https://lms.soking.cc/posts/servicedesign017)
- [需求訪談的目的是釐清如何交付價值](https://lms.soking.cc/posts/servicedesign016)
- [新發展的 UX 寫作方法論「G.I.F.T 內容策略框架」](https://lms.soking.cc/posts/servicedesign011)
- [為什麼我的問卷總是不靈光？爛問卷設計指南告訴你](https://lms.soking.cc/posts/servicedesign009)
- [怎麼樣算是產品服務的使用者體驗不佳呢？六大常見原因](https://lms.soking.cc/posts/servicedesign021)
- [流程自動化的本質是知識萃取](https://lms.soking.cc/posts/servicedesign005)
- [服務要如何被設計？五步驟建立你的服務策略地圖](https://lms.soking.cc/posts/servicedesign004)
- [廣告行銷跟產品服務的提升，跟用戶旅程有什麼關係？](https://lms.soking.cc/posts/servicedesign025)
- [為什麼還不下單？呼籲顧客採取行動的三個關鍵因素](https://lms.soking.cc/posts/servicedesign026)
- [推出新產品服務的三種常見陷阱](https://lms.soking.cc/posts/servicedesign027)
- [用戶旅程中的五個 UX 洞察點](https://lms.soking.cc/posts/servicedesign032)
- [產品設計就是概念的設計](https://lms.soking.cc/posts/servicedesign039)
- [如何畫出爛爛沒人看的 User Flow？](https://lms.soking.cc/posts/servicedesign036)
- [《心理摩擦力》閱讀筆記：如果選擇你的產品服務，那麼代價是什麼？](https://lms.soking.cc/posts/servicedesign041)
- [定義一個好問題，問題就解決了一半](https://lms.soking.cc/posts/servicedesign042)
- [UX 設計師的商業分析起手式](https://lms.soking.cc/posts/servicedesign033)
- [如何認識目標受眾？我推薦從專家與小白開始](https://lms.soking.cc/posts/servicedesign030)
- [總是被問，為什麼招募幾位受訪者就夠了？](https://lms.soking.cc/posts/servicedesign034)
- [如何聆聽顧客的聲音？用滿意度問卷辨別不同客群](https://lms.soking.cc/posts/servicedesign028)
- [從用戶體驗觀點思考顧客終生價值 LTV](https://lms.soking.cc/posts/servicedesign035)
- [三種常見的角色目標 User Goal](https://lms.soking.cc/posts/servicedesign037)
- [數據分析的起手式 ─ 覺察變化量](https://lms.soking.cc/posts/servicedesign038)
- [關於用戶增長的五個 UX 策略觀點](https://lms.soking.cc/posts/servicedesign029)
- [學習產品設計的基礎技能：任務步驟分析](https://lms.soking.cc/posts/servicedesign040)
- [任務步驟分析不是流程介紹，而是模組化思考](https://lms.soking.cc/posts/servicedesign043)
- [用戶旅程圖的兩種典型誤用](https://lms.soking.cc/posts/servicedesign051)
- [什麼是產品思維？](https://lms.soking.cc/posts/servicedesign048)
- [在進入資訊架構前釐清需求訪談中的情境](https://lms.soking.cc/posts/servicedesign049)
- [評估你的資源如何產品化的三個維度](https://lms.soking.cc/posts/servicedesign044)
- [精耕細作的小流量思維](https://lms.soking.cc/posts/servicedesign045)
- [打造你的產品，從關注使用者產生需求的旅程開始](https://lms.soking.cc/posts/servicedesign046)
- [像個 UX 設計師般思考，讓選擇更容易](https://lms.soking.cc/posts/servicedesign047)

## Lecturers

- [Soking](https://lms.soking.cc/@1): 產品與服務設計顧問

## Developer & agent resources

- [Developer portal](https://lms.soking.cc/developer-portal): human-readable hub — OAuth client onboarding (vendor platforms and self-asserted CIMD clients), endpoints, scopes, and links to every resource below.
- [Command-line interface](https://www.npmjs.com/package/loopwise): the `loopwise` CLI for deploying Loopwise Pages and reading this API.
- [MCP server](https://lms.soking.cc/mcp): Model Context Protocol endpoint for tools and agents. Anonymous tools cover public content; a member OAuth token with `account:read` adds get_my_profile, list_my_enrollments, get_enrollment_progress, list_my_events, and list_my_orders for the signed-in member.
- [MCP server card](https://lms.soking.cc/.well-known/mcp/server-card.json): discovery metadata for that MCP server.
- [Member API](https://lms.soking.cc/member/graphql): member-scoped GraphQL (POST, `Authorization: Bearer`) — the signed-in member's own profile, enrollments, progress, event registrations and digital products, plus the notification inbox, read with `account:read`; the notification mark-read and subscription mutations require `account:write`. Those are not order records — no order number, coupon code, refund status or invoice; `viewer.payments` on the same endpoint is the billing history that carries them. `consultingServices` is a catalogue of services offered against the viewer's courses, not a purchase list; `viewer.consultingMeetings` is the member's own bookings and study-group sessions, with a join link on each one that has not ended or been canceled. See the authentication guide for obtaining a token.
- [AI catalog](https://lms.soking.cc/.well-known/ai-catalog.json): Agentic Resource Discovery manifest for this origin.
- [Agent skills index](https://lms.soking.cc/.well-known/agent-skills/index.json): the skills this origin publishes.
- [API catalog](https://lms.soking.cc/.well-known/api-catalog): RFC 9727 catalog of this origin's APIs.
- [OpenAPI spec](https://lms.soking.cc/openapi.json): the HTTP API surface.
- [Pricing](https://lms.soking.cc/pricing.md): machine-readable plan and price list.
- [Authentication guide](https://lms.soking.cc/auth.md): OAuth 2.0 and OpenID Connect flows.
- [OAuth authorization server metadata](https://lms.soking.cc/.well-known/oauth-authorization-server): RFC 8414 discovery document.
- [OpenID Connect discovery](https://lms.soking.cc/.well-known/openid-configuration): OIDC discovery document.
- [Agentic Commerce manifest](https://lms.soking.cc/.well-known/acp.json): ACP checkout capabilities.
- [Developer documentation](https://docs.loopwise.com): guides for building against this platform.

## Optional

- [lms.soking.cc/llms-full.txt](https://lms.soking.cc/llms-full.txt): a single-document content bundle carrying the full text of up to 50 courses, posts and digital downloads each; a larger catalog is included in part, and that section states its true total — ~27k tokens, so check it against your context budget first.
- [Loopwise](https://loopwise.com): the platform this site runs on (formerly Teachify) — courses, events, and digital products for creators.