blueif16

Start, check, or continue any work. Analyzes intent, plans tasks, and orchestrates execution via subagents (L2) or Agent Teams (L3).

Generate Playwright test scripts for browser-based acceptance verification. Load when DAG tasks touch UI, routes, or user-facing API responses.

Classify intent, assess complexity, generate task DAGs. Activates on /go or when user describes work.

Guide for using Reddit MCP to gather community sentiment, pain points, and adoption trends. Load this skill when a DAG contains research tasks about market validation, developer experience, or community opinions.

解析PRD，决定水平拆分策略，生成带验收标准的mini-PRD。当主协调器收到初始PRD或需要重新拆分工作时使用。

使用git worktrees为并行子协调器生成和管理tmux会话。当各部分准备好执行时使用。

从验收标准创建检查清单，编排executor→validator循环并带重试逻辑。当子协调器开始实现或收到验证失败时使用。

自动合并所有已完成部分，解决冲突，验证集成。仅当执行管理器检测到所有部分完成时调用。

Define Apple-Keynote-style motion grammar for educational videos. Use when selecting builds, handoffs, object continuity, stage transitions, framed content motion, typography reveals, or smooth presenter-to-canvas movement for the Remotion/Hyperframes vlog pipeline.

Specify inserted generated-video clips for the composer pipeline. Use when a transcript section needs a generated visual metaphor, illustrative clip, b-roll, product-style animation, or cinematic insert that must match the global style and neighboring shots.

Split content between the voice and the slide so they complement instead of repeat. Use at node 03 (script / cue-plan) AND node 04 (visual / slide copy) when authoring any beat that has both narration and on-screen text — the anti-duplication contract that keeps the voice from reading the slide aloud.

Use when a recorded-video composition should use the Render Lab design system: production-control-room visuals, browser/render/QC instruments, frame-driven Remotion motion, and semantic components instead of generic cards or decorative UI.

Quality-check rendered video outputs, Hyperframes atoms, Remotion previews, and composer artifacts for this project. Use after creating or changing any atom, generated clip, render plan, timeline, caption layout, presenter framing, or final MP4.

Convert video-composer decisions into precise shot briefs for sub-agents or sub-nodes. Use when a section needs a self-contained spec containing global style, transcript excerpt, neighboring shots, dependencies, asset requirements, presenter/content layout, and expected output.

Orchestrate transcript-to-video composition for this Remotion/Hyperframes vlog system. Use when analyzing an input recording or transcript, splitting it into shots, defining the global visual spec, deciding which assets can be generated in parallel, and producing composer artifacts for downstream shot, motion, presenter, generated-video, caption, Remotion, or QC skills.

