527 件 ・ 関連度順
概要と使いどころ
Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences. Use when writing or repairing outbound email to qualified prospects. NOT FOR: building or qualifying the prospect list (use suede-prospecting), lifecycle or nurture email (use suede-emails), or broader sales collateral (use suede-sales-enablement).
日本語の概要は準備中です。原文の説明を表示しています。
Suede-owned retention discipline for voluntary and involuntary churn: cancel flows, pause paths, evidence-based save offers, failed-payment recovery, proactive signals, and win-back design. Use when diagnosing subscriber loss or designing a bounded retention intervention. NOT FOR: lifecycle-email production (use suede-emails), pricing architecture (use suede-pricing), paywall design (use suede-paywalls), or event instrumentation (use suede-analytics).
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Unreal Engine 5 C++ - the gameplay framework classes and where logic belongs, UObject/AActor/UActorComponent lifecycle, UPROPERTY/UFUNCTION and GC-safe pointers (TObjectPtr, TWeakObjectPtr), subsystems, the C++/Blueprint boundary, Enhanced Input, tick discipline, and compiling from the command line.
日本語の概要は準備中です。原文の説明を表示しています。
Root-cause debugging discipline. Use when a test, build or pipeline fails, behaviour does not match expectations, a bug task arrives, or a task comes back in need_revision — before proposing any fix.
日本語の概要は準備中です。原文の説明を表示しています。
Test-first discipline and what makes a test worth keeping. Use when implementing any feature or bug fix, before writing production code, and whenever writing or changing a test.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze startups with Paul Graham mindset (pressure, founder-market fit, brutal validation), Dan Koe discipline (monetization, offer, distribution, sales), and Seth Godin principles (differentiation, narrative, smallest viable audience). Triggers on startup idea, business validation, MVP, first customers, revenue model, GTM, product-market fit, "I have an idea".
日本語の概要は準備中です。原文の説明を表示しています。
用户在考虑是否卖出持仓、评估持有期限，或纠结于"何时卖出"时。 语言信号:"什么时候该卖"/"持有多久合适"/"已经涨了要不要卖"/"什么时候止盈" 不适用于:短期交易决策或投机性持仓的卖出判断。
日本語の概要は準備中です。原文の説明を表示しています。
Email/SMS lifecycle and deliverability framework for SMB Product-Builder products that send transactional or lifecycle messages (booking reminders, CRM sequences, receipts, win-back). Codifies provider selection (Resend/Postmark/Twilio/SendGrid), domain auth (SPF/DKIM/DMARC), consent and compliance (TCPA, CAN-SPAM, CASL, quiet hours, double opt-in), suppression-list discipline, and the transactional-vs-marketing split. Applied by integrations-engineer and senior-dev whenever a feature sends messages — so deliverability and consent are designed in, not bolted on after the first spam complaint.
日本語の概要は準備中です。原文の説明を表示しています。
The Execution Trader's procedure for turning an approved ticket into one Hyperliquid action and reconciling it - the pre-send checklist, order construction rules, single-send discipline, unknown-result handling and the execution report. Use before and after every send, cancel, modify, leverage change or close.
日本語の概要は準備中です。原文の説明を表示しています。
Anchor a multidisciplinary unit in a real-world phenomenon that requires multiple subject lenses to understand. Use when designing integrated or phenomenon-based units across disciplines.
日本語の概要は準備中です。原文の説明を表示しています。
Design a sequence where students compare AI's handling of the same question across disciplines, developing a mental model of where AI is reliable vs. distorting based on knowledge type.
日本語の概要は準備中です。原文の説明を表示しています。
Apply evidence-first engineering discipline to any agent-built software project: fact discovery before action, evidence-calibrated status reporting, explicit change boundaries and stage gates, controlled confirmation for risky or external actions, sensitive-information redaction for anything shared publicly, and resumable continuity after interruptions. Use when users ask an agent to take over an existing codebase, deliver a feature across stages, verify whether work is actually complete, judge release readiness, or keep conclusions honest about what is proven versus assumed. This foundation skill is domain-neutral; vertical suites (for example mini-program engineering) build on it by adding domain facts and platform rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating biology grant ideas in the Chinese funding context (NSFC, MOST, etc.) — diagnosing project legitimacy, mechanism-centered scientific questions, reviewer-aware logic, innovation discipline, feasibility, and scope control across funding levels (youth, general, key).
日本語の概要は準備中です。原文の説明を表示しています。
Drive one AI agent from another through kolu's terminals: spawn a Claude Code / Codex / opencode session in a PTY, prompt it, watch the screen, read the reply, prompt again. PRIMARY PATH: the kolu MCP tools (`lifecycle_create`/`lifecycle_sendInput`, `wait_outputSettled`/ `wait_agentState`, `screen_text`, the `terminals` resource). FALLBACK: the `kolu` CLI — same verbs, same discipline. Triggers on "drive another agent", "agent drives agent", "make Claude drive Codex", or wiring a loop where one coding agent supervises another.
日本語の概要は準備中です。原文の説明を表示しています。
Golden-fixture contract discipline: locations, bless workflow, env vars, volatile-field scrubbing, failure-artifact triage. Use when a golden/snapshot test fails or a new golden fixture is added.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain the durable, per-ticket run log that warp deploy/update skills append to at every milestone — a Linear-document-by-title primary with single-writer discipline and a local-file fallback, a machine-parseable per-chain row plus prose entry shape, and a surface-the-URL-as-proof hard gate. Referenced by any warp deploy/update skill that must leave a retrospective trail across worker restarts.
日本語の概要は準備中です。原文の説明を表示しています。
Operate the Ryuumonbuchi MCP server for headless Ghidra reverse engineering. Use when driving decompilation, disassembly, patching, type and symbol recovery, memory edits, transactions, and Ghidra project analysis through a Ryuumonbuchi server (stdio or streamable HTTP). Covers the safe read-only-first workflow, session and address discipline, mutation and transaction rules, headless.run, task and error recovery, raw ghidra.call/ghidra.eval/ghidra.script escape hatches, and a sleep/timing-gate bypass recipe.
日本語の概要は準備中です。原文の説明を表示しています。
Following what organisms do — behavior, metamorphosis, host-plant relationships, social dynamics, and the long-form ethograms that reveal how species actually live. Covers the vocabulary of ethology, the structure of a life cycle, the classic categories of species interaction, the discipline of recording behavior without premature interpretation, and the gap between a single observation and a statistically useful record. Use when the task is to understand or record what a species does rather than what it is.
日本語の概要は準備中です。原文の説明を表示しています。
Birding by sight and sound — gestalt, song and call vocabulary, behavioral and habitat clues, and the discipline of producing eBird-grade records. Covers the vocabulary of bird field marks, the primary categories of vocalization, the habits of habitat-filtering, and the protocol for submitting records to a citizen-science database without degrading data quality. Use when the task is bird-specific observation or record-keeping.
日本語の概要は準備中です。原文の説明を表示しています。
Identifying species in the field using dichotomous keys, gestalt recognition, diagnostic features, and habitat context. Covers the working identification protocol from first encounter through confidence-rated record, the vocabulary of field marks, the discipline of negative evidence, and the honest reporting of uncertain IDs. Use when the task is to name a living organism encountered in the field.
日本語の概要は準備中です。原文の説明を表示しています。
Experience-based and environment-based learning design drawn from Dewey and Montessori. Covers Dewey's criterion of continuity and interaction, the reflective-thinking cycle, Montessori's prepared environment, sensitive periods, child-led inquiry, the role of self-correcting materials, project-based learning, and the relationship between autonomy and discipline. Use when designing hands-on activities, arranging learning spaces, integrating classroom work with real experience, or evaluating whether a lesson is genuinely experiential versus merely "activity-based."
日本語の概要は準備中です。原文の説明を表示しています。
Design and analysis of combinational and sequential digital circuits using Boolean algebra, truth tables, K-maps, CMOS gate implementation, flip-flops, registers, counters, and finite state machines. Covers De Morgan's theorems, canonical sum-of-products and product-of-sums forms, minimization techniques, propagation delay, setup and hold times, metastability, synchronous design discipline, and FSM encoding. Use when designing, minimizing, verifying, or debugging any circuit whose signals take only discrete logic values.
日本語の概要は準備中です。原文の説明を表示しています。
Computational thinking as a problem-solving discipline independent of programming languages. Covers the four pillars (decomposition, pattern recognition, abstraction, algorithm design), computational problem-solving methodology (understand, decompose, generalize, formalize, verify), abstraction levels (from hardware through user interface), modeling and simulation, automata and formal languages (DFA, NFA, regular expressions, context-free grammars, Turing machines), computational complexity classes (P, NP, NP-complete, undecidable), and constructionist pedagogy (learning by building, Logo, Scratch, physical computing). Use when approaching unfamiliar problems, teaching problem-solving strategies, analyzing problem complexity, or bridging between domain knowledge and computational solutions.
日本語の概要は準備中です。原文の説明を表示しています。
Reliability engineering for cloud systems — SLIs, SLOs, error budgets, SRE practices, runbooks, incident response, on-call rotation, blameless postmortems, chaos engineering, and the NASA Systems Engineering methodology (MCR/SRR/PDR/CDR/ORR phase gates, TAID verification, requirements tracing) adapted to cloud operations. Use when establishing SLOs for a new service, running an incident, writing a runbook, preparing a launch readiness review, or bringing NASA SE discipline to cloud deployments.
日本語の概要は準備中です。原文の説明を表示しています。