Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
5,651 件 ・ 関連度順
概要と使いどころ
Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code', 'convert this modal/dialog/drawer/panel to Figma'. This is the preferred workflow skill whenever the user wants to build or update a full page, modal, dialog, drawer, sidebar, panel, or any composed multi-section view in Figma from code or a description. Discovers design system components, variables, and styles from Code Connect files, existing screens, and library search, then imports them and assembles views incrementally section-by-section using design system tokens instead of hardcoded values.
日本語の概要は準備中です。原文の説明を表示しています。
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
Triage Linear issues using bounded searches, duplicate checks, explicit team and project scope, and evidence-backed priority recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Create, revise, and verify slide presentations in an active iPolloWork Design session while retaining the selected template's visual and editable contracts.
日本語の概要は準備中です。原文の説明を表示しています。
Produce concise Linear project updates from current milestones, completed and blocked issues, delivery risks, and next actions.
日本語の概要は準備中です。原文の説明を表示しています。
Query and update Notion databases with explicit database identity, property-aware inputs, bounded reads, and confirmation before material writes.
日本語の概要は準備中です。原文の説明を表示しています。
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.
日本語の概要は準備中です。原文の説明を表示しています。
Compare bounded Sentry windows and releases to identify new issues, regressions, frequency changes, and user-impact changes.
日本語の概要は準備中です。原文の説明を表示しています。
Create or edit articles and reports in the current iPolloWork Design session.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate a Sentry issue from bounded event, stack, tag, environment, release, and timeline evidence before proposing a code change.
日本語の概要は準備中です。原文の説明を表示しています。
Generate image assets through iPolloWork's image service, whether Image Studio is open or closed.
日本語の概要は準備中です。原文の説明を表示しています。
Use with any iPolloWork template generating video, slides, websites or other designs from iPolloWork reference documents and a creative-context.json attachment. Read unified content, design evidence and asset paths; apply the edited brief and verify actual asset reuse. Does not parse documents with models.
日本語の概要は準備中です。原文の説明を表示しています。
Use the connected iPolloWork GitHub service to inspect repositories, pull requests, issues, reviews, and Actions, then route focused work to the review, CI, or publish skill.
日本語の概要は準備中です。原文の説明を表示しています。
用户说“发布抖音”“发到抖音”或生成视频后发布时优先使用。先复用插件已有登录账号,保存草稿、创建发布任务,再走 API 或插件账号浏览器,所有结果和验证码阻塞都回写运营台。也用于抖音搜索、数据、评论和账号登录。
日本語の概要は準備中です。原文の説明を表示しています。
Convert meeting material into decisions, action items, owners, dates, and open questions, then save it to an explicitly selected Notion destination.
日本語の概要は準備中です。原文の説明を表示しています。
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
日本語の概要は準備中です。原文の説明を表示しています。
Translates Figma motion and animations into production-ready application code. Use when implementing animation/motion from a Figma design — user mentions "implement this motion", "add animation from Figma", "animate this component", provides a Figma URL whose node is animated, or when `get_design_context` returns motion data or instructs you to call `get_motion_context`.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.
日本語の概要は準備中です。原文の説明を表示しています。
Search and summarize material from the Acme research service.
日本語の概要は準備中です。原文の説明を表示しています。
Publish intentional local changes by confirming scope, creating a branch when needed, staging selected files, committing, pushing, and creating a Draft Pull Request through the connected GitHub service.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when implementing a Figma design as code (design → code) — the read-FROM-Figma direction. Triggers: 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'code this up from Figma', 'design to code', or a figma.com design URL provided alongside a codebase. Encodes the workflow for reading a node out of Figma with get_design_context and adapting its reference output to the target project — reusing existing components, tokens, and conventions, and honoring Code Connect mappings, component docs, design annotations, and design tokens by priority. Complements figma-code-connect (component mapping) and figma-generate-design / figma-use (the reverse, code → design direction).
日本語の概要は準備中です。原文の説明を表示しています。
Plan and create short videos using the installed short-video-studio workspace app. Manage its creative canvas, scripts, storyboards, characters and local assets, generate images or video through connected Work channels, and hand off editable tracks to Work Video Studio.
日本語の概要は準備中です。原文の説明を表示しています。