「boundaries」の検索結果

Validate Commodore MPS-801 serial dot matrix printer behavior in EMULATORS, including SerialPrinterMPS801 classes and their MatrixPrinterEmulation and SerialPrinterPeripheralSimulation hierarchy, IEC/KERNAL-trap printer routing, device numbers, secondary addresses, PETSCII/character sets, 6x7 glyphs, double width, graphics mode, reverse field, tab and dot positioning, line/page geometry, PostScript output, and fidelity boundaries. Use when Codex reviews or edits COMMODORE MPS801 printer code, generated printer output, PostScript printer templates, C64/VIC-20/C264 serial-printer behavior, or compares implementation against .codex/docs/MPS801.pdf and historical MPS-801 sources.

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

Validate Commodore MPS-802 and 1526 serial dot matrix printer behavior in EMULATORS, including SerialPrinterMPS802 classes and their MatrixPrinterEmulation and SerialPrinterPeripheralSimulation hierarchy, IEC/KERNAL-trap printer routing, device numbers, secondary-address functions, PETSCII/character sets, 8x8 glyphs, enhanced width, reverse and paging modes, formatter strings, programmable characters, line/page geometry, PostScript output, and fidelity boundaries. Use when Codex reviews or edits COMMODORE MPS802 printer code, generated printer output, PostScript printer templates, C64/VIC-20/C264 serial-printer behavior, or compares implementation against .codex/docs/MPS802.pdf, the MPS-802 user guide, and 1526/MPS-802/4023 service information.

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

Validate Commodore 1540/1541/1541C/1541-II compatible disk-drive behavior in EMULATORS, including IEC serial bus protocol, device numbers, KERNAL traps, CBM DOS commands/status, D64 image parsing, BAM/directory/file chains, PETSCII filenames, 6502 drive CPU/ROM/RAM expectations, 6522 VIA wiring, GCR/track/sector geometry, motor/head timing, and compatibility boundaries for 1541-like devices. Use when Codex reviews or edits C64, VIC-20, C264, COMMODORE disk, serial I/O, D64, CBM DOS, IEC, VIA, GCR, or 1541 drive code.

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

Validate and implement Sinclair ZX Spectrum 16K/48K ULA and board-level behavior in the EMULATORS repository, including PAL/NTSC raster timing, bitmap and attribute fetches, FLASH/BRIGHT/INK/PAPER rendering, CPU clock generation, lower-RAM and I/O contention, floating bus, snow effect, DRAM addressing and refresh, port FE keyboard/tape/border/sound behavior, interrupts, and ULA revision boundaries. Use when Codex reviews or edits namespace ZXSPECTRUM ULA, ULARegisters, Memory, PortManager, Screen, Sound, Datasette, Z80 bus timing, raster, contention, or ZX Spectrum hardware tests.

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

SOP for the micro-execution C.O.R.E. phase. Trigger when: - Implementing plan steps, managing code changes at commit boundaries, and verifying incremental progress. - Navigating states: Absorb, Clarify, Plan, Execute. - Prompt contains: /core, core workflow, absorb, clarify, execution invariants, commit boundary, verify assertion.

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

Volatility-based decomposition review. Trigger when: - Evaluating module boundaries against axes of change and business volatility. - Prompt contains: /lowy, volatility, axis of change, design decomposition, boundary.

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

Build, install, validate, and debug custom Exasol virtual schema adapters. Covers source-specific JDBC dialect implementation with `virtual-schema-common-jdbc` including `SqlDialect`, metadata reader behavior, type mapping, and pushdown capabilities, custom document-file adapter code boundaries, custom adapter properties, JAR packaging, BucketFS deployment, adapter script setup, `EXPLAIN VIRTUAL` validation, and adapter-side remote debugging workflows.

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

Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.

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

Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.

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

Create, verify, transfer, and resume compact project handoff packets for long-running Codex work. Use after a second observed automatic context compaction, immediately after a third compaction, when attention or constraints degrade, a major phase ends, the user asks to move work into a fresh task, work must pause, or an existing handoff needs to be imported. Do not interrupt after the first normal compaction. Always ask before creating a new task, transfer the global roadmap only after explicit consent, preserve the old task title when available, then require the fresh task to ask what work matters most. Preserve objectives, constraints, decisions, evidence, approval boundaries, workspace state, validation, and risks without treating an old summary as current truth.

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

Architecture design and governance protocol for system structure, boundaries, contracts, APIs, schemas, migrations, rewrites, and long-lived codebase health. Use when designing or reviewing architecture, planning structural refactors or migrations, governing tech debt, or containing rewrite risk. Keeps the load-bearing spine small, owned, checked, and deletable over time.

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

