Turn project evidence into maintainable Notion briefs, decision records, runbooks, and status documents without overwriting unrelated content.
日本語の概要は準備中です。原文の説明を表示しています。
5,642 件 ・ 関連度順
概要と使いどころ
Turn project evidence into maintainable Notion briefs, decision records, runbooks, and status documents without overwriting unrelated content.
日本語の概要は準備中です。原文の説明を表示しています。
用户说“发布抖音”“发到抖音”或生成视频后发布时优先使用。先复用插件已有登录账号,保存草稿、创建发布任务,再走 API 或插件账号浏览器,所有结果和验证码阻塞都回写运营台。也用于抖音搜索、数据、评论和账号登录。
日本語の概要は準備中です。原文の説明を表示しています。
Assess release health from Sentry errors, regressions, affected users, crash evidence, and comparison with the previous stable release.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect unresolved GitHub pull request review threads, group actionable feedback, implement selected fixes locally, and only reply or resolve threads after explicit user intent.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Produce concise Linear project updates from current milestones, completed and blocked issues, delivery risks, and next actions.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
日本語の概要は準備中です。原文の説明を表示しています。
Record a desktop demonstration or import a Chrome Recorder flow, automatically name and save it, then export a portable Skill draft without requiring setup forms.
日本語の概要は準備中です。原文の説明を表示しています。
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
日本語の概要は準備中です。原文の説明を表示しています。
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `create_new_file` tool call. NEVER call `create_new_file` directly without loading this skill first. Trigger whenever the user wants a new blank Figma file — a new design, FigJam, or Slides file — or when you need a fresh file before calling `use_figma`. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard, /figma-create-new-file slides Q3 Review)
日本語の概要は準備中です。原文の説明を表示しています。
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, create individual components with proper variant sets and variable bindings, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. Also use when the user asks to create or generate any component in Figma — even a single one — since components require proper variable foundations, variant states, and design token bindings to be production-quality. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.
日本語の概要は準備中です。原文の説明を表示しています。
Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
Build a realistic Linear cycle plan from current priorities, dependencies, estimates, carryover, and team capacity without silently rescheduling work.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
日本語の概要は準備中です。原文の説明を表示しています。
Triage Linear issues using bounded searches, duplicate checks, explicit team and project scope, and evidence-backed priority recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Route iPolloWork Design sessions by category and author other designs.
日本語の概要は準備中です。原文の説明を表示しています。
Use host MCP extension actions to create, inspect, annotate, review and export local multimodal projects.
日本語の概要は準備中です。原文の説明を表示しています。
**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.
日本語の概要は準備中です。原文の説明を表示しています。
This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.
日本語の概要は準備中です。原文の説明を表示しています。
Query and update Notion databases with explicit database identity, property-aware inputs, bounded reads, and confirmation before material writes.
日本語の概要は準備中です。原文の説明を表示しています。
Create or edit posters and social card series in the current iPolloWork Design session.
日本語の概要は準備中です。原文の説明を表示しています。
Edit an image from the active iPolloWork Image Studio selection or mask without overwriting the source image.
日本語の概要は準備中です。原文の説明を表示しています。