「hn」の検索結果

Audits and optimizes websites for search engine visibility (SEO) and AI search citation (GEO), covering technical health, E-E-A-T content scoring, domain authority, structured data, rich results, and entity signals. Use when running SEO audits, diagnosing traffic drops or ranking losses, generating Schema.org JSON-LD, checking Core Web Vitals, crawlability, robots.txt, sitemaps, hreflang, backlinks, planning content strategy or site migrations, fixing indexing issues, or optimizing for AI Overviews, ChatGPT, and Perplexity. NOT for paid ads (PPC/SEM), social media strategy, email marketing, or general web development unrelated to search.

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

Write Persian with Persian words. Use when writing, editing, translating or reviewing Persian (Farsi) prose — articles, documentation, posts, essays, UI copy — to replace loanwords with Persian equivalents while leaving technical terminology, proper nouns and code untouched. Also use when the user asks for پارسی سره, سره‌نویسی, فارسی‌سازی, or "make this text more Persian".

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

Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

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

Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.

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

System architect and technical design leader. Use when the user asks to talk to Winston or requests the architect.

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

Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'.

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

Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".

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

CVSS 3.1 vector examples, executive summary template, full technical finding template, and remediation language bank for pentest reports

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

MITRE ATT&CK framework reference — tactics, techniques, and tool-to-TTP mappings for pentest documentation and detection rule writing

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

Search and inspect the harness memory namespace (HNSW + emergent-time decay).

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

Meta-enforcement layer that routes EVERY agent action through the correct skill. MUST check this routing table before ANY response involving code, files, or technical decisions. Default: route to rune:cook for code tasks. Prevents rationalization, enforces check-before-act discipline.

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

Web search and external knowledge lookup. Gathers data on technologies, libraries, best practices, and competitor solutions.

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

开源项目发布与场景主题营销，含 Web/CLI 数据采集验证。覆盖 GitHub star 增长、KOL 合作、Reddit / HN / Discord / Telegram 社群分发、 多语言落地（中英日韩）。从 gingiris-opensource 提炼。适用场景：要发布一个开源项目， 想在 6 个月内冲 10k star，或已发布但流量卡住要破局。

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

Build and measure Developer Relations programs across documentation, community, technical content, integrations, events and developer advocacy. Use when designing DevRel strategy, improving developer activation, launching an API/SDK, evaluating sponsorships, or connecting community activity to product adoption and revenue.

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

Reconstruct an open-source project's growth channels, key content, and stage-by-stage attribution from GitHub history and public web evidence. Use this skill when asked to research GitHub star growth, identify launch and amplification channels, explain viral milestones, find representative posts or videos, compare Product Hunt/Show HN/Reddit/KOL impact, or produce an evidence-backed OSS growth attribution report.

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

Marketing playbook for open-source projects led by non-technical founders. Covers README optimization, community building, contributor attraction, and translating OSS traction into revenue. By @WeiYipei.

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

Comprehensive Rust code review that fans out across detected technology areas, running them in parallel when the agent supports subagents and sequentially otherwise. Use for pre-push or pre-PR review of .rs files.

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

Reference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications. Triggers on reference docs, API reference, function reference, parameters table, symbol documentation.

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

Process external code review feedback with technical rigor. Use when receiving feedback from another LLM, human reviewer, or CI tool. Verifies claims before implementing, tracks disposition.

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

Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.

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

Use when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: "work backwards", "write a PRFAQ", "press release first", "is this idea worth building", "pressure-test this concept", "filter this before brainstorm", "is this a real product". Also catches solution-first pitches ("I want to build X that does Y") and technology-first pitches ("use AI to...") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs.

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

Core technical documentation writing principles for voice, tone, structure, and LLM-friendly patterns. Use when writing or reviewing any documentation.

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

Generate first-draft technical documentation from code analysis

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

Reference for the diagnostics pipeline (ripdpi-monitor-engine/ripdpi-diagnostics-* and core/diagnostics). Use when changing ScanRequest/ScanReport, ProbeTask families, probe scheduling, the catalog, or the wire contract. Techniques: desync-engine.

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