Loading...
Loading...
Found 209 Skills
Record transaction flow in accordance with unified rules. Save records by individual stock in Markdown format, and simultaneously write to SQLite for statistics and quantitative review.
Use when designing schema, writing migrations, writing transactions/concurrent code, optimizing queries, reviewing SQL or ORM code, or seeding/testing data for SQLite, MySQL, or PostgreSQL. Covers safety guards for destructive operations (DROP/TRUNCATE/ALTER), schema/data-type mapping across the three dialects, transaction and locking correctness, migration rollback safety, indexing/EXPLAIN-based query optimization, and evidence-based code review. Trigger this whenever a task touches a database connection, schema, SQL statement, or ORM query for any of these three engines.
Runs the forward-only Drift/SQLite schema-migration ritual — the most dangerous deterministic operation in an offline-first app: a bad migration silently destroys on-device rows that exist nowhere else. Enforces the exact ordered sequence: take a pre-migration file snapshot before the database is opened, bump schemaVersion by exactly one, write an append-only stepByStep forward step (never edit a shipped step, never write a down migration), commit the drift_dev make-migrations schema snapshot, regenerate, then prove it with tests covering every from→to path (incl. multi-version jumps), a write-at-v(n)/read-at-v(n+1) content test, PRAGMA integrity_check + foreign_key_check, and a forced mid-migration throw that restores the snapshot. Manual, side-effecting workflow. Use when adding or altering a Drift table, column, index, or CHECK; bumping schemaVersion; editing onUpgrade/stepByStep; or writing migration tests.
Insert campaigns, ad groups, keywords, and RSA ads directly into Google Ads Editor's local SQLite database. Bypass CSV import workflow.
Governs the on-device Drift/SQLite data layer: package:drift and package:sqlite3 confined to lib/data/ behind DAOs that map rows to immutable value objects (no Drift symbol leaks past the repository), invariants pushed into the schema (STRICT tables, CHECK/FK/partial-UNIQUE indexes), foreign_keys/WAL pragmas re-asserted idempotently in beforeOpen, one db.transaction per mutation, persist-before-publish, every query awaited, canonical integer storage, derived state recomputed-on-read never stored, scoped .watch streams, keyset (seek) pagination not OFFSET, and WAL-safe backups (checkpoint + VACUUM INTO, verify-by-reopen, never File.copy a live WAL DB). Use when defining or altering a Drift Table, Companion, DAO, index, or CHECK; writing a repository transaction or scoped watch provider; wiring the connection/beforeOpen pragmas; adding SQLCipher; building or verifying a backup; or reviewing a data-layer diff. Migrations and their tests live in run-migration.
Query macOS iMessage database (chat.db) via SQLite. Decode NSAttributedString messages, handle tapbacks, search conversations. TRIGGERS - imessage, chat.db, messages database, text messages, iMessage history, NSAttributedString, attributedBody
Pull every meal you ever logged out of MyFitnessPal — per-food CSV, agent-shaped trends, and a local SQLite store. Trigger phrases: `what did I eat this week`, `export my food diary`, `find every time I logged X`, `top foods driving my protein`, `am I hitting my calorie streak`, `use myfitnesspal`, `run myfitnesspal`.
Build, ship, and scale simple or full-stack Telegram bots and Mini Apps on Telegram Serverless with V8 JS, SQLite (sdk/db), Mini App RPC, and tgcloud. Use for any Telegram Serverless project—from a single-file bot handler to a stateful Mini App with tgcloud.jsonc static hosting, SQLite migrations (tgcloud migrate), sdk/api, sdk/fetch, Telegram.WebApp.Serverless.call, or Telegram Stars (XTR) payments.
Build with D1 serverless SQLite database on Cloudflare's edge. Use when: creating databases, writing SQL migrations, querying D1 from Workers, handling relational data, or troubleshooting D1_ERROR, statement too long, migration failures, or query performance issues. Prevents 14 documented errors.
Use when building, editing, or deploying code on Val Town - the serverless Deno platform. Triggers on val.town, vals, vt CLI, std/sqlite, std/openai, std/blob, esm.town imports, .http.tsx/.cron.tsx/.email.tsx file naming, deno.json with valtown.d.ts types, or HTTP/cron/email triggers needing free OpenAI, SQLite, blob storage, or scheduled execution.
Store and retrieve memories (notes, facts, decisions, snippets, images) using a local SQLite database with full-text search. Use when you need to remember information across sessions, recall previous decisions, store code snippets, or search your knowledge base.
Manage daily check-in records stored in local SQLite, supporting functions including adding check-ins, viewing records, statistical analysis, querying consecutive check-in days, deleting and modifying records. This skill should be actively used when users mention check-in, sign-in, recording daily habits such as exercise, reading, learning, fitness, meditation, running, cycling, etc., or want to check how many days they have stuck to a certain habit, how much time they spent exercising this week, what they checked in today. Even if the user does not explicitly say "check-in", it is applicable as long as it involves daily habit tracking and activity recording. It also works for English scenarios, such as check in, log my workout, track my reading, how many days in a row, streak, habits.