「write」の検索結果

Professional content generation system with a GSD-style phased workflow, integrated SEO optimization (claude-seo), and anti-AI auditing (humanizer). USE THIS SKILL whenever the user asks to write, draft, create, generate, or produce ANY content — including blog posts, articles, LinkedIn posts, Facebook posts, Twitter/X tweets or threads, Instagram captions, email newsletters, email campaigns or sequences, landing pages, product pages, web pages, sales pages, sales funnels, case studies, testimonials, product descriptions, or SEO metadata. Also triggers on: "/writer:discuss", "/writer:plan", "/writer:execute", "/writer:verify", "/writer:ship", "/writer:next", "/writer:profile-create", "/writer:profile-view", "/writer:profile-edit", "/writer:status", "/writer:help", "/writer:update" — or any request to manage a writer profile or create marketing materials. ALWAYS use this skill even for quick, casual content requests like "write me a LinkedIn post about X" or "draft a tweet thread." The profile and phased workflow produce significantly better output than ad-hoc generation.

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

Professional content generation with phased workflow (discuss→plan→execute→verify→ship), SEO optimization, and anti-AI auditing. Multi-profile support for unlimited brands. USE for: blog posts, LinkedIn, Twitter/X, Facebook, Instagram, email newsletters, landing pages, sales pages, case studies, product descriptions, SEO metadata. COMMANDS: /writer:discuss, /writer:plan, /writer:execute, /writer:verify, /writer:ship, /writer:next, /writer:profile-create, /writer:profile-list, /writer:profile-use, /writer:profile-view, /writer:profile-edit, /writer:status, /writer:help ALWAYS use for content requests like "write me a LinkedIn post" or "draft a blog article."

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

How to use the Appwrite CLI well. Covers when to use appwrite.config.json vs `appwrite client`, pull/push vs one-shot service calls, type-safe SDK and model generation, query flags, CI auth, Cloud regional endpoints, function/site variables, and traps that `--help` will not mention. Does not catalog commands — run `appwrite <command> --help` for flags. Use whenever running `appwrite`, deploying or pulling functions/sites/tables, generating application code from a table schema, initializing or linking a project, scripting Appwrite, or when the user mentions the Appwrite CLI, appwrite.config.json, `appwrite generate`, `appwrite types`, or `appwrite client`.

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

Design and review custom WordPress URL rewrites: add_rewrite_rule, add_rewrite_tag, query_vars, CPT/taxonomy rewrite slugs, add_rewrite_endpoint, soft vs hard flushes, rewrite_rules cache behavior, and the rule that flush_rewrite_rules() must not run on every request. Use for custom pretty URLs, CPT permalink 404s, endpoint rewrites, and code containing flush_rewrite_rules or add_rewrite_rule.

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

Set up automatic keepalive for Appwrite free-tier projects to prevent them from being paused after 7 days of inactivity. Use when working in a codebase that uses Appwrite, when the developer mentions Appwrite free tier, project pausing, or keeping an Appwrite project alive, or when you detect Appwrite configuration (node-appwrite dependency, APPWRITE_ env vars, Appwrite SDK imports).

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

Use when reviewing a DataFusion Comet pull request that touches Iceberg writes, the split-operator write plan (IcebergWriteStrategy, IcebergWriteExec, IcebergCommitExec), the native Iceberg writer (CometIcebergWriteExec, iceberg_write.rs, iceberg_partition_path.rs), its eligibility gate (CometIcebergNativeWrite), or the iceberg-rust pin. Load alongside review-comet-pr.

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

Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal. Use this skill whenever the user wants to write an article, draft website copy, edit existing content for clarity or voice, write a blog post, or produce general editorial content. Triggers on write a blog post, draft an article, write copy for, edit this, rewrite this, write content, write a guide, draft a how-to, write web copy. Also triggers when content has been outlined and now needs to be written, or when existing content needs voice or clarity edits.

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

Use when the user wants to write text in a specific 16-minds (MBTI) personality's voice — articles, blog posts, essays, SNS投稿, replies, or rewriting existing AI-generated text to feel less AI-like. Triggers on Japanese phrases like 「ENFPで書いて」「INTJ風の記事」「人間っぽく書き直して」「AI臭抜いて」, English equivalents like "write as INFJ" / "humanize", or any 16-minds command with a `--write` / `--rewrite` flag. Personality (one of intj/intp/entj/entp/infj/infp/enfj/enfp/istj/isfj/estj/esfj/istp/isfp/estp/esfp) must be specified or inferable.

Delegate writing predictable code to the `code-write` command, which has a cheaper writer model write the target file directly so the generated code never enters your context. Use for tests, scaffolding, fixtures, boilerplate, or a new file that copies an existing pattern, and when the user says "code write", "生成を委譲", or "雛形を書かせて". Do NOT use for design decisions, changes to public contracts or shared modules, edits inside an existing file that needs judgment, or logic with subtle correctness requirements.

