「tia」の検索結果

Run an honest market-fit and viability audit of any project or idea and produce a decision doc, not code. Use when someone asks "is this viable as a business", "audit the market fit", "make the case and compare to competitors", "should I apply to YC or bootstrap", or wants to validate a project, product, or market before investing more time. Gathers verifiable traction data first, researches the competitive field, gets an independent cold read, writes a doc with pre-committed pass/middle/kill criteria and a concrete week-1 assignment, then hardens it with an adversarial review loop.

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

Generate, refine, compare, and when needed validate distinctive names for startups, AI products, developer tools, protocols, open-source projects, apps, product families, local businesses, services, companies, nonprofits, and other organizations. Use when asked to name or rename a business, brand, product, venture, shop, studio, or organization; derive a name from an existing project or concept; create a company and product naming system; compare candidates; or check company, domain, package, repository, marketplace, or trademark conflicts. Default to a fast no-browse creative pass; use current validation when the user requests availability or research, or is choosing a final name. Do not claim legal clearance, purchase domains, or present stale or unverified availability as fact.

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

Provider-neutral deep-research orchestration for brainstorming, technology choices, comparisons, and state-of-the-art surveys. The Research Lead makes scope and decision calls while native subagents scout, search, verify, synthesize, audit, write, and commit every research artifact.

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

Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts, speeches, emails, documentation, product copy, and other style-sensitive text. Apply George Orwell's six rules and ASD-STE100 Simplified Technical English as a plain-English discipline while preserving the user's intended meaning, audience, tone, and explicit constraints.

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

Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).

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

Analyze a software repository at the latest remote main commit and turn its implemented architecture into a citation-backed interactive isometric system map with a legend, selectable infrastructure buildings, dependency and payload flows, and plain-language learner explanations. For eligible public GitHub repositories, also contribute the verified map to tamdogood/CodeTerrain with a pull request. Use when a user provides a repository URL or asks to visualize, explore, learn, explain, or map a repo's architecture, infrastructure, runtime control flow, data flow, services, queues, stores, external systems, or deployment topology in an interactive UI.

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

Use when the user asks to run or continue an autonomous build: turn a goal into an approved plan, dispatch implementation and review agents, and finish with one pull request. The Lead is a provider-neutral orchestrator that makes decisions but never writes code, edits files, runs commands, or reviews its own work.

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

Teach any topic deeply from first principles and build evidence-based paths toward exceptional capability. Use when a user asks to understand, explain, learn, or deep-dive into a topic; asks why or how something works, why it matters, how alternatives compare, or what different perspectives reveal; requests current paradigms, a complete roadmap or curriculum, deliberate practice and feedback, or a top-1%-level mastery plan. Answer explanation questions completely before offering a curriculum; route explicit mastery goals to an adaptive practice and proof-of-capability system.

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

Configure email verification, implement password reset flows, set password policies, and customise hashing algorithms for Better Auth email/password authentication. Use when users need to set up login, sign-in, sign-up, credential authentication, or password security with Better Auth.

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

One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write `.absolute.config.json` (project, committed) and `~/.absolute/config.json` (user defaults + per-project overrides). Every other absolute-* command reads it instead of re-detecting; non-blocking — commands proceed without it and soft-recommend it. Triggers on "absolute init", "set up absolute", "initialize absolute", "configure absolute", "first-time setup", "remember my conventions for this repo".

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

Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk. Use when evaluating a third-party skill before installing, enabling, updating, publishing, or distributing it; reviewing an untrusted SKILL.md, agent configuration, MCP integration, archive, or repository; comparing a package with a known-good version; or investigating unexpected tool, network, credential, or filesystem behavior.

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

Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration. Use when the user requests oauth 2 0 setup or provides relevant inputs for this workflow.

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

Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses. Use when the user requests ticket triage or provides relevant inputs for this workflow.

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

Design and operate bounded multi-agent workflows with task decomposition, dependency graphs, ownership, handoff contracts, shared-state controls, approvals, recovery, and synthesis. Use when a task contains genuinely independent workstreams, specialized roles, parallel research or implementation, reviewer-worker loops, or coordination problems that one agent should not execute sequentially.

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

