From a65d67679dceccbaba1ef3b314ec9ce70fe80ed4 Mon Sep 17 00:00:00 2001 From: Jack Felke Date: Tue, 10 Mar 2026 12:23:43 -0700 Subject: [PATCH 1/2] add .preflight/ example config directory with commented starter files MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - examples/.preflight/config.yml — profile, related projects, thresholds, embeddings - examples/.preflight/triage.yml — keyword rules and strictness tuning - examples/.preflight/contracts/api.yml — manual cross-service contract definitions - examples/README.md — quick setup instructions - README.md — link to examples from config reference section --- README.md | 2 + examples/.preflight/config.yml | 35 ++++++++++++++++ examples/.preflight/contracts/api.yml | 58 +++++++++++++++++++++++++++ examples/.preflight/triage.yml | 45 +++++++++++++++++++++ examples/README.md | 35 ++++++++++++++++ 5 files changed, 175 insertions(+) create mode 100644 examples/.preflight/config.yml create mode 100644 examples/.preflight/contracts/api.yml create mode 100644 examples/.preflight/triage.yml create mode 100644 examples/README.md diff --git a/README.md b/README.md index f60fefa..15b50f7 100644 --- a/README.md +++ b/README.md @@ -500,6 +500,8 @@ Manual contract definitions that supplement auto-extraction: Environment variables are **fallbacks** — `.preflight/` config takes precedence when present. +> 💡 **Ready-to-use examples:** Copy [`examples/.preflight/`](examples/.preflight/) into your project root for a working starter config with detailed comments. + --- ## Embedding Providers diff --git a/examples/.preflight/config.yml b/examples/.preflight/config.yml new file mode 100644 index 0000000..f59170f --- /dev/null +++ b/examples/.preflight/config.yml @@ -0,0 +1,35 @@ +# .preflight/config.yml — Drop this in your project root +# +# This is an example config for a typical Next.js + microservices setup. +# Every field is optional — preflight works with sensible defaults out of the box. +# Commit this to your repo so the whole team gets the same preflight behavior. + +# Profile controls how much detail preflight returns. +# "minimal" — only flags ambiguous+ prompts, skips clarification detail +# "standard" — balanced (default) +# "full" — maximum detail on every non-trivial prompt +profile: standard + +# Related projects for cross-service awareness. +# Preflight will search these for shared types, routes, and contracts +# so it can warn you when a change might break a consumer. +related_projects: + - path: /Users/you/code/auth-service + alias: auth + - path: /Users/you/code/billing-api + alias: billing + - path: /Users/you/code/shared-types + alias: types + +# Behavioral thresholds — tune these to your workflow +thresholds: + session_stale_minutes: 30 # Warn if no activity for this long + max_tool_calls_before_checkpoint: 100 # Suggest a checkpoint after N tool calls + correction_pattern_threshold: 3 # Min corrections before flagging a pattern + +# Embedding provider for semantic search over session history. +# "local" uses Xenova transformers (no API key needed, runs on CPU). +# "openai" uses text-embedding-3-small (faster, needs OPENAI_API_KEY). +embeddings: + provider: local + # openai_api_key: sk-... # Uncomment if using openai provider diff --git a/examples/.preflight/contracts/api.yml b/examples/.preflight/contracts/api.yml new file mode 100644 index 0000000..512543f --- /dev/null +++ b/examples/.preflight/contracts/api.yml @@ -0,0 +1,58 @@ +# .preflight/contracts/api.yml — Manual contract definitions +# +# Define shared types and interfaces that preflight should know about. +# These supplement auto-extracted contracts from your codebase. +# Manual definitions win on name conflicts with auto-extracted ones. +# +# Why manual contracts? +# - Document cross-service interfaces that live in docs, not code +# - Define contracts for external APIs your services consume +# - Pin down types that are implicit (e.g., event payloads) + +- name: User + kind: interface + description: Core user model shared across all services + fields: + - name: id + type: string + required: true + - name: email + type: string + required: true + - name: tier + type: "'free' | 'pro' | 'enterprise'" + required: true + - name: createdAt + type: Date + required: true + +- name: AuthToken + kind: interface + description: JWT payload structure from auth-service + fields: + - name: userId + type: string + required: true + - name: permissions + type: string[] + required: true + - name: expiresAt + type: number + required: true + +- name: WebhookPayload + kind: interface + description: Standard webhook envelope for inter-service events + fields: + - name: event + type: string + required: true + - name: timestamp + type: string + required: true + - name: data + type: Record + required: true + - name: source + type: string + required: true diff --git a/examples/.preflight/triage.yml b/examples/.preflight/triage.yml new file mode 100644 index 0000000..b3d394e --- /dev/null +++ b/examples/.preflight/triage.yml @@ -0,0 +1,45 @@ +# .preflight/triage.yml — Controls how preflight classifies your prompts +# +# The triage engine routes prompts into categories: +# TRIVIAL → pass through (commit, format, lint) +# CLEAR → well-specified, no intervention needed +# AMBIGUOUS → needs clarification before proceeding +# MULTI-STEP → complex task, preflight suggests a plan +# CROSS-SERVICE → touches multiple projects, pulls in contracts +# +# Customize the keywords below to match your domain. + +rules: + # Prompts containing these words are always flagged as AMBIGUOUS. + # Add domain-specific terms that tend to produce vague prompts. + always_check: + - rewards + - permissions + - migration + - schema + - pricing # example: your billing domain + - onboarding # example: multi-step user flows + + # Prompts containing these words skip checks entirely (TRIVIAL). + # These are safe, mechanical tasks that don't need guardrails. + skip: + - commit + - format + - lint + - prettier + - "git push" + + # Prompts containing these words trigger CROSS-SERVICE classification. + # Preflight will search related_projects for relevant types and routes. + cross_service_keywords: + - auth + - notification + - event + - webhook + - billing # matches the related_project alias + +# How aggressively to classify prompts. +# "relaxed" — more prompts pass as clear (experienced users) +# "standard" — balanced (default) +# "strict" — more prompts flagged as ambiguous (new teams, complex codebases) +strictness: standard diff --git a/examples/README.md b/examples/README.md new file mode 100644 index 0000000..778f15d --- /dev/null +++ b/examples/README.md @@ -0,0 +1,35 @@ +# Examples + +## `.preflight/` Config Directory + +The `.preflight/` directory contains example configuration files you can copy into your project root: + +``` +.preflight/ +├── config.yml # Main config — profile, related projects, thresholds +├── triage.yml # Triage rules — keywords, strictness +└── contracts/ + └── api.yml # Manual contract definitions for cross-service types +``` + +### Quick setup + +```bash +# From your project root: +cp -r /path/to/preflight/examples/.preflight .preflight + +# Edit paths in config.yml to match your setup: +$EDITOR .preflight/config.yml +``` + +Then commit `.preflight/` to your repo — your whole team gets the same preflight behavior. + +### What each file does + +| File | Purpose | Required? | +|------|---------|-----------| +| `config.yml` | Profile, related projects, thresholds, embedding config | No — sensible defaults | +| `triage.yml` | Keyword rules for prompt classification | No — sensible defaults | +| `contracts/*.yml` | Manual type/interface definitions for cross-service awareness | No — auto-extraction works without it | + +All files are optional. Preflight works out of the box with zero config — these files let you tune it to your codebase. From 33a3f0466e5ad983532be2aab88101a67e00d6bc Mon Sep 17 00:00:00 2001 From: Jack Felke Date: Wed, 11 Mar 2026 08:40:15 -0700 Subject: [PATCH 2/2] docs: add troubleshooting section with common setup issues --- README.md | 89 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 89 insertions(+) diff --git a/README.md b/README.md index 15b50f7..531e769 100644 --- a/README.md +++ b/README.md @@ -564,6 +564,95 @@ flowchart TB --- +## Troubleshooting + +### "Cannot find module 'vectordb'" or LanceDB import errors + +LanceDB uses native binaries. If you see module resolution errors: + +```bash +# Clean install with native deps rebuilt +rm -rf node_modules package-lock.json +npm install + +# If still failing, check your Node version (20+ required) +node --version +``` + +On Apple Silicon Macs, make sure you're running a native arm64 Node — not Rosetta. Check with `node -e "console.log(process.arch)"` (should print `arm64`). + +### First run is slow (~90MB model download) + +The local embedding provider ([Xenova/all-MiniLM-L6-v2](https://huggingface.co/Xenova/all-MiniLM-L6-v2)) downloads a ~90MB model on first use. This is a one-time cost — subsequent runs use the cached model. If the download hangs behind a corporate proxy, switch to OpenAI embeddings: + +```bash +export OPENAI_API_KEY=sk-... +export EMBEDDING_PROVIDER=openai +``` + +### "OpenAI API key required for openai embedding provider" + +You set `EMBEDDING_PROVIDER=openai` (or `embeddings.provider: openai` in `.preflight/config.yml`) but didn't provide a key. Either: + +- Set `OPENAI_API_KEY` in your environment, or +- Switch back to local: `export EMBEDDING_PROVIDER=local` + +### Tools not showing up in Claude Code + +1. Make sure the MCP server is registered. Run `claude mcp list` — you should see `preflight`. +2. If missing, re-add it: + ```bash + claude mcp add preflight -- npx tsx /path/to/preflight/src/index.ts + ``` +3. Restart Claude Code after adding. + +### `CLAUDE_PROJECT_DIR` not set + +Some tools (onboarding, session search, contracts) need to know your project root. If they return empty results: + +```bash +claude mcp add preflight \ + -e CLAUDE_PROJECT_DIR=/path/to/your/project \ + -- npx tsx /path/to/preflight/src/index.ts +``` + +Or set it globally: `export CLAUDE_PROJECT_DIR=/path/to/your/project` + +### `.preflight/config.yml` parse errors + +If you see `warning - failed to parse .preflight/config.yml`, your YAML is malformed. Common issues: + +- Tabs instead of spaces (YAML requires spaces) +- Missing quotes around values with special characters +- Incorrect indentation under `related_projects` + +Validate with: `npx yaml-lint .preflight/config.yml` or paste into [yamllint.com](https://www.yamllint.com/). + +### No session data found during onboarding + +`onboard_project` looks for JSONL files in `~/.claude/projects//`. If nothing is found: + +- Make sure you've actually used Claude Code on the project (at least one session) +- Check that `CLAUDE_PROJECT_DIR` matches the exact path Claude Code was opened in +- The path encoding is URL-style — `/Users/jack/my-app` becomes `%2FUsers%2Fjack%2Fmy-app` + +### Ollama embeddings connection refused + +If using Ollama as your embedding provider and getting connection errors: + +```bash +# Make sure Ollama is running +ollama serve + +# Pull the embedding model +ollama pull all-minilm + +# Verify it works +curl http://localhost:11434/api/embed -d '{"model":"all-minilm","input":"test"}' +``` + +--- + ## Contributing This project is young and there's plenty to do. Check the [issues](https://github.com/TerminalGravity/preflight/issues) — several are tagged `good first issue`.