「hn」の検索結果

🇺🇸 Open-Source Marketing & GitHub Stars Growth System — Decision framework for each growth stage. Pre-launch readiness → Show HN / Reddit / Product Hunt launch → 6-month growth loop. README rules, KOL outreach, dev-content matrix (dev.to / Zenn), anti-star-farming. Built from taking AFFiNE 0 → 60K stars. 🇨🇳 开源营销与 GitHub Star 增长系统 — 每个增长阶段的决策框架。Pre-launch 就绪 → Show HN / Reddit / Product Hunt 发布 → 6 个月增长循环。README 规则、KOL 合作、开发者内容矩阵（dev.to / Zenn）、防刷 star。提炼自 AFFiNE 0 → 60K star 实战。 🇯🇵 オープンソースマーケティング＆GitHub スター成長システム — 各成長段階の意思決定フレームワーク。Pre-launch → Show HN / Reddit / Product Hunt → 6ヶ月成長ループ。READMEルール、KOL連携、開発者コンテンツマトリックス。 🇰🇷 오픈소스 마케팅 & GitHub 스타 성장 시스템 — 각 성장 단계별 의사결정 프레임워크. 사전 출시 → Show HN / Reddit / Product Hunt → 6개월 성장 루프. README 규칙, KOL 아웃리치, 개발자 콘텐츠 매트릭스. Triggers: "open source marketing" | "GitHub stars" | "star growth" | "Show HN" | "Hacker News launch" | "OSS launch" | "developer marketing" | "Reddit launch" | "dev.to" | "open source growth" | "开源营销" | "GitHub star 增长" | "开源发布" | "Show HN 怎么发" | "开发者营销" | "オープンソース" | "오픈소스 성장"

Interact with Hacker News (news.ycombinator.com) — browse top, new, and best stories, read item details and comment threads, look up user profiles, and search posts via Algolia. Use this skill whenever the user mentions Hacker News, HN, YCombinator news, ycombinator.com, news.ycombinator.com, wants to browse tech news, read HN discussions, search HN posts, or look up HN users. Also trigger when the user pastes an HN URL (e.g. news.ycombinator.com/item?id=12345). Keywords: Hacker News, HN, YC, ycombinator, tech news, Show HN, Ask HN, HN front page.

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

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

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

"Apply Sociotechnical Systems Theory to analyze and design work systems through joint optimization of social and technical subsystems. Use this skill when the user needs to diagnose why a technology implementation disrupted work practices, design IT-enabled work systems that balance human and technical needs, or when they ask 'why did this system hurt productivity despite being technically sound', 'how do we design work around new technology', or 'why are people resisting this technically superior system'.".

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

Fetch and send Hacker News front-page posts on demand. Use when the user asks for HN, says 'hn', 'pull HN', 'hn 10', or specifies a topic like 'hn health', 'hn hacking', or 'hn tech'. Sends N (default 5) posts as individual messages with Title + Link. Exclude crypto.

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

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

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

Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, and when the user asks to write, rewrite, review, or check technical documentation, procedures, manuals, instructions, warnings, or reports.

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

Build a Hacker News + Reddit launch playbook for developer-tools and community-led products during PRD v0.9 Go-to-Market. Triggers on requests to plan HN/Reddit launch, "Show HN" post, community launch, or when user asks "HN launch", "Show HN", "Reddit launch", "launch on /r/SaaS", "Product Hunt vs HN", "community launch", "developer launch". Outputs GTM-* with Type=Channel-HN / Type=Channel-Reddit entries with timing, title, story angle, and engagement plan.

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

Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write an HN post", "craft a Show HN", "prepare our Hacker News launch", or "help me post on HN".

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

Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.

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

Triage technical SEO findings from Ahrefs Site Audit (and similar crawlers) by SEO impact, not just severity. Use this skill when reviewing crawl results, prioritizing technical fixes, scoping a technical SEO sprint, or after running any site-wide crawl. Triggers on site audit results, technical fix list, crawl errors, technical SEO triage, prioritize technical issues, what should we fix first, broken links, redirect chains. Also triggers when a long list of crawler issues is creating decision paralysis.

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

Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.

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

"Apply the TPACK framework to evaluate and design technology-integrated instruction at the intersection of technological, pedagogical, and content knowledge. Use this skill when the user needs to assess teacher readiness for technology integration, design professional development for ed-tech, or evaluate whether technology use is pedagogically grounded — even if they say 'how to integrate technology in teaching', 'ed-tech evaluation', or 'teacher technology competency'.".

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

Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.

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

Run a comprehensive technical SEO audit covering crawlability, indexability, rendering, site architecture, structured data, page experience, security, and internationalization. Use this skill whenever the user asks about technical SEO, crawl issues, indexing problems, sitemaps, robots.txt, canonical tags, schema markup, page speed, Core Web Vitals, hreflang, redirects, or site-wide search performance. Triggers on technical SEO, site audit, crawlability, indexability, sitemap, robots.txt, canonical, redirect chain, schema, JSON-LD, Core Web Vitals, page speed, hreflang, mobile usability, HTTPS, security headers, render-blocking, JavaScript SEO. Also triggers when a site has indexing problems, traffic drops, or migration concerns, even if 'technical SEO' is not said explicitly.

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