Turn 'should never happen' into 'cannot happen' by defining owned inductive invariants and enforcing them at parse/construct/API/DB/lock/txn boundaries with a verification signal. Use when prompts mention invariants, impossible states, validation sprawl, cache/index drift, idempotency/versioning, retries/duplicates/out-of-order events, race/linearization bugs, loop correctness, or hardening another workflow (for example /tw-fix) with invariant checks first.

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

Gauntlet for absolute claims (always/never/guaranteed/optimal); pressure-test, then refine with explicit boundaries. Use when users ask to prove or disprove strong certainty claims, request devil's-advocate challenge rounds, or want the /tw-prove-it gauntlet to run all 10 rounds continuously by default.

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

Implement functional Clawix UI wiring while respecting visual mutation boundaries, pattern contracts, protected surfaces, and debt baselines.

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

Split or contain large source files according to the source-file boundary ADR without changing behavior opportunistically.

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

Review secret handling, brokered execution, redaction, vault boundaries, host approval, and public hygiene.

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

Knowledge base from NIST SP 800-37 Revision 2, the Risk Management Framework (RMF) for information systems and organizations. Use for the seven RMF steps (Prepare, Categorize, Select, Implement, Assess, Authorize, Monitor) and their tasks; the three-tier organization-wide risk model; authorization boundaries; the requirements-to-controls relationship; security categorization (FIPS 199/200 high-water mark) and control selection/tailoring (SP 800-53/53B baselines); assessment, the authorization decision and risk acceptance, continuous monitoring and ongoing authorization; the security/privacy distinction; and supply chain risk management. This is the security-and-privacy-risk-governance edge of systems engineering — it governs how much protection and whether to accept residual risk, complementing the disciplines that decide how protection is built. Does NOT reproduce the SP 800-53 control catalog or its baselines, the FIPS impact tables, or the ISO/IEC/IEEE 15288 process text; it names and routes to them rather than restating them.

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

Project-first Research pipeline with live gates, source/PDF evidence, claim boundaries, compute and publication controls; includes an optional PubMed/arXiv standard-library helper.

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

Reviews one SKILL.md against the format rules and returns a findings table: strict YAML front matter with exactly name and description, name equal to the folder, description as the trigger, the eight-heading skeleton, capability-neutral wording, safety boundaries. Each finding carries severity, rule identifier, location, quoted evidence and replacement text; the verdict READY, REVISE or BLOCKED is an apparent state and the owner decides. Use when the user asks to "review this SKILL.md", "check my skill file before upload", "lint this skill description", "validate the front matter of this skill" or "score this skill folder". Do not use to write an agent's instructions field, use agent-instructions-drafter instead; for injection or leakage exposures use agent-instructions-red-team; for launch tests use agent-evaluation-plan. Drafts for human review; never approves, authorises or signs off.

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

Checks an extracted PFD register as a process model and returns findings and unknowns only: connectivity closure, stream numbering, presence of design conditions, equipment duty text, phase and service labels, package and off-sheet scope, boundaries, operating cases, and agreement between the drawing and attached process documents, then holds at gate G2. Creates no design values. Use when the user asks to "check the process model", "verify connectivity" or "is the PFD ready for enrichment" after gate G1 and before enrichment. Do not use for extraction from the drawing, use pfd-intake-and-extraction instead; do not use to propose lines or instruments, use piping-enrichment. Drafts for human review; never approves, authorises or signs off.

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

Write a self-contained handoff document so another session, person or machine continues the work without this session's context: decisions and why, what is done and tested, exact paths and values, open blockers, boundaries, and an explicit continue-from-here step. Lands in a synced folder with a short seed prompt. Triggers: "/handoff", "prepare a handoff", "hand this off".

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

Search indexed YouTube and podcast transcripts for quotes, speakers and clip boundaries with timestamped source links using Arcmira.

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

Design and review native presenter classes in WordPress plugins without requiring better-data - converting DTOs or domain objects into REST arrays, admin table rows, JS config payloads, email variables, and public view models with allowlisted fields, context methods, redaction by default, locale/date/number formatting, no DTO mutation, and correct WordPress escaping boundaries. Use when adding FooPresenter, response mappers, admin-row arrays, wp_send_json payloads, rest_ensure_response data, wp_add_inline_script config, or when code returns raw DTOs, WP_Post, WC_Order, get_object_vars, json_encode, or unescaped HTML from controllers.

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

Handle UTF-8 and text encoding safely in WordPress plugins, especially on WP 6.9+ where wp_is_valid_utf8(), wp_scrub_utf8(), and noncharacter helpers replace older seems_utf8-style checks. Covers when to validate, scrub, reject, or preserve invalid bytes; wp_check_invalid_utf8 behavior; XML/JSON/feed/export boundaries; and avoiding data loss from premature replacement. Use when processing imported text, CSV, XML, feeds, email, REST payloads, AI prompts, logs, filenames, or external API data.

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