「bounded」の検索結果

Design, preview, implement, and assess mini-program interfaces against an approved prototype, screenshot, visual reference, design system, or bounded UI request while preserving product semantics and existing accepted behavior. Use when users ask to reproduce a mini-program screen, refine visual hierarchy, adapt layouts across device sizes, handle safe areas or keyboards, inspect touch targets, scrolling, media, or gesture conflicts, compare an implementation with a reference, or prepare a device-verification matrix. Separates proposed visual previews, user approval, source integration, local checks, and real-device evidence; never invents product functionality for visual completeness or claims device validation without device-specific proof.

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

Translate a confirmed mini-program product specification or bounded feature into an implementable architecture covering modules, pages, components, services, canonical state sources, data models, interfaces, permissions, failures, caching, concurrency, idempotency, migration, rollback, external dependencies, and architecture decision records. Use when users ask how to structure a mini program, design data or APIs, divide frontend and cloud responsibilities, evolve an existing system safely, or prepare implementation after product semantics are stable. Preserves product meaning, current repository constraints, user-owned changes, and verifiable acceptance behavior rather than redesigning the product for technical convenience.

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

Implement bounded features and fixes in existing or new mini-program codebases while preserving repository rules, user-owned changes, approved behavior, assets, framework conventions, and evidence boundaries. Use when users ask to write or modify mini-program code, implement a confirmed specification or architecture, add a scoped feature, remove behavior semantically, update internal documentation required by a change, or carry out a well-defined small fix that does not require root-cause investigation. Establishes a baseline and change boundary, applies test-driven small steps, distinguishes source from generators and build artifacts, verifies the affected contract, and never reports source completion as device validation, formal acceptance, upload, or release.

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

Execute bounded, reproducible experiment rounds.

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

Reviews Remix v2 form code for manual fetch() mutations, native <form> misuse, wrong useNavigation/useFetcher choice, missing pending state, unbounded uploads, and intent-pattern violations. Use when reviewing form/mutation code in a Remix v2 codebase.

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

Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never treat another vendor's session ID as portable.

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

Audits Solidity liquidation mechanisms for denial of service vulnerabilities including unbounded loops over positions causing out-of-gas reverts, data structure corruption preventing liquidation, front-running to block liquidation via nonce changes or self-liquidation, pending withdrawals forcing reverts, malicious ERC721/ERC20 callback reverts, collateral in external vaults not seized, insufficient insurance fund blocking liquidation, fixed bonus exceeding available collateral, incorrect decimal handling, conflicting nonReentrant modifiers, zero value transfer reverts, token deny list issues, and single borrower edge cases

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

Expert guide for Domain-Driven Design (DDD). Covers tactical patterns (Aggregates, Value Objects), strategic patterns (Bounded Contexts), event storming, and CQRS / Panduan ahli Desain Berbasis Domain (DDD).

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

Manages skill-creator integration with GSD workflows including skill loading, session observation, bounded learning guardrails, and pattern detection. Use this skill whenever: executing any GSD phase (to ensure relevant skills are loaded first), starting or resuming a work session (to check for pending suggestions), the user asks about skills, patterns, or skill-creator status, performing code changes that might represent repeating patterns, the user corrects Claude's output (highest-signal observation), or when skill refinement, creation, or suggestion review is discussed. Critical for maintaining the adaptive learning layer.

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

Use when independently assessing how bounded Python code could accomplish the same behavior with less maintained code, more Pythonic design, newer language/stdlib capabilities, or well-maintained ecosystem libraries.

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

Use when independently hunting Python code smells, deviations from engineering standards, maintenance hazards, or suspicious design choices in a bounded review surface.

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

Review a change for material performance regressions or unbounded resource behavior. Use for an independent performance perspective on a defined change set.

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

Create one-off outbound phone calls, web calls, scheduled calls, and simple batch calls using the Vapi API. Use when making or testing individual calls or initiating a bounded /call request programmatically. Use create-campaign for a persistent multi-contact Campaign with lifecycle, reporting, cancellation, duplication, or campaign webhooks.

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