Guides privacy impact assessment for emerging technologies including IoT, blockchain, AR/VR, quantum computing, and digital twins. Covers risk identification methodology, proportionality assessment, and technology-specific privacy challenges. Activate when evaluating new technology adoption, innovation projects, or emerging tech procurement. Keywords: PIA, emerging technology, IoT, blockchain, AR/VR, quantum computing, digital twins, innovation privacy.

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

Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.

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

anti-reversing-techniques workflow skill. Use this skill when the user needs AUTHORIZED USE ONLY: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis: > 1 and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

anti-reversing-techniques workflow skill. Use this skill when the user needs AUTHORIZED USE ONLY: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis: > 1 and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

半导体芯片制造工艺 (Semiconductor Process Engineering / 半导体芯片制造工艺 — 以「物理化学极限 + 良率经济双重约束」为特征的集成电路前道/后道制造工艺认知操作系统：从「器件架构与微缩路线（planar→FinFET→GAA nanosheet→CFET、等效微缩 DTCO/STCO、背面供电 BSPDN）→ 工艺整合（FEOL/MOL/BEOL 模块协同、PDK、流片 tape-out）→ 单元工艺（光刻 litho（DUV 浸没式 193i / EUV 13.5nm / 多重曝光 SADP-SAQP / OPC / mask）、刻蚀 etch（RIE/ICP/原子层刻蚀 ALE）、薄膜沉积 depo（CVD/PECVD/LPCVD/ALD/PVD/外延 epi/电镀 Cu）、掺杂 doping（离子注入 ion implant / 退火 RTA-laser anneal）、CMP 化学机械抛光、清洗 cleaning）→ 量测检测 metrology（CD-SEM / OCD / overlay / 椭偏 ellipsometry / 缺陷检测 defect inspection / e-beam）→ 良率工程 yield（缺陷密度 / SPC 统计过程控制 / FDC / APC / DOE 实验设计 / 良率爬坡 yield ramp）→ 先进封装 advanced packaging（2.5D/3D、CoWoS、HBM、混合键合 hybrid bonding、chiplet、TSV）」的完整器件-工艺-良率-量产决策链。覆盖 (a) 第一性张力 — **物理/化学/材料的硬约束（量子隧穿、短沟道效应、RC 延迟、热预算、缺陷物理、ppb 级污染控制）⇄ 良率/成本/产能的经济约束（每片晶圆成本、良率是主经济指标、D0 缺陷密度、wafer-per-hour、折旧）**；**持续微缩/摩尔定律（dimensional + equivalent scaling、节点路线图 N5/N3/N2/A16/A14、high-NA EUV）⇄ 物理极限/微缩放缓（原子尺度、漏电、功耗墙、成本墙、'摩尔定律已死'之争）**；**协同优化/整合（DTCO 设计-工艺协同、STCO 系统-工艺协同、模块间 trade-off）⇄ 单模块极致优化（单一 unit process 工艺窗口）**；**工艺配方的 tacit 手艺（process recipe 调试、工艺窗口、缺陷根因分析、量产 ramp 的经验）⇄ 可建模/可仿真/数据驱动（TCAD 仿真、ML 良率分析、APC/FDC、数字孪生）**；**性能-功耗-面积-成本 PPAC 四角权衡 ⇄ 良率/可制造性 DFM 优先**；**自主可控/国产替代（卡脖子、EUV 出口管制、设备/材料/EDA 国产化、SMIC/长江存储/长鑫/中微/北方华创/上海微电子）⇄ 全球高度分工（ASML 光刻垄断、AMAT/Lam/TEL/KLA 设备、TSMC/Samsung/Intel 代工、全球供应链）**。(b) 核心工作流 / pipeline（最标准、最易蒸高质量 + CLI 化）— 新节点/新工艺导入：器件目标与 PPAC 定义 → 工艺整合方案与 PDK → 单元工艺开发与配方调试（DOE 找工艺窗口）→ 量测建立与 SPC → 良率爬坡（缺陷分类 + 根因分析 + 工艺改善）→ 量产移交与持续改善。具体单元工艺 SOP：光刻（曝光条件 / OPC / overlay 控制 / 多重曝光分解）、刻蚀（选择比 / profile / loading effect / ALE）、沉积（台阶覆盖 / 应力 / 均匀性）、CMP（去除速率 / 碟形 dishing / 侵蚀 erosion）、量测与缺陷分析、良率分析与 FA 失效分析。(c) 工具栈 — 设备（光刻 ASML/上海微电子 SMEE；刻蚀+沉积 AMAT/Lam/TEL/中微 AMEC/北方华创 Naura；离子注入 AMAT/Axcelis；CMP AMAT/荏原 Ebara；量测检测 KLA/AMAT/中科飞测/上海精测）、EDA/TCAD/仿真（Synopsys Sentaurus/Silvaco/Coventor SEMulator3D、OPC Calibre/Synopsys）、良率与制造软件（SPC、MES、FDC/APC、缺陷分析 yield management、PWS）、材料（光刻胶 photoresist、CMP 浆料 slurry、特气、靶材、掩膜 mask blank）。(d) 知识正典 — 半导体工艺 canon 横跨器件物理与制造工程：核心教材（Plummer/Deal/Griffin《Silicon VLSI Technology》、Sze《Physics of Semiconductor Devices》《VLSI Technology》、Wolf & Tauber《Silicon Processing for the VLSI Era》、Campbell《Fabrication Engineering at the Micro and Nanoscale》、May & Spanos《Fundamentals of Semiconductor Manufacturing and Process Control》、Quirk & Serda《Semiconductor Manufacturing Technology》、肖国勇/施敏中文教材）、路线图（ITRS/IRDS、IEEE 国际器件与系统路线图）、顶会论文（IEDM、Symposium on VLSI Technology、IRPS 可靠性、SPIE Advanced Lithography、ISSCC、DAC）、行业分析（SemiAnalysis、TechInsights、IC Knowledge）。(e) figures/流派 — 学术与器件奠基（Gordon Moore 摩尔、Robert Dennard 登纳德微缩、胡正明 Chenming Hu FinFET/UTB-SOI 发明人 UC Berkeley、刘明 Tsu-Jae King Liu Berkeley、Krishna Saraswat Stanford、Mark Bohr Intel 工艺架构）、产业领袖与工艺大师（张忠谋 Morris Chang TSMC、林本坚 Burn-Jeng Lin 浸没式光刻、Martin van den Brink ASML、米玉杰/梁孟松 SMIC/三星工艺、Mark Liu/魏哲家 TSMC）、行业分析师（Dylan Patel SemiAnalysis、Scotten Jones IC Knowledge、TechInsights 拆解、Handel Jones）、科普与拆解（Asianometry、The Chip Letter、半导体行业观察）。流派分歧：等效微缩派 vs 摩尔定律已死派、前道微缩 vs 先进封装 chiplet 异构集成、dimensional scaling vs DTCO 协同优化、IDM vs 纯代工 foundry 模式、自主可控/国产替代路线 vs 全球分工。(f) 行业话术/黑话 — 制程节点 node / 流片 tape-out / 工艺窗口 process window / 良率 yield / 缺陷密度 D0 / 关键尺寸 CD / 套刻 overlay / 掩膜 reticle-mask / 光刻胶 PR / 浸没式 immersion / EUV/DUV / 多重曝光 multi-patterning SADP-SAQP / OPC / 刻蚀选择比 selectivity / profile / loading effect / 原子层刻蚀 ALE / 台阶覆盖 step coverage / 外延 epi / 离子注入 implant / 退火 anneal / RTA / CMP / dishing-erosion / FEOL-MOL-BEOL / FinFET / GAA / 纳米片 nanosheet / CFET / 背面供电 BSPDN / high-NA / PPAC / DTCO-STCO / DFM / SPC / FDC-APC / DOE / WAT-PCM / 良率爬坡 yield ramp / FA 失效分析 / particle 颗粒 / 洁净室 cleanroom-级别 / 12寸-8寸 wafer / chiplet / CoWoS / HBM / 混合键合 hybrid bonding / TSV / PDK / 等效微缩. (g) 争议/批判 — 「摩尔定律是否已死 vs 等效微缩继续」、「节点命名营销化（N3/N2 ≠ 物理 3nm/2nm，gate pitch/metal pitch 才是真尺度）」、「前道微缩 vs 先进封装异构集成谁是未来」、「自主可控/国产替代的现实（EUV 卡脖子、设备/材料/EDA 国产化进度、出口管制 entity list、良率与成熟度差距）」、「良率/成本/性能三角权衡」、「人才稀缺与工艺 know-how 的 tacit 性」、「中国大基金/产能扩张是否过剩」、「制裁与技术封锁」。(h) 大量隐性工艺手艺（process recipe 调试与工艺窗口寻找、缺陷根因分析与 FA、量产良率爬坡的经验判

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

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

Structures technology diligence with architecture review, code quality assessment, scalability analysis, and technical debt evaluation. Use when evaluating startup technology, assessing engineering teams, or reviewing technical infrastructure.

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

Technical Analysis skill — price action, indicators (RSI/MACD/Stochastic), chart patterns, support/resistance, volume, Bollinger Bands, and relative strength vs SPY. Returns Technical Score (0-100). Triggered by "trade technical <TICKER>".

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

Use when you need to answer "which attacker techniques do our controls actually stop, and how well?", "what controls should I have for this threat?", or "what telemetry should I collect to detect it?" — joining a customer's or your own security control baseline to ATT&CK techniques using a public, versioned evidence base of 9,545 control-to-technique mappings from six sources. Produces four ranked lists (addressed strongly, addressed weakly, real gaps, and techniques no control anywhere addresses). Use for control gap analysis, security programme prioritisation, board reporting on coverage, or the Resistance Strength side of a FAIR risk assessment. Invoke after /threat-actor-profiling or /lookup-liberty91 has produced a technique list.

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