メニュー
Convert GitHub issues to discussions using agent-browser. Use when asked to convert, move, or change an issue to a discussion. Requires agent-browser installed and user to log in via headed browser.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.
Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.
Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.
| name | convert-issue-to-discussion |
| description | Convert GitHub issues to discussions using agent-browser. Use when asked to convert, move, or change an issue to a discussion. Requires agent-browser installed and user to log in via headed browser. |
Convert GitHub issues to discussions using browser automation when the gh CLI doesn't support this operation.
agent-browser installedagent-browser open "https://github.com/<owner>/<repo>/issues/<number>" --headed
The --headed flag shows the browser window so the user can log in.
Take a snapshot to check if logged in:
agent-browser snapshot -i
If you see "Sign in" in the elements, the user needs to log in. Let them know and wait for confirmation.
After login, go to the issue page:
agent-browser open "https://github.com/<owner>/<repo>/issues/<number>"
Take a snapshot and look for "Convert to discussion":
agent-browser snapshot -i
Look for a button like:
- button "Convert to discussion" [ref=e137]
agent-browser click @<ref>
A dialog will appear with category options:
agent-browser snapshot -i
You'll see options like:
- combobox "Category for new discussion" [ref=e2]
- option "General" [ref=e3] [selected]
- option "Ideas" [ref=e4]
- option "Q&A" [ref=e6]
- button "I understand, convert this issue" [ref=e9]
Select appropriate category (Q&A for support questions, Ideas for feature requests):
agent-browser select @<combobox-ref> "Q&A"
agent-browser click @<confirm-button-ref>
You don't need to verify, you are done now.
# Open issue page with visible browser
agent-browser open "https://github.com/owner/repo/issues/123" --headed
# Wait for user to log in, then get elements
agent-browser snapshot -i
# Click convert button (ref from snapshot)
agent-browser click @e137
# Wait for dialog, get new elements
agent-browser wait 1000 && agent-browser snapshot -i
# Select category and confirm
agent-browser select @e2 "Q&A"
agent-browser click @e9
# Verify - should redirect to discussions
agent-browser wait 2000 && agent-browser get url
You do not have to close the browser, as we'll use the login state again to convert other issues to discussions
When you are asked to find for more good issues to convert to discussions, use gh