「engine」の検索結果

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

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

Verify a completed implementation against the plan in .unikit/code/plans/. Checks that every task was implemented, nothing was forgotten, the code compiles, the recorded test run still matches the code, and {{engine_name}} conventions are followed. Use after /unikit-implement completes, or when the user says "verify", "check the work", "did we miss anything". For code review use /unikit-review instead.

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

Record a finding about the configured engine MCP server into .unikit/MCP-RECHECK-NOTES.md — the project's log of what has to be re-checked here. Use right after a call reported success while changing nothing, ate an argument, or validated a broken state, e.g. "write this down", "record this MCP finding", "the server lied — note it", "add a recheck note", "trap this". Takes three forms of input: the finding in one line, a path to a plan file (harvests the "## MCP Findings" table of that plan and nothing else), or nothing at all — then it takes findings already in the session first, and offers to scan the tables of plans touched since the last audit. The table only, never the plan body. Writes in the one allowed genre — a check to perform; never a lifted gate, never a named workaround, never a claim about what the server can or cannot do. Makes zero MCP calls and needs no editor. To replay, retire, or upstream existing notes use /unikit-mcp-audit instead.

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

Curate .unikit/MCP-RECHECK-NOTES.md — the project's log of findings about the configured engine MCP server. Four jobs: re-stamp (the server moved, so every entry is suspect), replay (reproduce a `replay: safe` finding inside a disposable sandbox to see whether it still holds), retire (offer to drop what was fixed or went upstream), and upstream (print a ready diff for the packaged INDEX.md). Use for "audit the MCP notes", "are these findings still true", "recheck the MCP traps", "clean up MCP-RECHECK-NOTES", "the server was updated — revisit the notes". Replaying mutates a live editor, so it starts by telling you how to prepare it — save your scene, open an empty one — and asks once before touching anything. Everything it creates lives under a single UNIKIT_AUDIT_<runid> prefix, is deleted in one action, and the scene is never saved. To record a NEW finding use /unikit-mcp-trap instead.

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

Cold-start brownfield reconnaissance — reconstruct the WHOLE game design from an existing codebase when there is no GDD yet. Optionally accepts a free-text game description, notes, or reference links to guide and enrich the scan. Use when the user wants to build the game design from the code, e.g. "create a GDD from this codebase", "reconstruct the design from our code — it's a roguelike deck-builder", "build a design doc from the existing project, here are some refs". Scans the project (engine auto-detected), extracts a system roster + dependency graph and content-type schemas / resources / entities into one passive .unikit/gamedesign/RECON.md, tags every fact provenance:extracted-from-code, and writes a mandatory Intent Gap for what code cannot know (pillars, fantasy, the "why"). Writes nothing else and calls no skill. STRICTLY whole-project cold-start — if a GDD already exists and the user wants a specific part investigated, use /unikit-gd-explore (code lens); to author the GDD use /unikit-gd-spec.

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

Write, open and — when allowed — merge a pull request for the current feature branch of a {{engine_name}} project, with or without a plan. Builds a plain-language PR text (one feature per line) from the plan's `## Modules` and task `WHY:` lines, or — without a plan — from the commits and the code changes themselves; pushes the current state (asking where to end when it stands inside a plan module), opens or updates the branch's single open PR through the GitHub MCP, and merges with a merge commit only when the merge brings nothing from the base branch. Levels: remind (text only), create, merge; capped by `git.pull_requests.max_level`. Trigger phrases: "pull request", "open a PR", "create PR", "PR description", "merge the PR". For commit messages use /unikit-commit; for reviewing a PR's code use /unikit-review.

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

Initialize the UniKit framework in a project. Scans the current project to detect the engine and real tech stack, then generates the base framework documents that give AI agents context about the project — the resolved project description, the architecture doc, AGENTS.md, and the user-editable .unikit/config.yaml. This is the one-time, whole-project setup run before any other unikit skill. Use whenever the user wants to initialize, set up, or onboard the framework, e.g. "initialize unikit", "init the framework", "set up unikit", "set up the project", "configure AI context", "scan my project and set it up", "bootstrap the project". It also actualizes the config of a project already set up — say "update the config", "add missing settings", "actualize configuration", "fix my config".

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

