「writing」の検索結果

Use when authoring or rewriting a roadmap in agents/roadmaps/ — phases, goal, acceptance criteria, council notes; fires even on 'write a plan for X' / 'draft a roadmap'.

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

Use when creating or rewriting a README for a reusable package or library. Focus on installability, minimal usage example, compatibility, and developer onboarding.

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

Use when creating, rewriting, or significantly improving a README based on the actual repository structure, commands, and intended audience.

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

When writing a commit message, branch name or squash title — measure the repo's own convention first, Conventional Commits as fallback — even on a bare 'commit this'.

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

Rewrite text that did not land, with clear context, plain language, and my writing preferences.

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

Project-level WeChat article drafting workflow for turning source materials, repo intakes, product notes, screenshots, or existing markdown into a publishable Chinese公众号 draft. Use for writing, rewriting, evidence-gating, title options, platform adaptation, and image planning before optional publishing.

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

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

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

Use this skill when a user asks to polish, rewrite, humanize, de-AI, localize, or oralize Chinese writing, including short-video scripts, articles, social posts, speeches, newsletters, and personal-IP content. The skill diagnoses “AI味”, preserves the user's meaning, adapts to optional style samples, replaces translation-like phrasing with natural Chinese expression, and outputs a polished version plus concise revision notes.

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

Use when the user wants text to sound more human, says writing sounds "too AI" or "too ChatGPT," asks to humanize or rewrite a draft to feel natural, or shares content wanting it to feel authentic and less robotic. Also applies to LinkedIn posts, blog drafts, or emails where the user wants a more genuine voice.

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

Analyze, design, write, revise, translate, and review empirical or technical research papers through an evidence-bounded dialectical workflow. Use when Codex must develop a research question, integrate reference papers with a user's ideas, build phenomenon-mechanism-conditions reasoning, design methods or experiments, restructure or edit a manuscript, translate Chinese academic text into restrained English, answer reviewers, or run multi-round peer-review convergence without fabricating evidence.

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

Writing quality guidelines, formatting conventions, and styling constraints for documentation. Trigger when: - Writing, editing, or auditing documentation files, READMEs, markdown files, or guides. - Modifying files with suffixes like: *.md, *.qmd, *.txt, *.rst. - Prompt contains keywords: doc, documentation, spelling, grammar, headers, links, table alignment, Divio, tone, voice, clarity.

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

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.

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

Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.

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

Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.

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

Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.

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

Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.

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

Audit and rewrite content to remove 21 categories of AI writing patterns with a 43-entry replacement table

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

Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing ...

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

Standard Operating Procedures for technical writing, README creation, API specifications, runbooks, and documentation updates.

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

Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and MDC component usage. Overrides brevity rules for proper grammar. Use nuxt-content for MDC syntax, nuxt-ui for component props.

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

Write new English text, or rewrite existing text, in ASD-STE100 Simplified Technical English. Use for STE, simple technical English, ASD-STE100, or 80% STE, for writing or rewriting procedures, manuals, SOPs, runbooks, and release notes.

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

Internal audit support skill aligned with IIA (Institute of Internal Auditors) International Standards. Provides risk-based audit planning, audit program development, workpaper documentation, finding development (Condition/Criteria/Cause/Effect), and Corrective Action Request (CAR) tracking. Use when: planning annual/quarterly audits, creating risk assessment matrices, developing audit programs and test procedures, documenting audit workpapers, writing audit findings and reports, tracking corrective actions and follow-ups, preparing for external audits (SOX, ISO). Triggers: "internal audit", "audit plan", "audit program", "audit workpaper", "audit finding", "risk assessment", "CAR tracking", "corrective action", "IIA Standards", "COSO framework", "監査計画", "監査プログラム", "監査調書", "是正措置", "リスク評価".

Guidance on writing high-quality requirements: the requirement quality characteristics and the EARS (Easy Approach to Requirements Syntax) patterns — ubiquitous, event-driven, state-driven, optional-feature, unwanted-behaviour — for unambiguous, singular, verifiable requirements, plus defect/anti-pattern review and verification & traceability. Use when authoring or reviewing requirements. Original synthesis citing EARS (Mavin et al.) and NASA public-domain guidance; not a reproduction of ISO/IEC/IEEE 29148 or the EARS paper.

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

Search academic references for a manuscript and export them to a verified refs CSV, then optionally hand off to cec-sheet. Uses Codex CLI as the search driver, but Codex calls a bundled deterministic PubMed tool (scripts/pubmed_search.py) instead of writing its own E-utilities code — bibliography is fetched live from PubMed so PMIDs are never fabricated. Triggers: "論文検索", "文献検索", "文脈検索", "コンテキスト検索", "原稿の引用を探して", "refs.csv", "codex-refs", "/codex-refs".