القائمة
Review staged rollouts so fallback paths stay visible, narrow and never fake success
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | honest-fallback-review |
| description | Review staged rollouts so fallback paths stay visible, narrow and never fake success |
| domain | quality |
| confidence | high |
| source | earned — mortgage comparator MVP live-first API consumption and local preview hardening |
Use this when the UI can degrade to local preview or partial backend support. The quality gate is simple: fallback may preserve continuity, but it must never disguise missing or broken backend behavior as a successful live result.
/api/v1 missing or feature_not_implemented on compare).500, contract drift or malformed payloads should surface unavailable/error states, not synthetic comparison success.api, local_preview or unavailable, and keep notices/user copy aligned with that source.apps/web/src/services/analysis-api.test.tsapps/web/src/pages/mortgage-analysis-page.tsxapps/web/tests/e2e/mortgage-comparison.spec.tsapps/api/tests/contract/analyses-lifecycle.contract.test.ts, apps/api/tests/integration/analysis-retention.test.tsPilot a community Spec Kit extension without pretending it is trusted, official, or a hard gate
Lock what an analytical financial redesign may beautify, but never hide, reorder, or distort
Test tripwires for mortgage analysis UI redesign — preserves logic integrity through visual changes
Choose Spec Kit extensions that reinforce real repo gaps without duplicating existing orchestration
Run Spec Kit through the repo-pinned official CLI and keep the official git extension as the branch workflow source of truth
Freeze cross-cutting contracts before parallel implementation starts