Use this skill when the user is building, running, or interpreting the doca/tools/gpunetio_ib_write_bw client+server benchmark — a CUDA kernel on the client posts RDMA WRITE work requests through the doca-gpunetio device-side surface to measure sustained GPU-driven WRITE bandwidth on a GPU+IB-device pair. Trigger even when the user does not explicitly mention "doca-gpunetio-ib-write-bw" or "GPUNetIO" — typical implicit phrasings include "measure WRITE BW when the GPU posts the WRs", "BW swings between runs on the same flags", "is the NIC saturated or am I CPU-bound on the CUDA kernel", "meson compile fails for the GPUNetIO bw tool", "nvidia_peermem isn't picking up my GPU buffer", or "GPU-initiated WRITE throughput vs CPU-initiated perftest". Refuse and route elsewhere for general doca-gpunetio library work, DOCA install, the GPU-initiated WRITE latency analog, the CPU-initiated upstream perftest, or application-level end-to-end throughput — those belong to other skills.

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

Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform. Each writer exports a function that accepts a config interface, creates directories (rules/, skills/, mcp configs), writes files with proper formatting and frontmatter, and returns string[] of written file paths. Use when adding platform support for a new agent, integrating a new code AI tool, or extending caliber to support new targets. Do NOT use for modifying existing writers, refactoring scoring logic, or changing how writers are invoked.

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

🇺🇸 GitHub README Writing System — Craft a README that converts visitors to stars in <3 seconds. Proven structure from AFFiNE's 0→60K star journey: tagline engineering, first-screen law, section-by-section copywriting guide, Claude Code integration section, anti-patterns, and a pre-publish checklist. Use when you need to write or rewrite a specific README file. 🇨🇳 GitHub README 写作系统 — 打造 3 秒内把访客转化为 star 的 README。来自 AFFiNE 0→60K star 实战：tagline 工程、首屏法则、逐节文案指南、Claude Code 集成板块、反模式、发布前自检清单。需要写或改一个具体 README 文件时使用。 🇯🇵 GitHub README 作成システム — 3秒以内にビジターをスターに変えるREADMEを作る。AFFiNE 0→60Kスター実績から: タグライン設計、ファーストスクリーン法則、セクション別ライティングガイド、Claude Codeインテグレーション、アンチパターン、公開前チェックリスト。 🇰🇷 GitHub README 작성 시스템 — 3초 안에 방문자를 스타로 전환하는 README 작성법. AFFiNE 0→60K 스타 실전: 태그라인 설계, 첫 화면 법칙, 섹션별 카피라이팅 가이드, Claude Code 통합 섹션, 안티패턴, 게시 전 체크리스트. Triggers: "write README" | "README template" | "GitHub README" | "project description" | "tagline" | "open source README" | "README structure" | "README review" | "fix README" | "rewrite README" | "README写作" | "写README" | "README模板" | "项目介绍" | "开源项目文案" | "改README" | "README检查" | "README 구조" | "README 작성" | "README 검토" | "READMEの書き方" | "READMEレビュー"

Windows アプリ開発 (DirectX / WinRT メディア) のグラフィックス・メディア API リファレンス。 Direct2D (ID2D1Factory, ID2D1DeviceContext, ID2D1Bitmap1, ID2D1Effect, ID2D1PathGeometry), DirectWrite (IDWriteFactory, IDWriteTextLayout, DWriteCore), Direct3D 11/12 (D3D11CreateDevice, DXGI SwapChain, HLSL, D3D12 PipelineState), Microsoft.UI.Composition (Compositor, Visual, ExpressionAnimation, InteractionTracker, MicaController), カメラ・画面キャプチャ (MediaCapture, MediaFrameReader, GraphicsCaptureSession, Windows Studio Effects)、音声・動画再生 (MediaPlayer, MediaPlaybackSession, AudioGraph, MediaTranscoder, AdaptiveMediaSource)。

Draft a full academic paper manuscript from analysis outputs, project spec, and lit review. Make sure to use this skill whenever the user wants to turn completed analysis into a written paper — not to run analysis or review existing writing. Triggers include: "write the paper", "draft the manuscript", "write up the results", "start the paper", "turn my results into a paper", "write the introduction", "draft the empirics section", "I have my results, now write the paper", "help me write this up", "write the abstract", or any request to produce academic prose from existing research outputs.

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

Scope a feature end to end and write an implementation spec under specs/ from an accepted proposal — current-system mapping, goals/non-goals, a Decision Log for one-way-door choices, a live Open Questions backlog, and a real migration + test plan. Read when asked to write a spec, scope this feature, turn this proposal into a spec, plan the implementation, or break this into tasks. Do NOT fire on frame a proposal or write the PRD (sibling frame-a-proposal — a PRD frames a change before it is accepted; this skill starts once one is), record a decision or write the ADR (record-a-decision), write a postmortem (write-a-postmortem), or review this design (review-a-design) — those are separate skills. Complements the platform open-knowledge skill; does not replace it.

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

