「cat」の検索結果

Spring Boot 4.0 patterns for enterprise Java 25 applications

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

Deploy applications to Vercel with auto-detection and preview URLs

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

Routes agent management tasks to the correct manager agent. Use when user requests agent creation, updates, audits, git operations, or verification.

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

Spec-Driven Development workflow — enforces sdd/ folder hierarchy with planning-first gates, current-state artifacts, and completion verification

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

React/Next.js performance optimization with 40+ rules in 8 categories

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

10-team parallel deep analysis with cross-verification for any topic, repository, or technology. Use when user invokes /research or asks for comprehensive research.

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

Full R017 verification (5+3 rounds) before commit

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

Quantitative agent evaluation using 4-metric framework (correctness/step_ratio/tool_call_ratio/latency_ratio) with ideal trajectory annotation and capability-categorical taxonomy. Use when measuring agent efficiency, comparing agent variants, or gating new agents through correctness→efficiency phases. Complements harness-eval (SE benchmarks) and evaluator-optimizer (qualitative rubric).

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

Django patterns for production-ready Python web applications

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

On explicit /homework invocation, analyze the current and linked previous sessions, extract mistakes (찐빠), and report them via omcustom-feedback with a confirmation gate. Auto-activation on session cleanup/session-end signals is OPT-IN (default OFF) — requires an explicit project/user directive. Use when explicitly auditing recent work for harness gaps.

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

Multi-angle release quality verification using parallel expert review teams

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

CVE triage workflow for vulnerability analysis, reproduction assessment, and patch verification

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

PostHog integration for React Router v6 applications

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

Skill for adding or updating educational algorithm guides, ensuring consistent patterns and simple explanations suitable for an 8-year-old.

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

Prepare a traceable local Fusion engineering review draft with source identities, artifacts and unresolved assurance gates. Not for sending, publication or release approval.

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

Configure and diagnose Fusion interoperability, transport selection, scoped profiles and qualification. Use for setup or connection problems, not design edits.

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

Stage and verify Fusion exports, drawing PDFs, flat-pattern DXF, viewport images and local renders. Use for engineering deliverables, not automatic publication or release.

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

Document-driven workflow for implementing, reviewing, and verifying Chisel processor and memory-subsystem RTL. Use when Codex must work from maintained Architecture and Design, trace a complete integration surface, reason in synthesized-hardware terms, keep source-adjacent _codex.md summaries current, avoid redundant or overprotective logic, or run focused functional verification.

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

Task-sized forensic analysis of Vivado synthesis and routed timing evidence for processor RTL. Use when Codex must trace a named setup or hold path, audit whole-design timing populations, compare implementation runs, map primitive, LUT, CARRY, BRAM, DSP, MUXF, register, and routed-net stages back to Chisel or generated RTL, distinguish logic from routing pressure, identify missing DCP queries, or write an evidence-backed timing report. This skill is read-only by default and stops at ranked modification directions. Use optimize-chisel-fpga-timing for RTL edits and routed A/B implementation closure.

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

Establish, author, restructure, or audit human-first processor Architecture, Design, Research, Review, and Verification documentation. Use for progressive documentation scaffolding, authority maps, reading paths, document-type content contracts, length-budgeted splitting, or maintainability reviews. Do not use as a substitute for cycle-accurate microarchitecture analysis or RTL implementation.

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

Use before non-trivial coding work to pick a task-appropriate working mode — debug, fix, review, test-first, refactor, optimize, migrate, upgrade, integrate, spike, or unstuck — then follow its checklist. Modes are procedures, not personas. Not needed for trivial one-line edits or non-coding tasks.

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

Use when the user asks about Codex Rules behavior, injected project rules, supported rule file locations, matching, or environment configuration.

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

Connect business positioning to a concrete visual language. Maps strategic positioning (category, differentiator, who-it's-for, who-it's-against) onto visual decisions — palette, type, imagery, tone — so the look reinforces the strategy. Use when the user says "positioning into visuals", "what should the brand look like given our strategy", "align visuals with positioning", or is moving from strategy to brand expression. Part of the Creative Production set.

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

Turn a reference image or mockup into a working local frontend that matches it closely. Inspects the image, extracts the design system (layout, type, spacing, color, components), implements it, then screenshot-compares and iterates to close the gap. Use when the user says "image to code", "build this mockup", "code this screenshot", "make this design real", or provides a UI image to implement. Part of the Product Design set. Uses a browser tool for screenshot verification.

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