Learn reusable 2D motion-generation knowledge from user-specified action resources with `/img2mo-learn <resource>`. Use when the user provides videos, extracted frame sequences, spritesheets, Spine assets, generated outputs, failed attempts, or reference motion folders and wants to summarize animation timing, pose beats, style traits, prompt patterns, extraction/cropping rules, or failure lessons into the project `img2mo-knowledge/` folder for later `/img2motion` generation.

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

Standardize a 2D animation baseline image with `/img2mo-std xxx.png/pos`. Use when preparing a character, creature, prop, or weapon baseline before motion generation, especially if the source image is too large, tightly cropped, lacks transparent action margin, has a white background, or later walk/attack/idle frames show clipping, overlap, scale popping, or inconsistent character size.

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

Use when a user provides one baseline image and requests game animation frames, sprite sequences, attack/walk/idle/hit/death/casting motion, transparent PNG frames, a spritesheet, keyframe prompts, or consistent whole-character pose animation.

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

Think and work like an expert Life-Cycle Assessment Analyst. Use when a task calls for Life-Cycle Assessment Analyst judgment. Reasons from functional unit, attributional-versus-consequential framing, and ISO 14044 allocation hierarchy through openLCA, SimaPro, Brightway2, ecoinvent, and LCIA methods like TRACI and EF 3.0 while treating allocation-driven ranking flips, biogenic-versus-fossil carbon mistagging, cut-off-masked hotspots, and PCR mismatch as first-class failure modes.

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

Think and work like an expert Mechatronics Engineer. Use when a task calls for Mechatronics Engineer judgment. Reasons from reflected inertia, control bandwidth, sensor physics, and thermal duty cycle through Bode loop-shaping with phase/gain margins, FOC current-velocity-position loops, plant identification, HIL, and IEC 61800-5-2 STO architecture while treating backlash and structural-mode resonance, transport-delay phase loss, encoder aliasing, and EMC ground loops as first-class failure modes.

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

Think and work like an expert Limnologist. Use when a task calls for Limnologist judgment. Reasons from stratification, Schmidt stability, and nutrient–light coupling; profiles with CTD/EXO and Carlson TSI components; models with rLakeAnalyzer and GLM while treating internal P loading, sensor fouling, and spatial pseudoreplication as first-class failure modes.

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

Think and work like an expert Geographic Information Scientist (GIS). Use when a task calls for Geographic Information Scientist (GIS) judgment. Reasons from location, topology, scale, and positional uncertainty through PostGIS/GDAL pipelines, explicit EPSG/datum choices, kriging with cross-validated variograms, and ISO 19115/FGDC metadata while treating MAUP and ecological fallacy, Web Mercator area statistics, floating-point slivers and broken topology, and spatial-autocorrelation-inflated significance as first-class failure modes.

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

Think and work like an expert Geotechnical Scientist. Use when a task calls for Geotechnical Scientist judgment. Reasons from Terzaghi effective stress, Mohr–Coulomb/CSSM, and consolidation/seepage through SPT/CPTU (Robertson SBT), triaxial/oedometer (ASTM D-series), Boulanger–Idriss liquefaction, Hoek–Brown/GSI rock mass, EC7 characteristic values, and PLAXIS/Slide2/RS2/GeoStudio workflows while treating sample disturbance, N-value correction chains, spatial variability, and LEM-vs-FEM mismatch as first-class failure modes.

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

Think and work like an expert Gerontologist. Use when a task calls for Gerontologist judgment. Reasons from senescence hallmarks, frailty, multi-morbidity, and life-course exposures through validated instruments (Fried phenotype, Rockwood CFS, SPPB/gait speed), epigenetic clocks (Horvath, PhenoAge, GrimAge), competing-risk survival (Fine-Gray), and NIA cohorts (HRS, NHATS, ITP) while treating survivor bias, differential attrition, healthy-volunteer bias, and frail-subset toxicity as first-class failure modes.

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

Think and work like an expert Environmental Microbiologist. Use when a task calls for Environmental Microbiologist judgment. Reasons from spatial patchiness, redox thermodynamic ceilings, and process-over-taxonomy guild function through DADA2/QIIME2 amplicons keyed to SILVA/GTDB/PR2/UNITE, metaSPAdes/MetaBAT2 MAGs vetted by CheckM/GUNC, and SIP/qSIP rate assays paired with IC/GC/ICP-MS chemistry, while treating extraction-batch effects, relic and extracellular DNA, primer-window bias, and core pseudoreplication as first-class failure modes.

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