Use this skill when the user is measuring GPU-kernel-initiated RDMA WRITE latency through doca-gpunetio — building and running the `gpunetio_ib_write_lat` client + server pair under `doca/tools/gpunetio_ib_write_lat/`, checking GPU-NIC pairing, reading the half-iter / full-iter / CUDA-side usec columns, characterizing median / p99 / jitter for a real-time control loop, picking GPUNetIO vs GPI vs CPU-initiated `perftest`, or weighing the latency-vs-batching trade-off. Trigger even without 'GPUNetIO' or 'ib_write_lat': 'GPU kernel RDMA latency benchmark', 'how fast can a CUDA kernel post a WRITE', 'p99 RDMA latency on H100 + ConnectX', 'kernel-launched WR tail latency', or 'compare GPU-init vs CPU-init perftest'. Route elsewhere for bandwidth runs (doca-gpunetio-ib-write-bw), the GPI surface (doca-gpi), library debugging (doca-gpunetio), or DOCA install.

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

Write, restructure, or review documentation — tutorials, how-to guides, reference pages, concept/explanation docs, API references, READMEs, changelogs, release notes, and troubleshooting guides. Distills documentation craft from Mintlify's guides (compiled from technical writers at Stripe, GitHub, Amplitude, and Anaconda), the Diátaxis framework (including the compass and per-type voice), the Google and Microsoft style guides, Every Page Is Page One, Write the Docs, and Docs for Developers: audience analysis, content-type selection, style and word-level rules, procedure writing, structure for humans and AI agents, code-example standards, page templates (templates.md), mechanical enforcement and llms.txt (mechanics.md), maintenance, and success metrics. Use this skill when the user asks to "write docs", "document this feature", "improve this page", "review these docs", "write a tutorial / how-to / reference page", "structure the docs", "write API documentation", "write a README / changelog", or when authoring any file under a `docs/` tree. For SKMTC docs specifically, this skill governs the *craft* (what makes the page good); the content split between skills, `llms.md`, and the docs tree is governed by `docs/skills/README.md`. Distinct from `skmtc-retro` (captures observations about work) and the `skmtc-*` operational skills (guide doing the work) — this skill guides writing *about* the work for readers.

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

Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use write-a-spec), record a decision (use record-a-decision), or review a design (use review-a-design) — a postmortem documents an incident that already happened, it does not propose, specify, decide, or critique future work.

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

Write how-to guides and tutorials that naturally integrate affiliate product recommendations. Triggers on: "write a how-to guide", "tutorial for [task]", "step by step guide to [goal]", "how to [verb] with [product]", "write a tutorial blog post", "guide on how to [task]", "beginner guide to [topic]", "walkthrough for [product]", "write an educational article", "how do I [task] blog post", "write a tutorial that promotes [product]".

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

Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines. Handles new content creation from a keyword, topic, or brief, and full-page rewrites. Use when asked to "write a blog post", "create a landing page", "write content about X", "content for keyword X", "draft an article", "blog post about", "landing page for", "service page", "product page copy", "rewrite this page", "how-to guide", or "listicle". NOT for analyzing/auditing existing content (seo-geo-optimizer, content-quality-auditor), title tags or meta descriptions (meta-tags-optimizer), or keyword expansion (keyword-research) — those skills own their triggers.

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

Request write permission from the user before making file changes. MUST be invoked before any write attempt when the write gate is closed. Creates scoped approval via AskUserQuestion + TaskCreate, opens the write gate, and closes it when work is done. Triggers: write hook blocks an edit, agent is about to write files outside .craft/, agent needs to modify project source files. This skill requires user approval 100% of the time - never bypass AskUserQuestion.

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

Medical/scientific paper writing workflow skill. Manages the full pipeline from literature search to submission-ready manuscript. Creates and manages a project directory with IMRAD-format section files, literature matrix, reference management, and quality checklists. Supports both English and Japanese papers. Triggers: 'write paper', 'paper-write', 'start manuscript', '論文を書く', '論文執筆', '論文プロジェクト', 'manuscript', 'research paper', '原稿作成'.

Write personalized pitch emails to journalists, podcasters, newsletter writers, and analysts using AIDA adapted for media pitching and Ryan Holiday's journalist psychology from "Trust Me I'm Lying." Different from press releases (use /press-release-writer for those). Use when the user asks to pitch a journalist, pitch a reporter, "get coverage in X", media outreach, podcast pitch, analyst briefing request, or wants to land a story. Reads brand voice and positioning from knowledge/. For the press release itself, see press-release-writer. For the underlying customer story, see case-study-writer.

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

Write or edit Japanese articles, reports, guides, and public-facing drafts so the argument is clear and the prose reads naturally. Preserve the author's meaning, evidence, and voice when revising. Use for requests to write from a topic or notes, remove AI臭 / AIっぽさ, improve awkward wording or structure, or format notes as 箇条書き, チーム共有, 社内共有, a decision note, handoff, Slack post, or Teams post. For existing prose, ask Gemini through Antigravity CLI to rewrite naturally by default, then audit against the source; use the current model if unavailable. Do NOT use for ordinary Japanese answers, progress updates, technical explanations, code review, English-only prose that is not a bullet-formatting request, or an explicitly incompatible format.