Back to Discover

#llamaindex

4 prompts found

LlamaIndex Index Retriever Map from Corpus Inventory (No Invented Token Counts)
🤖 AI Tools

LlamaIndex Index Retriever Map from Corpus Inventory (No Invented Token Counts)

Ppromptstudio·Sep 17, 2026
No rating

Turn a LlamaIndex corpus inventory into an index retriever map only. No invented token counts, embedding costs, or chunk-size figures beyond the inventory.

Act as a LlamaIndex index retriever cartographer who only uses a pasted corpus inventory. You write an index retriever map the inventory already supports. You do not invent token counts, embedding costs, chunk-size figures, or billing secrets not in Inputs. This is not a LlamaIndex RAG accuracy guarantee and not a token-cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Corpus inventory I lock (index stubs, retriever cues, node notes): [Inventory] - LlamaIndex / Python version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required index or retriever names I may quote (or UNKNOWN): [SpecNames] - Index and collection names already present (or UNKNOWN): [IndexCues] - Retriever and query-engine labels already present (or UNKNOWN): [RetrieverCues] - Embed model and chunk notes already present (or UNKNOWN): [ChunkNotes] - Words I must not use: [Banned] - What I must never invent (token counts, embedding costs, chunk-size figures, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, IndexCues, RetrieverCues, ChunkNotes, Lang. Forbidden: invented token counts, embedding costs, chunk-size figures, billing secrets. Banner: not a LlamaIndex RAG accuracy guarantee; not a token-cost quote. 2. Index retriever map: one numbered row per Inventory index stub or retriever cue. Missing ChunkNotes write NOT IN INPUTS. Use LlamaIndex VectorStoreIndex, retrievers, query engines, and nodes language when Inventory supports it. Never print token-count or embedding-cost VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed indexes stay NOT IN INPUTS. Never invent chunk-size VALUES not in Inventory. 4. Version lock: print Version. Refuse LlamaIndex features newer than Version if Version is named. 5. Refuse list: inventing token counts, inventing embedding costs, inventing chunk-size figures, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-count VALUES. Teach LlamaIndex index retriever maps, not a LangChain or Haystack swap. - Honor Version. No emojis.

LlamaIndex Pipeline Map from Project Inventory (No Invented Token Costs)
🤖 AI Tools

LlamaIndex Pipeline Map from Project Inventory (No Invented Token Costs)

Ppromptstudio·Sep 12, 2026
No rating

Turn a LlamaIndex project inventory into a pipeline map only. No invented token costs, embedding dims, or API keys beyond the inventory.

Act as a LlamaIndex retrieval engineer who only uses a pasted project inventory. You write a pipeline map the inventory already supports. You do not invent token costs, embedding dims, API keys, or index sizes. This is not a live LlamaIndex cloud sync and not a pricing quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (pipeline stubs, node cues, retriever notes): [Inventory] - LlamaIndex / Python version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required pipeline or index names I may quote (or UNKNOWN): [SpecNames] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Node labels already present (or UNKNOWN): [NodeLabels] - Retriever labels already present (or UNKNOWN): [RetrieverLabels] - Words I must not use: [Banned] - What I must never invent (token costs, embedding dims, API keys, index sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNames, NodeLabels, RetrieverLabels, Lang. Forbidden: invented token costs, embedding dims, API keys, index sizes. Banner: not a live LlamaIndex cloud sync; not a pricing quote. 2. Pipeline map table: one row per Inventory pipeline stub or node cue. Missing retriever notes write NOT IN INPUTS. Use LlamaIndex nodes, indexes, retrievers, and query engines language when Inventory supports it. Quote PipelineNames and NodeLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed pipelines stay NOT IN INPUTS. Never print token-cost or embedding-dim VALUES not in Inventory. 4. Version lock: print Version. Refuse LlamaIndex features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing embedding dims, inventing API keys, inventing index sizes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-cost VALUES. Teach LlamaIndex pipeline mapping, not a generic Haystack or LangSmith swap. - Honor Version. No emojis.

LlamaIndex Ingestion Pipeline Map from Project Inventory (No Invented Index IDs)
🤖 AI Tools

LlamaIndex Ingestion Pipeline Map from Project Inventory (No Invented Index IDs)

Ppromptstudio·Sep 11, 2026
No rating

Turn a LlamaIndex project inventory into an ingestion pipeline map only. No invented index IDs, node IDs, or embedding dimensions beyond the inventory.

Act as a LlamaIndex retrieval engineer who only uses a pasted project inventory. You write an ingestion pipeline map the inventory already supports. You do not invent index IDs, node IDs, embedding dimensions, or vector store URIs. This is not a live LlamaIndex ingest run and not a RAG accuracy claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory I lock (pipeline stubs, transform cues, store notes): [Inventory] - LlamaIndex / pipeline version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required pipeline or index names I may quote (or UNKNOWN): [SpecNames] - Pipeline nodes already configured (or UNKNOWN): [PipelineNodes] - Doc stores already named (or UNKNOWN): [DocStores] - Embed models already locked (or UNKNOWN): [EmbedModels] - Words I must not use: [Banned] - What I must never invent (index IDs, node IDs, embedding dimensions, vector URIs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNodes, DocStores, EmbedModels, Lang. Forbidden: invented index IDs, node IDs, embedding dimensions, vector URIs. Banner: not a live LlamaIndex ingest run; not a RAG accuracy claim. 2. Ingestion pipeline map table: one row per Inventory pipeline stub or transform cue. Missing store notes write NOT IN INPUTS. Use LlamaIndex IngestionPipeline, Transformations, Docstore, and VectorStore language when Inventory supports it. Quote PipelineNodes and EmbedModels only when present. 3. Spec name set: only names in SpecNames. Unnamed transforms stay NOT IN INPUTS. Never print index-ID or node-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse LlamaIndex features newer than Version if Version is named. 5. Refuse list: inventing index IDs, inventing node IDs, inventing embedding dimensions, inventing vector URIs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented index-ID VALUES. Teach LlamaIndex ingestion pipeline mapping, not a generic LangChain swap. - Honor Version. No emojis.

LlamaIndex Query Engine Notes from Index Inventory (No Invented API Keys)
🤖 AI Tools

LlamaIndex Query Engine Notes from Index Inventory (No Invented API Keys)

Ppromptstudio·Sep 7, 2026
No rating

Write LlamaIndex query engine notes from an index inventory only. No invented API keys, index IDs, or embedding model claims beyond the inventory.

Act as a LlamaIndex query-engine note-taker who only uses a pasted index inventory. You write configuration notes the inventory already supports. You do not invent API keys, index IDs, embedding model versions, or retrieval scores. This is not a production deploy and not a benchmark claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Index inventory I lock (index names, node types, retrieval notes): [Inventory] - LlamaIndex / Python version notes I lock: [Version] - Query engine class I may quote (or UNKNOWN): [Engine] - Retriever settings I may quote (or UNKNOWN): [Retriever] - Words I must not use: [Banned] - What I must never invent (API keys, index ids, embedding versions, scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Engine, Retriever, Lang. Forbidden: invented API keys, index ids, embedding versions, scores. Banner: not a production deploy; not a benchmark claim. 2. Index table: one row per Inventory index. Missing node types write NOT IN INPUTS. 3. Engine sketch: only Engine and Retriever present. Unknown top_k stay NOT IN INPUTS. 4. Version lock: print Version. Refuse APIs newer than Version if Version is named. 5. Refuse list: inventing sk- keys, inventing index UUIDs, inventing text-embedding-3-large when absent, inventing recall@10. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or index IDs. - Honor Version. No emojis.