「route」の検索結果

Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.

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

Busabase-backed App-in-Skill dashboard for a shared LLM gateway's cost and model governance — daily spend trend, cost breakdown by service/model, a canary-rollout status board, and a deterministic cost/error anomaly list. Use when the user invokes $kelly-llm-gateway or /kelly-llm-gateway, or wants to review LLM gateway spend, model routing, canary rollouts, rollback readiness, or cost/error anomalies for services routed through one shared gateway to multiple LLM providers/models. Human actions (promote/rollback/hold a rollout, acknowledge an anomaly) write directly onto the route's own Busabase record — this skill never changes a real routing config.

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

Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.

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

Reads a CARLA Leaderboard results.json — per-route driving score, route completion, infraction penalty and the infraction lists — explains how the score was computed for that leaderboard version, and rescores an existing result under the other version's rules (2.0 multiplicative vs 2.1 additive) without re-running anything. Also diffs two runs and merges sharded result files. Use when the user asks "what did I score", "why is my score low", "did my agent pass", "why don't my scores match the leaderboard", or hands over a results.json.

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

Use when working with access policies, field access, authorization middleware, gates, route access control, AccessResult semantics, permission handlers, or files in packages/access/, packages/routing/src/AccessChecker.php, packages/user/src/Middleware/. Covers entity-level access (deny-by-default via isAllowed), field-level access (open-by-default via !isForbidden), the Gate system, route options (_public, _permission, _role, _gate), and the SessionMiddleware/AuthorizationMiddleware pipeline in public/index.php.

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

Playwright (E2E / コンポーネントテストフレームワーク) リファレンス。 test, expect, page, locator, getByRole / getByText / getByLabel / getByTestId、 toBeVisible, click, fill, route, mock, fixtures、 playwright.config.ts、auth 永続化、trace viewer、codegen、UI モード。

Fix the psychologically significant moment, not the logically significant metric — Rory Sutherland on experience. Use when the outcome is fine but the journey feels bad: complaints about waiting, anxiety, uncertainty, or 'it's technically fast/cheap/correct but people still hate it'; when the user asks 'how do we reduce complaints', 'how do we make waiting/onboarding/checkout feel better', 'people are anxious during X', or is about to spend big to shave a number (wait time, load time, steps) when the real pain is how the moment feels. Covers uncertainty reduction, idle vs occupied waiting, and the peak-end rule. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「待ち時間のクレームが多い」「手続きの途中で離脱される」「お客様を不安にさせている」）にも使う。中文咨询（“等待时间投诉多”“办理中途流失”“让客户感到不安”）也适用。

Generate ideas that don't sound logical, then validate them with cheap behavioural experiments — Rory Sutherland's 'the opposite of a good idea can be a good idea' plus revealed-preference testing. Use when the obvious/logical solution is saturated and the user wants genuinely different options, asks 'what's a creative/unconventional angle', 'how do we stand out', 'should we run a test/experiment', 'how do we know what people actually want', or is about to trust a survey/focus group. Covers deliberate inversion of the obvious move, why stated preferences lie, and designing small reversible experiments that watch behaviour. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「競合と同じ案しか出ない」「アンケートは好評なのに売れない」「思い切った案を安く試したい」）にも使う。中文咨询（“只能想出和竞品一样的方案”“问卷好评却卖不动”）也适用。

Change what something MEANS before you change what it IS — Rory Sutherland's cheapest lever. Use when a product, price, feature, or message is objectively fine but feels cheap, generic, boring, overpriced, or unjustified; when the user says 'how do we make this feel more premium/valuable/exciting', 'people don't get why it's worth it', 'how do we reposition/rename/repackage this', or wants to raise perceived value without changing the product or cutting the price. Covers renaming, recategorising, mental accounting (price framing), creating artificial value, and context-shifting. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「高いと言われる」「安っぽく見える」「値下げせずに高級感を出したい」）にも使う。中文咨询（“被说太贵”“显得廉价”“不降价也想显得高级”）也适用。

The live fieldwork layer for psycho-logic — go look at the actual target market NOW instead of reasoning from your training-data stereotype of it. Use when a psycho-logic move needs grounding in a specific place: the user asks 'what do competitors in [region/country] actually do', 'what's the real price band / norm here', 'how do local leaders position themselves', 'research this market before we localise', 'what signals trust to buyers in X', or is about to launch/adapt in a market you haven't studied. Runs structured web research in the local language — local competitors and their signals, price bands, category conventions, review/trust sources, local terminology, taboos and regulations — and synthesises a compact perception profile the four moves consume. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic; pair with cultural-context (the lens that tells you what to look for). 日本語・中文の相談（「現地の実態を調べて」「调研当地市场」）にも使う。

Rory Sutherland's 'psycho-logic' approach to marketing, product, and business problems — solve the human perception, not just the engineering or economic metric. Use when the obvious 'logical' fix is expensive, slow, or already done by every competitor; when the user asks 'how do we make people want X', 'the product/price/funnel is fine but nobody converts', 'how do we stand out', 'is there a cheaper way to fix this', or mentions behavioral economics, nudges, irrational behavior, perception, or 'it doesn't make sense but it works'. This is the ROUTER skill: it diagnoses the problem in human terms, then dispatches to reframing, costly-signaling, counterintuitive-tests, or experience-design. Inspired by Rory Sutherland's book *Alchemy*. 日本語の相談（「商品はいいのに売れない」「値下げしかない？」「競合と差別化できない」）にも使う。中文咨询（“产品很好却卖不动”“只能降价吗？”“无法差异化”）也适用。For a catalogue of individual biases, use marketing-psychology (separate plugin) instead.

