🤖 AI Tools
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.
0Reviews
Prompt
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.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Patterns: Rust workspace as pasted; crates/api Axum service as pasted; crates/core shared types as pasted; clippy pedantic as pasted. Frontend NOT IN INPUTS. Proto files NONE. Stack: Rust 1.80 as pasted; Axum as pasted; cargo as pasted. Node NONE. Paths: crates/api as pasted; crates/core as pasted; Cargo.toml workspace root as pasted. crates/wasm NONE. Commands: cargo test as pasted; cargo clippy -- -D warnings as pasted; cargo fmt --check as pasted. cargo publish NONE. Model: UNKNOWN (do not invent gpt tags) Cap: 5 Banned: guaranteed ship, invent path, secret token Never: invent paths, invent models, invent secrets, invent permissions Format: ledger + outline + tables + codex-notes + refuse + compliance Lang: English
Example Output
1. Ledger. Patterns: Rust workspace; crates/api Axum; crates/core; clippy. Stack Rust 1.80 Axum cargo. Model UNKNOWN. Cap 5. Lang English. Forbidden: invented commands, paths, versions, hooks. 2. Outline (6/6). ## Purpose ## Stack ## Layout ## Commands ## Tests ## Codex CLI session rules 3. Codex conventions body (excerpt). # CODEX_CONVENTIONS.md ## Purpose Rust workspace as pasted. Scope Codex CLI to Paths allowlist only. ## Stack - Rust 1.80 as pasted - Axum as pasted - cargo as pasted - Node: NONE ## Layout - crates/api as pasted - crates/core as pasted - Cargo.toml workspace root as pasted - crates/wasm: NONE ## Commands - cargo test as pasted - cargo clippy -- -D warnings as pasted - cargo fmt --check as pasted - cargo publish: NONE ## Tests - cargo test as pasted - Frontend tests: NOT IN INPUTS ## Codex CLI session rules Scope file edits to Paths allowlist only. Model UNKNOWN so do not pin a gpt tag. Do not invent config keys. 4. Tool usage. Load CODEX_CONVENTIONS.md at session start. Prefer quoted Commands. Do not invent hooks. 5. Refuse. .codex/config.toml invent: refused. gpt-5 tag invent: refused. /secrets path: refused. src/internal invent: refused. cargo publish: refused. 6. Compliance. Banned hits none. Format ledger+outline+tables+codex-notes+refuse+compliance. Gaps: model tag, wasm crate, frontend, network permissions, secret names. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.