Results for “writing-guide”

Write developer-focused technical blog posts with structured templates, code formatting rules, and audience-specific guidance for tutorials, deep dives, postmortems, and architecture posts.

Write clear, helpful UI copy including microcopy, error messages, empty states, and CTAs that guide users and reinforce product voice.

Guide users through installing CUDA-Q, writing quantum kernels, running GPU-accelerated simulations, connecting to QPU hardware, and exploring built-in applications.

Write clear, concise, and accurate technical documentation including API references, user guides, tutorials, changelogs, and architecture docs, tailored to the target audience. Use when the user requests technical writing or provides relevant inputs for this workflow.

Write scientific manuscripts in full paragraphs using IMRAD structure, with citations (APA/AMA/Vancouver), figures/tables, and reporting guidelines (CONSORT/STROBE/PRISMA) for research papers and journal submissions.

Write long-form content like blog posts, guides, tutorials, and newsletters with a distinctive, non-generic voice derived from supplied examples or brand guidance.

Write long-form content such as blog posts, guides, tutorials, and newsletters with a distinctive voice derived from supplied examples or brand guidance, ensuring structure, pacing, and credibility.

Creates high-quality software documentation following the Diátaxis framework, covering tutorials, how-to guides, reference, and explanation documents.

Guides users through a structured three-stage workflow for co-authoring documents, from context gathering to reader testing.

Guides users through a structured three-stage workflow for co-authoring documents, from context gathering to reader testing.

Guides users through a structured three-stage workflow for co-authoring documents, from context gathering to reader testing.

Guides users through a structured three-stage workflow for co-authoring documents, from context gathering to reader testing.

Produces high-quality written knowledge artifacts such as READMEs, guides, API specs, tutorials, runbooks, and wikis, with audience-appropriate structure and accuracy.

Write end-user documentation including tutorials, how-to guides, walkthroughs, onboarding flows, and feature documentation. Use when creating documentation for non-technical or semi-technical end users. Also trigger for 'user guide', 'tutorial', 'how-to', 'walkthrough', 'onboarding docs', 'help article', 'user manual', or 'getting started guide'.

Guides users through a structured three-stage workflow for co-authoring documentation, proposals, technical specs, and similar documents.

Generate comprehensive authoring guides for content authors taking over an AEM Edge Delivery Services project, covering blocks, templates, configurations, and publishing workflows.

Write grant reports with progress, financials, and outcomes. TRIGGERS - Use when user needs help with grant-report related tasks.

Generates thorough README.md documentation by exploring a codebase, identifying the tech stack, and producing setup, architecture, and deployment guides.

claude-code-guide の更新キューを処理し、変更されたスクリプト・設定ファイルに合わせてガイドのsource Markdownを更新し convert.py で再生成する。ユーザーが「/update-guide」を実行した時にトリガーする。

Guides a structured software requirements specification workflow from topic intake through brainstorming, spec writing, planning, review, SRS generation, validation, and improvement reporting.

Guides users through a structured three-stage workflow for co-authoring documentation, from context gathering to iterative refinement and reader testing.

Guides a structured requirements pipeline from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Generate clear documentation for each task including technical descriptions, architecture diagrams, and usage guides. Use when documenting completed features, creating README files, writing API documentation, generating architecture diagrams, or maintaining project documentation. Ensures knowledge is preserved and accessible.

Guide a team through writing a structured, blameless post-mortem after a production incident, covering timeline reconstruction, root cause analysis, impact quantification, and action item generation.

Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.

Creates scientific documentation using markdown with embedded Mermaid diagrams as the default format, enforcing a text-based diagram standard with style guides, 24 diagram type references, and document templates.

Remove signs of AI-generated writing from academic medical papers. Use when editing or reviewing manuscripts to make them sound more natural and professionally written. Based on Wikipedia's "Signs of AI writing" guide, adapted for medical literature. Detects and fixes patterns including: inflated significance claims, superficial -ing analyses, vague attributions, AI vocabulary words, copula avoidance, excessive hedging, generic conclusions, informal word choices (linked/beyond/via/where/yield), overly assertive causal claims, and artificially condensed expressions. Preserves legitimate academic transitions (Notably, Prior studies have shown, etc.).

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.