[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMNA5Q14YPJSV5H151W40G":3,"skill-same:01M7EMNA5Q14YPJSV5H151W40G":109},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EMNA5Q14YPJSV5H151W40G","tds-ui-figma",null,"Use when implementing, reviewing, or planning Angular UI from a Figma link\u002Fframe using tds-ui components and tds-color tokens, updating\u002Fsyncing TDS token JSON maps, or setting up Framelink Figma MCP for this workflow. Generic for any Angular project using tds-ui. Do not use for generic Angular bugfixes.","baobao0303\u002FRoom_Agent","baobao0303","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F110554959?v=4","01M7EMJ6GAWBRY5JNAH4PKB10S","Lê Tấn Bảo Bảo","01M7EMJ6H0FDB2MW9G9CS2FDX4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tds-ui-figma\ndescription: Use when implementing, reviewing, or planning Angular UI from a Figma link\u002Fframe using tds-ui components and tds-color tokens, updating\u002Fsyncing TDS token JSON maps, or setting up Framelink Figma MCP for this workflow. Generic for any Angular project using tds-ui. Do not use for generic Angular bugfixes.\n---\n\n# TDS UI Figma Workflow (Team)\n\n## 📚 Liên kết nhanh & Mục lục TDS\n- **Mục lục components:** [[components-index]]\n- **Quy tắc mapping Figma sang TDS:** [[figma-to-tds-ui-rules]]\n- **Quy tắc màu sắc:** [[figma-color-to-tds-token-rules]]\n- **Cấu hình Figma MCP:** [[figma-framelink-mcp-setup]]\n- **Quy định Review:** [[Quy-Dinh-Code-Review-Va-Chuan-TDS]]\n\n## Overview\n\nUse this as the required workflow for turning a selected Figma design into Angular code using **tds-ui** components and **tds-color** tokens. Generic for any Angular project — does not depend on a specific project's conventions.\n\nKeep loaded context limited to the selected node, required visual assets, and TDS components actually used.\n\n## MCP Preflight (REQUIRED)\n\nBefore reading or analyzing a Figma link, check whether Framelink MCP provides\n`get_figma_data` and `download_figma_images`.\n\nIf both tools are available, continue to Step 0.\n\nIf either tool is unavailable, stop the Figma workflow and give the user the\nsetup command for the current client:\n\n```bash\n# Codex\nbash ~\u002F.codex\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-codex.sh\n\n# Claude Code on Ubuntu\nbash ~\u002F.claude\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-claude-ubuntu.sh\n```\n\nTell the user to run only the command matching their client. The script shows\nhow to create a Figma Personal Access Token and asks for it locally. The token\nmust have only **File content: Read** (`file_content:read`); no write,\ncomments, variables, projects, or library scopes are required. Never ask the\nuser to paste the token into chat.\n\nAfter the script finishes, tell the user to restart Codex or Claude Code and\ninvoke the skill again (`$tds-ui-figma` in Codex or `\u002Ftds-ui-figma` in Claude\nCode). Do not continue Figma analysis until the MCP tools are available.\n\n## Required Sub-Skills\n\n- **tds-ui-usage**: Load only after the Figma frame reveals concrete TDS components or when an API detail is needed. Prefer specific component docs over the full catalog.\n- **figma:figma-use**: Optional. Load only for Figma write actions or JavaScript execution in the Figma file. For normal reads, use Framelink `get_figma_data` \u002F `download_figma_images` (structure, layout, assets) directly — neither needs this skill.\n\n## Core Rules\n\n- Prioritize readability, maintainability, scalability, and reusable solutions.\n- Avoid quick fixes, duplicated code, hardcoded logic, and deeply nested logic.\n- Keep functions small and single-responsibility.\n- Follow existing project patterns before adding new abstractions.\n- Reply to the developer in the language of their latest message.\n\n## Updating Token Maps\n\nWhen the developer asks to update, refresh, sync, or pull the latest TDS token JSON maps, run:\n\n```bash\nnode \u003Cskill-dir>\u002Fscripts\u002Fsync-tds-tokens.js\n```\n\nThis fetches the latest remote files configured in `references\u002Fconfig\u002Ftds-token-sources.json`:\n\n- `themeTokens` from `theme.json`\n- `globalTokens` from `global.json`\n- `aliasTokens` from `alias.json`\n\nThe lookup helper uses cached files for speed and offline reliability. Do not edit cached token JSON by hand. If a lookup result seems stale, sync first, then rerun `node \u003Cskill-dir>\u002Fscripts\u002Ftds-token-lookup.js \u003Chex> \u003Crole> [project] [themePreset] [mode]`.\n\n## Setting Up Framelink MCP\n\nWhen the developer asks to setup\u002Finstall\u002Fconfigure Figma MCP or Framelink MCP for Codex, direct them to run:\n\n```bash\nbash ~\u002F.codex\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-codex.sh\n```\n\nThe Codex script asks for the Figma token locally with visible input and writes\nan NVM-aware `[mcp_servers.figma]` block to `~\u002F.codex\u002Fconfig.toml`. It removes\nboth old `figma-framelink` and `figma` blocks first. The default image directory\nis the current project's `.figma-assets`; the developer can enter a custom directory\nwhen prompted. `~\u002F.codex\u002Fconfig.toml contains the Figma token`, so\ntell the developer not to commit or share it. Never ask the user to paste a\nFigma token into chat.\n\nWhen the developer asks to setup Claude Code on Ubuntu, direct them to run:\n\n```bash\nbash ~\u002F.claude\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-claude-ubuntu.sh\n```\n\nThe Claude Ubuntu script asks for the token locally with visible input, checks\n`~\u002F.claude.json`, migrates legacy `framelink` to `figma-framelink`, writes the\ntoken directly into Claude config, and detects Node PATH dynamically from the\nactual Node.js binary on that machine.\n\n## Step 0: Ask for Theme Preset (REQUIRED)\n\n**Before any analysis**, determine the project's theme preset:\n\n1. Read `\u003Cskill-dir>\u002Freferences\u002Fconfig\u002Ftds-project-token-map.json` and resolve the requested project, falling back to `projects.default`.\n2. Treat a missing or `null` `themePreset` as unconfigured.\n3. If a saved `themePreset` is not present in the current remote `theme.json` and is not \"other\" or \"none\", stop and report that the current theme is not supported. Run `node \u003Cskill-dir>\u002Fscripts\u002Fset-tds-theme-preset.js --list` to show the supported presets.\n4. If the preset is unconfigured, **stop immediately before calling Figma MCP or analyzing layout**. Sync\u002Fread remote `theme.json`, list the supported preset names, and ask the user to choose one or \"other\".\n5. If the user asks for a preset\u002Fcolor that is not supported and is not \"other\" or \"none\", ask them to choose a supported preset. Do not invent a preset or manually map primary\u002Fsecondary.\n6. Persist the selected preset by running `node \u003Cskill-dir>\u002Fscripts\u002Fset-tds-theme-preset.js \u003CthemePreset> [project]`. This updates the single skill-local project map.\n7. Reuse the saved preset later. Ask again only when it is missing, null, unsupported, or explicitly changed.\n8. Store the answer for color mapping (Step 3). Remote token JSON remains in the disposable cache configured by `references\u002Fconfig\u002Ftds-token-sources.json`; the project map does not.\n\nNever assume a default theme preset. If no supported project `themePreset` (or \"other\" \u002F \"none\") is configured and the user has not answered yet, stop before Figma analysis, component mapping, color mapping, or implementation. Do not continue with \"I will gather Figma structure first.\"\n\nThis step is mandatory because the same hex value maps to different TDS classes depending on the active theme preset. The supported preset list is not hardcoded in this skill; it comes from the synced remote `theme.json` array.\n## Figma Sources\n\nWhen the user provides a Figma URL, frame, or node, gather the full design context before coding, planning final implementation details, or reviewing visual parity.\n\nCollect only the sources needed for the request:\n\n1. **Figma node data - required**: Use `get_figma_data` with the file key and selected `node-id` whenever available. Read layout, spacing, typography, hierarchy, fills, strokes, effects, constraints, variants, component names, and text content from node data.\n2. **Image\u002FSVG\u002FGIF assets - conditional**: Use `download_figma_images` only when the MCP data identifies a real asset needed by the implementation. Do not download TDS icons such as `tdsi-*`; use TDS icon classes instead.\n3. **Screenshot or visual export - optional**: Capture\u002Fexport only when the user asks for visual comparison, pixel\u002Fvisual parity, or when node data is insufficient to understand composition.\n\nDo not rely only on screenshots when MCP node data can provide spacing, hierarchy, typography, or constraints. If a conditional source is needed but cannot be retrieved, report exactly what is missing and treat it as a Figma verification gap.\n\nIf Figma MCP access is missing or token setup is requested, read `references\u002Fsetup\u002Ffigma-framelink-mcp-setup.md`. Never ask the user to paste a Figma token into chat.\n\n## Figma MCP Layer\n\nUse Framelink MCP as the Figma source for this workflow. Do NOT call the Figma REST Variables API.\n\n**Framelink MCP** (`get_figma_data`, `download_figma_images`) is REST-based, fast, and headless (no Figma desktop app needed). Use it for the node tree, layout, spacing, typography, component\u002Fvariant metadata, icon flags, and image references. It returns resolved hex values, not variable\u002Falias names.\n\nFor colors, use Framelink's resolved hex as evidence and map it through the maintained token maps with `node scripts\u002Ftds-token-lookup.js \u003Chex> \u003Crole> [project] [themePreset] [mode]`. The helper syncs and caches `theme.json`, `global.json`, and `alias.json` from `references\u002Fconfig\u002Ftds-token-sources.json`. Accept exact one-class matches only; ask on ambiguous\u002Fmissing matches. If lookup returns `reason=themePresetRequired`, ask the user for the project theme preset and rerun lookup. Never invent hex-to-class mappings outside the maintained maps.\n\n## Output Modes\n\nUse **Analysis Mode** when the user asks to analyze, review, compare, map, inspect, or read the Figma design, or when the user sends only a Figma link without explicitly asking to implement immediately.\n\nUse **Implementation Mode** when the user clearly asks to implement, code, build, or proceed directly while skipping the analysis report, regardless of the language used. In Implementation Mode, skip the full analysis report, but still determine theme preset before gathering Figma data. If theme preset is missing, stop and ask before writing code.\n\n### Analysis Report Template\n\nWhen using Analysis Mode, return the sections in this exact order. Keep the report concise, but do not omit a section.\n\n#### 1. JS\u002FToken Lookup Output\n\nStart with the result generated from `node scripts\u002Ftds-token-lookup.js` or the `COLOR_MAP` emitted by `scripts\u002Ffigma-digest.js`. Summarize exact, ambiguous, missing, and `themePresetRequired` results before any layout diagram.\n\n````md\n## JS\u002FToken Lookup Output\n\nTheme preset: green\nToken cache: ~\u002F.cache\u002Ftds-ui-figma\u002Ftokens\n\n| Hex | Role | Source | Result | Status |\n|---|---|---|---|---|\n| `#0C1014` | text | aliasTokens | `tds-color-text-primary` | exact |\n| `#27A745` | background | themeTokens | `bg-tds-color-primary-500-light dark:bg-tds-color-primary-500-dark` | exact |\n| `#ABCDEF` | border | none | ask user | missing |\n| `#1A6DE3` | background | themeTokens | ask theme preset | themePresetRequired |\n\nQuestions:\n- `#ABCDEF` is not found in TDS tokens. Which TDS class should be used, or is a custom local color allowed?\n- Project theme preset is required before mapping `#1A6DE3`.\n````\n\n#### 2. Layout\n\nDescribe the layout hierarchy and include a lightweight Markdown\u002FASCII or Mermaid diagram when useful.\n\n````md\n## Layout\n\nScreen structure:\n- Header with title and actions\n- Filter bar with search and status select\n- Data table with row actions\n- Pagination footer\n\n```text\nPage\n|-- Header\n|-- Filter bar\n|-- Table\n`-- Pagination\n```\n````\n\n#### 3. Figma Component to TDS UI Mapping\n\nMap visible Figma components to `tds-ui` components. Include gaps instead of inventing custom UI.\n\n````md\n## Component Mapping\n\n| Figma evidence | Proposed TDS UI | Notes |\n|---|---|---|\n| Primary button | `tds-ui\u002Fbutton` | Use existing primary variant |\n| Search input | `tds-ui\u002Finput` | Preserve placeholder, disabled, error states |\n| Data table | `tds-ui\u002Ftable` | Confirm columns and row actions |\n| Unknown chart block | ask user | No clear mapped component yet |\n````\n\n#### 4. Color Mapping\n\nShow the Figma color evidence and lookup result. Missing or ambiguous values must become questions.\n\n````md\n## Color Mapping\n\n| Figma source | Hex | Role | TDS result | Status |\n|---|---|---|---|---|\n| Title text | `#0C1014` | text | `tds-color-text-primary` | exact |\n| CTA fill | `#27A745` | background | `bg-tds-color-primary-500-light dark:bg-tds-color-primary-500-dark` | exact |\n| Border line | `#ABCDEF` | border | ask user | missing |\n````\n\n## Workflow\n\n1. **Parse Figma input**\n   - Extract `fileKey` and `node-id` from the Figma URL.\n   - Prefer the selected frame or node over the full file.\n   - If the node id is absent and the task needs exact UI, ask for the target frame or clearly state the ambiguity.\n\n2. **Gather Figma context**\n   - Call Framelink `get_figma_data` for the target node (structure, components\u002Fvariants, layout, typography, icon flags).\n   - When color classes are needed and Framelink returned resolved hex values, use the maintained token maps via `node scripts\u002Ftds-token-lookup.js \u003Chex> \u003Crole> [project] [themePreset] [mode]`. The helper checks project overrides, then cached remote `theme.json`, `alias.json`, and `global.json`. Accept exact one-class matches only; ask on ambiguous\u002Fmissing matches. If lookup returns `reason=themePresetRequired`, ask the user for the project theme preset and rerun lookup. Never invent hex-to-class mappings outside the maintained maps.\n   - Pass the theme preset from Step 0 as the `themePreset` parameter.\n   - For a new project, if `references\u002Fconfig\u002Ftds-project-token-map.json` has no configured `themePreset`, run `node \u003Cskill-dir>\u002Fscripts\u002Fset-tds-theme-preset.js --list`, ask the user to choose one supported preset from remote `theme.json`, save it with the setter, then continue.\n   - Download only referenced images\u002FSVG\u002FGIF assets that cannot be represented by existing TDS icons or CSS.\n   - Capture\u002Fexport a screenshot only for visual parity requests or when the node data is not enough to understand the layout.\n   - Record missing required\u002Fconditional sources as verification gaps before continuing.\n\n3. **Map design to `tds-ui`**\n   - Start from `references\u002Fmapping\u002Ftds-ui-component-map.md`.\n   - For Framelink MCP component evidence, typography class rules, color role rules, icon size, font weight, spacing, radius, and \"ask instead of guess\" rules, read `references\u002Fmapping\u002Ffigma-to-tds-ui-rules.md`.\n   - Read `references\u002Fmapping\u002Ffigma-color-to-tds-token-rules.md` for the token-map source order and reporting rules. Never manually guess a class from hex.\n   - Then load only specific `tds-ui-usage\u002Freference\u002Fdocs\u002F*.md` files for components used by the design. Use the full component index only when no likely TDS component can be identified.\n   - Use `tds-ui` modules and public APIs instead of custom primitives when an equivalent exists.\n   - If no `tds-ui` component fits, record the gap first. For behavioral UI, ask the user before implementing custom markup. For purely structural wrappers, use project-local Angular markup and Tailwind utilities while preserving repo tokens, spacing, and behavior.\n\n4. **Plan implementation**\n   - Identify target component, module, route, service, DTO, state model, and asset paths.\n   - Include loading, empty, error, disabled, and responsive states expected by the screen.\n   - Keep scope limited to the requested screen or component.\n   - Explain any Figma-to-code tradeoff before or while implementing when the design conflicts with project rules.\n\n5. **Implement**\n   - Use Angular 18+ and strict TypeScript.\n   - Never use the `any` type unless there is no reasonable alternative and the reason is stated.\n   - Prefer explicit typing over implicit typing for public API boundaries.\n   - Use `interface` for DTOs and API responses.\n   - Use `type` for unions, mapped types, and utility types.\n   - Define return types for public methods.\n   - Name DTO interfaces with a `Dto` suffix.\n   - Import `tds-ui` from sub-paths only, for example `tds-ui\u002Fbutton`, not root `tds-ui`.\n   - Prefer Tailwind utility classes for new feature UI. Add component SCSS only when selectors, media queries, complex reusable styles, or existing local structure require it.\n   - Avoid hardcoded design tokens when `tds-ui` variables, Tailwind tokens, or component inputs can express the design.\n   - Render TDS color aliases directly as utility classes, for example `tds-color-text-secondary`, `tds-color-surface-low`, or `tds-color-border-success`; do not prefix them with `text-`, `bg-`, or `border-`.\n   - Render TDS typography classes with the `tds-` prefix, for example `tds-body-2 font-semibold`; do not use `text-body-2` or combine weight into names like `tds-body-2-semibold`.\n   - For data-heavy Figma screens, set the common default typography\u002Fcolor once on the nearest stable container, usually `tds-body-2 tds-color-text-primary`. Do not repeat those classes on every `span`. Only add typography\u002Fcolor classes to child text when MCP shows a different size, weight, semantic role, or color.\n   - For Single-Row Page Headers \u002F Toolbars with horizontal auto-layout: preserve the single-row structure (`h-14` \u002F `56px`, `px-6`). Wrap `tds-tabset` with a constrained width and hide `.tds-tabs-content-holder { display: none !important; }` so native `...` overflow triggers cleanly without tab clipping. Set uniform button & input height (`h-9` \u002F `36px`), outline button padding `px-3.5`, primary CTA `px-4 font-semibold`, and search input `min-w-[300px]` to prevent text truncation.\n   - For TDS icon classes, always verify exact class names from `node_modules\u002Ftds-ui\u002Ficon\u002Flist-icon.js` (e.g. `tdsi-user-list-fill`, `tdsi-sort-arrow-up-down-line`, `tdsi-filter-1-fill`, `tdsi-plus-fill`).\n\n6. **Verify**\n   - Run the narrowest useful check first.\n   - Then run `npx tsc -p tsconfig.json --noEmit` or `npx ng build` when appropriate for the change.\n   - For Figma-driven UI, verify structural\u002Fcomponent parity from node data. Verify visual parity against a screenshot\u002Fexport only when one was requested or captured.\n   - Report unrelated existing failures separately.\n\n## Decision Rules\n\n| Situation | Action |\n|---|---|\n| Figma component has a clear `tds-ui` equivalent | Use `tds-ui` and load the relevant component doc if API details are needed. |\n| Figma component is not in the map | Search `tds-ui-usage` docs before building custom UI. |\n| No `tds-ui` component fits | Record the gap first. For behavioral UI, ask the user before custom markup. For structural wrappers, use project-local markup\u002FCSS with project tokens and behavior. |\n| Figma MCP cannot read the file | Explain the access\u002Fsetup issue, use `references\u002Fsetup\u002Ffigma-framelink-mcp-setup.md`, and only use screenshot\u002Fexport as fallback after reporting the node data gap. |\n| Node data is available but optional assets or screenshot\u002Fexport are missing | Continue when they are not required for the requested implementation. If they are required, state the gap and ask before proceeding. |\n| Design conflicts with project rules | Follow project rules, then note the tradeoff. |\n| Implementation touches shared behavior | Broaden tests and verification beyond the narrow component. |\n\n## Output Style\n\n- Reply in the user's language (match the language of their latest message).\n- Keep implementation notes concise.\n- List the `tds-ui` modules used.\n- Call out missing Figma sources, MCP access issues, visual verification gaps, and unrelated existing failures plainly.\n- Include file references and verification commands\u002Fresults when work is complete.\n\n\n","# TDS UI Figma Workflow (Team)\n\n## 📚 Liên kết nhanh & Mục lục TDS\n- **Mục lục components:** [[components-index]]\n- **Quy tắc mapping Figma sang TDS:** [[figma-to-tds-ui-rules]]\n- **Quy tắc màu sắc:** [[figma-color-to-tds-token-rules]]\n- **Cấu hình Figma MCP:** [[figma-framelink-mcp-setup]]\n- **Quy định Review:** [[Quy-Dinh-Code-Review-Va-Chuan-TDS]]\n\n## Overview\n\nUse this as the required workflow for turning a selected Figma design into Angular code using **tds-ui** components and **tds-color** tokens. Generic for any Angular project — does not depend on a specific project's conventions.\n\nKeep loaded context limited to the selected node, required visual assets, and TDS components actually used.\n\n## MCP Preflight (REQUIRED)\n\nBefore reading or analyzing a Figma link, check whether Framelink MCP provides\n`get_figma_data` and `download_figma_images`.\n\nIf both tools are available, continue to Step 0.\n\nIf either tool is unavailable, stop the Figma workflow and give the user the\nsetup command for the current client:\n\n```bash\n# Codex\nbash ~\u002F.codex\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-codex.sh\n\n# Claude Code on Ubuntu\nbash ~\u002F.claude\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-claude-ubuntu.sh\n```\n\nTell the user to run only the command matching their client. The script shows\nhow to create a Figma Personal Access Token and asks for it locally. The token\nmust have only **File content: Read** (`file_content:read`); no write,\ncomments, variables, projects, or library scopes are required. Never ask the\nuser to paste the token into chat.\n\nAfter the script finishes, tell the user to restart Codex or Claude Code and\ninvoke the skill again (`$tds-ui-figma` in Codex or `\u002Ftds-ui-figma` in Claude\nCode). Do not continue Figma analysis until the MCP tools are available.\n\n## Required Sub-Skills\n\n- **tds-ui-usage**: Load only after the Figma frame reveals concrete TDS components or when an API detail is needed. Prefer specific component docs over the full catalog.\n- **figma:figma-use**: Optional. Load only for Figma write actions or JavaScript execution in the Figma file. For normal reads, use Framelink `get_figma_data` \u002F `download_figma_images` (structure, layout, assets) directly — neither needs this skill.\n\n## Core Rules\n\n- Prioritize readability, maintainability, scalability, and reusable solutions.\n- Avoid quick fixes, duplicated code, hardcoded logic, and deeply nested logic.\n- Keep functions small and single-responsibility.\n- Follow existing project patterns before adding new abstractions.\n- Reply to the developer in the language of their latest message.\n\n## Updating Token Maps\n\nWhen the developer asks to update, refresh, sync, or pull the latest TDS token JSON maps, run:\n\n```bash\nnode \u003Cskill-dir>\u002Fscripts\u002Fsync-tds-tokens.js\n```\n\nThis fetches the latest remote files configured in `references\u002Fconfig\u002Ftds-token-sources.json`:\n\n- `themeTokens` from `theme.json`\n- `globalTokens` from `global.json`\n- `aliasTokens` from `alias.json`\n\nThe lookup helper uses cached files for speed and offline reliability. Do not edit cached token JSON by hand. If a lookup result seems stale, sync first, then rerun `node \u003Cskill-dir>\u002Fscripts\u002Ftds-token-lookup.js \u003Chex> \u003Crole> [project] [themePreset] [mode]`.\n\n## Setting Up Framelink MCP\n\nWhen the developer asks to setup\u002Finstall\u002Fconfigure Figma MCP or Framelink MCP for Codex, direct them to run:\n\n```bash\nbash ~\u002F.codex\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-codex.sh\n```\n\nThe Codex script asks for the Figma token locally with visible input and writes\nan NVM-aware `[mcp_servers.figma]` block to `~\u002F.codex\u002Fconfig.toml`. It removes\nboth old `figma-framelink` and `figma` blocks first. The default image directory\nis the current project's `.figma-assets`; the developer can enter a custom directory\nwhen prompted. `~\u002F.codex\u002Fconfig.toml contains the Figma token`, so\ntell the developer not to commit or share it. Never ask the user to paste a\nFigma token into chat.\n\nWhen the developer asks to setup Claude Code on Ubuntu, direct them to run:\n\n```bash\nbash ~\u002F.claude\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-claude-ubuntu.sh\n```\n\nThe Claude Ubuntu script asks for the token locally with visible input, checks\n`~\u002F.claude.json`, migrates legacy `framelink` to `figma-framelink`, writes the\ntoken directly into Claude config, and detects Node PATH dynamically from the\nactual Node.js binary on that machine.\n\n## Step 0: Ask for Theme Preset (REQUIRED)\n\n**Before any analysis**, determine the project's theme preset:\n\n1. Read `\u003Cskill-dir>\u002Freferences\u002Fconfig\u002Ftds-project-token-map.json` and resolve the requested project, falling back to `projects.default`.\n2. Treat a missing or `null` `themePreset` as unconfigured.\n3. If a saved `themePreset` is not present in the current remote `theme.json` and is not \"other\" or \"none\", stop and report that the current theme is not supported. Run `node \u003Cskill-dir>\u002Fscripts\u002Fset-tds-theme-preset.js --list` to show the supported presets.\n4. If the preset is unconfigured, **stop immediately before calling Figma MCP or analyzing layout**. Sync\u002Fread remote `theme.json`, list the supported preset names, and ask the user to choose one or \"other\".\n5. If the user asks for a preset\u002Fcolor that is not supported and is not \"other\" or \"none\", ask them to choose a supported preset. Do not invent a preset or manually map primary\u002Fsecondary.\n6. Persist the selected preset by running `node \u003Cskill-dir>\u002Fscripts\u002Fset-tds-theme-preset.js \u003CthemePreset> [project]`. This updates the single skill-local project map.\n7. Reuse the saved preset later. Ask again only when it is missing, null, unsupported, or explicitly changed.\n8. Store the answer for color mapping (Step 3). Remote token JSON remains in the disposable cache configured by `references\u002Fconfig\u002Ftds-token-sources.json`; the project map does not.\n\nNever assume a default theme preset. If no supported project `themePreset` (or \"other\" \u002F \"none\") is configured and the user has not answered yet, stop before Figma analysis, component mapping, color mapping, or implementation. Do not continue with \"I will gather Figma structure first.\"\n\nThis step is mandatory because the same hex value maps to different TDS classes depending on the active theme preset. The supported preset list is not hardcoded in this skill; it comes from the synced remote `theme.json` array.\n## Figma Sources\n\nWhen the user provides a Figma URL, frame, or node, gather the full design context before coding, planning final implementation details, or reviewing visual parity.\n\nCollect only the sources needed for the request:\n\n1. **Figma node data - required**: Use `get_figma_data` with the file key and selected `node-id` whenever available. Read layout, spacing, typography, hierarchy, fills, strokes, effects, constraints, variants, component names, and text content from node data.\n2. **Image\u002FSVG\u002FGIF assets - conditional**: Use `download_figma_images` only when the MCP data identifies a real asset needed by the implementation. Do not download TDS icons such as `tdsi-*`; use TDS icon classes instead.\n3. **Screenshot or visual export - optional**: Capture\u002Fexport only when the user asks for visual comparison, pixel\u002Fvisual parity, or when node data is insufficient to understand composition.\n\nDo not rely only on screenshots when MCP node data can provide spacing, hierarchy, typography, or constraints. If a conditional source is needed but cannot be retrieved, report exactly what is missing and treat it as a Figma verification gap.\n\nIf Figma MCP access is missing or token setup is requested, read `references\u002Fsetup\u002Ffigma-framelink-mcp-setup.md`. Never ask the user to paste a Figma token into chat.\n\n## Figma MCP Layer\n\nUse Framelink MCP as the Figma source for this workflow. Do NOT call the Figma REST Variables API.\n\n**Framelink MCP** (`get_figma_data`, `download_figma_images`) is REST-based, fast, and headless (no Figma desktop app needed). Use it for the node tree, layout, spacing, typography, component\u002Fvariant metadata, icon flags, and image references. It returns resolved hex values, not variable\u002Falias names.\n\nFor colors, use Framelink's resolved hex as evidence and map it through the maintained token maps with `node scripts\u002Ftds-token-lookup.js \u003Chex> \u003Crole> [project] [themePreset] [mode]`. The helper syncs and caches `theme.json`, `global.json`, and `alias.json` from `references\u002Fconfig\u002Ftds-token-sources.json`. Accept exact one-class matches only; ask on ambiguous\u002Fmissing matches. If lookup returns `reason=themePresetRequired`, ask the user for the project theme preset and rerun lookup. Never invent hex-to-class mappings outside the maintained maps.\n\n## Output Modes\n\nUse **Analysis Mode** when the user asks to analyze, review, compare, map, inspect, or read the Figma design, or when the user sends only a Figma link without explicitly asking to implement immediately.\n\nUse **Implementation Mode** when the user clearly asks to implement, code, build, or proceed directly while skipping the analysis report, regardless of the language used. In Implementation Mode, skip the full analysis report, but still determine theme preset before gathering Figma data. If theme preset is missing, stop and ask before writing code.\n\n### Analysis Report Template\n\nWhen using Analysis Mode, return the sections in this exact order. Keep the report concise, but do not omit a section.\n\n#### 1. JS\u002FToken Lookup Output\n\nStart with the result generated from `node scripts\u002Ftds-token-lookup.js` or the `COLOR_MAP` emitted by `scripts\u002Ffigma-digest.js`. Summarize exact, ambiguous, missing, and `themePresetRequired` results before any layout diagram.\n\n````md\n## JS\u002FToken Lookup Output\n\nTheme preset: green\nToken cache: ~\u002F.cache\u002Ftds-ui-figma\u002Ftokens\n\n| Hex | Role | Source | Result | Status |\n|---|---|---|---|---|\n| `#0C1014` | text | aliasTokens | `tds-color-text-primary` | exact |\n| `#27A745` | background | themeTokens | `bg-tds-color-primary-500-light dark:bg-tds-color-primary-500-dark` | exact |\n| `#ABCDEF` | border | none | ask user | missing |\n| `#1A6DE3` | background | themeTokens | ask theme preset | themePresetRequired |\n\nQuestions:\n- `#ABCDEF` is not found in TDS tokens. Which TDS class should be used, or is a custom local color allowed?\n- Project theme preset is required before mapping `#1A6DE3`.\n````\n\n#### 2. Layout\n\nDescribe the layout hierarchy and include a lightweight Markdown\u002FASCII or Mermaid diagram when useful.\n\n````md\n## Layout\n\nScreen structure:\n- Header with title and actions\n- Filter bar with search and status select\n- Data table with row actions\n- Pagination footer\n\n```text\nPage\n|-- Header\n|-- Filter bar\n|-- Table\n`-- Pagination\n```\n````\n\n#### 3. Figma Component to TDS UI Mapping\n\nMap visible Figma components to `tds-ui` components. Include gaps instead of inventing custom UI.\n\n````md\n## Component Mapping\n\n| Figma evidence | Proposed TDS UI | Notes |\n|---|---|---|\n| Primary button | `tds-ui\u002Fbutton` | Use existing primary variant |\n| Search input | `tds-ui\u002Finput` | Preserve placeholder, disabled, error states |\n| Data table | `tds-ui\u002Ftable` | Confirm columns and row actions |\n| Unknown chart block | ask user | No clear mapped component yet |\n````\n\n#### 4. Color Mapping\n\nShow the Figma color evidence and lookup result. Missing or ambiguous values must become questions.\n\n````md\n## Color Mapping\n\n| Figma source | Hex | Role | TDS result | Status |\n|---|---|---|---|---|\n| Title text | `#0C1014` | text | `tds-color-text-primary` | exact |\n| CTA fill | `#27A745` | background | `bg-tds-color-primary-500-light dark:bg-tds-color-primary-500-dark` | exact |\n| Border line | `#ABCDEF` | border | ask user | missing |\n````\n\n## Workflow\n\n1. **Parse Figma input**\n   - Extract `fileKey` and `node-id` from the Figma URL.\n   - Prefer the selected frame or node over the full file.\n   - If the node id is absent and the task needs exact UI, ask for the target frame or clearly state the ambiguity.\n\n2. **Gather Figma context**\n   - Call Framelink `get_figma_data` for the target node (structure, components\u002Fvariants, layout, typography, icon flags).\n   - When color classes are needed and Framelink returned resolved hex values, use the maintained token maps via `node scripts\u002Ftds-token-lookup.js \u003Chex> \u003Crole> [project] [themePreset] [mode]`. The helper checks project overrides, then cached remote `theme.json`, `alias.json`, and `global.json`. Accept exact one-class matches only; ask on ambiguous\u002Fmissing matches. If lookup returns `reason=themePresetRequired`, ask the user for the project theme preset and rerun lookup. Never invent hex-to-class mappings outside the maintained maps.\n   - Pass the theme preset from Step 0 as the `themePreset` parameter.\n   - For a new project, if `references\u002Fconfig\u002Ftds-project-token-map.json` has no configured `themePreset`, run `node \u003Cskill-dir>\u002Fscripts\u002Fset-tds-theme-preset.js --list`, ask the user to choose one supported preset from remote `theme.json`, save it with the setter, then continue.\n   - Download only referenced images\u002FSVG\u002FGIF assets that cannot be represented by existing TDS icons or CSS.\n   - Capture\u002Fexport a screenshot only for visual parity requests or when the node data is not enough to understand the layout.\n   - Record missing required\u002Fconditional sources as verification gaps before continuing.\n\n3. **Map design to `tds-ui`**\n   - Start from `references\u002Fmapping\u002Ftds-ui-component-map.md`.\n   - For Framelink MCP component evidence, typography class rules, color role rules, icon size, font weight, spacing, radius, and \"ask instead of guess\" rules, read `references\u002Fmapping\u002Ffigma-to-tds-ui-rules.md`.\n   - Read `references\u002Fmapping\u002Ffigma-color-to-tds-token-rules.md` for the token-map source order and reporting rules. Never manually guess a class from hex.\n   - Then load only specific `tds-ui-usage\u002Freference\u002Fdocs\u002F*.md` files for components used by the design. Use the full component index only when no likely TDS component can be identified.\n   - Use `tds-ui` modules and public APIs instead of custom primitives when an equivalent exists.\n   - If no `tds-ui` component fits, record the gap first. For behavioral UI, ask the user before implementing custom markup. For purely structural wrappers, use project-local Angular markup and Tailwind utilities while preserving repo tokens, spacing, and behavior.\n\n4. **Plan implementation**\n   - Identify target component, module, route, service, DTO, state model, and asset paths.\n   - Include loading, empty, error, disabled, and responsive states expected by the screen.\n   - Keep scope limited to the requested screen or component.\n   - Explain any Figma-to-code tradeoff before or while implementing when the design conflicts with project rules.\n\n5. **Implement**\n   - Use Angular 18+ and strict TypeScript.\n   - Never use the `any` type unless there is no reasonable alternative and the reason is stated.\n   - Prefer explicit typing over implicit typing for public API boundaries.\n   - Use `interface` for DTOs and API responses.\n   - Use `type` for unions, mapped types, and utility types.\n   - Define return types for public methods.\n   - Name DTO interfaces with a `Dto` suffix.\n   - Import `tds-ui` from sub-paths only, for example `tds-ui\u002Fbutton`, not root `tds-ui`.\n   - Prefer Tailwind utility classes for new feature UI. Add component SCSS only when selectors, media queries, complex reusable styles, or existing local structure require it.\n   - Avoid hardcoded design tokens when `tds-ui` variables, Tailwind tokens, or component inputs can express the design.\n   - Render TDS color aliases directly as utility classes, for example `tds-color-text-secondary`, `tds-color-surface-low`, or `tds-color-border-success`; do not prefix them with `text-`, `bg-`, or `border-`.\n   - Render TDS typography classes with the `tds-` prefix, for example `tds-body-2 font-semibold`; do not use `text-body-2` or combine weight into names like `tds-body-2-semibold`.\n   - For data-heavy Figma screens, set the common default typography\u002Fcolor once on the nearest stable container, usually `tds-body-2 tds-color-text-primary`. Do not repeat those classes on every `span`. Only add typography\u002Fcolor classes to child text when MCP shows a different size, weight, semantic role, or color.\n   - For Single-Row Page Headers \u002F Toolbars with horizontal auto-layout: preserve the single-row structure (`h-14` \u002F `56px`, `px-6`). Wrap `tds-tabset` with a constrained width and hide `.tds-tabs-content-holder { display: none !important; }` so native `...` overflow triggers cleanly without tab clipping. Set uniform button & input height (`h-9` \u002F `36px`), outline button padding `px-3.5`, primary CTA `px-4 font-semibold`, and search input `min-w-[300px]` to prevent text truncation.\n   - For TDS icon classes, always verify exact class names from `node_modules\u002Ftds-ui\u002Ficon\u002Flist-icon.js` (e.g. `tdsi-user-list-fill`, `tdsi-sort-arrow-up-down-line`, `tdsi-filter-1-fill`, `tdsi-plus-fill`).\n\n6. **Verify**\n   - Run the narrowest useful check first.\n   - Then run `npx tsc -p tsconfig.json --noEmit` or `npx ng build` when appropriate for the change.\n   - For Figma-driven UI, verify structural\u002Fcomponent parity from node data. Verify visual parity against a screenshot\u002Fexport only when one was requested or captured.\n   - Report unrelated existing failures separately.\n\n## Decision Rules\n\n| Situation | Action |\n|---|---|\n| Figma component has a clear `tds-ui` equivalent | Use `tds-ui` and load the relevant component doc if API details are needed. |\n| Figma component is not in the map | Search `tds-ui-usage` docs before building custom UI. |\n| No `tds-ui` component fits | Record the gap first. For behavioral UI, ask the user before custom markup. For structural wrappers, use project-local markup\u002FCSS with project tokens and behavior. |\n| Figma MCP cannot read the file | Explain the access\u002Fsetup issue, use `references\u002Fsetup\u002Ffigma-framelink-mcp-setup.md`, and only use screenshot\u002Fexport as fallback after reporting the node data gap. |\n| Node data is available but optional assets or screenshot\u002Fexport are missing | Continue when they are not required for the requested implementation. If they are required, state the gap and ask before proceeding. |\n| Design conflicts with project rules | Follow project rules, then note the tradeoff. |\n| Implementation touches shared behavior | Broaden tests and verification beyond the narrow component. |\n\n## Output Style\n\n- Reply in the user's language (match the language of their latest message).\n- Keep implementation notes concise.\n- List the `tds-ui` modules used.\n- Call out missing Figma sources, MCP access issues, visual verification gaps, and unrelated existing failures plainly.\n- Include file references and verification commands\u002Fresults when work is complete.\n\n\n",{"name":5,"description":7},"main","9a0e463878cc8f95f6e1e54f8773a42697a3fe34","profiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent","https:\u002F\u002Fgithub.com\u002Fbaobao0303","baobao22.work@gmail.com","2026-11-06 10:30:30",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add baobao0303\u002FRoom_Agent --skill tds-ui-figma",{"tool":37,"command":38},"bunx","bunx skills add baobao0303\u002FRoom_Agent --skill tds-ui-figma",{"tool":40,"command":41},"pnpm","pnpm dlx skills add baobao0303\u002FRoom_Agent --skill tds-ui-figma","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002FSKILL.md",true,[45,51,55,59,63,67,71,75,79,83,89,93,97,101,105],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",246,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"INSTALL.md",6784,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002FINSTALL.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"OVERVIEW.md",8456,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002FOVERVIEW.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fconfig\u002Ftds-project-token-map.json",424,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Freferences\u002Fconfig\u002Ftds-project-token-map.json",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fconfig\u002Ftds-token-sources.json",295,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Freferences\u002Fconfig\u002Ftds-token-sources.json",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fmapping\u002Ffigma-color-to-tds-token-rules.md",4329,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Freferences\u002Fmapping\u002Ffigma-color-to-tds-token-rules.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fmapping\u002Ffigma-to-tds-ui-rules.md",19062,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Freferences\u002Fmapping\u002Ffigma-to-tds-ui-rules.md",{"path":76,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fmapping\u002Ftds-ui-component-map.md",2476,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Freferences\u002Fmapping\u002Ftds-ui-component-map.md",{"path":80,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fsetup\u002Ffigma-framelink-mcp-setup.md",4476,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Freferences\u002Fsetup\u002Ffigma-framelink-mcp-setup.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Ffigma-digest.js","SCRIPT","脚本",8303,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Ffigma-digest.js",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fset-tds-theme-preset.js",3964,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fset-tds-theme-preset.js",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fsetup-figma-framelink-claude-ubuntu.sh",4855,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-claude-ubuntu.sh",{"path":98,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fsetup-figma-framelink-codex.sh",5722,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsetup-figma-framelink-codex.sh",{"path":102,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fsync-tds-tokens.js",2206,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Fsync-tds-tokens.js",{"path":106,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Ftds-token-lookup.js",9290,"https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fpeer\u002Fskills\u002Ftds-ui-figma\u002Fscripts\u002Ftds-token-lookup.js",[110,117,124,131,138,145],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7EMX6PB6T8J2NZ21CXTRA7E","workflow-launch-exec","Launch, orchestrate, and drive end-to-end multi-agent pipelines (BA -> DESIGN -> DEV -> VERIFY) for any task.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Fworkflow-launch-exec\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7EMX3197ZW7G22MV6A7K8M2","paseo-handoff","Hand off the current task to another agent with full context. Use when the user says \"handoff\", \"hand off\", \"hand this to\", or wants to pass work to another agent.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Fpaseo-handoff\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M7EMWZSS3TX7MJYQYZMNCCJF","loop-me","Grill me about specs for the workflows I want to build, within this workspace.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Floop-me\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M7EMWPP2C0D3QW8A274JQE75","loop-engineering","Use when the user wants Claude Code to keep working on its own until a goal is met — a self-running loop instead of write→wait→review→re-prompt. Helps decide if a loop is even worth building, picks manual vs automatic and open vs closed, distinguishes \u002Fgoal vs \u002Floop vs routines (\u002Fschedule), and wires up a CLOSED loop with a real verification gate (Stop hook running tests, or an LLM-judge + rubric when output isn't testable) plus a turn\u002Fbudget ceiling so it never spins forever. Triggers on \"loop\", \"döngü\", \"loop engineering\", \"auto mode\", \"run until tests pass\", \"self-running \u002F autonomous agent\", \"\u002Fgoal\", \"Stop hook\", \"ralph wiggum\".","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Floop-engineering\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":19},"01M7EMWKJ1JJ0T1P8Q09H3YFM6","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":19},"01M7EMWGSXRRGVZFQZYR4DKWHW","claude-handoff","Hand the current conversation off to a fresh background agent that picks up the work immediately.","https:\u002F\u002Fgithub.com\u002Fbaobao0303\u002FRoom_Agent\u002Fblob\u002Fmain\u002Fprofiles\u002Fsupervisor\u002Fskills\u002Floop-and-orchestration\u002Fclaude-handoff\u002FSKILL.md",[],[]]