VibeRaven Guides

Use this when the user asks what a VibeRaven finding id means, for example rls_disabled or env_var_drift, or pastes a finding from a VibeRaven 1.6.1 report. Returns what the rule detects in repository files, why it matters, how to fix it and what it does not check, quoted from viberaven.dev with a source link for each part. It does not read the user's repository, database or Vercel project. Known ids: rls_disabled, rls_no_policies, rls_policy_allows_all_read, rls_policy_allows_all_write, security_definer_function_executable, pooler_port_mismatch, service_role_key_in_client_code, env_var_drift. An unknown id returns found: false and the list of known ids.

{
  "type": "object",
  "properties": {
    "gap_id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100,
      "description": "The finding id as printed by VibeRaven, for example rls_disabled."
    }
  },
  "required": [
    "gap_id"
  ],
  "additionalProperties": false
}

{
  "type": "object",
  "properties": {
    "found": {
      "type": "boolean"
    },
    "gap_id": {
      "type": "string"
    },
    "viberaven_version": {
      "type": "string"
    },
    "named_on": {
      "type": "string"
    },
    "detects": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "text": {
            "type": "string"
          },
          "source": {
            "type": "string"
          }
        },
        "required": [
          "text",
          "source"
        ]
      }
    },
    "why_it_matters": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "text": {
            "type": "string"
          },
          "source": {
            "type": "string"
          }
        },
        "required": [
          "text",
          "source"
        ]
      }
    },
    "how_to_fix": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "text": {
            "type": "string"
          },
          "source": {
            "type": "string"
          }
        },
        "required": [
          "text",
          "source"
        ]
      }
    },
    "does_not_check": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "text": {
            "type": "string"
          },
          "source": {
            "type": "string"
          }
        },
        "required": [
          "text",
          "source"
        ]
      }
    },
    "known_ids": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "found",
    "viberaven_version"
  ]
}

Use this when the user has a launch question about an AI-built app on Vercel + Supabase, such as Supabase RLS, env vars on Vercel, a Stripe webhook after deploy or a client handoff. Searches the launch guides published on viberaven.dev by keyword and returns up to 5 matches, each with its title, URL and the short answer from the page. It only searches those published pages: it does not browse the web or read the user's project. No match returns an empty list.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 200,
      "description": "A few keywords from the question, for example \"supabase tables missing rls\"."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

{
  "type": "object",
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string"
          },
          "url": {
            "type": "string"
          },
          "answer": {
            "type": "string"
          }
        },
        "required": [
          "title",
          "url",
          "answer"
        ]
      }
    }
  },
  "required": [
    "results"
  ]
}

Use this when the user wants a manual pre-launch checklist for a Lovable + Supabase app or a Next.js + Supabase app on Vercel. Returns the checklist published on viberaven.dev for that stack with its sources, and the one optional local VibeRaven step (`npx -y [email protected] check`), which is advice, not a gate. The items are manual checks the user does in their dashboards and code; this tool does not run any of them.

{
  "type": "object",
  "properties": {
    "stack": {
      "type": "string",
      "enum": [
        "lovable-supabase",
        "nextjs-supabase-vercel"
      ],
      "description": "lovable-supabase for a Lovable app with Supabase, nextjs-supabase-vercel for a Next.js app with Supabase deployed on Vercel."
    }
  },
  "required": [
    "stack"
  ],
  "additionalProperties": false
}

{
  "type": "object",
  "properties": {
    "stack": {
      "type": "string"
    },
    "title": {
      "type": "string"
    },
    "url": {
      "type": "string"
    },
    "short_answer": {
      "type": "string"
    },
    "items": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "optional_repo_check": {
      "type": "object",
      "properties": {
        "command": {
          "type": "string"
        },
        "details": {
          "type": "string"
        }
      },
      "required": [
        "command",
        "details"
      ]
    },
    "sources": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "stack",
    "title",
    "url",
    "short_answer",
    "items",
    "optional_repo_check",
    "sources"
  ]
}