群众路线：从持有真实情况的多方（用户、使用者、代码库、日志、运行结果）收集分散意见，系统化为方案，再带回去对齐与检验，循环改进。当多方意见分歧、需要汇总零散反馈、方案要拿回给真实使用者确认、或你发觉自己在闭门造车时触发；信息源单一且完整、处于执行阶段时不触发。 English: Mass line. Collect scattered input from everyone who holds ground truth (users, operators, codebase, logs, runtime results), synthesize it into a coherent plan, take it back for alignment and validation, and iterate. Trigger when inputs conflict, feedback must be consolidated, a plan needs sign-off from real users, or you sense you are designing in isolation; skip when there is a single complete source and the work is pure execution.

调查研究：在下判断、做决策、给建议之前，先用第一手材料弄清现状，产出「事实 / 推断 / 未知」三栏调查结论。当上下文不完整、证据薄弱、领域陌生、用户说"先别动手"、或你发现自己在凭印象作答时触发；已充分调查后的执行阶段不要重复触发。 English: Investigate before judging. Gather firsthand facts and produce a fact / inference / unknown ledger before any recommendation. Trigger when context is incomplete, evidence is thin, the domain is unfamiliar, the user says "look first", or you notice yourself answering from impression; skip when investigation is already done and the task is pure execution.

AI-powered adversarial UI testing via the browse CLI. Analyzes git diffs to test only what changed, or explores the full app to find bugs. Tests functional correctness, accessibility, responsive layout, and UX heuristics. Use when the user asks to test UI changes, QA a pull request, audit accessibility, or run exploratory testing. Supports local browser (localhost) and remote Browserbase (deployed sites).

Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.

Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcp__qmd__query, mcp__qmd__get, mcp__qmd__multi_get, mcp__qmd__status — if they appear in your tool menu, use them first; (2) CLI `qmd --index <name> ...` as fallback; (3) Grep/Glob only when QMD is not installed. Trigger proactively for past decisions, incidents, people, meetings, architecture, patterns, or any vault content — and after creating/editing notes to check for duplicates and related content.

How extensions render as widgets inside other apps via named UI slots — the framework's optional extension system. Use when an extension-enabled app needs to wire an ExtensionSlot or make an existing one-off custom block installable into a slot.

Open or create a repo-native visual documentation workspace backed by local Plan MDX files. Use when the user asks to visualize a repository, create durable visual docs for APIs/components/models/flows, launch a visual repo viewer, review repo docs like a visual IDE, or collect Plan comments that should become coding-agent changes.

Audit whether a multi-agent setup earns its coordination cost — use before adding an agent, or when a workflow feels slow or agents agree without adding signal

Use Ontoly's deterministic Software Graph and MCP capabilities for architecture review, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source-file search.

Use when the user asks about unused code, cleanup, deleting files or exports, refactoring old areas, reducing bundle size, code hygiene, technical debt, or maintenance in a Repowise-indexed repository.

This skill should be used when drafting GitHub issues for the Positron repository. It provides workflows for searching duplicates, selecting appropriate labels, gathering complete context through questioning, and writing terse, fluff-free issues that precisely describe what is needed or wrong. The skill prepares issues for manual submission by the user. Use this skill when the user asks to draft or prepare an issue for Positron.

Investor-first workflow for drafting a structured deal memo, IC memo, partnership memo, or acquisition-style brief from existing diligence materials. Use for prompts like "draft a deal memo", "turn this diligence packet into a memo", or "write the IC draft". Best when you already have research findings, model review notes, meeting outputs, and supporting documents. Optional Open Brain search and capture can pull prior context and store the final memo or recommendation summary.

Submit compact Reactome ContentService requests for pathway, event, participant, search, and diagram-related data. Use when a user wants concise Reactome summaries

Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.

Build voice call logic using TwiML (Twilio Markup Language). Covers the core verbs (Say, Play, Gather, Dial, Record, Conference), generating TwiML with Python and Node.js SDKs, and a complete inbound call IVR example. Use this skill to define call behavior for inbound or outbound calls.

Create, manage, and send message templates using Twilio's Content API. Covers template creation for WhatsApp, SMS, RCS, and MMS; variable usage; WhatsApp Meta approval; and sending templates via ContentSid. Use this skill when building structured messages that require pre-approval or consistent formatting across channels.

Implement and review macOS SwiftUI Liquid Glass UI. Use when adopting system glass, removing conflicting custom chrome, or building glass surfaces.

Choose and apply automatic layout strategies for node-link diagrams and connected-node visuals. Use when the user asks how to auto-arrange nodes, reduce line crossings, route edges, avoid overlaps, stabilize layout, or choose graph-layout algorithms for network diagrams, dependency graphs, database schema diagrams, ERDs, state machines, decision trees, flow diagrams, box-and-line editors, or other line-connected nodes.

Test data visualizations and dashboards. Use when the user needs chart or diagram test strategy, screenshot or image diff testing, visual regression, mocked or synthetic chart data, component or unit tests, E2E dashboard QA, interactive UML-like diagram verification, scroll-driven story verification, export verification, or guidance on avoiding brittle over-testing.

Operate and troubleshoot CircleCI using the CircleCI CLI. Use when users ask to authenticate CLI access, inspect pipeline/workflow/job status, validate configuration locally, rerun pipelines/jobs, trigger pipelines, or gather actionable diagnostics from CLI outputs.