「ir」の検索結果

Memory management and FreeRTOS context for the Megahub ESP32 project. Use when dealing with heap allocation, stack size, task creation, inter-task communication, semaphores, queues, or any ESP32 memory constraints.

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

LEGO Powered Up protocol context for the Megahub project. Use when working on LEGO device communication, lpfuart library, UART parsing, motor control, sensor modes, device initialization, or debugging UART noise/corruption issues.

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

Code formatting and linting context for the Megahub project. Use when writing or reviewing code in C++ or JavaScript, or when running format/lint checks. Describes tool commands, style conventions, and when to apply them.

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

Blockly visual programming context for the Megahub project. Use when adding, modifying, or debugging custom Blockly blocks, the Lua code generator, the toolbox, block colors, or the BLOCKS.md documentation generation script.

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

Documentation structure and maintenance rules for the Megahub project. Use whenever making user-facing changes — adding features, changing behavior, fixing hardware compatibility, or modifying configuration. Describes which files to update, the README structure, and writing style.

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

Ensure architecture docs define RPO/RTO, failover paths, data consistency, and DR drillability.

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

Ensure designs document third-party dependencies, SLAs, quotas, failure modes, and vendor lock-in mitigation.

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

Ensure architecture updates document affected stakeholders, notification plan, and deprecation/retirement signals to keep knowledge aligned.

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

Check common security risks in application code (SQLi, XSS, secrets, open redirect).

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

Checks React Router v7 action conventions: validation errors returned as data with 4xx status (not thrown), redirect on success, and 3-branch ErrorBoundary handling.

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

Ensure architecture/design docs define clear boundaries, ownership, dependency direction, and change impact to avoid tight coupling.

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

Reviews GitHub Actions workflow diffs for script injection of untrusted input, pull_request_target with untrusted checkout, over-broad GITHUB_TOKEN permissions, and unpinned third-party actions.

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

Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.

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

Use when reviewing a project's architecture for design pattern applicability -- either validating a design document before implementation, or analyzing an existing codebase for pattern improvement opportunities.

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

Use when the user wants a wall of album covers, an image wall, a covers grid, or any square art drifting slowly in the background of a site. Includes collecting their saved albums from Spotify and building the wall from them. The wall goes behind whatever front the site already has; a frosted panel is the default when the site has none.

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

Self-verification loop. After completing a task, re-read the original request, list each requirement, verify whether it was met, and fix gaps before stopping.

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

Capture the creator's idea in their exact words. Use at the braindump stage, or when the user says "braindump", "let me talk this through", or "here is my idea".

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

Distill an already-built or near-launch product into one incisive brand kernel — the "reveal" already hiding in its name, story, or the product itself — then build the name, voice, visual identity, and a developer-ready handoff kit around it. This is LATE-STAGE branding: use it when there is a real, thought-through product that is about to launch, or already live but not explained in a way people grasp in an instant. Use whenever the user wants to name or rename a product, find a tagline or slogan, create a brand identity / brand kit / style guide / design system, design a logo, wordmark, palette, or type system, mock up a homepage for a launch, or hand brand assets to a coding agent (Claude Code, Codex, Cursor). Trigger even when the user only says their product needs to "land" or "feel like" something, or that they can't explain it simply yet. Do NOT use for half-baked, pre-product ideas with nothing to excavate — this skill extracts a kernel that already exists; it does not invent one from a blank canvas.

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

Bootstrap an AI-agent skill from a TypeScript codebase by running the deterministic skillit generate/audit loop and enriching repo source (JSDoc, README, config-type properties, MCP tool annotations, examples, package.json) until the skill reaches its grade target. Use for cli, typedoc, config, or mcp (build-mode) projects; never edit SKILL.md/references directly.

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

Create an Estuary derivation that continuously aggregates metrics (daily totals, running counts, min/max, lifetime revenue) using reduction annotations. Use for real-time dashboards, continuous materialised views, and replacing batch ETL aggregations with streaming. Derivations add complexity and cost — confirm the user wants a derivation before reaching for this. Use when user says "aggregation derivation", "derivation to sum daily totals", "running-count derivation", "transformation for min/max per group", "derive lifetime metrics", "aggregate-by-date derivation", or "real-time-dashboard derivation".

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

Create an Estuary derivation with custom SQLite state (internal tables) to make per-document decisions based on accumulated history — account balances, inventory levels, approval workflows, deduplication. Derivations add complexity and cost — confirm the user wants a derivation before reaching for this. Use when user says "stateful derivation", "derivation to track balance", "transformation to approve based on state", "derive an approval workflow", "deduplication derivation", or "build a stateful derivation".

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

Create an Estuary derivation that flattens a nested array into one output document per array element. Use for normalising nested JSON, exploding line items, unpacking tags, or producing one-row-per-item tables from arrays. Derivations add complexity and cost — confirm the user wants a derivation before reaching for this (some destinations can `UNNEST` server-side without one). Use when user says "flatten-array derivation", "derivation to explode an array", "transformation to unnest", "derive one row per item", or "flatten nested data with a derivation".

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

Create an Estuary derivation for stateless filtering, field selection, and per-document field transformation. Use for WHERE clauses, projecting fields, computing new fields from existing ones, or data cleansing. Derivations add complexity and cost — confirm the user wants a derivation before reaching for this (renaming alone is usually a projection, not a derivation). Use when user says "filter-transform derivation", "derivation to filter by status", "transformation with WHERE clause", "derive computed fields", "cleanse data with a derivation", or "stateless derivation".

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

Add or define specific fields in a collection's readSchema. Use when fields are missing from materialization field selection, pruned by complexity limit, need type refinement, need to be protected from future inference changes, or need to be required for downstream consumers. Use when user says "missing fields", "pruned fields", "field not showing up", "complexity limit", "define field in read schema", "restrict field type", or "protect field from inference".

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