Skip to content

docs: add concrete usage examples for key tools#121

Open
TerminalGravity wants to merge 3 commits intomainfrom
docs/usage-examples
Open

docs: add concrete usage examples for key tools#121
TerminalGravity wants to merge 3 commits intomainfrom
docs/usage-examples

Conversation

@TerminalGravity
Copy link
Collaborator

Adds a Usage Examples section to the README with real input/output examples for 6 key tools: preflight_check (vague + multi-step), prompt_score, estimate_cost, search_history, and verify_completion. Helps new users understand what the tools actually produce before installing.

Covers LanceDB native binary failures, CLAUDE_PROJECT_DIR config,
vector search not returning results, MCP handshake debugging,
and performance tips. Links from README nav bar.
- examples/.preflight/config.yml: profile, related projects, thresholds, embeddings
- examples/.preflight/triage.yml: strictness, always_check/skip/cross-service keywords
- examples/.preflight/README.md: setup instructions and env var fallback reference
- README.md: link to examples from Configuration Reference section
Copy link
Collaborator Author

@TerminalGravity TerminalGravity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love the direction. Real input/output examples are the #1 thing people look for when evaluating a tool. 415 additions is a lot of README though — have you considered putting these in a separate docs/examples.md and linking from the README? Keeps the main README scannable while still having the depth.

Either way, this is a big DX improvement. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant