菜单
Update the vendored `frontend-design` skill in `.agents/skills/frontend-design/` from upstream `anthropics/skills` on GitHub. Use when the user asks to "sync frontend-design", "update the frontend-design skill", or "pull the latest frontend-design from GitHub".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sync-frontend-design |
| description | Update the vendored `frontend-design` skill in `.agents/skills/frontend-design/` from upstream `anthropics/skills` on GitHub. Use when the user asks to "sync frontend-design", "update the frontend-design skill", or "pull the latest frontend-design from GitHub". |
The frontend-design skill in this repo is vendored from https://github.com/anthropics/skills (path: skills/frontend-design/). This skill refreshes the local copy.
Fetch the upstream SKILL.md and LICENSE.txt from the main branch:
curl -fsSL -o .agents/skills/frontend-design/SKILL.md \
https://raw.githubusercontent.com/anthropics/skills/main/skills/frontend-design/SKILL.md
curl -fsSL -o .agents/skills/frontend-design/LICENSE.txt \
https://raw.githubusercontent.com/anthropics/skills/main/skills/frontend-design/LICENSE.txt
Show git diff -- .agents/skills/frontend-design/ so the user can review what changed.
If there are no changes, report that and stop.
If there are changes, ask the user whether to commit. On approval, commit with message chore: sync frontend-design skill from anthropics/skills.
curl against a new file path 404s, check the upstream tree at https://github.com/anthropics/skills/tree/main/skills/frontend-design and add it to the fetch list.Keep the Threa Pi remote-control extension in `extensions/pi-remote/` aligned with the current Pi extension API and Threa bot-runtime public API. Use when asked to update, verify, sync, or troubleshoot the Pi remote plugin, `/remote-control`, or `threa-remote.ts`.
Create a well-structured pull request with proper description, design decisions, and file changes. Use when asked to create a PR, open a PR, or submit changes for review.
Call Threa's public REST API (send/list/search/update/delete messages, list streams/users/members, search memos/attachments) with curl or a Bun script. Use when asked to post messages to a stream, seed a stream with test data, drive the API from automation, dedupe by metadata, inspect a production workspace (streams, messages, members) for troubleshooting, or otherwise hit https://staging.threa.io / https://app.threa.io endpoints with an API key. Reads from production should use the read-only prod key.
Rewrite user-facing copy (marketing pages, docs, headings, UI microcopy, READMEs, PR descriptions) to strip AI-slop and salesy tone, leaving plain, understated, factual prose. Use when asked to "deslopify", "deslop", "remove the AI slop", "make this less salesy/less AI-sounding", "make the copy plainer", or when reviewing copy for slop tells.
Run multi-perspective code review on a PR or the local branch
Write a session handover doc for the next agent picking up this line of work. Use when asked to "write a handover", "hand over", "handoff doc", or at the end of a session whose work continues in a future session.