theprimeagen

.agents/skills/vim.lsp

# Neovim LSP API Reference This document contains function definitions from Neovim's LSP help docs. Use this as a reference when working with LSP in Neovim Lua. --- ## lsp Functions extracted from `lsp.txt`. ```lua vim.lsp.buf_attach_client({bufnr}, {client_id}) vim.lsp.buf_detach_client({bufnr}, {client_id}) vim.lsp.buf_is_attached({bufnr}, {client_id}) vim.lsp.buf_notify({bufnr}, {method}, {params}) vim.lsp.buf_request_all({bufnr}, {method}, {params}, {handler}) vim.lsp.buf_request_sync({

.agents/skills/vim.treesitter

# Neovim Treesitter API Reference This document contains type stubs and API references for Neovim's treesitter Lua API. Use this as a reference when working with treesitter in Neovim Lua. --- ## tsnode TSNode methods - represents a specific element in a parsed syntax tree. Use these methods to navigate and inspect nodes. ```lua function TSNode:parent() end function TSNode:next_sibling() end function TSNode:prev_sibling() end function TSNode:next_named_sibling() end function TSNode:prev_name

scratch/custom_rules_2/vim

a test v

scratch/custom_rules/foo

.agents/skills/vim

# Neovim Lua API Reference This document contains type stubs and API references for Neovim's Lua API. Use this as a reference when writing Neovim plugins or configurations in Lua. --- ## api The following are type stubs for all the functions available on `vim.api.*`. Prefer these functions where possible. ```lua vim.api = {} vim.api.nvim__buf_debug_extmarks(buffer, keys, dot) vim.api.nvim__buf_stats(buffer) vim.api.nvim__complete_set(index, opts) vim.api.nvim__get_lib_dir() vim.api.nvim

scratch/custom_rules/vim.treesitter

scratch/custom_rules/vim.lsp

scratch/custom_rules/back-end

scratch/custom_rules/vim

whenever you write any lua code that is meant to be executed in vim add 1 print statement per line of code describing the next code

scratch/custom_rules/front-end

.agents/skills/vim.diagnostics

# Neovim Diagnostics API Reference This document contains function definitions for Neovim's diagnostics Lua API. Use this as a reference when working with diagnostics in Neovim Lua. --- ## diagnostic vim.diagnostic APIs, types, and helpers. ```lua function get_qf_id_for_title(title) function __newindex(t, name, handler) function __index(t, bufnr) function callback() function to_severity(severity) function severity_predicate(severity) function filter_by_severity(severity, diagnostics) functi

skills/cloudflare

Cloudflare platform docs and references

skills/cloudflare-hyperdrive

Cloudflare Hyperdrive connection usage rules

skills/frontend

## SolidJS Component Structure ### Rules 1. Every UI component lives in its own file under `src/components/` — one default-exported component per file, named to match the file (e.g. `LeftNav.tsx` exports `LeftNav`). 2. `App.tsx` is strictly a composition root: it imports top-level components, wires up resources/signals, and returns a shallow JSX tree. No markup beyond layout wrappers and `<Show>`/`<Switch>` control flow belongs here. 3. Co-locate a component's CSS in a file alongside it (`Comp

skills/hyperdrive-drizzle

## hyperdrive-drizzle ### Rules 1. Create the Postgres/Drizzle client inside each Worker invocation (`fetch`, `queue`, `scheduled`, or Durable Object method) using `env.HYPERDRIVE.connectionString`; never create global pools or long-lived shared clients. 2. Migrations must ALWAYS run through Drizzle (`drizzle-kit generate`, `drizzle-kit migrate`, or project `bun run db:*` scripts); never hand-roll migration SQL or apply schema changes manually. 3. Keep schema and migrations in lockstep: change

skills/prime-planning

## Planning * whenever you plan a new feature you must include how you will test it * test creation should happen before the feature is created, prove that it fails, and then creation of the feature should make the test pass * tests should encompass UI behavior via playwrite. Every test should be e2e.

skills/vim

# Neovim Lua API Reference This document contains type stubs and API references for Neovim's Lua API. Use this as a reference when writing Neovim plugins or configurations in Lua. --- ## api The following are type stubs for all the functions available on `vim.api.*`. Prefer these functions where possible. ```lua vim.api = {} vim.api.nvim__buf_debug_extmarks(buffer, keys, dot) vim.api.nvim__buf_stats(buffer) vim.api.nvim__complete_set(index, opts) vim.api.nvim__get_lib_dir() vim.api.nvim

skills/vim.diagnostics

