105 lines
2.7 KiB
Markdown
105 lines
2.7 KiB
Markdown
## Check Fact
|
|
|
|
Verifies if a statement is true by checking your project's code and documentation.
|
|
|
|
### Usage
|
|
|
|
```bash
|
|
# Basic usage
|
|
/check-fact "The Flutter app uses Riverpod"
|
|
|
|
# Check multiple facts at once
|
|
/check-fact "This project uses GraphQL and manages routing with auto_route"
|
|
|
|
# Check technical details
|
|
/check-fact "JWT is used for authentication, and Firebase Auth is not used"
|
|
```
|
|
|
|
### How It Works
|
|
|
|
1. **Where I Look (in order)**
|
|
- The actual code (most trustworthy)
|
|
- README.md and docs/ folder
|
|
- Config files (package.json, pubspec.yaml, etc.)
|
|
- Issues and PR discussions
|
|
|
|
2. **What You'll See**
|
|
- `✅ Correct` - Statement matches the code exactly
|
|
- `❌ Incorrect` - Statement is wrong
|
|
- `⚠️ Partially correct` - Some parts are right, some aren't
|
|
- `❓ Cannot determine` - Not enough info to check
|
|
|
|
3. **Proof I Provide**
|
|
- File name and line number
|
|
- Relevant code snippets
|
|
- Matching documentation
|
|
|
|
### Report Format
|
|
|
|
```text
|
|
## Fact Check Results
|
|
|
|
### What You Asked
|
|
"[Your statement]"
|
|
|
|
### Verdict
|
|
[✅/❌/⚠️/❓] [True/False/Partial/Unknown]
|
|
|
|
### Evidence
|
|
- **File**: `path/to/file.dart:123`
|
|
- **Code**: [The actual code]
|
|
- **Note**: [Why this proves it]
|
|
|
|
### Details
|
|
[If wrong, here's what's actually true]
|
|
[If partial, here's what's missing]
|
|
[If unknown, here's what I'd need to check]
|
|
```
|
|
|
|
### Basic Examples
|
|
|
|
```bash
|
|
# Check the tech stack
|
|
/check-fact "This app is built with Flutter + Riverpod + GraphQL"
|
|
|
|
# Check if a feature exists
|
|
/check-fact "Dark mode is implemented and can be switched from user settings"
|
|
|
|
# Check architecture choices
|
|
/check-fact "All state management is done with Riverpod, BLoC is not used"
|
|
|
|
# Check security setup
|
|
/check-fact "Authentication tokens are encrypted and stored in secure storage"
|
|
```
|
|
|
|
### Collaboration with Claude
|
|
|
|
```bash
|
|
# Check dependencies
|
|
ls -la && find . -name "pubspec.yaml" -exec cat {} \;
|
|
/check-fact "The main dependencies used in this project are..."
|
|
|
|
# Check how something is built
|
|
grep -r "authentication" . --include="*.dart"
|
|
/check-fact "Authentication is custom built, not using third-party auth"
|
|
|
|
# Check if docs match reality
|
|
cat README.md
|
|
/check-fact "Everything in the README is actually implemented"
|
|
```
|
|
|
|
### When to Use This
|
|
|
|
- Writing specs: Make sure your descriptions are accurate
|
|
- Taking over a project: Check if you understand it correctly
|
|
- Client updates: Verify what's actually built
|
|
- Blog posts: Fact-check your technical content
|
|
- Presentations: Confirm project details before presenting
|
|
|
|
### Important
|
|
|
|
- Code beats docs: If they disagree, the code is right
|
|
- Old docs happen: Implementation is what matters
|
|
- No guessing: If I can't verify it, I'll say so
|
|
- Security matters: Extra careful with security-related facts
|