1,215 件 ・ 関連度順
概要と使いどころ
Classify curriculum content into Know, Understand, and Do categories to align teaching and assessment approaches. Use when planning units, writing objectives, or selecting assessment methods.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
日本語の概要は準備中です。原文の説明を表示しています。
Socratic ideation and idea routing — think through ideas before committing to plans
日本語の概要は準備中です。原文の説明を表示しています。
LLMOps Architect: Run LLM features in production: model routing, evals, observability, caching, cost, safety.
日本語の概要は準備中です。原文の説明を表示しています。
Clerk Organizations for B2B SaaS - create multi-tenant apps with org switching, role-based access, verified domains, and enterprise SSO. Use for team workspaces, RBAC, org-based routing, member management.
日本語の概要は準備中です。原文の説明を表示しています。
Overview of the Neon platform for apps and agents, spanning Postgres, Auth, Data API, and the new services: Object Storage, Compute Functions, and AI Gateway. Use whenever "Neon" is mentioned for an overview of how to work with Neon and how to get started. Otherwise, the individual capabilities are the triggers: "object storage" or "S3-compatible storage", "serverless functions", "background jobs", or "run code near my database", "AI gateway", "LLM proxy", "model routing", or "call an LLM" → AI Gateway; "database", "Postgres", or "authentication" → Postgres and Auth.
日本語の概要は準備中です。原文の説明を表示しています。
Craft CMS 5 front-end Twig development — atomic design, template architecture, components, Vite buildchain. Covers atoms/molecules/organisms, props/extends/block patterns, layout chains, view routing, content builders, image presets, Tailwind named-key collections, multi-brand CSS tokens, JavaScript boundaries (Alpine/DataStar/Vue, tabs, accordions), Vite asset loading, and front-end auth (login, registration, password reset, profiles).
日本語の概要は準備中です。原文の説明を表示しています。
React Router v7 best practices for data-driven routing. Use when implementing routes, loaders, actions, Form components, fetchers, navigation guards, protected routes, or URL search params. Triggers on createBrowserRouter, RouterProvider, useLoaderData, useActionData, useFetcher, NavLink, Outlet.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews Remix v2 route files for naming convention violations, missing layouts, resource-route shape, and v1 holdovers. Use when reviewing files under app/routes/ in a Remix v2 codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews axum web framework code for routing patterns, extractor usage, middleware, state management, and error handling. Use when reviewing Rust code that uses axum, tower, or hyper for HTTP services. Covers axum 0.7+ patterns including State, Path, Query, Json extractors.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews FastAPI code for routing patterns, dependency injection, validation, and async handlers. Use when reviewing FastAPI apps, checking APIRouter setup, Depends() usage, or response models.
日本語の概要は準備中です。原文の説明を表示しています。
Go application architecture with net/http 1.22+ routing, project structure patterns, graceful shutdown, and dependency injection. Use when building Go web servers, designing project layout, or structuring application dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews Phoenix code for controller patterns, context boundaries, routing, and plugs. Use when reviewing Phoenix apps, checking controllers, routers, or context modules.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for developing messaging channel adapters via WASM Plugins and managing routing, session state, pairing codes, and accounts in internal/channels/.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for developing REST API endpoints in internal/server/. Covers routing, request validation, WebSocket streaming, and API conventions.
日本語の概要は準備中です。原文の説明を表示しています。
MTProto-over-WebSocket tunnel for Telegram: DC classification, obfuscated2 detection, TLS backend choice, and the relay loop. Use when touching Telegram DC routing, MTProto classification, or ripdpi-ws-tunnel.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous novel writing CLI agent with web workbench (JiaOS Studio) - use for creative fiction writing, standalone short-fiction packages, cover generation, novel generation, style imitation, chapter continuation/import, EPUB export, AIGC detection, and fan fiction. Native English support with 10 built-in English genre profiles (LitRPG, Progression Fantasy, Isekai, Cultivation, System Apocalypse, Dungeon Core, Romantasy, Sci-Fi, Tower Climber, Cozy Fantasy). Also supports Chinese web novel genres (xuanhuan, xianxia, urban, horror, other). Multi-agent pipeline, two-phase writer (creative + settlement), stronger long-form chapter craft rules, hook-ledger payoff checks, 33-dimension auditing, token usage analytics, creative brief input, structured logging (JSON Lines), multi-model routing, custom OpenAI-compatible provider support, and JiaOS Studio web UI for visual book management, short-fiction runs, cover generation, chapter review, real-time writing progress, market radar, and analytics.
日本語の概要は準備中です。原文の説明を表示しています。
Interactive demo: Generate pseudo-labels from a strong teacher model, build a cheap student function, and evaluate accuracy. Showcases pseudo-labeling and teacher-student distillation.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guide for type-safe Python AI agent development with Pydantic AI — dependency injection, structured outputs, model-agnostic routing, and graph workflows / Panduan ahli pengembangan agen AI Python type-safe dengan Pydantic AI.
日本語の概要は準備中です。原文の説明を表示しています。
Generates RESTful API Controllers with proper routing, versioning, authorization, and MediatR integration. Follows REST conventions and Clean Architecture patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Create a Datagrok application with routing, views, and data access
日本語の概要は準備中です。原文の説明を表示しています。
Yoga practice with an emphasis on alignment, props, and staged progression as the Iyengar lineage teaches it, alongside enough context about the broader lineage landscape (Krishnamacharya's three students, modern Hatha, Ashtanga vinyasa, restorative, Yin, and chair yoga) that a routing agent can place a user correctly before giving instruction. Covers asana families, alignment heuristics, prop use, sequencing, and the non-negotiable injury-prevention rules. Use for any query about yoga postures, home practice design, teacher-training-level questions, or whether a given pose is safe for a given body.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Instruction dispatch pipeline for routing work items to available agents. Implements a 7-stage fetch-allocate-prepare-hook-store-launch-confirm pipeline with batch convoy mode, formula expansion, idempotent dispatch, and crash recovery.
日本語の概要は準備中です。原文の説明を表示しています。