300 件（tonone-ai のリポジトリ） ・ 人気順
概要と使いどころ
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".
日本語の概要は準備中です。原文の説明を表示しています。
Design a caching strategy for an application — pattern selection, key design, TTL, and eviction policy. Use when asked to "add caching to this", "design a cache strategy", or "what should we cache".
日本語の概要は準備中です。原文の説明を表示しています。
Audit UX copy in a product or codebase — find passive errors, generic labels, missing states. Use when asked to "audit our UX copy", "our error messages are bad", or "review the microcopy".
日本語の概要は準備中です。原文の説明を表示しています。
ML reconnaissance — inventory all models, pipelines, data sources, and monitoring. Use when asked "what ML do we have", "model inventory", or "ML assessment".
日本語の概要は準備中です。原文の説明を表示しています。
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
日本語の概要は準備中です。原文の説明を表示しています。
Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".
日本語の概要は準備中です。原文の説明を表示しています。
Design a data cleaning and transformation pipeline — missing values, outliers, and deduplication. Use when asked to "clean this dataset", "handle missing values", or "deduplicate this data".
日本語の概要は準備中です。原文の説明を表示しています。
Generate negotiation playbook for a specific contract type. Use when asked to "build a negotiation playbook", "how do we negotiate this clause", or "what are our fallback positions".
日本語の概要は準備中です。原文の説明を表示しています。
Build a forecasting model for a time series — demand, revenue, or usage prediction. Use when asked to "forecast demand", "predict next quarter revenue", or "build a time series model".
日本語の概要は準備中です。原文の説明を表示しています。
Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".
日本語の概要は準備中です。原文の説明を表示しています。
Survey legal artifacts for audit readiness. Use when asked "are we audit ready", "what legal artifacts exist", or "survey our legal docs".
日本語の概要は準備中です。原文の説明を表示しています。
Design escalation path -- Tier 1 to Tier 2 to Engineering handoff, decision criteria, and communication templates. Use when asked to "design our escalation process", "when should support escalate to engineering", "build an escalation runbook", or "reduce escalation rate".
日本語の概要は準備中です。原文の説明を表示しています。
Run a compliance gap analysis against SOC2, GDPR, HIPAA, or ISO 27001. Use when asked "are we SOC2 ready", "run a GDPR gap analysis", or "what is missing for ISO 27001".
日本語の概要は準備中です。原文の説明を表示しています。
Design a performance benchmark for an API — test scenarios, metrics, and tooling. Use when asked to "benchmark this API", "design a load test", or "measure throughput".
日本語の概要は準備中です。原文の説明を表示しています。
Survey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues. Use when asked "how accessible is our codebase", "find accessibility debt", or "where are our a11y gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Internal legal controls review — approval workflows, contract lifecycle, access to sensitive docs. Use when asked to "audit our controls", "review approval workflows", or "who can access sensitive contracts".
日本語の概要は準備中です。原文の説明を表示しています。
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
日本語の概要は準備中です。原文の説明を表示しています。
Full legal compliance audit — contracts, policies, regulatory, IP, corporate hygiene. Use when asked to "run a legal audit", "are we legally compliant", or "full compliance review".
日本語の概要は準備中です。原文の説明を表示しています。
Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.
日本語の概要は準備中です。原文の説明を表示しています。
Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
日本語の概要は準備中です。原文の説明を表示しています。
Audit AI spend — per-model cost breakdown, top consumers, waste identification, optimization levers. Use when asked "why is our AI bill so high", "audit LLM spend", or "where is our token waste".
日本語の概要は準備中です。原文の説明を表示しています。
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
日本語の概要は準備中です。原文の説明を表示しています。