「technical」の検索結果

Language-agnostic writing style guidelines covering structure, tone, rhetorical constraints, banned phrases, and review checks. Use when writing any kind of content in any language. Including blog posts, notes, technical articles, technical writing, chitchat, social media posts, etc., even when you are just sending a text message. Also use when reviewing or editing existing content for tone and style compliance. For Traditional Chinese (zh-TW) content, apply `chinese-content-writing-guideline` alongside this skill.

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

Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.

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

Document and prioritize technical debt. Use when the user says "tech debt", "legacy code", "this code is a mess", "refactoring plan", "we need to clean this up", "paying down debt", "this is hard to change", "how do we fix this codebase", or has code that's difficult to understand or modify - even if they don't explicitly say "technical debt".

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

Write a technical tax position memo that documents a tax filing position with authorities, facts, analysis, and conclusion. Use when a tax professional says "write a tax memo", "document this tax position", "research memo for the partner", "we need to support this deduction", "document the tax treatment", "write up the authority for this position", "technical memo on [tax issue]", "MLTN analysis", "reasonable basis memo", "document the IRC section that supports this", or needs to formally document a tax conclusion. Also trigger when someone has a tax question that needs a written conclusion backed by legal authority - even if they don't use the words "tax memo" or "tax position".

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

Audit technical SEO across crawlability, indexability, security, URLs, mobile, Core Web Vitals, rendering, structured data, and IndexNow. Exclude content strategy and backlinks.

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

Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability, indexability, Core Web Vitals with INP), schema markup, content quality (E-E-A-T), image optimization, sitemap analysis, and GEO for AI Overviews/ChatGPT/Perplexity. Industry detection for SaaS, e-commerce, local, publishers, agencies. Triggers on: SEO, audit, schema, Core Web Vitals, sitemap, E-E-A-T, AI Overviews, GEO, technical SEO, content quality, page speed. Use this hub only when the SEO domain is clear and the requested workflow is not; otherwise use the exact retained leaf or command.

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

Run a full-site SEO audit and return a scored, prioritized report. Use only for site-wide checks; use seo-page for one URL or seo-technical for a technical-only review.

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

Open, classify, and escalate support cases with Salesforce Technical Support via the Help portal: choosing severity, engaging Premier Success, the Escalate to Technical Support Management path, tracking incidents on the Trust site. NOT for escalating your own org's cases after N hours - use admin/escalation-rules. NOT for SLA milestone timers and entitlement processes - use admin/entitlements-and-milestones.

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

Technical documentation expert for clear, concise, user-friendly documentation and tutorials

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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

Applies rigorous adversarial analysis to generate, critique, fix, and consolidate solutions for any problem (technical or non-technical). Use when facing complex problems requiring thorough analysis, multiple solution approaches, and validation of proposed fixes before implementation.

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

Technical blog post writing guide. rooftopsnow.tistory.com style — Korean formal technical prose, architecture diagrams, code blocks + design intent commentary, table comparisons, checklist wrap-up. Triggers on "blog", "포스팅", "블로그", "기술 글", "tech blog".

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

Expert in developer tool documentation as a product. Activate on: docs site, getting started guide, API reference, developer documentation, Docusaurus, Mintlify, Nextra, ReadMe, migration guide, troubleshooting page, docs information architecture, documentation testing, llms.txt. NOT for: marketing copy (use seo-content-blogging), API design itself (use api-architect), general technical writing (use technical-writer).

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

Systematic framework for resurrecting and modernizing legacy codebases through archaeology, resurrection, and rejuvenation phases. Activate on "legacy code", "inherited codebase", "no documentation", "technical debt", "resurrect", "modernize". NOT for greenfield projects or well-documented active codebases.

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

Model organizations as BDI systems with filtered perception, discourse-shaped desires, accommodations, and abstraction-level hierarchy. Use for socio-technical coordination and organizational modeling. NOT for mechanistic workflows, individual psychology, or non-social domains.

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

Estimates the minimum biological replicates (or cells/events) for a target power at a target FDR in genomics experiments using ssizeRNA, PROPER, powsimR for scRNA-seq, and pilot-data dispersion estimation from DESeq2/edgeR. Covers the biological-versus-technical replication distinction (technical replicates do not add degrees of freedom for biological inference), replicate-number-versus-sequencing-depth budgeting, scRNA-seq sample-versus-cell allocation under a pseudobulk model, and the critique that "n=3" is a publication convention rather than a power calculation. Use when budgeting a sequencing experiment, writing the sample-size justification in a grant, estimating replicates from pilot data, allocating a fixed budget between samples and depth, or planning scRNA-seq cohort size. For clinical-trial sample size see clinical-biostatistics/power-and-sample-size; for the power-given-n direction see experimental-design/power-analysis.

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

Aligns sample metadata with count matrices and constructs design matrices for downstream DE, handling the alphabetical-reference-level trap (relevel BEFORE DESeq), LRT reduced-model rules, the interaction-term resultsNames trap, continuous-covariate scaling and splines, repeated measures via duplicateCorrelation or dream, high-cardinality categorical pseudo-singular designs, sample swap detection via XIST/RPS4Y1 expression and somalier/NGSCheckMate genotypes, SABV (sex-as-biological-variable) mandate, Simpson's-paradox collapsing of technical replicates, and the `~ 0 + group` parameterization for clean contrasts. Use when building a design matrix, troubleshooting reversed fold-change direction, encoding paired or repeated-measures designs, detecting sample swaps, deciding sex-as-covariate, or aggregating technical replicates.

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

Write technical documentation that matches the measured profile of professionally-written docs. Carries the craft rules derived from 114k words of pre-2022 documentation (SQLite, PostgreSQL, Python, Django, Rust, Go, Pro Git, nginx), the per-Diátaxis-type numeric targets, and the copywriting register for page leads. Use when drafting or rewriting any documentation prose, or when a page is factually right but reads as machine-written.

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

Standard operating procedure for producing a documentation page end to end — gather source material, classify, draft against the measured corpus profile, then run the reader-level and humanizer passes and both gates. Use for any page on a documentation surface, or when rewriting a page that reads as machine-written. Orchestrates technical-writing, reader-level and humanizer in a fixed order.

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

When the user wants to create step-by-step technical tutorials, quickstarts, or code walkthroughs. Trigger phrases include "tutorial," "quickstart," "getting started guide," "walkthrough," "step by step," "how to guide," "hands-on guide," or "code tutorial."

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

Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

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

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

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