「rtm」の検索結果

Use when publishing, open-sourcing, exporting, sanitizing, or moving code, agent skills, prompts, templates, fixtures, datasets, workshop assets, or other artifacts from a private repository, vendor/runtime environment, or mixed working directory into a public repository or registry. Builds a provenance inventory, license/security review, explicit allowlist, clean staging package, approval dry run, and fresh public clone/install smoke. Triggers on "open source this", "publish these skills", "make this repo public", "export and sanitize", "подготовь публичный релиз", "выложи скиллы", "опенсорсни", "санитизируй и опубликуй". NOT for ordinary upstream bugfix PRs, vulnerability disclosure, or creating a corp-* department.

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

Use when the user asks "что сегодня", "задачи на сегодня", "план на день", or wants the current department's living weekly plan refreshed from task facts.

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

Use when a completed department retro should become accepted outcomes and a full living ISO-week plan, or the user asks "планирование", "план недели", or "что делаем на следующей неделе".

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

Use when the user asks for "ретро", "обзор недели", or "что было за неделю" and the department needs a fact-based closeout plus its next Area goal.

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

Classify expenses by category, department, and tax deductibility from transaction data. Use when the user requests expense categorization or provides relevant inputs for this workflow.

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

Create and manage budgets with variance analysis and departmental allocation. Use when the user requests budget planning or provides relevant inputs for this workflow.

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

Think and work like an expert Fire Protection Engineer. Use when a task calls for Fire Protection Engineer judgment. Reasons from NFPA 13 Hazen-Williams hydraulics (K-factor, remote area, hose stream) and NFPA 101 egress (occupant load, travel distance, capacity factors) through NFPA 92 smoke containment/management, ASET/RSET PBD, and FDS/CFAST/CONTAM/PyroSim modeling while treating breached compartmentation, C-factor/fitting errors, and supply-curve shortfall as first-class failure modes.

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

Think and work like an expert Composites Engineer. Use when a task calls for Composites Engineer judgment. Reasons from CLT/ABD laminate mechanics, Halpin–Tsai micromechanics, and CMH-17/NCAMP allowables through autoclave/OOA/RTM process control, ASTM D30 mechanical qualification, ultrasonic C-scan and CAI damage tolerance while treating fiber waviness, void content, under-cure, and quasi-isotropic strength traps as first-class failure modes.

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

Think and work like an expert Cell Biologist. Use when a task calls for Cell Biologist judgment. Reasons from compartment thermodynamics, membrane electrophysics, and necessity-plus-sufficiency logic through STR authentication, confocal/TIRF imaging, CRISPR and siRNA perturbation with rescue, and Western blot, treating mycoplasma, passage and serum-lot drift, edge effects, antibody cross-reactivity, siRNA seed off-targets, and well-as-n pseudoreplication as first-class failure modes.

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

Workflow for Hi-C and related 3D genomics analyses including compartments, loops, TADs, differential contacts, and visualization.

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

World-class growth strategy expertise combining Andrew Chen's marketplace and network effects wisdom, Brian Balfour's growth frameworks, Casey Winters' Pinterest/Grubhub playbooks, and the best of Silicon Valley growth thinking. Growth is not marketing. Growth is the systematic application of product, engineering, and data to create compounding user acquisition, activation, and retention. It's a mindset, not a department. Use when "growth strategy, how do we grow, acquisition strategy, retention strategy, viral growth, network effects, growth loops, product-led growth, plg, ltv cac, unit economics, growth model, flywheel, compound growth, channel strategy, referral program, activation rate, magic moment, aha moment, growth experimentation, growth, strategy, acquisition, retention, viral, network-effects, plg, loops, experimentation" mentioned.

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

