القائمة
Performance review discipline for algorithms, database queries, rendering, network behavior, caching, concurrency, memory, benchmarks, and scalability risks in code, data, and frontend work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Metric, SQL, dbt, dashboard, semantic-layer, and BI validation discipline for high-stakes analytics work. Use for grain, joins, nulls, filters, freshness, lineage, reconciliation, dashboard semantics, and decision relevance checks.
Compact task-state and handoff ledger for long Opus 4.8 High sessions, subagent orchestration, compaction, and resumable workflows. Use to preserve decisions, files, commands, evidence, risks, and next actions while dropping noisy logs.
Classify high-rigor work into S0-S4 scope levels and choose the minimal sufficient subagent set. Use for ultracode-high orchestration, complex coding, analytics, BI, strategy, writing, audits, migrations, and multi-domain tasks.
Evidence, claim, assumption, and uncertainty ledger for high-rigor agent work. Use when synthesizing research, analytics, code review, strategy, or writing so important claims are labeled as verified, calculated, inferred, assumed, or unknown with source evidence.
Final response contract for ultracode-high and high-rigor subagent workflows. Use to synthesize work into a relayable result with changes, verification, final-gate improvements, risks, and next actions.
Gate vocabulary and runner support for ultracode-high. Use to define precondition and completion gates, prefer deterministic command/file/grep gates where possible, flag attestation gates honestly, and run gates with the bundled gate_check.py helper.
| name | performance-rigor |
| description | Performance review discipline for algorithms, database queries, rendering, network behavior, caching, concurrency, memory, benchmarks, and scalability risks in code, data, and frontend work. |
| model | claude-opus-4-8 |
| effort | high |
Identify the bottleneck before optimizing.
This skill is part of ultracode-high. For the full orchestration map, tool
catalog, agent roster, and card schemas, read
../ultracode-high/references/runtime-context.md when available. Performance
claims should become measurements or clearly labeled hypotheses.
Do not trade correctness, security, or maintainability for unmeasured speed.
