القائمة
Verify Supabase connection, TypeScript health, and schema before any database or implementation work. Use when starting a session, before migrations, or when something feels off.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Read ACT's energy-orbit relational CRM — where a person sits (supporter ring vs community constellation), their evidence or owes, flags (violation/dupe/ghost/uncaptured), and the gated next move. Read-only by default; never auto-writes. Use when user says "orbit", "/orbit", "where does <person> sit", "show me the orbit", "is <person> on the wrong lane / a community-line violation", "who's uncaptured", or wants to read or act on the relationship system before any GHL write.
BAS quarter preparation, receipt acquittal, and learning loop for ACT. Use for BAS prep, missing receipt hunts, vendor reconciliation, and quarterly retrospectives. Accumulates patterns and learnings across quarters so each BAS cycle gets cleaner.
Drives the NAB Visa
Query actual database schema before writing any query, migration, or API endpoint. Prevents wrong column names — the
Review and tag untagged Xero transactions / bank lines / invoices with project codes — the cross-project spend & income alignment workflow. Use when user says "tag transactions", "fix transaction tagging", "improve transaction coverage", or "align spend/income across projects".
OCAP consent gate. Run BEFORE publishing, syndicating, or externally sharing ANY storyteller content — a story, quote, name, photo, or video — to wiki story pages, newsletters, Empathy Ledger syndication, social, funder decks, or the website. Grills the consent provenance, verifies names and place names, and BLOCKS publish if the audit trail is incomplete or anything is unverified. Use whenever you are about to make community or storyteller content visible outside ACT.
| name | preflight |
| description | Verify Supabase connection, TypeScript health, and schema before any database or implementation work. Use when starting a session, before migrations, or when something feels off. |
Run this mandatory checklist before any database or implementation work.
# Check which project MCP is connected to
mcp__supabase__get_project_url
Cross-reference with expected projects (refs verified 2026-06-01 against codebase + memory command-center-finance-truth):
tednluwflfhxyucgwigh — Command Center, Telegram bot, GrantScope, scripts (operational DB; all money/finance work)yvnuayzslukamizrlhwb — Empathy Ledger v2 storyteller contentuaxhjzqrdotoahjnxmbj — media-only public storage; serves the story-media/ gallery image URLs in minderoo-gallery.json (NOT unused — don't deprovision without rehosting)If the URL doesn't match the project you need, STOP and tell the user.
Run via MCP:
SELECT current_database(), count(*) as table_count
FROM information_schema.tables
WHERE table_schema = 'public';
Report the table count. If it seems wrong (e.g., expecting 571 tables but seeing 153), you're on the wrong project.
cd apps/command-center && npx tsc --noEmit 2>&1 | head -20
Report: clean or number of errors found.
For any tables you'll be working with, query the actual schema:
SELECT column_name, data_type, is_nullable
FROM information_schema.columns
WHERE table_name = '<table>'
ORDER BY ordinal_position;
Keep this in context and reference it when writing queries or migrations.
For finance/money tables, also load the money guards before any dollar-emitting query — see the db-check skill's "Money tables" section + memory command-center-finance-truth.md (exclude DELETED, never SUM via supabase-js, two-account rule, verify vs project_monthly_financials).
Summarize: