「final」の検索結果

把多页 HTML 报告(主页 + N 子页 + PNG 资产)合并为单一独立 HTML / PDF / XLSX 三件交付物。 Use when finalizing a disease market sizing report and need shareable deliverables — single-file HTML for email/IM(零依赖,双击浏览器开), optional PDF for print/archive, XLSX for data export. 领域无关、跨疾病通用。 下游 of disease-market-sizing-html-template;上游 of email/IM/print 分发。 Use proactively whenever the user says "做交付物" / "生成 PDF" / "导 Excel" / "合并单文件 HTML"。

日本語の概要は準備中です。原文の説明を表示しています。

Prepare deployment configs, final checks, and pre-launch readiness artifacts for production release.

日本語の概要は準備中です。原文の説明を表示しています。

Run authorized Xiaohongshu browser workflows for login checks, creator preview fill, publish blockers, final posting, search, export, or approved engagement. Prefer native signed-in Chrome; keep Python/CDP for deterministic batch fallback.

日本語の概要は準備中です。原文の説明を表示しています。

GStack ship method for final landing, PR, changelog, release, and deploy readiness checklists when the user explicitly wants to ship.

日本語の概要は準備中です。原文の説明を表示しています。

Use when splitting content work between a raw drafting model/window, an editor-in-chief, and the user's final taste review. It keeps prompts loose enough for judgment while preserving facts, account boundaries, and publish gates.

日本語の概要は準備中です。原文の説明を表示しています。

Draft and revise evidence-grounded academic manuscripts with adaptable author preferences. Use for section writing, implementing structural edits, claim calibration, citation-integrated prose, prose cleanup, standalone review excerpts, and LaTeX template migration. Use paper-review for critique or author responses, and paper-figures-tables for final visual artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Review an author's manuscript, its argument and paragraph structure, analyze reviewer comments, draft rebuttals, and verify revisions. Use for self-review, structural edit plans, simulated reviewer objections, author responses, revision closure, and submission-readiness assessment. Formal assigned peer review is outside this skill; manuscript edits and final figures/tables use their owning skills.

日本語の概要は準備中です。原文の説明を表示しています。

Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.

日本語の概要は準備中です。原文の説明を表示しています。

intake 全 JSON を統合したいとき、intake.md と intake.json を Jinja2 で render して quality_gate と cross_check を通したいときに使う。

業務委託契約書の下書きを確認後にPDF発行・確定したいとき、ユーザーの明示指示でdraftをcompletedへ遷移したいときに使う。

Audit a composer output against four hard checks before delivery — cite integrity, voice rules, word count, schema validity. Always invoked after the polisher (English) or humanizer-* (Arabic / Hebrew). Emits a VerificationReport Pydantic object; orchestrator branches on `overall_passed`. Target ≥0.9 score per run. Triggers automatically as the final composer sub-agent; not user-facing.

日本語の概要は準備中です。原文の説明を表示しています。

Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

日本語の概要は準備中です。原文の説明を表示しています。

Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

日本語の概要は準備中です。原文の説明を表示しています。

Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits. Skip for Q&A or trivial edits.

日本語の概要は準備中です。原文の説明を表示しています。

Companion to atlas-contract. Auto-invoked by its Final Audit on caught drift; also use after Post Reviews or user requests to record a mistake. Distills drift into WHEN/DON'T/INSTEAD clauses, writes to Atlas.md after confirmation.

日本語の概要は準備中です。原文の説明を表示しています。

ADHD-friendly output shaping for subagent responses. Lead with the next action, number multi-step tasks, end with one concrete next step, suppress tangents, restate state across turns, give specific time estimates, make wins visible, matter-of-fact errors, cap visible lists to 5, no preamble or closers. Loaded by genin, jonin, anbu, tokubetsu-jonin, and chunin when shaping final responses.

日本語の概要は準備中です。原文の説明を表示しています。

Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.

日本語の概要は準備中です。原文の説明を表示しています。

Verify a tested web agent's real behavior from its recorded Pi or Codex session and selected screenshots before scoring. The judge prompt provides absolute artifact paths; use targeted queries to compare actual outputs, errors, and the final answer with the recorded behavior, then return only the verdict JSON. Only for ego-bench judging—never to drive a browser or rerun the agent.

日本語の概要は準備中です。原文の説明を表示しています。

Run a targeted fresh-eyes blunder pass over code, specs, plans, reviews, closure gates, or skill edits. Use when asked to reread with fresh eyes, find obvious bugs, catch mistakes/oversights/omissions, check for embarrassing misses, or do a second independent pass before closure. Use it as the final falsification/check pass for another workflow, not as a substitute for implementation or verification.

日本語の概要は準備中です。原文の説明を表示しています。

Render a Template + data + Style into a final artifact in one of HTML, PDF, PNG, SVG or PPTX. Use whenever the user asks for a concrete deliverable like "make me a poster", "render a card", "give me a one-pager".

日本語の概要は準備中です。原文の説明を表示しています。

Create a study cheatsheet by extracting and synthesizing key concepts from lecture materials, homework, and past exams. Use this skill whenever a user asks for help making a cheatsheet, study sheet, formula sheet, exam reference sheet, or "one-pager" — especially when they upload lecture slides (PDF/PPTX/DOCX), problem sets, past exams, or scanned/handwritten notes. Trigger this even for casual phrasings like "help me prep for my final," "summarize my course materials into something I can bring to the exam," or "make me a study reference from these slides and homeworks." Tuned for math/science (formulas, proofs, theorems) and CS/engineering (code, algorithms). Processes one file at a time and persists intermediate summaries to disk to avoid blowing past the context window on large courses.

日本語の概要は準備中です。原文の説明を表示しています。

Synthesized reference notes from three US Government vehicle-safety sources: NHTSA Cybersecurity Best Practices for the Safety of Modern Vehicles (updated 2022, final), NHTSA Automated Driving Systems 2.0: A Vision for Safety (2017), and a 16-section selection of 49 CFR Part 571 (FMVSS) pinned at eCFR versioner date 2025-01-01. Use for voluntary vehicle cybersecurity practices, the ADS 2.0 twelve priority safety design elements, and FMVSS occupant protection, brakes/stability/lighting, and fuel/EV integrity requirements. Not ISO 26262, not ASPICE, not ISO/SAE 21434, not UNECE R155/R156, not SAE J3016, and not the full Part 571; the FMVSS material is a selection of vehicle-level minimum performance standards, not a process standard.

日本語の概要は準備中です。原文の説明を表示しています。

Barrido sistemático de errores con un valor objetivo escalado a la base de código, escalado por duplicación, seguimiento de áreas y verificación final. Se utiliza al ejecutar /bugsweep o cuando el usuario solicita una revisión sistemática de errores.

日本語の概要は準備中です。原文の説明を表示しています。

Systematic bug sweep with a codebase-scaled target value, doubling escalation, area tracking, and final verification. Use on /bugsweep or whenever the user requests a systematic bug pass.

日本語の概要は準備中です。原文の説明を表示しています。