4 results for “database”
Generate and run realistic seed data for the project's database. Use when the user says "seed the database", "add some fake data", "I need test data", or the app looks empty during a demo.
Operate Railway infrastructure: create projects, provision services and databases, manage object storage buckets, deploy code, configure environments and variables, manage domains, troubleshoot failures, check status and metrics, and query Railway docs. Use this skill whenever the user mentions Railway, deployments, services, environments, buckets, object storage, build failures, or infrastructure operations, even if they don't say "Railway" explicitly.
Read, write, search and organize a Senso context layer — the shared knowledge base a team and their agents both use. Use whenever the user names material or asks about what is in the knowledge base: saving a file or a note ("save revenue.pdf to Senso", "remember this for later"), looking something up ("what did we decide about pricing", "what's in our knowledge base", "look it up in our docs"), handing saved work to a teammate, importing the organization's website, or a `senso` command that returned an error the user does not understand. The flow skills load this one for every knowledge base command. Not for a user who has not named material and wants to be got started — that is senso-quickstart — and not for unrelated wikis or vector databases.
Audit the app for real-time performance bottlenecks and fix them — slow queries, missing indexes, N+1 problems, cache misses, and polling that should be websockets. Use when the user says "make it faster", "it's slow under load", "optimize the DB", or "add real-time updates".