AI บาริสต้า specialty coffee — SCA cupping, espresso dial-in, latte art, café menu engineering, bean sourcing, Thai climate considerations

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

ที่ปรึกษาเจ้าของร้านอาหาร — menu engineering, pricing, food cost, labor cost, marketing playbook (LINE OA, FoodPanda, GrabFood)

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

AI bartender — cocktail recipe, mixology technique, bar setup, menu engineering, food pairing, responsible alcohol service

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

ผู้จัดการร้านอาหาร — food cost (28-32%), labor (25-30%), menu engineering, inventory, staffing, ROI สาขา

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

ตรวจช่องโหว่ OWASP Top 10 JWT SQL injection CSRF พร้อมเสนอวิธีแก้แบบ pentester

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

Materials engineering expert covering properties, processing, testing, and applications of materials

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

Expert in ODEs and PDEs covering solution methods, qualitative analysis, and applications to physics and engineering

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

Use Tanso, an AI Search CLI for exploring Chinese internet signals. Use when the user asks to search Chinese web sources, Zhihu, Zhihu hotlists, Bocha, Volcengine Ark, Chinese internet topics, source-backed briefs, contradiction checks, counterintuitive topic discovery, popular answers, live provider testing, or current Chinese web signals.

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

The model-generator shape for Skmtc: one definition per component schema, built by copying the shipped SKELETON package and filling its SLOT markers with the target library's syntax. Covers the edge cases every model generator must survive — refs, recursion, optional vs nullable, additionalProperties, enums, readOnly/writeOnly. Use when authoring or editing a generator that maps schemas to a validator/schema/type library ("write a gen-<lib>", "map OpenAPI models to <lib>"). Load ALONGSIDE skmtc-generator (engine rules) and skmtc-lang-typescript (TS layer).

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

Author and edit Skmtc generators — packages that project an OpenAPI domain model into application code. Method: clone the nearest stock generator, then apply the engine rules imitation can't teach. Assumes zero prior Skmtc knowledge. Use when asked to "write a skmtc generator", "author/clone/customize gen-x", "add a field type", "change export paths", "add enrichment options", or when editing generator source. ALWAYS pair with the target language's skill (skmtc-lang-typescript).

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

The GraphQL pipeline for SKMTC generators — authoring generators whose input schema is GraphQL SDL rather than OpenAPI. Covers `toGqlOperationEntry`, `GqlOperation`, `synthesizeArgsObject` (mutation args -> object schema), the GQL enrichment routing (`[id][rootKind][fieldName][variant]` — two nested subject keys where OAS has path+method), the `to<Lang>GqlOperationProjectionBase` companion factories, and the `GeneratorKey` shape `id|rootKind|fieldName|variant`. Use this skill ALONGSIDE `skmtc-generator` whenever the schema source is GraphQL SDL or the task mentions "GraphQL", "SDL", "GqlOperation", "toGqlOperationEntry", or GraphQL query/mutation generators. Engine rules (producers, register/insert, the axioms) stay in `skmtc-generator`; this skill carries only what differs for GraphQL.

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

PC and console game development principles. Engine selection, platform features, optimization strategies.

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

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

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

React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

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

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

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

Complete MCP engineering work on the live path: build or repair servers and Apps, debug stdio or Streamable HTTP, migrate protocol/SDK/transport versions, reconcile source with package and activated runtime, inspect capability/effect authorization, and verify named-host claims without promoting weaker evidence. Use for real Model Context Protocol implementation, review, migration, runtime, or host-integration tasks. Do not use for ordinary non-MCP APIs, generic frontend work, or incidental product copy.

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

Unified verification engine for Python data science projects. Covers environment checks, type checking, linting, tests, security scans, code review with DS anti-patterns, and notebook checks. Commands (/verify, /quality-gate) invoke different subsets of this skill.

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