'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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft Appwrite blog posts around concrete developer problems and search intent. Structure the article, prepare titles, summaries, FAQs, and article metadata, check product claims against local documentation, and generate a cover image using Appwrite's cover API.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft a practical Appwrite tutorial
• Outline a comparison article around search intent
• Prepare titles, summaries, FAQs, and article metadata

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."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review existing Appwrite blog posts for tone, structure, SEO, formatting, and product accuracy. Compare claims with local documentation, identify specific problems, and produce a structured report with suggested rewrites and prioritized fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review an Appwrite blog draft before publication
• Audit titles, summaries, and search intent
• Verify feature descriptions and API details against local docs

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare coordinated Appwrite launch materials: documentation updates, an announcement blog post, and a changelog entry. Keep feature names, examples, dates, and links consistent, with the documentation serving as the factual reference.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Announcing a new Appwrite feature
• Preparing an SDK or integration launch
• Updating documentation and the changelog together

Write large text files when write_file or shell_agent fails because of content size limits. The fallback passes multiline content through run_shell to Python, with guidance on escaping characters and checking the saved file.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving large source files after a write_file failure
• Writing long JSON or Markdown files
• Handling content with complex shell escaping

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create and edit reports, memos, and other Writer documents, saving them as ODT by default. Read existing files before changing content, add or replace text, and use DOCX when Microsoft Word compatibility is required.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a report as an ODT document
• Add or replace text in an existing document
• Prepare a DOCX file for Microsoft Word

Use shell heredocs, which pass multiline text directly to a command, when write_file fails on complex code. Save TypeScript, JSX, JSON, or shell scripts with literal quotes and formatting, then verify the file and its contents.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving TypeScript or JSX files after repeated write_file failures
• Writing JSON files containing quotes and special characters
• Preserving variables and line breaks in shell scripts

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review Appwrite blog posts for search visibility and clear answers that answer engines can extract. Measure titles and content, assess structure and links, and receive evidence-based findings with prioritized fixes and suggested replacements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a blog post before publication
• Reviewing titles, descriptions, and headings
• Assessing search intent and direct answers

Create, update, or review Bifrost feature documentation for Mintlify using MDX, a format combining Markdown and components. Research the interface and backend, validate configuration examples, and organize pages with screenshot placeholders and navigation entries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write documentation for a new Bifrost feature
• Update guides after interface or API changes
• Validate config.json examples against the schema

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レビュー"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare Bifrost releases by turning Git history into release summaries and module changelogs. Coordinate version updates across dependent modules, document database migration risks, and include closed issues and outside contributor credits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing changelogs for a Bifrost release
• Coordinating version updates across dependent modules
• Documenting database migration rollback limits

Work around file-writing errors caused by quotes, backticks, or JavaScript template literals using a temporary Python script. The workflow includes reading back each saved file to check its contents and removing the helper script afterward.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recovering from write_file errors
• Saving TypeScript files containing template literals
• Writing multiple files with mixed quote styles

Save large text files when write_file or shell_agent encounters payload size limits. Create the parent directory first, write the content with Python through run_shell, and verify the resulting file.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Saving large source files after write errors
• Writing files into new nested directories
• Saving long JSON or Markdown content

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.