Coding & Dev Tools

VR/AR development principles. Comfort, interaction, performance requirements.

2D game development principles. Sprites, tilemaps, physics, camera.

PC and console game development principles. Engine selection, platform features, optimization strategies.

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

Mobile game development principles. Touch input, battery, performance, app stores.

Use when triaging a study before any writing — stress-tests whether it clears Cell's bar (a complete, mechanistic, hypothesis-driven story with multiple converging lines of evidence) or belongs at a sibling. Use this first to decide Cell vs Molecular Cell vs Cell Reports vs Cell Reports Medicine before investing in framing or figures.

Use this first, before any writing, to stress-test whether a clinical study clears NEJM's bar — practice-changing clinical impact, methodological rigor, and generalizability. Decides NEJM vs Lancet/JAMA vs a specialty journal.

Use to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.

Use to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.

Use before any writing to stress-test whether a result clears Science's (AAAS) desk-reject filter — broad significance and general interest across disciplines. Decides Science vs Science Advances vs a specialist journal before you invest in prose.

Use to build Science's data, code, and materials availability — mandatory deposition in approved repositories, accession numbers, a compliant data-availability statement, and materials/reagent sharing.

Use to write Cell's Summary — a single unstructured paragraph of ≤ ~150 words that conveys the complete story, the mechanism, and the broad significance, quantified and readable by a general life-scientist. Late-stage polish.

Use to structure a Cell Article and hold its length — Summary, Introduction, Results, Discussion, STAR Methods, figure legends, references — with main-text length and display-item budgets, and Results subheadings driving the single arc.

Use when scoping a project and before any writing, to stress-test whether a study clears The Lancet's bar — clinically or public-health important, globally relevant, and likely to change practice or policy, often with an equity lens. Decides The Lancet vs a Lancet family title vs another general medical journal.

Use to structure a PNAS main text and hold its length — Title, Significance Statement, Abstract, Introduction, Results, Discussion, in-text Materials and Methods, references — and to choose the required Classification (Biological/Physical/Social Sciences + minor subject) and keywords at submission.

Use when auditing an ACL submission before an ACL Rolling Review cycle deadline, covering long/short paper page budgets, the mandatory Limitations section, Responsible NLP checklist, anonymized PDFs and supplements, preprint declarations, dual-submission rules, resubmission linking, and ARR desk-reject triggers on OpenReview.

Use when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.

Use after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.

Use after NEJM reviews arrive — often including a dedicated statistical reviewer and an editor letter — to triage the decision, answer statistical comments rigorously, and draft a point-by-point response that quotes each comment, the response, and the revised manuscript text. Do not run before the main text is actually revised.

Use to write the PNAS abstract — a single self-contained paragraph of ~250 words, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the Significance Statement (why-it-matters, for everyone). Late-stage polish.

处理和分析用户上传的文件引用，提取关键信息并提供应用建议。适用于解析@符号引用、自然语言引用、提取短剧策划相关信息

智能截断文本，保持内容的完整性和语义连贯性。适用于长文本预处理、确保文本不超过指定长度限制

创作竖屏短剧剧本，包括宏观建构、剧本创作、精准优化、创意发想。适用于从零开始创作短剧、优化现有剧本、设计故事大纲和悬念钩子

梳理IP网络信息并进行多维度评估打分。适用于评估小说、剧本等IP的改编价值、分析市场潜力和创新属性

调用generateTreeMind工具创建可视化思维导图，返回图片URL和编辑链接。适用于故事结构可视化、情节关系图谱展示

分析故事文本，提炼主要情节点并分析戏剧功能。适用于分析小说、剧本大纲、故事梗概等文本，识别关键转折点和情感节点

梳理故事主线，提炼并按发展阶段排列主要情节点。适用于快速掌握故事结构、制作大纲及剧本改编结构梳理

严格细致判断与评分故事文本，从市场潜力、创新属性、内容亮点维度分析质量。适用于小说初筛选、多维度评估打分

智能截断文本，保持内容完整性。适用于小说文本预处理、确保文本不超过指定长度限制

分析已播剧集，包括信息获取、拉片分析、五元素分析及联网搜索。适用于深度分析剧集创作技法、学习情节设计

专业评估故事大纲，从市场潜力、创新属性、内容亮点维度判断评分。适用于故事大纲质量评估、IP改编潜力判断、项目立项决策

整合智能体输出结果为结构化最终输出，支持多种格式。适用于整合分析报告、生成结构化报告

整合多情点分析结果为综合报告，通过去重、分类、排序、总结生成高质量分析。适用于整合多分析源、生成统一报告

分析故事情节点，识别关键情节与转折点。适用于深度分析情节结构、评估情节发展有效性

基于故事文本分析人物特征，生成详细的人物小传。适用于深度理解故事人物设定、为演员塑造角色提供参考、为剧本创作建立人物档案

Decide whether Git submodules are the right boundary for external dependencies, then execute the appropriate workflow: add and pin, bootstrap recursively, sync to a recorded commit, advance a tracked branch, edit inside a submodule without detached-HEAD surprises, remove cleanly, or configure CI checkout constraints.