Explore a website (public OR behind a login) and capture high-quality assets — retina stills and crisp motion video (.mp4; .webm opt-in) — into the asset library, by driving a REAL Chrome attached over CDP. Use when: (1) an agent needs UI footage/ stills from a page, especially an authenticated dashboard/app/console, (2) someone says "capture my app / grab the dashboard / record this flow", (3) you need UI-as-texture material (FloatingScreen / CaptureSurface / screen-rec) for a video. The agent EXPLORES first (it does not assume what's on the site), reports an inventory, then captures what the designer chooses. Never one-shot.

Viewer-first discipline for early-childhood Remotion lesson scenes. Before any choreography or JSX, the subagent must inhabit the kid's eye — measure how the smallest teaching mark and the smallest label actually render at the composition size, declare disjoint visual zones, refuse decoration. Pairs with visual-discipline (contract mechanics) and early-childhood-visual-taste (color/tone).

Use when writing per-cue teacher narration and captions for a Remotion lesson. The narration is COMMENTARY ON THE VISUAL — Wave 2a's per-cue motion budget is the input, and you write narration to fit each cue's budget. No invented hold timings.

Concrete visual discipline for Remotion lesson scenes — Visual Contract before choreography, one-metaphor rule, container earns existence, occupancy budget, semantic groups dominate visual groups, render-and-self-critique loop, iteration economy. Pairs with kids-eye (viewer-first) and early-childhood-visual-taste (color/tone).

Compose the Remotion lesson scene from approved upstream artifacts (Visual Contract, audio-captions intent, ASR-aligned cue boundaries, sketch-overlay schedule). Wave 4 of the lesson pipeline. NEVER hardcodes frame numbers; every timing derives from cue boundaries.

Visual taste — palette, tone, motion vocabulary — for early-childhood Remotion math lessons. Companion to kids-eye (viewer-first) and visual-discipline (Contract mechanics). Use during Wave 2 visual-design to set the lesson's visual language AFTER the kids-eye measurement block and BEFORE the Visual Contract.

Specify teacher-mark overlays (Excalidraw-style hand-drawn ink) for a Remotion lesson scene. Wave 4 (parallel with composer). Marks are specified in CUE-RELATIVE frames, never master-timeline absolutes. Restraint is the rule.

Wave 1 — turn pedagogy.md into the cue spine for ANY lesson (math, language/L2, …): cue IDs in order, per-cue narration-beat INTENT (no copy), and required visuals (real component vocabulary). This is where the pedagogy's reinforcement rhythm becomes an actual sequence of cues. NO durations, NO frames, NO code.

Wave 3b — scan the lesson's TEACHING demands against the capability catalog, REUSE existing primitives by default, and ship a new prop-driven primitive ONLY when a gap is explicitly named. Owns primitive aesthetic quality (verified via test stills) and the topic-intro card layout. Lesson-agnostic — never bakes a topic, value, or string into a primitive.

Turn your daily activity into authentic social media posts across X, LinkedIn, and Reddit. Use when the user says '2x', '2x now', 'set up 2x', 'post to x/linkedin/reddit', or wants help turning their work into social media content.

Collects activity from configured sources, summarizes each independently, writes a local session index.

Generates a draft for ONE platform. Called once per platform by the orchestrator. Writes to local file — sync daemon handles cloud.

Posts content to LinkedIn via browser automation. Reads local draft, posts, calls publish-draft.

Posts or replies on Reddit via browser automation. Reads local draft, posts, calls publish-draft.

Posts content to X/Twitter via browser automation. Reads local draft, posts, calls publish-draft.

Onboarding wizard for the 2X skill. Configures platforms, data sources, browser logins, and cron schedule.

Pi Flow — author, enhance, and run structured filesystem-coordinated workflows (a DAG of producer/verify nodes) as a fleet of efficient pi agents driven by non-Claude coding-plan models, with Claude Code as the single console. This is the plugin OVERVIEW/router; the work lives in three skills — piflow-init (create), piflow-enhance (improve), piflow-start (run). Source of truth is a structured workflow TEMPLATE; the `@piflow/core` SDK loads it and runs one `pi` per node.

Take any Claude Code Workflow (a `.claude/workflows/*.js` script that uses agent()/parallel()/ pipeline()/phase()) and run the IDENTICAL pipeline efficiently on a fleet of pi agents (pi.dev / earendil-works/pi) driven by non-Claude coding-plan models — with Claude Code as the single console and monitor. Use when someone wants to run a proven Workflow at lower cost / at scale, "run my workflow on pi", "run this on a non-Claude model", "pi-runner", "offload the workflow to more efficient agents", or to stand up the pi-runner harness in a new repo. Ships copy-paste templates (extract.mjs, run.mjs, provider extension, .env) so any project can adopt it.

Pi Flow · INIT — create a structured workflow (a DAG of producer/verify nodes coordinating through the filesystem) and stand it up to run as a fleet of efficient pi agents (pi.dev / earendil-works/pi) driven by non-Claude coding-plan models, with Claude Code as the single console. The source of truth is a structured workflow TEMPLATE (`.piflow/<wf>/template/`); the `@piflow/core` SDK loads it into a WorkflowSpec and runs it one `pi` per node. INIT triages your starting point — PORT an existing Claude `.js`, IMPORT another engine's workflow (n8n/YAML/JSON), or COMPOSE fresh — then builds the template and the per-repo runner. Use to "create/author a pi-flow workflow", "stand up the runner in a repo", "port my Claude workflow to pi", "import an n8n workflow", "run my workflow on a non-Claude model", "pi-runner". To RUN/monitor an existing workflow use piflow-start; to IMPROVE one use piflow-enhance.

Pi Flow · START — run & monitor an already-created pi-flow workflow on the pi fleet via the SDK CLI, with Claude Code as the single console. LOAD THIS SKILL BEFORE running ANY piflow/pi command — it pins the canonical invocation: the npm-linked global `piflow run <templateDir>` bin (NOT `node …/dist/cli.js` nor `pi-runner/run.mjs`, both non-canonical) with `--provider <gw> --thinking low --sandbox local` + `--from`/`--until`. Do NOT reconstruct the command from memory. Triggers — load on ANY of: "run / kick off / start / resume my piflow workflow", "do a live run on pi", "run game-omni on pi", "companion-mode run", "monitor / follow / poll a run", "diagnose a stalled / never-wrote / blocked node", or the words "piflow" / "pi-runner" / "pi fleet" / "pi run" appearing at all. The run is ALWAYS: pull the next prompt from the bank → dry-run (free) → live background → poll. To CREATE or PORT the template first use piflow-init; to IMPROVE a node/the chain use piflow-enhance.

Pi Flow · ENHANCE — improve an existing, running pi-flow workflow the disciplined way: turn a spotted flaw, a recurring finding, or human feedback into ONE atomic, generalizing change via capture→route→edit→verify→ approve→commit, never a one-off hack. Owns the criteria fixture (the per-node quality bar) and Companion-Mode judging. Use to "improve a wave/node", "fix a recurring failure in the pipeline", "the generated output is wrong — fix the system not the case", "edit the skill vs edit the chain". To CREATE a workflow use piflow-init; to RUN one use piflow-start. STATUS — STUB: the canonical method is the hermes-skill-system skill; this routes to it and pins the piflow-specific precedence.

Build a premium, dark, "Linear/Vercel/daytona"-grade SaaS or dev-tool frontend by composing from a BOUNDED MENU of vetted choices — a few locked-in premium picks per layer (tokens, type, layout, background effects, motion/scroll, component idioms, particles, cursor, kinetic text, optional 3D) so that any recomposition stays in-scope and premium and never drifts into generic. Use when someone wants to make a landing page / marketing site / product hero "feel premium / cool / expensive", replicate the dark dev-tool aesthetic, pick the right animation / shader / particle / scroll library, or stand up the whole stack. Triggers: "make it look premium", "dark SaaS landing page", "Linear/Vercel vibe", "which animation library", "premium hero", "particle background", "the entire stack", "replicate this site's feel".

当用户要求'发起审批'、'查看审批'、'催办审批'、'请假'、'报销'、'采购申请'，或提到钉钉OA审批相关操作时使用此技能。管理钉钉审批流程：发起审批实例、查询审批状态、获取审批列表、催办超时审批。

当用户提到'考勤'、'打卡'、'迟到'、'早退'、'补卡'、'请假'、'出勤'、'缺勤'、'考勤报表'、'考勤异常'时使用此技能。查询钉钉考勤打卡记录、考勤结果、排班信息，识别异常并生成汇总报告。

当用户提到'日历'、'日程'、'会议'、'约会'、'日报'、'周报'、'待办'、'任务'、'todo'，或要求生成工作汇报、查看本周安排时使用此技能。管理钉钉日历事件和待办任务，辅助自动生成日报周报。

当用户提到'微信客服'、'客服消息'、'客户咨询'、'智能客服'、'客服接待'、'转人工'、'客服账号'，或需要通过企业微信管理微信客服会话时使用此技能。管理微信客服账号、收发客服消息、分配会话、处理客户咨询。

当用户提到'客户'、'外部联系人'、'客户标签'、'跟进'、'销售'、'CRM'、'客户群'、'联系我'、'渠道活码'，或需要管理企业微信中的客户关系时使用此技能。查询客户详情、管理客户标签、跟踪跟进记录、管理客户群。

The out-of-band "dreaming" pass that keeps the OKF memory bundle small, fresh, and non-contradictory. Run on a schedule, at session spin-down, or just before compaction - NEVER on the hot path of an active task. Triggers on "consolidate memory", "the index is getting long", "memory feels stale", "dream", end-of-session cleanup.

Recall the right past decision, fact, or reason from the OKF memory bundle + git history BEFORE acting. Use when about to make a decision that may already be settled, when you need the reason behind an existing choice, when an error may have a known fix, or when starting work in an unfamiliar area. Triggers on "have we decided", "why is X this way", "did we hit this before", "what's our convention for".

启动Chrome DevTools mcp服务器并加载到Claude Code

Analyze and replicate website UI/animations. Use when asked to clone, replicate, or analyze a website's visual implementation.

Human-like mouse movement patterns. Use when automating browser interactions to avoid bot detection.

Reddit writing conventions and content guidelines. Use when creating posts or comments for Reddit.

启动 Telegram Webhook 服务器（主服务器或项目服务器）

每当有新的swift文件 自动更新 .xcodeproj