Devin-AXIS/iPolloWork skills

Search and summarize material from the Acme research service.

Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.

Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.

Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.

Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.

Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.

Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.

Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.

Electron and Den, desktop plus cloud, two-sandbox e2e, cloud auth, marketplace, org policy, worker proxy, provider sync, desktop handoff. Validate Electron against a Daytona Den server with unified proof.

frame proof, HTML frames, screenshots, recording, PR proof, e2e evidence, validate visually. Daytona artifacts workflow for validated screenshots and optional videos.

test on Windows, enterprise CA, corporate certificate, GPO cert, TLS fetch failed, Windows sandbox, daytona windows, self-hosted cert. Use when validating iPolloWork Windows enterprise TLS/OS-trust fixes in a Daytona Windows sandbox.

Let the OpenCode host delegate code review, development, and research tasks to DeepSeek Harness.

通过 iPolloWork 已有日程和会话执行抖音运营任务，固定账号、运行标识和操作编号，避免发布与回复重复发送。用于抖音定时运营、日程发布或定期数据查询。

用户说“发布抖音”“发到抖音”或生成视频后发布时优先使用。先复用插件已有登录账号，保存草稿、创建发布任务，再走 API 或插件账号浏览器，所有结果和验证码阻塞都回写运营台。也用于抖音搜索、数据、评论和账号登录。

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.

