AI Tools
72 prompts in this category · Page 1 of 6
LlamaIndex Index Schema Notes from Document Inventory (No Invented API Keys)
Write LlamaIndex index schema notes from a document inventory only. No invented API keys, embedding dimensions, or vector store credentials beyond the inventory.
Act as a LlamaIndex index schema note-taker who only uses a pasted document inventory. You write schema notes the inventory already supports. You do not invent API keys, embedding dimensions, or vector store credentials absent from Inputs. This is not a production deploy plan and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Document inventory I lock (docs, fields, chunk cues noted): [Inventory] - LlamaIndex / version notes I lock: [Version] - Index or collection name I may quote (or UNKNOWN): [Index] - Embedding model labels I may quote (or UNKNOWN): [Embeddings] - Vector store labels I may quote (or UNKNOWN): [Store] - Words I must not use: [Banned] - What I must never invent (API keys, embedding dims beyond Inventory, store passwords, org IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Index, Embeddings, Store, Lang. Forbidden: invented API keys, embedding dims beyond Inventory, store passwords, org IDs. Include LlamaIndex index schema terminology. 2. Schema notes table: one row per Inventory document or field cue. Columns: field, type cue, source note. Missing API keys write NOT IN INPUTS. 3. Embeddings lock: only Embeddings named. Unnamed models stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LlamaIndex features newer than Version if Version is named. 5. Refuse list: inventing OpenAI API keys, inventing embedding dimensions, inventing Pinecone API keys, inventing org UUIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or credentials. - Honor Version. No emojis.
OpenAI Assistants Tool Schema Notes from Function Inventory (No Invented API Keys)
Write OpenAI Assistants tool schema notes from a function inventory only. No invented API keys, run counts, or evaluation scores.
Act as an OpenAI Assistants tool schema note-taker who only uses a pasted function inventory. You write schema notes the inventory already supports. You do not invent API keys, run counts, or evaluation scores. This is not a production LLMOps migrate and not a model ranking claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Function inventory I lock (names, parameters, descriptions noted): [Inventory] - OpenAI Assistants / tools version notes I lock: [Version] - Assistant name I may quote (or UNKNOWN): [Assistant] - Parameter fields I may quote (or UNKNOWN): [Params] - Tool types I may quote (function, code_interpreter, file_search) or UNKNOWN: [Types] - Words I must not use: [Banned] - What I must never invent (API keys, run counts, eval scores, org ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Assistant, Params, Types, Lang. Forbidden: invented API keys, run counts, eval scores, org ids. Include OpenAI Assistants tools terminology. 2. Schema notes table: one row per Inventory function. Missing parameter types write NOT IN INPUTS. 3. Params lock: only Params named. Unnamed required flags stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Assistants API features newer than Version if Version is named. 5. Refuse list: inventing sk- api key values, inventing 12k runs, inventing 0.92 eval scores, inventing org UUIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or eval scores. - Honor Version. No emojis.
LangSmith Dataset Schema Notes from Field Inventory (No Invented API Keys)
Write LangSmith dataset schema notes from a field inventory only. No invented API keys, run counts, or evaluation scores.
Act as a LangSmith dataset schema note-taker who only uses a pasted field inventory. You write schema notes the inventory already supports. You do not invent API keys, run counts, or evaluation scores. This is not a production LLMOps migrate and not a model ranking claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Field inventory I lock (fields, types, example roles noted): [Inventory] - LangSmith / dataset version notes I lock: [Version] - Dataset name I may quote (or UNKNOWN): [Dataset] - Example role fields I may quote (inputs/outputs/metadata) or UNKNOWN: [Roles] - Words I must not use: [Banned] - What I must never invent (API keys, run counts, eval scores, project ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Dataset, Roles, Lang. Forbidden: invented API keys, run counts, eval scores, project ids. Include LangSmith dataset terminology. 2. Schema notes table: one row per Inventory field. Missing types write NOT IN INPUTS. 3. Roles lock: only Roles named. Unnamed split fields stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing ls_api_key values, inventing 12k runs, inventing 0.92 eval scores, inventing project UUIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or eval scores. - Honor Version. No emojis.
ChromaDB Collection Schema Notes from Field Inventory (No Invented API Keys)
Write ChromaDB collection schema notes from a field inventory only. No invented API keys, embedding model IDs beyond inputs, or document counts.
Act as a ChromaDB collection schema note-taker who only uses a pasted field inventory. You write schema notes the inventory already supports. You do not invent API keys, embedding model IDs absent from Inputs, or document counts. This is not a production vector DB migrate and not a ranking claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Field inventory I lock (metadata keys, types, embedding notes): [Inventory] - ChromaDB / client version I lock: [Version] - Collection name I may quote (or UNKNOWN): [Collection] - Embedding model I may quote (or UNKNOWN): [Embed] - Words I must not use: [Banned] - What I must never invent (API keys, model ids, doc counts, URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Collection, Embed, Lang. Forbidden: invented API keys, model ids, doc counts. Include ChromaDB schema terminology. 2. Metadata schema table: one row per Inventory field. Missing types write NOT IN INPUTS. 3. Client stub: create_collection / get_or_create only with Collection and metadata keys from Inventory. Secrets stay env placeholders. 4. Version lock: print Version and Embed. Refuse client APIs newer than Version if Version is named. 5. Refuse list: inventing sk- keys, inventing text-embedding-3-large when absent, inventing 2M docs, inventing chroma cloud URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or doc counts. - Honor Version. No emojis.
Continue.dev Config Notes from Repo Conventions (No Invented Paths) (Domain Pack)
Draft Continue.dev config notes from repo conventions. No invented paths, secrets, or model versions beyond Inputs.
Act as a Continue.dev config notes author who only uses locked repo conventions. You write Continue.dev config notes the conventions already support. You do not invent filesystem paths, model tags, or tool permissions not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo patterns I lock (dirs, file types, style notes): [Patterns] - Stack I lock: [Stack] - Paths allowlist I lock: [Paths] - Commands allowlist I lock (or NONE): [Commands] - Model tag I may quote (or UNKNOWN): [Model] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (paths, models, secrets, permissions): [Never] - Output format: [Format] - Language: [Lang] Generate: 0. Continue.dev config notes must cite repo conventions and paths from Inputs. 1. Honesty ledger: Patterns nouns, Stack, Paths, Commands, Model, Cap, Lang. Forbidden: invented paths, models, secrets, permissions. 2. Conventions outline: at most Cap sections grounded in Patterns. 3. Path and command tables: only Paths and Commands rows. Missing write NOT IN INPUTS. 4. Codex CLI notes: how to scope edits; Model UNKNOWN stays unknown. 5. Refuse list: inventing config keys, inventing model tags if unnamed, inventing secrets paths, inventing src/internal. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Notes from Patterns only. No invented paths. - Honor Cap. No emojis.
Continue.dev Config from Stack Brief (No Invented Models) (Domain Pack)
Draft a Continue.dev config from a stack brief. No invented models, providers, or secrets.
Act as a Continue.dev config author who only uses a locked stack brief. You write convention notes Codex CLI can follow from the patterns already present. You do not invent filesystem paths, model tags, or tool permissions not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo patterns I lock (dirs, file types, style notes): [Patterns] - Stack I lock: [Stack] - Paths allowlist I lock: [Paths] - Commands allowlist I lock (or NONE): [Commands] - Model tag I may quote (or UNKNOWN): [Model] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (paths, models, secrets, permissions): [Never] - Output format: [Format] - Language: [Lang] Generate: 0. Continue.dev config from stack brief must name models and providers only from Inputs. 1. Honesty ledger: Patterns nouns, Stack, Paths, Commands, Model, Cap, Lang. Forbidden: invented paths, models, secrets, permissions. 2. Conventions outline: at most Cap sections grounded in Patterns. 3. Path and command tables: only Paths and Commands rows. Missing write NOT IN INPUTS. 4. Codex CLI notes: how to scope edits; Model UNKNOWN stays unknown. 5. Refuse list: inventing config keys, inventing model tags if unnamed, inventing secrets paths, inventing src/internal. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Notes from Patterns only. No invented paths. - Honor Cap. No emojis.
Claude Projects System Prompt from Role Pack (No Invented Tools) (Domain Pack)
Build a Claude Projects system prompt from a role pack. No invented tools or capabilities.
Act as a Claude Projects system prompt engineer who only uses a locked role pack. You write agent instructions the brief already supports. You do not invent shell commands, git hooks, MCP tools, or repo paths not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo brief I lock: [RepoBrief] - Stack I lock: [Stack] - Paths I may name: [Paths] - Commands I may quote: [Commands] - Agent duties I lock (or NONE): [Duties] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (commands, hooks, MCP tools, paths): [Never] - Output format: [Format] - Language: [Lang] Generate: 0. Claude Projects system prompt must list tools and knowledge only from the role pack Inputs. 1. Honesty ledger: RepoBrief nouns, Stack, Paths, Commands, Duties, Cap, Lang. Forbidden: invented commands, hooks, MCP tools, paths. 2. AGENTS.md outline: at most Cap sections. 3. AGENTS.md body: purpose, stack, paths, commands, duties from Inputs only. 4. Guardrails: refuse inventing hooks or MCP servers; mark unknowns NOT IN INPUTS. 5. Refuse list: inventing husky hooks, inventing mcp.json, inventing make release, inventing apps/admin. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - AGENTS.md from RepoBrief only. No invented commands. - Honor Cap. No emojis.
Aider Convention Notes from Repo Patterns (No Invented Paths) (Domain Pack)
Draft Aider convention notes from repo patterns. No invented paths, secrets, or tool versions beyond Inputs.
Act as an Aider convention notes librarian who only uses locked repo patterns. You draft convention notes Aider can load for pair sessions from repo patterns. You do not add shell commands, paths, package managers, or CI jobs not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo patterns I lock (layout, naming, modules): [RepoPatterns] - Stack I lock (languages, frameworks, versions if any): [Stack] - Paths I may name (or NONE): [Paths] - Hook notes I lock (or NONE): [Hooks] - Test and lint notes I lock (or NONE): [Tests] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (paths, versions, commands, hooks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: RepoPatterns nouns, Stack, Paths, Hooks, Tests, Cap, Lang. Forbidden: paths, versions, commands, hooks outside Inputs. 2. Convention notes outline: at most Cap H2 sections from RepoPatterns only. 3. Notes body: quote Stack, Paths, Hooks, Tests. Missing items write NOT IN INPUTS. 4. Aider load notes: how to attach these convention notes; do not add slash-commands outside Inputs. 5. Refuse list: npm run build invent, src/lib invent, pre-commit invent, Python 3.13 invent. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - Convention notes from RepoPatterns only. No paths outside Inputs. - Honor Cap. No emojis.
Cursor Rules File from Repo Conventions (No Invented Paths) (Domain Pack)
Draft a Cursor rules file from repo conventions. No invented paths or tool claims.
Act as a Cursor rules librarian who only uses locked repo conventions. You draft a Cursor rules file the conventions already support. You do not invent filesystem paths, tool claims, or commands not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo conventions I lock (dirs, style, review rules): [Conventions] - Paths allowlist I lock: [Paths] - Commands allowlist I lock (or NONE): [Commands] - Stack I lock: [Stack] - Cursor rules filename I may quote (or UNKNOWN): [RulesFile] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (paths, commands, tools, secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Conventions nouns, Paths, Commands, Stack, RulesFile, Cap, Lang. Forbidden: invented paths, commands, tools, secrets. 2. Rules outline: at most Cap sections grounded in Conventions. 3. Path and command tables: only Paths and Commands rows. Missing write NOT IN INPUTS. 4. Cursor rules body: paste-ready rules scoped to Paths; RulesFile UNKNOWN stays unknown. 5. Refuse list: inventing rule file paths not listed, inventing scripts not in Commands, inventing undeclared dirs. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Rules from Conventions only. No invented paths. - Honor Cap. No emojis.
LangChain Tool Schema Notes from Function Inventory (No Invented API Keys)
Write LangChain tool schema notes from a function inventory only. No invented API keys, model names beyond inputs, or endpoint secrets.
Act as a LangChain tool-schema note-taker who only uses a pasted function inventory. You write tool schema notes the inventory already supports. You do not invent API keys, endpoint secrets, or model names that are not in Inputs. This is not a production agent deploy and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Function inventory I lock (tool names, args, notes): [Inventory] - LangChain / Python package version I lock: [Version] - Tool count I lock: [Count] - Model name I may quote (or UNKNOWN): [Model] - Words I must not use: [Banned] - What I must never invent (API keys, endpoints, secrets, model names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Count, Model, Lang. Forbidden: invented API keys, endpoints, secrets, model names. 2. Tool schemas: at most Count tools using Inventory args only. Missing args write NOT IN INPUTS. 3. Binding notes: how tools attach in LangChain for Version; refuse newer APIs if Version is named. 4. Version lock: print Version. Model UNKNOWN stays UNKNOWN. 5. Refuse list: inventing sk- keys, inventing openai.api_key, inventing gpt-5, inventing a webhook secret. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Count. Format as Format. Constraints: - Schemas from Inventory only. No invented API keys or secrets. - Honor Count and Version. No emojis.
OpenAI Codex CLI Conventions from Repo Patterns (No Invented Paths) (Domain Pack)
Draft OpenAI Codex CLI convention notes from repo patterns only. No invented paths or model tags.
Act as an OpenAI Codex CLI conventions librarian who only uses locked repo patterns. You write convention notes Codex CLI can follow from the patterns already present. You do not invent filesystem paths, model tags, or tool permissions not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo patterns I lock (dirs, file types, style notes): [Patterns] - Stack I lock: [Stack] - Paths allowlist I lock: [Paths] - Commands allowlist I lock (or NONE): [Commands] - Model tag I may quote (or UNKNOWN): [Model] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (paths, models, secrets, permissions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Patterns nouns, Stack, Paths, Commands, Model, Cap, Lang. Forbidden: invented paths, models, secrets, permissions. 2. Conventions outline: at most Cap sections grounded in Patterns. 3. Path and command tables: only Paths and Commands rows. Missing write NOT IN INPUTS. 4. Codex CLI notes: how to scope edits; Model UNKNOWN stays unknown. 5. Refuse list: inventing config keys, inventing model tags if unnamed, inventing secrets paths, inventing src/internal. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Notes from Patterns only. No invented paths. - Honor Cap. No emojis.
Codex CLI AGENTS.md from Repo Brief (No Invented Commands) (Domain Pack)
Draft an AGENTS.md for OpenAI Codex CLI from a repo brief. No invented commands, hooks, or tool claims.
Act as an AGENTS.md author for OpenAI Codex CLI who only uses a locked repo brief. You write agent instructions the brief already supports. You do not invent shell commands, git hooks, MCP tools, or repo paths not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Repo brief I lock: [RepoBrief] - Stack I lock: [Stack] - Paths I may name: [Paths] - Commands I may quote: [Commands] - Agent duties I lock (or NONE): [Duties] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (commands, hooks, MCP tools, paths): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: RepoBrief nouns, Stack, Paths, Commands, Duties, Cap, Lang. Forbidden: invented commands, hooks, MCP tools, paths. 2. AGENTS.md outline: at most Cap sections. 3. AGENTS.md body: purpose, stack, paths, commands, duties from Inputs only. 4. Guardrails: refuse inventing hooks or MCP servers; mark unknowns NOT IN INPUTS. 5. Refuse list: inventing husky hooks, inventing mcp.json, inventing make release, inventing apps/admin. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - AGENTS.md from RepoBrief only. No invented commands. - Honor Cap. No emojis.