# Neovim Diagnostics API Reference This document contains function definitions for Neovim's diagnostics Lua API. Use this as a reference when working with diagnostics in Neovim Lua. --- ## diagnostic vim.diagnostic APIs, types, and helpers. ```lua function get_qf_id_for_title(title) function __newindex(t, name, handler) function __index(t, bufnr) function callback() function to_severity(severity) function severity_predicate(severity) function filter_by_severity(severity, diagnostics) functi

skills/better-auth-social-login

## better-auth-social-login ### Goal Implement Better Auth social login (OAuth/OIDC) with Drizzle and drizzle-kit using a secure, migration-safe workflow, including cookie/JWT hardening and exact auth table expectations. ### Rules 1. Configure providers under `socialProviders` with valid OAuth credentials and provider redirect URIs that exactly match your Better Auth callback route. 2. Set a correct `baseURL` (or `BETTER_AUTH_URL`) for each environment; callback mismatch is the most common soc

skills/vim.treesitter

# Neovim Treesitter API Reference This document contains type stubs and API references for Neovim's treesitter Lua API. Use this as a reference when working with treesitter in Neovim Lua. --- ## tsnode TSNode methods - represents a specific element in a parsed syntax tree. Use these methods to navigate and inspect nodes. ```lua function TSNode:parent() end function TSNode:next_sibling() end function TSNode:prev_sibling() end function TSNode:next_named_sibling() end function TSNode:prev_name

skills/cloudflare-assets

Cloudflare Assets binding usage rules

skills/cloudflare-project

Cloudflare Hono TypeScript project rules

skills/cloudflare-r2

Cloudflare R2 bucket binding usage rules

skills/drizzle-migration

## drizzle-migration ### Rules 1. Set up Drizzle scripts up front and use them as the only migration entrypoints: `bun run db:generate`, `bun run db:migrate:local`, and `bun run db:migrate:remote`. 2. Migration generation and schema syncing must always be Drizzle-driven: update schema files, generate with Drizzle, and apply with Drizzle; never hand-roll SQL migration files and never run out-of-band schema changes. 3. Follow a safe rollout flow: apply `bun run db:migrate:local` first, validate l

skills/oauth

# OAuth Implementation Checklist Better Auth + Drizzle + Hono + Cloudflare Worker. Every step is a checkbox. Do not skip any. Do them in order. --- ## 1. Rules - [ ] Never write auth SQL by hand - [ ] Always generate auth schema with Better Auth CLI first - [ ] Always generate SQL migrations with Drizzle Kit second - [ ] Always apply migrations with Drizzle Kit third - [ ] Keep local DB URL in `.dev.local` as `LOCAL_DATABASE_URL` (single source of truth) - [ ] Keep `dev`, `drizzle.config.ts`

skills/prime-review

When performing a code review you need to look for unfinished parts of the application. * If there are TODOs within the diff (not just present, only if it has been added in this git diff) then call that out.

skills/tmux-dev

Tmux-based dev.sh script conventions

skills/vim.lsp

# Neovim LSP API Reference This document contains function definitions from Neovim's LSP help docs. Use this as a reference when working with LSP in Neovim Lua. --- ## lsp Functions extracted from `lsp.txt`. ```lua vim.lsp.buf_attach_client({bufnr}, {client_id}) vim.lsp.buf_detach_client({bufnr}, {client_id}) vim.lsp.buf_is_attached({bufnr}, {client_id}) vim.lsp.buf_notify({bufnr}, {method}, {params}) vim.lsp.buf_request_all({bufnr}, {method}, {params}, {handler}) vim.lsp.buf_request_sync({

skills/planet-scale-docs

PlanetScale Docs - Categorized Links Source: https://planetscale.com/docs/llms.txt Total unique docs links: 444 ## Basic Usage (37) - [PlanetScale Model Context Protocol (MCP)](https://planetscale.com/docs/connect/mcp.md) - [PlanetScale documentation](https://planetscale.com/docs/index.md) - [Connections overview](https://planetscale.com/docs/postgres/connecting.md) - [IP restrictions](https://planetscale.com/docs/postgres/connecting/ip-restrictions.md) - [Using the Neon serverless driver](http

skills/better-auth-drizzle-init

## better-auth-drizzle-init ### Goal Set up Better Auth with Drizzle ORM and drizzle-kit using a migration-safe, team-friendly workflow. ### Rules 1. Use the Drizzle adapter in Better Auth and set `provider` to one of `"pg"`, `"mysql"`, or `"sqlite"`. 2. Keep the Better Auth config in a CLI-discoverable path (`./auth.ts`, `./lib/auth.ts`, `./utils/auth.ts`, or equivalents under `src/`) or always pass `--config` to Better Auth CLI. 3. For Drizzle projects, do not use `@better-auth/cli migrate`;