mock-vs-real-detector

Apply this skill WHEN verifying that a route, page, or integration serves REAL data and not silent mock/placeholder data. Detects the "false-green" failure mode: an endpoint returns 200 (or a page renders) while the underlying data is fabricated because a provider is unconnected. Trigger WHENEVER classifying a section's readiness, reviewing integration wrappers, or before marking anything GREEN. P2 — load on audit/verify tasks.

インストールへ移動

リポジトリ: CleanExpo/Unite-Group
ソースの最終更新活動: 2026年6月12日 05:29
検出された SKILL.md の言語: 英語
スター: 0
フォーク: 0

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。

npx skills add https://github.com/CleanExpo/Unite-Group --skill mock-vs-real-detector

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md

ソースの指示 · 読み取り専用プレビュー

検索に戻るインストールに戻る

env-var-canon

The authoritative environment-variable registry for the Unite-Group Nexus. Use whenever adding, reading, renaming, or debugging an env var or secret — new integration config, a `process.env.X` read, an auth/OAuth wiring, a cron secret, a "which variable holds this" question, or a "works locally but not in prod" symptom. Also use before pinning any variable name in code, and when reconciling the two credential planes (Vercel prod vs the local hermes fleet). Prevents the `APIFY_API_KEY` vs `APIFY_API_TOKEN` class of drift.

2026-08-07

supabase-db-branch

Create, verify, and promote Supabase schema changes via database branches. Every schema change/migration must be validated on a Supabase database branch before prod (see CLAUDE.md line 44).

2026-07-12

supabase-schema-gate

Verify production Supabase schema before shipping code that touches it. Use BEFORE writing or reviewing ANY code that reads or writes a Supabase table in the Nexus — new queries, inserts, updates, CHECK-constrained values, RLS-dependent reads, cron data access — even one-line changes and even when the table "obviously" exists. Also use immediately when a query fails with "column does not exist", when inserts appear to succeed but produce no rows, or when generated TypeScript types disagree with runtime behaviour.

2026-07-12

このリポジトリのすべてを見る

Mock-vs-Real Detector

The Default Being Overridden

Left unchecked, LLMs default to:

Treating an HTTP 200 as proof the data is real
Treating a rendered page as proof it is wired to a backend
Marking a section "working" because it compiles and returns a shape

This skill overrides those defaults with: a 200 is not evidence. Real data must be proven by tracing the source discriminator end-to-end.

ABSOLUTE RULES (Never Violate)

NEVER mark a section GREEN while it can return source: 'mock' without the caller surfacing it. NEVER present mock/placeholder data as real to the user. Fail loud, not fake. ALWAYS trace: page → fetch → API route → integration → does it have a getMock* fallback?

Detection checklist

Run these greps against the section under audit:

# 1. Silent mock fallbacks in integrations
rg "getMock|source:\s*'mock'|mockData|placeholder|TODO|FIXME|hardcoded" src/lib/integrations src/app/api/<section>

# 2. Pages that render a component but fetch nothing (facade detection)
#    A page.tsx with no await/fetch/createClient and just <SomeClient /> is a facade
rg -L "await|fetch|createClient|getUser" src/app/<section>/page.tsx

# 3. Integration "connected?" gates — confirm the route surfaces the unconnected state
rg "isXeroConfigured|isConfigured|connected|hasToken|accessToken" src/app/api/<section>

Classification rule

Signal	Class
Real fetch + auth guard + `.eq('founder_id', user.id)` + no silent mock	GREEN
Returns real data but can silently fall back to mock / missing source surfacing	AMBER
Page renders a component that fetches nothing; or route returns hardcoded data	RED

The required fix for AMBER (silent mock)

A degradable integration MUST return a discriminated result and the caller MUST surface it:

// integration
return connected
  ? { data, source: 'xero' as const }
  : { data: null, source: 'not_connected' as const }   // NOT 'mock'

// caller (page/route) — explicit, never silent
if (result.source === 'not_connected') {
  return <NotConnectedState provider="Xero" connectHref="/founder/xero" />
}

Prefer an explicit "not connected" empty-state over a mock fallback for anything user-facing. Reserve mock strictly for tests and local dev — never let it reach a dashboard.

Output format

Report each item as: path | class | source-trace | fix. List RED+AMBER first. Cite file:line.

name	mock-vs-real-detector
category	verification
version	1.0.0
priority	P2
auto_load	false
triggers	["auditing a route or page for production readiness","classifying a section GREEN/AMBER/RED","reviewing integration code (xero/gmail/calendar/linear/social)","any time a 200 response or rendered UI must be proven to be real data"]
description	Apply this skill WHEN verifying that a route, page, or integration serves REAL data and not silent mock/placeholder data. Detects the "false-green" failure mode: an endpoint returns 200 (or a page renders) while the underlying data is fabricated because a provider is unconnected. Trigger WHENEVER classifying a section's readiness, reviewing integration wrappers, or before marking anything GREEN. P2 — load on audit/verify tasks.

name	mock-vs-real-detector
category	verification
version	1.0.0
priority	P2
auto_load	false
triggers	["auditing a route or page for production readiness","classifying a section GREEN/AMBER/RED","reviewing integration code (xero/gmail/calendar/linear/social)","any time a 200 response or rendered UI must be proven to be real data"]
description	Apply this skill WHEN verifying that a route, page, or integration serves REAL data and not silent mock/placeholder data. Detects the "false-green" failure mode: an endpoint returns 200 (or a page renders) while the underlying data is fabricated because a provider is unconnected. Trigger WHENEVER classifying a section's readiness, reviewing integration wrappers, or before marking anything GREEN. P2 — load on audit/verify tasks.