fix: add scaffolding triggers and reference loading guide to supabase-postgres-best-practices#99
Open
JesseVent wants to merge 1 commit into
Conversation
…-postgres-best-practices Greenfield prompts like 'create a supabase backend' previously loaded zero references from this skill because the description only triggered on optimization/performance vocabulary. Two changes: - Extend description to include scaffolding/setup language - Add Reference Loading Guide table so the model knows which references to load for each scenario rather than guessing from file titles alone
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
supabase-postgres-best-practicesreferences never load when an agent is given a greenfield scaffolding task. Prompts likecreate a supabase backend,use supabase as the database, orI'm building a new app with Supabasepreviously returned zero references from this skill — the agent proceeded using stale training data to make schema decisions.Tested against
claude-haiku-4.5without the skill, the model produced@supabase/auth-helpers-nextjs(deprecated),NEXT_PUBLIC_SUPABASE_ANON_KEY(old key name), andcreateClientas a singleton (wrong pattern for App Router).Root Cause
Two compounding issues:
1. Description only triggers on optimization vocabulary
An agent scaffolding a new project isn't "optimizing" — it's building from scratch. The trigger never fires.
2. Skill body had no conditional loading guidance
The model was left guessing which references to load from file titles alone. For vague prompts, titles like
query-missing-indexes.mddon't match.Changes
supabaseskillEval Results
Tested with
claude-haiku-4.5, 97 prompts.create a supabase backenduse supabase as the databaseI'm building a new app with SupabaseI'm new to Supabase, where do I startTotal reference loads across all 97 prompts: 227 → 245 (+18). No regressions on existing prompts. All 63 tests pass.
Closes #100