Universal, shareable AI-Context for any AI, human or team, regardless of size, location, languages, stack, setup or documentation.
.faf is now an officially recognized Internet standard format.
Official Media Type: application/vnd.faf+yaml
IANA Status: Registered alongside PDF, JSON, XML, and other Internet standards
Registration Date: October 31, 2025
- β IANA - Internet Assigned Numbers Authority (Official Internet Standard)
- β Anthropic - Official MCP Registry (PR #2759 merged)
- β Google - Chrome Web Store (Approved 2x: Sep 11 & Oct 29, 2025)
- β Community - 11,000+ downloads, production-tested
- Internet-Scale Legitimacy - Same recognition as
application/pdf,application/json,application/xml - HTTP Standard Headers -
Content-Type: application/vnd.faf+yamlofficially recognized - Universal Compatibility - Browsers, email clients, APIs handle
.faffiles properly - Future-Proof - Format backed by Internet standards body
New Standard: project.faf - visible, universal, like package.json
| File | Purpose | Who Reads It |
|---|---|---|
package.json |
Dependencies, scripts, metadata | npm, Node.js, developers |
project.faf |
Context, architecture, purpose | AI, Claude, Cursor, any AI tool |
README.md |
Human documentation | Developers, users |
The shift:
# Before (hidden like secrets)
ls -la
.env # Hidden (secrets - should be hidden) β
.faf # Hidden (AI context - should be visible!) β
# After (visible like package.json)
ls
package.json # Visible (dependencies) β
project.faf # Visible (AI context) β
README.md # Visible (documentation) β
.env # Still hidden (secrets stay secret) β
.env hides secrets. project.faf shares context.
Migration: Legacy .faf files still work. Use faf migrate to rename to project.faf.
.faf (Foundational AI-context Format) is an IANA-registered open format for AI context. Transform individual files or entire projects into structured data that AI instantly understands. Your tech stack, dependencies, architecture, and goals - all in one concise, shareable format.
Instead of explaining your project every time, AI reads your .faf once and knows exactly how to help.
11,000+ downloads across faf-cli and claude-faf-mcp combined.
AI tools need context. Files have context. But there's no standard way to measure or structure that context for optimal AI understanding.
# example.faf
version: 1.0
score: 85
type: package
confidence: 0.92
content:
name: "my-project"
dependencies: ["react", "typescript", "vite"]
scripts: ["dev", "build", "test"]
metadata:
source: "package.json"
processed: "2024-01-26T12:00:00Z"
engine: "faf-v1"
π©΅ faf-cliCommand-Line Tool - v3.0.1
npm install -g faf-cli |
π§‘ claude-faf-mcpClaude Desktop MCP - v2.5.5
npm install -g claude-faf-mcp |
Total: 11,000+ downloads combined π
- Universal - 153+ file types supported
- Scored - 0-100% context completeness score
- AI-Optimized - Structured for maximum AI comprehension
- Human-Readable - Simple, structured format
- Shareable - One file contains complete context
Input: package.json
{
"name": "my-app",
"version": "1.0.0",
"dependencies": {
"react": "^18.0.0"
}
}Output: package.faf (85% context score)
version: 1.0
score: 85
type: package
content:
name: "my-app"
version: "1.0.0"
dependencies: ["react@^18.0.0"]
metadata:
processed: "2024-01-26"- π― Measure - Know exactly how complete your AI context is
- π Optimize - See what's missing, improve your score
- π Standardize - One format for all file types
- π€ AI-Ready - Optimized for LLM consumption
| Score | Meaning | AI Readiness |
|---|---|---|
| 0-60% | Incomplete | Poor context |
| 61-80% | Basic | Acceptable |
| 81-90% | Good | Recommended |
| 91-99% | Excellent | Optimal |
| 100% | Perfect | Maximum context |
- File Conversion: Transform any file type into .faf format
- Project Context: Create a single .faf file for your entire project
- Build Integration: Companies can create custom implementations
- AI Optimization: Perfect context for any AI tool
# CLI Tool (recommended for getting started)
npm install -g faf-cli
cd your-project
faf init
# Or Claude Desktop Integration
npm install -g claude-faf-mcp
# Add to Claude Desktop configUniversal tools. Zero configuration. Production-ready.
β faf-cli on npm (4,600+ downloads) β claude-faf-mcp on npm (800+ weekly downloads)
- Specification - Complete format documentation
- Examples - Real-world .faf files (5 examples)
- example.faf - Basic example file
- WHERE-TO-FIND-FAF.md - Tools and resources
π IANA-Registered Internet Standard - Specification v1.1.0 (October 2025)
- β
IANA Registration -
application/vnd.faf+yaml(October 31, 2025) - β Anthropic Official - MCP Registry PR #2759 merged (October 17, 2025)
- β Google Chrome Verified - Web Store approved 2x (Sep 11 & Oct 29, 2025)
- β Format specification complete
- β Enhanced with project-level context and AI workflows
- β Production tools available (faf-cli, claude-faf-mcp)
- β 11,000+ combined downloads (4,600+ CLI, 800+/week MCP)
- β Battle-tested with 12,500+ test iterations (WJTTC GOLD Certified)
- β Open source (MIT License)
- Oct 31, 2025 - π IANA Registration (
application/vnd.faf+yaml) - Oct 29, 2025 - Google Chrome Web Store approval (2nd)
- Oct 17, 2025 - Official Anthropic MCP Registry merger (PR #2759)
- Oct 12, 2025 - Specification v1.1.0 published
- Sep 24, 2025 - CLI v2.1.0 published to npm
- Sep 16, 2025 - MCP Server v2.0.0 published to npm
- Sep 11, 2025 - Google Chrome Web Store approval (1st)
- Sep 1, 2025 - Developer platform launch (fafdev.tools)
- Aug 8, 2025 - Format created, first official .faf file generated
Quadruple Validation: IANA, Anthropic, Google (2x)
This is an open standard. Ideas, feedback, and contributions welcome.
This repository contains the format specification only. For working implementations:
- Use faf-cli for command-line tools
- Use claude-faf-mcp for Claude Desktop
The package.json in this repo provides spec metadata and versioning but contains no executable code.
MIT - Use freely, build anything.
Created by wolfejam.dev
**STOP .fafFing About! Let's RACE ποΈβ‘οΈπ

