「three」の検索結果

Adversarial verification of research theses — cross-run/cross-thesis contradiction via the entity index, pre-mortem (Klarman/Kahneman: assume the loss already happened, reverse the path), inversion (Munger: invert, always invert), and wrong_if falsifiability review. ≈50-finding cap sorted by severity; content-derived finding IDs; incremental scoping with three backstops; lifecycle hooks at pillar-complete / thesis-complete / pre-reduction.

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

3-statement financial model, integrated IS BS CF, income statement projection, balance sheet forecast, cash flow statement, cross-statement balancing, financial model build, operating model, three statement model, integrated financial statements

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

Post-event analyst note (conferences, KOL events, site visits) with the professional note anatomy — headline verdict, per-stock takeaways with model numbers, KOL distillation, cross-trial comparison lattices, modeled deltas vs consensus (peak × POS), three what's-changed vectors, risk bullets, and materiality-rated conflicting views. Use after any med event to convert the event into actionable takeaways.

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

Institutional-grade equity research skills for AI agents. 80 Claude-type skills across 14 verticals (equity-research-core, models-and-pitches, bio-pharm, scenarios, quantitative-analysis, idea-generation, options-derivatives, business-intelligence, industry-analysis, macro-strategy, portfolio-strategy, technical-analysis, risk-and-psychology, trading-as-business) powered by agentii.ai's agent-use-ready SEC filing data plane — SEC filings and 15K+ earnings call transcripts, 15.99M XBRL facts, and company profiles for 1,146+ US-public-equity tickers. Features the three-layer retrieval protocol (Document Discovery → Page Map → Deep Read, with deep-outline escalation) — measured, not asserted: 97.5% saved against a sequential read, and the page map itself is 10.0% of one (spec 062 T030, 2026-09-23) — server-side parallel multi-period search via search_cross_period, a full Excel/PPT generation pipeline with 3-tier office backend support, and the spec-046 governance layer (constitution, thesis and single-skill modes, mechanical gates, and a template-owned disclaimer on generated reports).

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

Think and work like an expert Genetic Counselor. Use when a task calls for Genetic Counselor judgment. Reasons from probabilistic penetrance, Bayesian pretest probability, and patient autonomy through three-generation pedigrees, ACMG/AMP variant criteria, ClinVar/ClinGen/gnomAD, NCCN and CPIC guidelines, and cascade-testing protocols while treating VUS over-upgraded to pathogenic, screening-versus-diagnostic confusion (NIPT vs amnio/CVS), and unaddressed psychosocial and GINA discrimination risk as first-class failure modes.

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

Think and work like an expert Cosmochemist. Use when a task calls for Cosmochemist judgment. Reasons from oxygen three-isotope taxonomy (Δ17O), chondrite–achondrite classification, and presolar grain NanoSIMS through Meteoritical Bulletin curation, Al–Mg and Pb–Pb isochrons, CRE vs formation-age separation, and clean-lab sample prep while treating terrestrial weathering, mount contamination, and breccia mixing as first-class failure modes.

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

Think and work like an expert Bioprocess Engineer. Use when a task calls for Bioprocess Engineer judgment. Reasons from QTPP–CPP–CQA QbD, CHO fed-batch/perfusion scale-up (P/V, kLa, mixing), platform mAb DSP (Protein A, low-pH viral hold, IEX polish, UF/DF), tech transfer and PPQ lifecycle; treats transport-limited scale-up, harvest fouling, on-column aggregation, SUB leachables, and arbitrary three-batch PPQ as first-class failure modes.

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

Maps GWAS-implicated loci to candidate effector (causal) genes by integrating variant-to-gene (V2G) features via Open Targets L2G (Mountjoy 2021), MAGMA gene-based association (de Leeuw 2015), FUMA SNP2GENE, cS2G combined SNP-to-gene scores (Gazal 2022), Polygenic Priority Scores (PoPS, Weeks 2023), FLAMES, INQUISIT, DEPICT, and enhancer-gene predictors (ABC, ENCODE-rE2G). Use when narrowing a GWAS lead locus to a candidate causal gene, picking between proximity, eQTL-based, and similarity-based prioritizers, integrating multi-evidence streams (fine-mapping, colocalization, ABC enhancer-gene, distance, chromatin), reconciling discordant L2G vs PoPS calls, prioritizing tissue-specific eQTL evidence, or triangulating across at least three independent lines of evidence for a publication-grade effector-gene nomination.

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

Identifies differentially bound ChIP-seq regions between conditions using DiffBind, csaw (sliding windows), DESeq2/edgeR/PyDESeq2 on count matrices, NormR (control-aware), or MAnorm2. Distinguishes three distinct normalization problems (composition bias, trended bias, global shifts) and matches each to its appropriate fix including spike-in scaling. Use when comparing ChIP-seq binding between experimental conditions, choosing normalization for global vs local changes, integrating spike-in data, or reconciling DiffBind/DESeq2 disagreement.

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

