「technical」の検索結果

Create runbooks, playbooks, and technical documentation for engineering teams. Use when the user wants to document a process, create a runbook, build operational docs, or formalize any repeatable technical procedure. Triggers on requests like "create a runbook for...", "document this process", "write a playbook", or any technical documentation request.

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

Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".

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

Create HTML technical documentation with code blocks, API workflows, system architecture diagrams, and syntax highlighting. Use when users request technical documentation, API docs, API references, code examples, or developer documentation.

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

Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.

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

A skill for technical writing. This skill should be used when users want to write a technical article.

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

Translate technical analysis into business language. Use when explaining statistical concepts to non-analysts, simplifying technical findings, or bridging communication between data teams and business stakeholders.

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

Compute technical indicators like RSI, MACD, Bollinger Bands, SMA, EMA for a stock. Use when user asks about technical analysis, indicators, RSI, MACD, moving averages, overbought/oversold, or chart analysis.

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

Implements HIPAA Security Rule technical safeguards under 45 CFR §164.312 for electronic protected health information. Covers access controls with unique user identification, emergency access procedures, automatic logoff, encryption, audit controls, integrity controls, and transmission security. Keywords: HIPAA Security Rule, ePHI, access controls, encryption, audit controls, technical safeguards.

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

Manages backup and archive data under retention schedules and erasure obligations. Covers the technical infeasibility exception for backup deletion, backup cycle alignment with retention periods, restore-and-delete procedures, and interim protective measures during backup retention. Activate for backup deletion, archive erasure, backup retention, restore and delete, technical infeasibility queries.

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

Technical Analysis Agent — price action, indicators, chart patterns, support/resistance, and momentum analysis with Technical Score (0-100)

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

Detect and analyze areas with high maintenance cost, poor design, or accumulated technical debt. Use this skill when reviewing codebases for quality issues, planning refactoring efforts, conducting code audits, assessing project health, identifying maintenance hotspots, or prioritizing technical improvements. Analyzes code smells, architectural issues, dependency problems, test quality, documentation gaps, and provides actionable recommendations with priority rankings.

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

Use when drafting or revising internal technical design docs, review notes, architecture writeups, or sharing posts in Chinese, especially when the tone should stay evidence-backed, calm, and suitable for peers or leaders rather than marketing or literary writing.

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

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.

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

Think and work like an expert Geotechnical Scientist. Use when a task calls for Geotechnical Scientist judgment. Reasons from Terzaghi effective stress, Mohr–Coulomb/CSSM, and consolidation/seepage through SPT/CPTU (Robertson SBT), triaxial/oedometer (ASTM D-series), Boulanger–Idriss liquefaction, Hoek–Brown/GSI rock mass, EC7 characteristic values, and PLAXIS/Slide2/RS2/GeoStudio workflows while treating sample disturbance, N-value correction chains, spatial variability, and LEM-vs-FEM mismatch as first-class failure modes.

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

Think and work like an expert Geotechnical Engineer. Use when a task calls for Geotechnical Engineer judgment. Reasons from effective stress and LRFD/EC7 limit states through GDR/GBR/FDR deliverables, shallow and deep foundations (GEC 6/10/12), excavation support (DeepEX, LPILE), ground improvement, ASCE 7 liquefaction, observational-method triggers, and FHWA pile acceptance while treating DSC claims, setup vs. blow count, and GBR-vs-design conflation as first-class failure modes.

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

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

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

The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.

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

Legendary blog writing that makes readers forget they're reading. This skill combines the narrative mastery of Paul Graham's essays, the technical accessibility of Julia Evans, the conversational wit of Wait But Why, and the viral mechanics of James Clear. Great blog posts don't inform—they transform. They take complex ideas and make them feel obvious. They turn strangers into superfans. They get shared not because someone should read them, but because someone needs to read them. This skill adapts to any topic: cybersecurity that reads like a thriller, AI explainers that feel like conversations, marketing insights that make you screenshot every paragraph, and coding tutorials that make you excited to build. Use when "write a blog post, blog post about, write an article, create content about, explain this topic, write about, long-form content, thought leadership, technical blog, how-to article, tutorial post, educational content, industry analysis, opinion piece, newsletter content, make this engaging, write for developers, explain like, writing, blog, content, articles, long-form, storytelling, technical-writing, thought-leadership, educational, tutorials, explainers, engagement" mentioned.

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

Keeping codebases healthy, performant, and maintainable - refactoring, performance optimization, and technical debt managementUse when "refactor, optimize, performance, technical debt, cleanup, architecture, speed up, bundle size, memory leak, slow query, code smell, complexity, dead code, performance, refactoring, optimization, technical-debt, architecture, cleanup, bundle, memory" mentioned.

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

Technical SEO site audit via the DataForSEO On-Page API. Crawls the site (up to 100 pages by default), surfaces critical errors (broken links, redirect chains, missing meta, slow pages, schema gaps, indexability issues), and returns a Technical Score (0-100) with prioritized fixes.

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

Deep technical SEO auditing covering crawlability, indexation, Core Web Vitals, site architecture, canonicalization, structured data validation, and performance optimization. Use when the user asks about technical SEO, site audits, crawl issues, indexation problems, Core Web Vitals, page speed, or site architecture optimization. For content-focused SEO, see the seo-content-writer skill.

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

Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".

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

Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation, and category-aware AEO-optimized content. Use when: (1) writing, editing, or proofreading a blog article or post, (2) transforming unstructured brain dumps into polished posts, (3) writing in specific personal voices (Jarad, Nick Nisi), (4) creating category-aware technology/company/product posts, (5) building tutorials, deep dives, postmortems, benchmarks, or architecture posts, (6) writing engineering blogs, dev blogs, programming blogs, coding tutorials, or documentation posts. Triggers: blog post, blog writing, technical blog, dev tutorial, brain dump, article, content writing, developer article, engineering blog, programming blog, coding tutorial, documentation post, technical writing, blog editing, proofreading, developer content

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

Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report

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