6,912 件 ・ 関連度順
概要と使いどころ
Startup Launch Day Playbook — Hour-by-hour execution checklist for your big launch day. Covers timezone timing, channel sequencing, real-time crisis management, and post-launch momentum. By @WeiYipei.
日本語の概要は準備中です。原文の説明を表示しています。
Design viral loops into your product — referral programs, invite systems, and share mechanics that drive exponential growth. Includes K-factor calculations and real examples from Dropbox, Slack, and Notion. By @WeiYipei.
日本語の概要は準備中です。原文の説明を表示しています。
First AI Product Launch — Zero to Live in 30 Days. Step-by-step guide for shipping your first AI product from idea validation to paying customers. Includes day-by-day timeline and real examples. By @WeiYipei.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
How a downstream app consumes the shared @kolu/surface stack (@kolu/surface · surface-app · surface-remote · surface-mcp) — declaring a typed reactive surface, serving it, consuming it (SolidJS hooks or a CLI), and mirroring a remote surface over ssh. Grounded in the real consumers: kolu, drishti, odu, and the TUIs. Load when wiring a surface server/client/mirror, or reaching for makeSession / a link / the `.use()` hooks. CHANGING the framework is gated separately — `.claude/rules/surface.md` (a paired, CI-green drishti PR pinned to final kolu HEAD).
日本語の概要は準備中です。原文の説明を表示しています。
Provision and drive a `pu` box — an Incus container used as a clean Linux host for CI, builds, and evidence capture. Use when you need to run something on a fresh remote box instead of the user's machine: `nix run` a build, run CI against a real host, capture screenshots/video off-machine, or reproduce on a pristine environment. Covers create/connect/scp/destroy, running remote commands, copying artifacts back, and the no-egress failure mode. Triggers on "pu box", "spin up a box", "run this on a box", "ephemeral host", "pu create/connect/destroy".
日本語の概要は準備中です。原文の説明を表示しています。
Write a kolu blog post grounded in the real build history — mine the Claude Code session logs behind a feature for the actual story (for large efforts, fan out over the transcripts with an ultracode workflow), draft it in the author's voice, and wire it into the Astro site. Use when asked to write a blog post or engineering essay about something that was built, especially one that should read as a narrative of what actually happened rather than invented marketing copy.
日本語の概要は準備中です。原文の説明を表示しています。
确认漏洞后产出正式 SRC/0day 提交稿 DOCX 报告的收口 skill。仅在漏洞已确认、准备成稿时使用——负责查重、过分层验证门、按固定 DOCX 骨架生成报告（Heading 2 章节 + Step 式 PoC + 内嵌真实截图）、语义化命名、放对目录、处理驳回追加。不负责挖掘/验证漏洞本身。TRIGGER：用户说"写报告/出报告/成稿/提交稿/生成漏洞报告"，或漏洞已验证到位准备交付时；或 /report。EN: Turns confirmed vulnerabilities into submission-ready DOCX reports for SRC/0day platforms (verification gates, fixed layout, step-style PoC, mandatory real screenshots). Trigger on "write report" or /report.
日本語の概要は準備中です。原文の説明を表示しています。
Semi-automated fact-checking, source credibility evaluation, misinformation detection, prebunking, and evidence-ledger based claim verification. Use when a user asks to verify a claim, article, social post, screenshot, URL, quote, data point, compare sources, detect manipulation, evaluate source reliability, or generate an HTML fact-check card/share-safe correction. Supports text, URLs, screenshots/images, two-source comparison, and topic-level prebunking in Bulgarian, English, Russian, EU policy, health, science, and geopolitical contexts. Trigger phrases: "is this true?", "is this fake?", "fact check this", "compare these sources", "проверка на факти", "истина ли е", "дезинформация ли е", "сравни тези източници".
日本語の概要は準備中です。原文の説明を表示しています。
ADB-based RIPDPI device/emulator debugging: build/install/launch, logcat filtering, fixture port-forwarding, instrumented tests, crash/ANR triage. Use when debugging on a real device or emulator.
日本語の概要は準備中です。原文の説明を表示しています。
Reference for the ripdpi-dns-resolver crate: DoH/DoT/DNSCrypt/DoQ/ODoH, health scoring, bootstrap IPs, tamper diagnostics. Use when touching encrypted DNS resolution, failover, or tamper detection.
日本語の概要は準備中です。原文の説明を表示しています。
Act as an end-to-end data scientist: turn business questions into defensible analysis, validated models, and decision-ready reports. Use whenever the user asks to analyze, explore, or profile a dataset or CSV/Parquet/Excel file; asks what drives a metric or why a number changed ("why did churn go up?"); wants to test whether a difference is real (A/B tests, experiments, "is this significant?", "how many samples do I need?"); wants a predictive model (churn, forecast, scoring, segmentation, classification, regression); asks to review an existing analysis, notebook, or model for flaws; or needs results written up for decision-makers. Triggers in any language ("phân tích dữ liệu", "xây model dự đoán", "kiểm định A/B"), even when they never say "data science" or "statistics".
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and explain bmad-loop run artifacts under `.bmad-loop/runs/`. Use for live health checks ("is it stuck?", "is the loop alive?", "what is the agent doing?") and post-run forensics ("what happened?", "why did story X fail?", "where did the tokens go?"). Also triggers on "monitor/check/summarize the loop", "why did the run pause?", Vietnamese "theo dõi bmad loop", "phân tích run", "đọc log của run", and equivalent requests in other languages. Use only for bmad-loop's own run artifacts, not application runtime logs or CI-provider build logs.
日本語の概要は準備中です。原文の説明を表示しています。
Act as the team's Scrum Master of record, or copilot to a human one: plan sprints, run daily pulses, close sprints, prepare and follow up retrospectives, track and escalate impediments, and detect process anti-patterns across sprint history. Use whenever the user asks for Scrum or agile process help, in any language — "plan the sprint", "chuẩn bị retro", "how is the sprint going", "our velocity dropped", "track this blocker", "the same problem keeps coming back" — even without the word "Scrum", and whenever `_project/scrum-master/` exists and the question touches sprints, ceremonies, impediments, or team process health. Not for delivery dates and budget (project-manager) or deciding what to build (product-manager).
日本語の概要は準備中です。原文の説明を表示しています。
Investment portfolio analyzer. Audits current allocation vs target, asset class diversification (stocks, bonds, real estate, alternatives), expense ratios, tax efficiency, rebalancing needs, factor tilts (value, momentum, quality), three-fund portfolio fit, target-date fund analysis, and Boglehead-style optimization. Produces FINANCE-PORTFOLIO.md with a portfolio score, specific rebalancing trades, and fund swap recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Retirement projection with Monte Carlo simulation logic. Calculates required nest egg via 4% rule and 25x expenses, projected vs needed gap, contribution recommendations, asset allocation by age, Social Security claim optimization, healthcare cost projections, and withdrawal sequence planning. Use when the user says "/finance retirement", "am I on track for retirement", "how much do I need to retire", "Social Security timing", or any retirement question.
日本語の概要は準備中です。原文の説明を表示しています。
Professional PDF financial plan generator. Scans current working directory for FINANCE-*.md files, extracts scores and financial data, then runs the bundled Python ReportLab script to produce a polished, client-ready PDF with cover page, Financial Health Score gauge, score breakdown, cash flow, debt, retirement, portfolio, and prioritized action plan. Output: FINANCE-PLAN.pdf.
日本語の概要は準備中です。原文の説明を表示しています。
60-Second Financial Snapshot — fast assessment of financial health based on six core inputs (income, expenses, savings, debt, age, retirement goal). No subagents. Produces a compact terminal scorecard with savings rate, DTI ratio, emergency fund coverage, retirement on-track status, and top 3 priority actions in under 40 lines.
日本語の概要は準備中です。原文の説明を表示しています。
Ein evidenzbasiertes, tragfähiges Content-Portfolio für Zielgruppen, Geschäftsziele, Distribution und die real vorhandene Produktionskapazität planen. Nutze diesen Skill für Content-Strategien, Themenfelder, Redaktionspläne und Backlogs, für die Diagnose eines bestehenden Contentbestands, für die Abbildung von Kauf- und Nutzungswegen und für Entscheidungen zu CMS und Governance. Priorisiert offen nach Nachfrage, Aufwand und Evidenz, schützt vor dünnen Massenseiten und benennt Belegklassen. Einzelne Texte schreibt copywriting, die technische Prüfung macht seo-audit.
日本語の概要は準備中です。原文の説明を表示しています。
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never treat another vendor's session ID as portable.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous novel writing CLI agent with web workbench (JiaOS Studio) - use for creative fiction writing, standalone short-fiction packages, cover generation, novel generation, style imitation, chapter continuation/import, EPUB export, AIGC detection, and fan fiction. Native English support with 10 built-in English genre profiles (LitRPG, Progression Fantasy, Isekai, Cultivation, System Apocalypse, Dungeon Core, Romantasy, Sci-Fi, Tower Climber, Cozy Fantasy). Also supports Chinese web novel genres (xuanhuan, xianxia, urban, horror, other). Multi-agent pipeline, two-phase writer (creative + settlement), stronger long-form chapter craft rules, hook-ledger payoff checks, 33-dimension auditing, token usage analytics, creative brief input, structured logging (JSON Lines), multi-model routing, custom OpenAI-compatible provider support, and JiaOS Studio web UI for visual book management, short-fiction runs, cover generation, chapter review, real-time writing progress, market radar, and analytics.
日本語の概要は準備中です。原文の説明を表示しています。
Simulate pending Sealevel (SVM) warp-route governance txs — signed directly or via a Squads multisig — by forking Solana mainnet locally with surfpool, replaying the exact transactions, then running warp check against the desired registry config. Use to verify that a not-yet-submitted SVM governance change produces the intended on-chain config before it is signed/executed.
日本語の概要は準備中です。原文の説明を表示しています。
The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.
日本語の概要は準備中です。原文の説明を表示しています。
Create, check, and read on-chain Sealevel (SVM) Address Lookup Tables (ALTs) for a warp route. Use after deploying, extending, or upgrading an SVM warp route, when transfers fail with transaction-too-large errors, or when asked to inspect or verify a route's ALTs. Fee-enabled SVM transfers bundle 40+ accounts and require ALTs to fit under the 1232-byte tx limit.
日本語の概要は準備中です。原文の説明を表示しています。