An almost defiantly minimal documentation-first system that treats the home page like a Markdown README — paper-white canvas, 36px center-aligned heading, a single black pill CTA, an inline terminal install snippet, and a hand-drawn llama mascot as the only ornamental element. No gradient, no hero photography, no marketing pyrotechnics. The chrome is a tiny utility palette of pure black, pure white, and three neutral grays; every interactive element is fully rounded into a pill (`{rounded.full}`); typography is SF Pro Rounded for headings paired with system sans for body and ui-monospace for code. Pricing tiers, FAQs, and "your data stays yours" guarantees all sit on the same flat canvas inside thin-border cards — the system is the documentation, and the documentation is the system.

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

Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

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

Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design audit", or asks for a critique that should lead to a plan.

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

Use this skill for the architecture phases of an MBSE workflow in MATLAB, when writing idempotent buildXxx.m scripts that produce a three-layer RFLPV architecture (Functional, Logical, Physical) with interface dictionaries, stereotype profiles, allocation sets, and requirements Implement links. Trigger for defining stereotype properties, functional-to-logical / logical-to-physical allocation, mapping requirements to components via slreq Implement links, or running quantitative roll-up analysis on the architecture. Do NOT trigger for ad-hoc structural edits to an already-built System Composer model (adding one component, rewiring a port) — use `building-simulink-models` with `model_edit` for that. Works alongside the `system-composer` skill for detailed SC API patterns.

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

Evaluates a property across three investment strategies — Buy & Hold, BRRRR, and Fix & Flip — with feasibility scores, multi-year projections, tax benefits, and break-even analysis

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

Move quality earlier in the development lifecycle. Covers dev/QA pairing patterns, Three Amigos sessions, TDD facilitation (Red-Green-Refactor), PR review checklists for testability, and Definition of Done with quality gates. Includes shift-left maturity model for team assessment. Use when: "shift left," "TDD," "dev-QA pairing," "definition of done," "testability," "quality culture," "QA in sprint planning." Not for: writing the unit tests themselves — use unit-testing; automated PR test-quality review at scale — use ai-qa-review; multi-quarter QA direction or roadmap — use test-strategy. Related: unit-testing, ai-qa-review, test-strategy.

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

Orchestrate go-to-market strategy by running positioning, offer construction, and channel allocation as a sequenced workflow during PRD v0.9 Go-to-Market. Triggers on requests to plan launch, define GTM strategy, or when user asks "how do we launch?", "go-to-market", "launch plan", "marketing strategy", "GTM", "launch this product". Chains three framework-grounded sub-skills (Dunford → Hormozi → ORB) and reconciles their outputs.

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

Adversarially review the current implementation plan with three independent critic subagents, reconcile their findings into a consensus, and apply the agreed feedback to the plan. Use after drafting a plan (in plan mode or a plan/design doc) and before starting implementation, or whenever the user asks to pressure-test, critique, or harden a plan.

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

Choose and run ACU-only, adaptive PPU in-kernel timeline, or optional bounded joint analysis for a PPU kernel. Use for device-level bottleneck diagnosis, kernel-internal critical-path questions, or evidence that genuinely needs both; do not require all three modes.

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

"/specify", "specify", "요구사항 정의", "requirements", "스펙 잡기", "뭘 만들어야 하는지", "기획 정리", "인터뷰해서 스펙" Turn a goal into structured requirements through systematic interview. Three phases: Interview → Extract → Cross-check. Writes requirements.md in the cli format (consumed by /blueprint).

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

Turn one line ("a turbofan jet engine", "a mechanical watch", "an LVAD heart pump") into a photoreal, physics based, interactive 3D simulation of that machine in a single HTML file, plus a 20 to 30 second film to post it. Real proportions in metres, real materials (PBR metals, paints, polymers, glass), studio lighting with soft shadows, moving parts driven by a small solver that computes real numbers (thrust, torque, rpm, flow, pressure, efficiency), and modes to explode it, cut it open with clean section caps, x-ray it, slow it down, label it and break it. Use this whenever someone asks to build, simulate, visualise, explain or "show how X works" for any machine, engine, mechanism, device, instrument or piece of hardware, wants an interactive 3D model or a cutaway, or wants a video of a machine for a post, even if they never say "simulation" or "three.js".

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

Designs the public interface of a module before any implementation exists: writes the caller scenarios first, produces three candidates with genuinely different shapes, type-checks each one against the scenarios, scores them on measurable criteria and records the decision. Use when someone says "design the API for this module", "what should this signature look like", "compare interface options", "this function is awkward to call", "show me alternatives before I build it", or is about to add a module, library entry point, endpoint or command that other code will depend on.

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

Make kinetic-typography motion reels (MP4) in code: showreels, portfolio or work reels, product promos, intro films, "motion design"-style videos with bold condensed type, HUD micro-type, black/cream/lime palette, three.js generative layers (particle terrain, liquid marble, chrome knot, particle clouds), shape-continuity transitions and a synthesized, beat-locked score. Canvas 2D + WebGL rendered frame by frame in headless Chrome, encoded with ffmpeg. Use when the user asks for a reel, showreel, motion-graphics / kinetic-type video, a "Work Reel" in this style, or to extend/re-cut the Work Reel ’26.

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

60-second SEO snapshot powered by the DataForSEO API. Three parallel calls (DataForSEO Labs domain overview, Backlinks summary, ranked keywords) for core metrics on any domain — total keywords, traffic estimate, backlinks, top rankings — without waiting for a full audit.

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

Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance. Three modes: generate (new), audit (check existing), update (patch). Detects repo type and adapts sections, tone, and badges accordingly.

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