Use this skill when a human needs to review a Deepline Play result and hand feedback, labels, or approval back to the agent for revision, evaluation, comparison, or bounded iteration. Triggers on “put this run in a Sheet,” “review these results,” “read my feedback,” “make this a standing rule,” “never regress on this case,” “compare these runs,” “keep improving,” or “add the revised run to the same spreadsheet.” Skip ordinary Play authoring or execution with no human review loop, generic spreadsheet work, and one-off CSV export.

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

Spawns full Claude Code peer sessions in separate terminal panes and git worktrees, real sessions rather than subagents, each with a directed task and contract brief, monitored and merged by the spawning lead. Detects the environment and uses herdr first, then tmux, then a native claude background agent. Use when work must persist or run beside the current session, needs a separate worktree or permission settings, should remain user-steerable in a visible pane, or when the user asks to spawn, hand off, or parallelize full sessions. Also spawns Codex peers into those panes. Excludes bounded consults and subagent-scale work.

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

Spawn full peer Codex or Claude sessions in their own panes and git worktrees — real sessions, not subagents — briefed by the lead and merged back. Not for bounded consults a subagent covers. Use when work must outlive or run beside this session, needs its own worktree, or must stay user-steerable.

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

Orchestrate complex work from an active gpt-6-astra or gpt-6.1-sol Codex session. The detected lead owns decomposition, integration, and verification; Astra keeps the hardest reasoning in the lead, while Sol escalates unusually difficult units to Astra. Both route bounded work to Sol at medium effort, mechanical work to Luna, and can use a cross-vendor Claude peer. Not for routine single-context work. Use when the user explicitly asks to orchestrate, delegate, fan out, parallelize, assign subagents, obtain independent checks, or have Codex act as tech lead.

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

Launch and collect independent Codex sessions (gpt-6-luna at high, xhigh or max; gpt-6.1-sol at low to xhigh) for bounded parallel work, from Claude Code or from Codex: one manifest, one detached launcher, one report a session, a drain while it runs, and a retry of the sessions that ended without a report. Owns the Codex transport when another skill sets the questions, as whole-run-investigation does for its lanes. Use when the operator asks for Luna or Sol sessions, a swarm, many sessions, a reasoning effort, a Codex subagent from Claude Code, or a later collection of reports. Tell a request to launch from one to wait and collect.

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

Reverse-engineer a supplied video into a shot-by-shot generation specification, displayed evidence frames, and paired Chinese-English prompt packages. Use for requests such as 视频反推提示词, 视频转提示词, 从视频生成提示词, 视频逆向提示词, 逐镜头反推, 分镜拆解并生成提示词, 反推视频 prompt, or video-to-prompt; also use for Veo, Sora, Kling, Wan, generic prompt adaptation, and bounded generate-compare-optimize loops. Do not use for ordinary video summaries or basic transcription.

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

Run Claude Code, Codex CLI, Gemini CLI, or OpenCode through bounded H100 post-training tasks and compare how well each agent improves a base LLM.

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

Assess a public HTTP(S) page before building browser automation, extraction, or an integration. Use this skill to collect bounded structural evidence, readiness signals, risk flags, acceptance tests, and remediation priorities without sending credentials or accessing private targets.

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

Add controlled retries to pytest runs so agents can contain flaky tests and report final failures without rerunning whole suites by hand.

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

Use GitHub Agentic Workflows to let an agent triage issues, inspect CI failures, or deliver scheduled repository upkeep inside GitHub Actions with explicit workflow definitions and reviewable runs. This is for bounded, repeatable repository operations, not for listing GitHub as a general coding platform.

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

Checks evidence about an unfamiliar autonomous agent before delegation, verifies signed Agent Guild passports, and returns a bounded hire, caution, or avoid recommendation without taking consequential action.

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