**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)

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).

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.).

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.

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`.

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.

**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.

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.

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.

create a fraimz, make fraimz, prove it works, frame proof, PR proof, validate experience, e2e evidence, fraimz.html. The full fraimz loop — frame the claim, drive the real app via CDP, validate/repair, output fraimz.html. Use whenever a task ends with "please create a fraimz" or any change needs end-to-end proof.

get an env var, fetch a secret, missing env var, missing token/API key, load secrets from Infisical, infisical. Fetch secrets from the team's Infisical workspace into the shell environment so subsequent commands can use them.

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.

Diagnose failing GitHub Actions runs from bounded run, job, and step evidence, propose a focused fix, and modify the local checkout only when the requested task includes implementation.

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.

Inspect unresolved GitHub pull request review threads, group actionable feedback, implement selected fixes locally, and only reply or resolve threads after explicit user intent.

Edit an image from the active iPolloWork Image Studio selection or mask without overwriting the source image.

Edit an image from the active iPolloWork Image Studio selection or mask without overwriting the source image.

Generate image assets through iPolloWork's image service, whether Image Studio is open or closed.

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.

Create or edit articles and reports in the current iPolloWork Design session.

Create or edit posters and social card series in the current iPolloWork Design session.

Route iPolloWork Design sessions by category and author other designs.

Create or edit websites and application interfaces in the current iPolloWork Design session.

Mandatory iPolloWork code-change gate for modern, minimal, performant, reuse-first implementation and clean repository ownership. Use whenever AI creates, edits, deletes, or refactors application code, server code, packages, scripts, tests, dependencies, schemas, routes, UI, or generated-file workflows. Reuse existing code before creating files, keep one source of truth, prevent parallel implementations and junk directories, justify every new file or dependency, and audit the current change before completion.

为 iPolloWork 新插件或插件工作区复用 UI 组件、颜色、字体及交互规范。按 Figma 成熟状态和代码清单优先采用已确认组件，区分宿主 React 与独立 HTML/iframe 的接入方式；适用于插件表单、导航、浮层、反馈、状态和进度设计及实现，不改变用户作品的视觉风格。

Create, revise, and verify slide presentations in an active iPolloWork Design session while retaining the selected template's visual and editable contracts.

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.

Create or update reusable iPolloWork templates through conversation for Design, Slides/native editable PPT, and HyperFrames Video. Use when planning, generating, repairing, validating, or saving a template package, manifest, reusable variables, cover, slide/PPT markers, video composition, or design-system token integration.

Develop or update reusable visual components for iPolloWork Video, including maps, charts, rankings, diagrams, openings and endings. Use for component authoring rules, manifests, editable variables, shared data forms, inherited design themes, AI editing slots and seekable HyperFrames timelines. Not for producing a whole video, authoring a full-project template, or packaging a DeepSeek host plugin.

Create or edit the active iPolloWork video's visual assets, installed recipes, editable composition and seek-safe motion; use for assembly or local picture/text/theme changes.

Add or revise music, sound effects and their mix in the active iPolloWork video, using authorized sources, real editable tracks and measured event cues.

Write or revise the active iPolloWork video's native STORYBOARD.md, with source coverage, content-led sequence and provisional timing; use for script-only work.

Route the active iPolloWork video request to its current storyboard, compose, voiceover or soundtrack work, using the engine's native workflow and existing media tools.

Create, repair, validate, or package a reusable iPollo Video template in an active HyperFrames template-authoring session. Use for video template structure, editable variables, reusable scenes, GSAP motion, component reuse, cover metadata, and save-ready validation; do not use for ordinary one-off video edits.

Add or revise scene-bound narration or speech-linked captions in the active iPolloWork video using actual voice settings, measured audio and alignment.

Use Jev to select among available tools, skills or agents, or evaluate outputs against explicit rubrics. Use when the user requests Jev or a bounded decision would help; not for open-ended writing or research.

Use host MCP extension actions to create, inspect, annotate, review and export local multimodal projects.

Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.

Produce concise Linear project updates from current milestones, completed and blocked issues, delivery risks, and next actions.

Build a realistic Linear cycle plan from current priorities, dependencies, estimates, carryover, and team capacity without silently rescheduling work.

Triage Linear issues using bounded searches, duplicate checks, explicit team and project scope, and evidence-backed priority recommendations.

Query and update Notion databases with explicit database identity, property-aware inputs, bounded reads, and confirmation before material writes.

Search connected Notion pages and databases, verify the relevant sources, and produce concise answers that preserve links and uncertainty.

Convert meeting material into decisions, action items, owners, dates, and open questions, then save it to an explicitly selected Notion destination.

Turn project evidence into maintainable Notion briefs, decision records, runbooks, and status documents without overwriting unrelated content.

Create and revise locally installable iPolloWork plugins with the right-side Plugin Workshop.

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.

Step through versioning, tagging, and verification

do e2e tests, run e2e, validate feature, prove it works, PR proof, frame proof, pnpm evals. Launches iPolloWork on Daytona or local Electron and runs the coded eval flows via CDP. Launch + run mechanics; the proof loop itself is the fraimz skill.

Verify a production fix by linking the changed code and release to Sentry issue state and post-release event trends without resolving issues prematurely.

Investigate a Sentry issue from bounded event, stack, tag, environment, release, and timeline evidence before proposing a code change.

Compare bounded Sentry windows and releases to identify new issues, regressions, frequency changes, and user-impact changes.

Assess release health from Sentry errors, regressions, affected users, crash evidence, and comparison with the previous stable release.

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

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.

Use the 35 installed native business diagram components in the active iPolloWork video project. Edit their native text, graphics, shared data forms and seekable GSAP timelines with the standard Video Studio workflow.

Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.

Investigate Stripe payment failures and unexpected outcomes from exact object IDs, lifecycle state, events, amounts, currency, refunds, and dispute evidence.

Reconcile bounded Stripe payment and payout records with supplied business records while preserving object IDs, currency, time zone, and discrepancy evidence.

Review and execute explicitly requested Stripe writes with exact environment, object, amount, currency, customer, and irreversible-effect confirmation.

upload a photo/image/screenshot, host an image, get a public image URL, put images on Vercel Blob, embed images in a PR/comment/doc. Upload local images to Vercel Blob and print public URLs.

write the voice-over, demo script first, voiceover instead of PRD, voiceover-first development, align on the demo, script the demo, ship a feature demo-first. The whole demo-driven journey — approve the narration BEFORE any code, then build on a fresh worktree until the demo holds and open the PR with the proof on it. Use when a feature request arrives, or when the user runs /voiceover.

复用 iPolloWork 日程按固定视频号执行草稿准备、发布和运营数据同步，维持稳定操作标识与真实结果回读。

在 iPolloWork 当前会话中管理微信视频号本地草稿、素材和账号，通过账号独立浏览器执行已授权发布、作品同步和评论回复，记录真实页面结果。

Prepare selected workspace images and information cards as WeChat Official Account cover and article assets without reading outside the active workspace.

Triage WeChat article comments, prepare safe reply drafts, and only reply, feature, delete, or change comment state with explicit user intent.

Inspect WeChat Official Account followers and safely review or update custom menus with explicit before-and-after confirmation.

Create accurate, readable WeChat Official Account article drafts with a clear title, digest, HTML body, source links, and a reviewable call to action.

Design safe WeChat follower-message automation and send customer-service text only when the user provides an explicit target and confirmation.

Manage WeChat Official Account drafts and publication with explicit preview, confirmation, and post-publication status checks.

Turn bounded draft, publication, and comment evidence into a concise WeChat Official Account operating review and next-step plan.

Dispatch due Xiaohongshu browser jobs to locked account workers.

Execute authorized Xiaohongshu publishing, comments and replies from iPolloWork Schedule or a project session using the selected account's persistent browser.