1,528 件 ・ 関連度順
概要と使いどころ
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Access 20+ years of global financial data: equities, options, forex, crypto, commodities, economic indicators, and 50+ technical indicators.
日本語の概要は準備中です。原文の説明を表示しています。
Add GitHub permalinks with fixed SHA/commit references to research documentation containing code snippets. Use when writing technical docs with code examples, creating investigation/research docs that reference source files, user asks to "add permalinks" or "add GitHub links", documenting code research findings with file:line references, or creating audit trails needing permanent code references. Triggers on "add github links", "add permalinks", "link to source", "make code references permanent".
日本語の概要は準備中です。原文の説明を表示しています。
Multi-timeframe crypto technical analysis with scored trading signals, structured trade plans, and position sizing via Binance public API. Use when user asks to "analyze BTC", "what's the signal on ETH/USDT", "crypto analysis", "trade setup for SOL", "scan crypto pairs", "check the trend on BTC", "multi-timeframe analysis", "generate a trading signal", "what's the bias on ETH", "TA on BTC/USDT", "is it a good time to buy BTC", or "position size for a crypto trade".
日本語の概要は準備中です。原文の説明を表示しています。
Generates sourced, BDR-ready account research briefs for named target accounts in B2B SaaS ABM and outbound motions. Use after a target account list is built and before outreach sequences are written. Best for Tier 1, Tier 2, and intent-qualified accounts where BDRs need a clear "why this account, why now, why this persona" hypothesis. Designed for B2B SaaS teams selling compliance, security, GRC, risk, or other technical platforms into mid-market and enterprise buyers. Not intended for broad list building or mass enrichment.
日本語の概要は準備中です。原文の説明を表示しています。
Produces and audits externally published marketing copy where factual claims must survive scrutiny — landing pages, product pages, launch emails, one-pagers, search/social metadata. Every statistic, competitor comparison, capability description, and proof point is traced to a fetched source or the project's own documents, labeled, and adversarially verified before it ships. Use when writing or rewriting high-stakes marketing copy; when copy must pass legal, compliance, brand, or claims review; when the audience is skeptical technical or executive buyers; when the company has little or no customer proof yet (pre-launch, zero customers); or when auditing existing copy for unsupported claims, invented capabilities, unverified statistics, or AI-slop language.
日本語の概要は準備中です。原文の説明を表示しています。
Build structured communication templates for malware incidents including stakeholder notifications, executive briefings, technical advisories, and regulatory disclosures with severity-based escalation procedures.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
日本語の概要は準備中です。原文の説明を表示しています。
Code refactoring strategies, technical debt reduction, architecture modernization, and code quality improvement. Use when refactoring code, modernizing legacy code, reducing complexity, or improving maintainability.
日本語の概要は準備中です。原文の説明を表示しています。
Audit technical SEO — meta tags, structured data, Open Graph, sitemaps, robots.txt, performance, and accessibility signals.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Document technical decisions as Architecture Decision Records (ADRs) with context, options considered, and rationale.
日本語の概要は準備中です。原文の説明を表示しています。
Designs genomics experiments so technical nuisance variation (batch, lane, plate, flow cell, operator, reagent lot, processing day) is balanced against the biological variable of interest and therefore estimable rather than confounded, using constrained sample-to-batch assignment (designit, OSAT), the confounder/mediator/collider distinction, and the principle that no post-hoc correction recovers a fully confounded design. Covers detecting hidden batches with surrogate variable analysis, a decision table for downstream correction (ComBat-seq, RUVSeq, SVA) whose execution is deferred to differential-expression/batch-correction, and reproducibility metadata. Use when assigning samples to sequencing batches/lanes/plates, avoiding batch-condition confounding, deciding whether a design is salvageable by correction, choosing a correction method, or estimating the number of hidden batches. For the experimental unit, randomization, and blocking concepts see experimental-design/randomization-blocking.
日本語の概要は準備中です。原文の説明を表示しています。
Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"
日本語の概要は準備中です。原文の説明を表示しています。
Draft Stellar Community Fund Build Award applications interactively. Use when helping teams write their SCF submission — walks through project description, Stellar integration rationale, technical architecture, team section, deliverables, budget, and traction evidence. Produces a complete draft aligned with what funded projects look like.
日本語の概要は準備中です。原文の説明を表示しています。
System architect and technical design leader. Use when the user asks to talk to Tyler or requests the architect.
日本語の概要は準備中です。原文の説明を表示しています。
Review Stellar Community Fund (SCF) Build Award applications. Use when evaluating SCF submissions, covering project fit assessment, technical architecture evaluation, team readiness, traction validation, budget analysis, and funding recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Technical documentation specialist and knowledge curator. Use when the user asks to talk to Bri or requests the tech writer.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch external documents linked in SCF submissions — Google Docs, Google Drive PDFs, GitHub, Notion, IPFS. Use when a submission links to an architecture doc, whitepaper, or technical spec hosted externally. Handles URL transformation for Google services.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
日本語の概要は準備中です。原文の説明を表示しています。
Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a professional product specification sheet with images, feature tables, technical specs, and contact information.
日本語の概要は準備中です。原文の説明を表示しています。
Extract vehicle identification, owner details, registration dates, and technical specifications from vehicle registration documents.
日本語の概要は準備中です。原文の説明を表示しています。