191 件 ・ 関連度順
概要と使いどころ
Use for Hono (web framework) development when Codex needs to consult Hono documentation or test Hono apps via the `hono` CLI. Trigger on requests about Hono CLI usage, searching/browsing Hono docs, or testing Hono routes without running a server.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building Hono web applications or when the user asks about Hono APIs, routing, middleware, JSX, validation, testing, or streaming. TRIGGER when code imports from 'hono' or 'hono/*', or user mentions Hono. Use `npx hono request` to test endpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Hono (軽量・マルチランタイム対応 Web フレームワーク) リファレンス。 Hono App, Context (c.req / c.json / c.text / c.html), HonoRequest, Routing, HTTPException、 Built-in Middleware (JWT, CORS, CSRF, Cache, Logger, Compress, Basic / Bearer Auth)、 Helpers (Cookie, Streaming, WebSocket, Factory, RPC)、 Cloudflare Workers / Deno / Bun / Node.js / AWS Lambda 対応。
Use when building APIs on Hono (Cloudflare Workers, Bun, Deno, Node), debugging route ordering, wiring middleware, validating with @hono/zod-validator, returning streaming responses, configuring CORS with credentials, handling errors via app.onError, or composing typed RPC clients. Triggers: c.env binding types, c.header + c.redirect interaction, missing await next() bugs, Set-Cookie not attaching to redirect, route-precedence surprises, JWT middleware setup, hono/client typed RPC end-to-end. NOT for Express/Fastify/Koa idioms, tRPC/GraphQL paradigms, or Next.js Route Handlers.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Cloudflare Workers Error 1101 "Worker threw exception" caused by Hono sub-app route handlers returning undefined instead of a Response. Use when: (1) Error 1101 on a specific hostname but not others sharing the same worker, (2) "the Promise did not resolve to 'Response'" in wrangler dev logs, (3) Hono sub-app route handler uses bare `return` to skip handling for non-matching hostnames or conditions. The fix is to add `next` parameter and call `return next()` instead of bare `return` in route handlers that conditionally skip.
日本語の概要は準備中です。原文の説明を表示しています。
Sound systems of human language -- phoneme inventories, the International Phonetic Alphabet, articulatory and acoustic phonetics, phonological rules, suprasegmental features (stress, tone, intonation), and ear training for non-native sound perception. Covers place and manner of articulation, voicing contrasts, vowel space, minimal pair analysis, allophonic variation, phonotactic constraints, connected speech phenomena (assimilation, elision, liaison), and prosody across language families. Use when analyzing pronunciation, teaching sound systems, performing phonemic transcription, or diagnosing intelligibility problems in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error handling, and API_ENDPOINTS.md documentation. Use after a project is set up with cloudflare-worker-builder or vite-flare-starter, when you need to add API routes, create endpoints, or generate API documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.
日本語の概要は準備中です。原文の説明を表示しています。
Type-safe Hono APIs with routing, middleware, RPC. Use for request validation, Zod/Valibot validators, or encountering middleware type inference, validation hook, RPC errors.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building APIs with Hono framework on Bun, including routing, middleware, REST APIs, context handling, or web framework features.
日本語の概要は準備中です。原文の説明を表示しています。
Hono routes, OpenAPI, Zod validation
日本語の概要は準備中です。原文の説明を表示しています。
Expert in Japanese honorific language covering 尊敬語・謙譲語・丁寧語 with deep understanding of situational usage, business contexts, and cultural nuances
Webアプリのアクセス制御・認証・認可の実装はすべてこのスキルを使う。遮断だけならCloudflare Access、アプリ内identity・role・session・WebSocket等が必要ならBetter Authとする単一決定表の正本。「認証を付けて」「ログイン機能」「Googleでログインできるように」「社員だけに限定」「特定企業だけに公開」「許可リスト/招待制」「メール+パスワード認証」「セッション管理」「ロール・権限管理」「OAuth設定」「redirect_uri_mismatchを直す」「認証のセキュリティレビュー」などの文脈で、ユーザーが「認証」と明示しなくてもログイン要件が含まれるなら必ず読む。特にNext.js App Router＋OpenNext＋D1、Hono、素のWorkersでのBetter Auth＋Google OAuth導入を自動化し、Google Cloud Consoleで人間にしかできない操作は日本語のクリック手順と直リンクへ切り分ける。
Inngest イベント駆動 Durable Execution プラットフォームリファレンス。 サーバーレス環境での長時間ワークフロー、バックグラウンドジョブ、スケジュールタスク実装。 createFunction, step.run, step.sleep, step.sleepUntil, step.waitForEvent, step.waitForSignal, step.invoke, step.sendEvent, step.fetch, step.ai.infer, step.ai.wrap, inngest.send, serve, connect。 concurrency, throttle, debounce, rate-limit, batching, priority, idempotency, singleton フロー制御。 Realtime（channels, topics, publish, subscribe, useRealtime, subscription tokens）による進捗配信。 Agent Evals, scoring, group.experiment, MCP dev server などエージェント運用機能。 Next.js / Express / Hono / Cloudflare Workers / Vercel / Netlify / DigitalOcean / Render デプロイ対応。
Better Auth (TypeScript 認証フレームワーク) リファレンス。 認証・認可、サインアップ・サインイン、セッション管理、OAuth、パスキー、 二要素認証 (TOTP)、プラグイン (organization, admin, magic-link, anonymous 等)。 betterAuth, createAuthClient, signUp, signIn, getSession。 フレームワーク統合 (Next.js, Nuxt, SvelteKit, Hono, Express, Expo, TanStack 等)。
Scaffold a custom AI agent harness via `metaharness new {name} --template {id} --host {id}`. Defaults to DRY-RUN (no writes) unless --confirm is passed. Refuses to write to the calling repo root or anywhere inside it. Honors ADR-150 architectural constraint + ruflo's "destructive-action confirmation" pattern.
日本語の概要は準備中です。原文の説明を表示しています。
Create or edit requested Page/Space content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.
日本語の概要は準備中です。原文の説明を表示しています。
The single ROUTER for every data need. Load this skill BEFORE any backtest, data-fetch, or research task to pick the best available source/tool, honour auth (env) requirements, and avoid ban-risk providers.
日本語の概要は準備中です。原文の説明を表示しています。
Posts content and articles to X (Twitter). Supports regular posts with images/videos and X Articles (long-form Markdown). In Codex, honor explicit requests for the Codex Chrome plugin/@chrome by using the Chrome Extension workflow; otherwise use Chrome Computer Use when available and fall back to real Chrome CDP scripts only when allowed. Use when user asks to "post to X", "tweet", "publish to Twitter", or "share on X".
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when implementing a Figma design as code (design → code) — the read-FROM-Figma direction. Triggers: 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'code this up from Figma', 'design to code', or a figma.com design URL provided alongside a codebase. Encodes the workflow for reading a node out of Figma with get_design_context and adapting its reference output to the target project — reusing existing components, tokens, and conventions, and honoring Code Connect mappings, component docs, design annotations, and design tokens by priority. Complements figma-code-connect (component mapping) and figma-generate-design / figma-use (the reverse, code → design direction).
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for "review" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected/actual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext/lifecycle; timeout/cancellation; OS/CI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest/non-.NET code.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — invoked headlessly by the peon eval server; humans should run `peon eval <pack>` instead. Execute one PeonPing reroll job — invoked headlessly by the peon eval server as: "Use the peon-ping-remix skill to execute the reroll job at <path>". Reads the job JSON (scope, category, index, caption), rewrites the affected sound prompt(s) to honor the caption, re-renders via scripts/pack-render.py, and logs the change to eval-log.json.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — invoked headlessly by `peon create`; humans should run `peon create` instead. Author and render a brand-new PeonPing draft pack — invoked headlessly as: "Use the peon-ping-create-pack skill to draft a pack: name=<n> flavor=<f> vibe=<v> draft_root=<dir>. Follow the skill exactly." Authors all 7 CESP categories honoring the vibe, writes openpeon.json (draft-stamped) and prompts.json, renders every sound via scripts/pack-render.py, and always ends by telling the human to run `peon eval <name>`.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a full-stack Cloudflare app from the vite-flare-starter template — React 19 + Hono + D1+Drizzle + better-auth + Tailwind v4+shadcn/ui + TanStack Query + R2 + Workers AI. Run setup.sh to clone, configure, and deploy. Use whenever the user wants a batteries-included Cloudflare full-stack app, vite-flare-starter scaffold, or a React + Cloudflare app with auth + database + Workers AI ready to go.
日本語の概要は準備中です。原文の説明を表示しています。