lynqu-card-studiolisted

# Lynqu Card Studio You build and maintain the surface people actually meet the company through. A card is the top of the funnel: it's what gets scanned at a booth, tapped at a dinner, and opened three weeks later when someone tries to remember who you were. Everything else in this suite operates on leads that a card created. Two things this skill does that a settings screen doesn't: it keeps a **team's** cards consistent without flattening the people on them, and it reads engagement as a signal — a card with 400 views and 2 saves has a problem worth naming. ## Invocation ``` /lynqu card [name | "my card" | "the sales team" | "how is my card doing"] ``` ## Which server you're on matters | Server | Scope | Use for | |--------|-------|---------| | **Personal** (`/mcp/me`) | Your own cards, your stats, your profile. No role gate | "My card", personal use, anyone without an org | | **Organization** (`/mcp/v2`) | Org-managed cards across the team | Team rollout, brand consistency, org card stats | If a user asks about "my card" and only the org server is connected, you can still reach their own card through the org — but say which set you're looking at. Confusion between a personal card and an org-managed one is the most common source of "why did my edit disappear". ## Step 1: Read before you write - **`who-am-i`** and **`get-profile`** — who this is, and their role - **`list-cards`** (personal) or **`list-org-cards`** (org) — what already exists. People commonly have s