独立开发者与微型 SaaS — 单人或极小团队 (≤3 人) 构建可持续订阅收入的软件产品商业, 有别于自由职业/咨询、企业级 SaaS 和开源维护: (a) 产品发现与验证 (自己的痒 vs 市场优先 Nugent/Walling; 着陆页冒烟测试; 先接 Stripe 再写代码; JTBD 访谈适配独立开发者场景; Reddit/HN/X/社区痛点挖掘; Mom Test 验证框架; 公开构建作为验证机制); (b) 独立开发者技术架构 (无聊技术论 McKinley; 单体优先; serverless vs VPS 在 ≤$100/月预算下的取舍; Rails/Django/Laravel/Next.js 等框架的出货速度选型; 托管服务优先于自建; Supabase/PlanetScale/Neon 数据库即服务; Clerk/Auth0 认证即服务; Stripe/Paddle/LemonSqueezy 支付; Vercel/Fly.io/Railway 部署; AI 辅助编码 Cursor/Copilot 作为力量倍增器); (c) 无营销团队的分发与增长 (SEO 作为微型 SaaS 护城河; Product Hunt 发布; AppSumo 终身授权利弊; 冷邮件; Twitter/X 公开构建; IndieHackers 社区分发; 集成市场 Shopify/WordPress/Zapier/Slack 应用目录; 联盟计划; 一人内容营销); (d) 定价与变现 (SaaS 定价心理学; freemium vs 免费试用 vs 纯付费; 按席位 vs 按用量 vs 固定费率; 年付折扣; 老用户保价; 微型 SaaS 流失率控制; MRR/ARR/LTV/CAC 在微型规模的含义; $10K MRR 里程碑心理学); (e) 独立创始人心智模型与生活设计 (default alive vs default dead Graham; 拉面盈利 Levels; 生活方式生意 vs 增长生意的光谱; 独立开发者倦怠预防; 时间管理与上下文切换成本; 地理套利与远程优先; 一次构建反复销售的资产思维; 社区作为支持网络 IndieHackers/WIP/MicroConf); (f) 法务与运营基础 (公司注册地选择 LLC/Ltd/GmbH 税效; Stripe Atlas vs Firstbase vs 本地律师; 服务条款与隐私政策; GDPR/CCPA 低成本合规; 知识产权基础; 首次雇人的承包商 vs 员工选择; 独立开发者会计 SaaS — Xero/QuickBooks; 多辖区税务义务)。中国独立开发者生态: 出海作为主导策略 (从中国构建面向全球市场的产品以避开国内竞争/监管); 即刻/V2EX/少数派作为社区枢纽; 微信小程序作为替代分发; 小报童/爱发电作为中文市场变现; 人民币定价心理学; 支付宝/微信支付集成; ICP 备案要求; 中国区 App Store 审核差异; 独立开发者周刊。诚实处理: 生存偏差 (每一个 Pieter Levels 背后是数千个从未达到 $1K MRR 的人), AI 对微型 SaaS 生态位的颠覆 (wrapper 产品脆弱), 独自构建的孤独与心理健康成本, 公开构建的表演性质 vs 真正透明, AppSumo 终身授权上瘾毁坏单位经济, 样板代码销售的伦理边界。不含: 企业级 SaaS (不同 GTM/销售/融资模型), 不含: 自由职业/咨询 (用时间换钱非建资产), 不含: 开源维护 (不同可持续性模型), 不含: 风投支持的创业 (不同增长期望), 不含: 无代码/低代码平台构建 (相邻但不同受众), 不含: 内容创作作为主业。 (Independent Developer and Micro-SaaS — the craft of single-person or tiny-team (≤3 people) software product businesses that generate sustainable recurring revenue without venture capital, distinct from freelancing/consulting, enterprise SaaS, and open-source maintainership: (a) product discovery and validation (scratching your own itch vs market-first Nugent/Walling; landing page smoke tests; Stripe checkout before code; Jobs-to-Be-Done interview adapted to solo context; Reddit/HN/X/community pain-point mining; idea validation frameworks Fitzpatrick Mom Test; build-in-public as validation mechanism); (b) technical architecture for solo operators (boring technology thesis Mckinley; monolith-first; serverless vs VPS tradeoffs for ≤$100/mo infra; framework selection for shipping speed — Rails/Django/Laravel/Next.js/Remix/SvelteKit; managed services over self-hosted whenever possible; database-as-a-service Supabase/PlanetScale/Neon/Turso; auth-as-a-service Clerk/Auth0/Supabase Auth; payment integration Stripe/Paddle/LemonSqueezy; deployment Vercel/Fly.io/Railway/Render; monorepo vs polyrepo for solo; AI-assisted coding Cursor/Copilot as force multiplier); (c) distribution and growth without a marketing team (SEO as moat for micro-SaaS Ahrefs-style content marketing on 1-person budget; Product Hunt launches; AppSumo lifetime deals tradeoffs; cold email outreach; Twitter/X building in public; IndieHackers community distribution; integration marketplaces Shopify/WordPress/Zapier/Slack app directories as channels; affiliate programs; content marketing at scale-of-one); (d) pricing and monetization (SaaS pricing psychology Patel/Campbell; freemium vs free trial vs paid-only; per-seat vs usage-based vs flat-rate; annual discount strategies; grandfathering existing customers; churn reduction for micro-SaaS — Baremetrics/ProfitWell/ChartMogul analytics; MRR/ARR/LTV/CAC at micro scale; the $10K MRR milestone psychology); (e) solo founder mental model and lifestyle design (default alive vs default dead Graham; ramen profitability Levels; lifestyle business vs growth business spectrum; burnout prevention for solo operators — no team to delegate to; time management and context-switching costs; geographic arbitrage and remote-first; the 'build once sell twice' asset mindset; community as support network IndieHackers/WIP/MicroConf); (f) legal and operational basics (incorporation LLC/Ltd/Gm

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

Routes, triages, flags and rates a piece of text with a probability for every option: which department or queue a ticket goes to, which intent a message expresses, whether a yes/no condition holds (is this tool call grounded, should the agent ask first, is the customer angry), and how severe or urgent it is on a rubric, each with a calibrated confidence. Runs Claude Haiku in the request and response shapes of OpenAI's Decisions API, for when no purpose-built decision model is at hand. Use for "route this ticket", "triage these", "classify with a confidence", "give me a probability that", "rate the severity", "score against this rubric", guardrail checks before a tool call, or "a Decisions API without OpenAI".

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

Use this skill whenever reasoning about immunology, host-pathogen interactions, innate immunity, Toll-like receptors (TLRs), or experimental design in molecular biology. It is also highly relevant for scientific career strategy, particularly when discussing independence, pivoting research domains, or using reverse genetics (like knockout mice) for discovery. Channel Shizuo Akira, immunologist and pioneer of pattern-recognition receptors, to apply rigorous experimental standards (e.g., demanding chemically synthesized mimics over purified extracts) and to view innate immunity as a highly specific, compartmentalized system rather than a primitive defense.

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

Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.

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

This skill should be used when the user asks about "production management", "film budget", "scheduling", "crew management", "location logistics", "risk assessment", "act as a production manager", "production manager mode", "line producing", "production budget", "crew roles", "film insurance", "production timeline", "location permit", "production paperwork", or needs expertise in film budgets, production scheduling, crew management, location logistics, and risk mitigation for film projects. Part of the AlterLab FC Skills collection (Cinema & Digital Media department).

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

Design or review annual operating budget — headcount plan, departmental spending, revenue targets, and variance tracking. Use when asked to "build our budget", "plan headcount for next year", or "review our spending".

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

Foundational concepts in nutrition science — macronutrients, micronutrients, energy balance, Atwater factors, reference intakes (DRI/RDA/AI/UL), food composition tables, and the methods of human nutrition research. Grounds the rest of the department in a shared vocabulary and in the measurement limits of the field, including controlled-trial history, observational-study limits, and the biochemical basis for calorie accounting. Use when a question asks what something "is" nutritionally, how energy and nutrients are measured, or what the reference numbers mean.

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

A survey of the best-known active scientific controversies in nutrition — saturated fat and cardiovascular disease, dietary cholesterol, low-carb vs low-fat, ultra-processed foods, red meat and cancer, salt and blood pressure, and the replication status of popular single-nutrient claims. Use when a question asks whether a widely reported nutritional claim is settled, or when the department needs to distinguish "contested but plausible" from "settled" from "disproven."

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

Comparative framing across contemplative and mind-body traditions — Sōtō Zen and Rinzai Zen, Theravada vipassana, Tibetan Vajrayana, classical yoga and its eight limbs, Daoist internal cultivation, secular MBSR and MBCT, engaged mindfulness as Thich Nhat Hanh teaches it, Christian contemplative prayer, Sufi dhikr, the Hesychast tradition of the Eastern Orthodox church — for the routing agent who has to understand where a user is already standing before recommending a practice. Covers the pedagogical voice of each tradition, the places they overlap, the places they genuinely disagree, and the non-sectarian framing the college department uses. Use when a user arrives with a prior tradition, when a query spans more than one tradition, or when the agent needs a vocabulary for what is shared and what is lineage-specific.

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

Use when the user asks to forge, scaffold, or author a new cartridge — content cartridge, department cartridge, or chipset bundle. Drives the cartridge-forge loop (scaffold → fill → gate checks → commit) via the skill-creator cartridge CLI.

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

OpenStack monitoring operations skill for deploying, configuring, and operating the cloud health monitoring stack. Covers Prometheus metric collection and scrape targets, Grafana dashboard provisioning and visualization, Alertmanager notification channels and routing, alerting rules for service health and resource exhaustion, service endpoint health checks, log aggregation strategies, SLA tracking with availability and response time percentiles, and capacity trend analysis from historical metrics. Use when deploying monitoring via Kolla-Ansible, configuring alert thresholds, troubleshooting blank dashboards, tuning noisy alerts, or analyzing cloud performance trends.

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

Create parameterized Quarto or R Markdown reports that can be rendered with different inputs to generate multiple variations. Covers parameter definitions, programmatic rendering, and batch generation. Use when generating the same report for different departments, regions, or time periods; creating client-specific reports from a single template; building dashboards that filter to specific subsets; or automating recurring reports with varying inputs.

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

Fix missing theorem proof terms when analyzing Lean 4 environments via importModules. Use when: (1) ConstantInfo.value? returns none for theorems despite TheoremVal.value being Expr, (2) building code graph / dependency extractor for Lean 4 and getting 0 proof dependency edges, (3) Lean 4.30+ project where theorem proofs appear missing from loaded environment, (4) analyzing Mathlib or any Lean 4 project and proof terms are empty. Root cause: breaking change in Lean 4.30 — value? treats theorems as opaque by default.

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