bigdata-company-brief

Build bull, base, and bear cases for a public company using Bigdata.com data — with explicit line-item assumptions, justified probability weights summing to 100%, a value or price per scenario with the bridge shown, a probability-weighted expected value and expected return versus spot, the upside/downside skew and risk-reward ratio, and what would move probability between the cases. Triggers: "scenario analysis for X", "bull base bear for X", "what's the upside and downside on X", "expected value for X", "probability-weighted view on X", "risk reward on X", "model out the cases for X".

Write a day-179 post-IPO note on the 180-day lock-up expiry using Bigdata.com data plus filings and market data. Covers lock-up terms from the prospectus (expiry date, covered holders, share count, early-release provisions), float and overhang math (post-expiry float, days-to-trade versus ADV), insider and VC selling-intention signals, positioning into the event (short interest, borrow, options skew), the historical lock-up-expiry effect with analogs, and a two-sided read. Balanced, no buy/avoid call. Triggers: "180-day lock-up expiry for X", "lockup expiration impact", "post-IPO day 179", "shares unlocking for X", "insider selling after lockup", "float expansion at lockup".

Write a day-365 post-IPO note on the 366-day founder and significant-investor lock-up expiry and float expansion toward 15-20%, using Bigdata.com data plus filings and market data. Covers the staggered lock-up structure from the prospectus, float expansion math and days-to-trade, the offsetting float-adjusted index reweight demand netted against new supply, a realistic read on whether founders actually sell, the dual-class governance angle, and a two-sided setup. Balanced, no buy/avoid call. Triggers: "366-day lock-up for X", "founder lock-up expiry", "float expansion for X", "post-IPO one year lockup", "index reweight after float increase", "founder selling after IPO".

Produce a balanced pre-IPO research note on an upcoming, not-yet-listed company using its S-1/F-1 plus Bigdata.com data. Covers deal structure (price range, shares, greenshoe, implied valuation, underwriters, lock-ups, share classes), two years plus interim financials, business model and funding history, TAM and listed comparables, IPO-window conditions, and 90-day sentiment — closing with bull and bear debates and watch points, never a participate/avoid call. Triggers: "analyze the IPO of X", "S-1 analysis", "upcoming listing for X", "IPO report on X", "should I look at X's IPO", "pre-IPO research on X", "X IPO valuation".

Give a fast, PM-style quick take on a stock using Bigdata.com data — a one-line current view, the 2-3 drivers that actually matter right now, the key risks and what would change the view, and the near-term setup with the next catalyst. Deliberately short: one page, no full thesis, no model. Triggers: "quick take on X", "what do you think of X", "give me a fast view on X", "thoughts on X", "X in a nutshell", "one-liner on X", "is X interesting right now".

Compare regions or blocs using Bigdata.com data — economic indicators, market performance, and cross-asset views — and turn that into an allocation recommendation. Covers growth, inflation, policy and labor per region, comparative developed-versus-emerging analysis, regional equity valuations, and fixed income and currency views for each. Triggers: "compare US vs Europe vs Asia", "which regions look attractive", "regional allocation", "developed vs emerging markets", "Europe vs US equities", "global allocation view".

Produce a comprehensive risk assessment for a public company using Bigdata.com data (10-K risk factors, 8-K material events, news, tearsheet financials). Covers six categories — regulatory and legal, competitive and moat erosion, operational, financial and balance sheet, macro, and management and governance — each rated by likelihood and impact, with a distress screen when leverage is stretched, mitigation status, a priority matrix, and a scenario bridge to value drivers. Triggers: "risk assessment for X", "assess risks for X", "what are the risks with X", "what could go wrong at X", "risk factors for X", "how risky is X", "downside risks for X".

State explicitly where your view on a public company differs from consensus, using Bigdata.com data. Establishes the consensus baseline from estimates and sell-side posture, applies the EPIC filter to candidate differentiators, frames the view on FaVeS (fundamentals, valuation, sentiment), and states the variant view as a specific, falsifiable claim with a time horizon — plus what the market is missing, why the mispricing persists, the evidence for the view, and what would disprove it. Triggers: "variant perception on X", "where do I differ from consensus on X", "what is the market missing on X", "non-consensus view on X", "what's priced in versus reality for X", "contrarian case for X".

About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.

Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.

Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.

Obtain or reuse a Prisma Postgres database and connect an application. Use when the user needs a database and has none configured ("I need a database", "add a Postgres database", "set up a database for this app"), runs or mentions `create-db` or `npx create-db`, or asks to set up or connect Prisma Postgres, including in v0 and the Vercel Marketplace. Hands Prisma ORM configuration to prisma-orm-setup; reuses an existing connection first and honors an explicit provider, driver, alternative ORM, or database-only choice.

Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).

Set up Prisma ORM in an application, connect its database, or troubleshoot the connection of an existing Prisma 6, 7, or 8 app. Defaults new applications to Prisma ORM 8 and loads the package-owned prisma-8 skill; keeps existing Prisma 6/7 apps on their version with provider references for PostgreSQL, MySQL, SQLite, SQL Server, CockroachDB, MongoDB, and Prisma Postgres.