「english」の検索結果

Writing anything the fleet produces for a person to read: a README, a changelog, a commit message, a review note, a task file, a docblock, a user-facing string. Carries the WordPress Documentation Style Guide rules in `references/`. Use before drafting or rewriting prose, then run the pass that takes the machine out: `humanizer` for English, `humaniseur-fr` for French.

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

First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English.

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

Generate custom quality checklists for validating requirements completeness and clarity. Use to create unit tests for English that ensure spec quality before implementation.

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

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

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

Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find bloat", "what can I delete", /ponytail-audit.

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

This skill should be used when creating cost estimates and quotations for software development projects. Use this skill when you have an RFQ (Request for Quotation), project requirements, or a project description and need to create a comprehensive estimate with WBS, effort calculations, cost breakdowns, and ROI analysis. Supports Japanese (default) and English, with systematic work breakdown, effort estimation, and markdown-formatted estimate documents.

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

This skill should be used when creating RFQ (Request for Quotation) documents for software development projects to send to vendors. Use this skill when you have received vague requirements from clients and need to structure them into clear, comprehensive RFQs that enable vendors to provide accurate estimates. Supports Japanese (default) and English, with systematic requirements elicitation, clarification, and markdown-formatted output.

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

Prepare comprehensive meeting assets including agendas, reference materials, decision logs, and action items. Use when user says "prepare meeting", "create agenda", "meeting prep", "会議準備", or needs bilingual (Japanese/English) meeting documentation for cross-regional teams. Triggers include requests for decision log templates, action item tracking, or compiling reference materials from project estimates and specs.

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

This skill should be used when creating bug/defect reports during system testing. Use this skill when you discover a bug, need to document test failures, or want to create comprehensive bug tickets with proper reproduction steps, severity assessment, and environment details. Guides users through interactive questioning to gather all necessary information and generates professional bug ticket documents in Markdown format. Supports Japanese (default) and English.

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

Transform client hearing sheets and meeting notes into structured requirements documents. Use when converting raw hearing data (Japanese/English) into formal requirements, generating traceability matrices, identifying gaps/ambiguities, and mapping requirements to WBS items. Triggers include "hearing to requirements", "meeting notes to specs", "requirements traceability", "gap analysis for requirements", or requests involving hearing sheet analysis.

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

Write, validate, and (optionally) execute an NQL query against a Narrative dataset. Drafts the query from the user's question, runs `narrative_nql_validate` until it compiles, explains the query in plain English, and only runs it on explicit approval (or when invoked with `--run`). Use when: "write an NQL query for X", "query this dataset", "validate this NQL", "run NQL against dataset <id>", "how many rows match Y", "show me the top N records from <dataset>". (narrative-common)

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

Review translated documentation for content fidelity — detect injected, off-topic, or unauthorized content by comparing against the English source. Use when reviewing translation PRs or translated docs.

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

Recast a supplied everyday photo as a witty illustrated product instruction sheet with a large Chinese title and concise English annotations. Use for 日常说明书、宠物使用说明、生活物品冷幽默说明图 or a fictional everyday object manual poster.

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

Build full-paper Chinese-English side-by-side, figure/table-aware, source-grounded Markdown readers for journal or conference papers from PDF, DOI, arXiv, publisher HTML, or pasted text. Use whenever the user asks to translate or read a paper, make 中英文对照/原文对照/全文翻译解读, extract figures or tables into the right positions, preserve figure/table placement near relevant prose, or keep exact source anchors for every block. This skill must not degrade into a summary-only output unless the user explicitly asks for a summary. Also trigger on general paper-reading and translation requests even without the word "Nature", such as reading/translating an academic paper, literature reading, understanding a paper, and Chinese phrasings like 读论文、精读论文、论文翻译、文献翻译、文献阅读、学术阅读、帮我读这篇文章、翻译这篇paper.

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

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

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

How to add a page to the tdmcp VitePress docs site so it builds, gets a clean URL, and lands in the right nav — including the repo's partial-translation convention (only the artist guide is EN+PT; reference/legal pages are English). Use when authoring the privacy policy or any new docs page for tdmcp.

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

Hard-edged writing style contract for timeless, forceful English prose without AI tics

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

Use for any code, documentation, config, dependency, test, review, or maintenance task in the Nauthilus repository that must follow AGENTS.md, POLICY.md, focused reproducer-first debugging, strict DRY/OOP boundaries, English comments, GOEXPERIMENT=runtimesecret test discipline, Makefile-driven validation, prompt-sync checks, and dirty-tree preservation.

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

Shape FriendlyBet Pundit content, bilingual product copy, community voice, share-card copy, social moments, video briefs, Hebrew/English wording, and group-chat friendly communication. Use when a task touches copy, Pundit tone, social videos, share text, community loops, or public-facing FriendlyBet voice.

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

Create or refresh FriendlyBet Story of the World Cup image assets and app overlays. Use when generating new 9:16 World Cup story artwork, replacing story-assets PNGs, writing image-generation prompts, checking real player shirt numbers, placing Hebrew/English story captions, or validating that story text does not cover player faces or get cropped in WhatsApp previews.

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

Review or design FriendlyBet user experience, visual direction, mobile-first flows, premium sports interface, Hebrew/English copy fit, RTL behavior, accessibility, interaction patterns, and product UI polish. Use when a task touches screens, flows, layout, visual hierarchy, onboarding, prediction UX, share UX, or design quality.

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

Multi-source research synthesizer. Takes a question, runs 3-5 parallel web searches with varied phrasings, deduplicates, and returns a cited, concise answer. For Hebrew questions, searches in both Hebrew and English. Output is always under ~400 words.

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

Use when the user wants to humanize text, make writing sound less like AI, or rewrite content to feel more natural. Triggers on "humanize", "make it sound natural", "too robotic", "sounds like AI", or similar. Works in Hebrew and English. Always output only the rewritten text — no explanations.

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

Transcribe WhatsApp voice messages using local Whisper CLI. Use when: owner or contact sends an audio/ogg voice message. Combines Whisper transcription + CRM update + task creation. Works offline for short clips, uses OpenAI API for long clips. Hebrew and English supported.

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