102 件 ・ 関連度順
概要と使いどころ
Use when the user explicitly chooses iPollo Onto or starts an Onto workbench task. Build and maintain business systems directly in its connected tables, relationships and documents, saving useful results progressively. A generic CRM, search or writing request alone does not activate this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
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.).
日本語の概要は準備中です。原文の説明を表示しています。
Let the OpenCode host delegate code review, development, and research tasks to DeepSeek Harness.
日本語の概要は準備中です。原文の説明を表示しています。
Edit an image from the active iPolloWork Image Studio selection or mask without overwriting the source image.
日本語の概要は準備中です。原文の説明を表示しています。
Produce concise Linear project updates from current milestones, completed and blocked issues, delivery risks, and next actions.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Search and summarize material from the Acme research service.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate a Sentry issue from bounded event, stack, tag, environment, release, and timeline evidence before proposing a code change.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Convert meeting material into decisions, action items, owners, dates, and open questions, then save it to an explicitly selected Notion destination.
日本語の概要は準備中です。原文の説明を表示しています。
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
日本語の概要は準備中です。原文の説明を表示しています。
Generate image assets through iPolloWork's image service, whether Image Studio is open or closed.
日本語の概要は準備中です。原文の説明を表示しています。
通过 iPolloWork 已有日程和会话执行抖音运营任务，固定账号、运行标识和操作编号，避免发布与回复重复发送。用于抖音定时运营、日程发布或定期数据查询。
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Route iPolloWork Design sessions by category and author other designs.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
Create or edit articles and reports in the current iPolloWork Design session.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
日本語の概要は準備中です。原文の説明を表示しています。
Turn project evidence into maintainable Notion briefs, decision records, runbooks, and status documents without overwriting unrelated content.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a production fix by linking the changed code and release to Sentry issue state and post-release event trends without resolving issues prematurely.
日本語の概要は準備中です。原文の説明を表示しています。
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
日本語の概要は準備中です。原文の説明を表示しています。
Triage Linear issues using bounded searches, duplicate checks, explicit team and project scope, and evidence-backed priority recommendations.
日本語の概要は準備中です。原文の説明を表示しています。