The perception-by-culture lens for psycho-logic — establish HOW a specific region, country, or subculture reads a signal before you send it, because perception is culturally coded and the same move can mean the opposite elsewhere. Use when adapting a product, price, message, or campaign to a new market; when the user asks 'will this work in [country/region]', 'why does this land in X but flop in Y', 'how do people here perceive Z', 'how do we localise/differentiate by region', or is about to copy a US/global playbook into another market. Covers the cultural dimensions that move Sutherland's levers — uncertainty avoidance, individualism/collectivism, status/power distance, high- vs low-context communication, mental-accounting norms, trust locus, and taboo/sacredness — and how each rewires reframing, costly-signaling, and experience-design. Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic; pair with market-recon for live local data. 日本語・中文の相談（「この地域で通用する？」「适合本地市场吗？」）にも使う。

Why expensive, wasteful, effortful, or self-deprecating actions build trust and desire — Rory Sutherland on signalling. Use when the problem is credibility or desirability rather than meaning: the user asks 'why don't people trust us', 'how do we look more credible/committed/premium', 'is our guarantee/warranty worth it', 'should we spend on brand advertising', 'how do we justify a higher price', or wonders why a cheaper-looking competitor wins. Covers costly signals (advertising spend, guarantees, over-delivery), price-as-quality-signal (Veblen goods), and the Pratfall Effect (admitting a real flaw to gain trust). Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「信頼されない」「安心してもらえない」「強気な価格で売りたい」「広告費に意味はある？」）にも使う。中文咨询（“不被信任”“想以高价出售”“广告费有意义吗？”）也适用。

Lay out how a job search will actually run alongside a current job: the hours available each week and what they go to, how weekday daytime slots for interviews will be found, which routes to use (direct applications, job boards, scout sites, agents, referrals, public employment services) and what each one discloses to whom, how to keep the search from reaching the current employer through public profiles or workplace equipment, a single tracker of every application's stage, next action, and deadline, and a date and conditions for reviewing, reducing, or pausing the search. Use when someone has decided to start looking, or to gather information while employed, and asks how to fit it in, which routes to use, whether the applications they are running fit the time they have, or how to keep track of them; do not use to decide whether to change jobs, to pick or rate employers or job postings, to predict outcomes, or to send applications, publish profiles, or contact agents on the user's behalf.

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

Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.

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

FastAPI conventions for REST APIs: routers, Pydantic v2 schemas, dependency injection, error handling, pagination, and project structure. Trigger: When writing any router, endpoint, schema, or dependency in a FastAPI project.

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

Route Expo application, EAS, native module, styling, deployment, and upgrade work to focused Expo skills. Use when building or operating an Expo or Expo Router project.

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

Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

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

Use when the user asks to switch AI role/mode/persona or uses role-trigger words such as Captain, Coordinator, 寫文章, 寫文章模式, 文章模式, 技術文章, 部落格, 出版, 預覽. Routes the request to Project Captain, Publishing Director, or Article Writing Mode, loads the matching keep memory when available, and applies the role's workflow without excessive roleplay.

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

Route natural-language cleanup, refactor, migration, and candidate ranking goals through ATM before local analysis.

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

Match a user request to the right skill using trigger matching, project context, and conversation history. Score ambiguity 1–10 and resolve it using context signals or a single clarifying question. Load when project-orchestrator needs to route a request, or when multiple skills could match and the right one is unclear. Also triggers on "which skill should handle this", "route this request", "I'm not sure which skill to use", "disambiguate this", "skill routing". Called by project-orchestrator for request routing. For finding whether a skill exists for a capability, use skill-finder instead.

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

Pick a product archetype from a curated catalog before any UI gets built — the single biggest lever for not looking vibecoded. Routes the request to one of B2B-productivity, enterprise-trust, premium-consumer, playful-consumer, editorial, brutalist-distinctive, dev-tool, or marketing-landing, and returns a complete design philosophy: typography pair, color logic, motion curve, density, icon stance, reference sites, and a "feels like X" claim. Load when the user asks to pick an aesthetic, choose a design direction, decide what a UI should feel like, classify a product visually, says "what should this look like", "make this feel like [Linear/Stripe/Apple/Duolingo/...]", "give me a design direction", "what's the right aesthetic for this", or when frontend-design routes here during archetype selection. Sub-skill of frontend-design.

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

Tactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or when process-decomposer routes here after determining the user needs lightweight planning deliverables. Also triggers on "create tasks from this problem", "make this actionable", or "turn this into a plan agents can execute". For feature-sized work that needs an executable spec + constitution + cross-check gate, route to `spec-driven-development` (or `feature-spec`) instead.

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

Performs retrosynthetic planning using AiZynthFinder (MCTS, template-based), Chemformer (template-free transformer), ASKCOS, and emerging RetroSynFormer with explicit handling of route scoring, building-block availability (eMolecules, Enamine, Mcule), forward prediction validation (Molecular Transformer), and disconnection-aware multi-objective search (MO-MCTS). Use when assessing synthetic feasibility of generated or selected molecules, planning multi-step syntheses, building synthesis-aware design pipelines, or screening libraries for retro-route feasibility.

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