Hey team,
Since Flight explicitly focuses on AI-powered developer experience (skeleton app with AI instruction files, dedicated AI docs page), I think it would make a lot of sense to officially register the Flight documentation on Context7 (https://context7.com).
Context7 feeds current, version-specific docs directly into AI coding assistants (Cursor, Claude Code, Windsurf) via MCP — so developers get accurate Flight API references instead of hallucinated or outdated suggestions.
What's involved:
- Claim the library at
https://context7.com/flightphp/core/admin
- Add a
context7.json file to the repo root
- Verify ownership
Takes about 5 minutes. Full guide: https://context7.com/docs/howto/claiming-libraries
You'd also get access to usage analytics, version management, and the ability to set custom rules for how AI assistants should use Flight.
Bonus idea: It would be awesome if this could also be done for the official plugins — active-record, runway, permissions, container, tracy-extensions, apm, async, etc. Since each plugin has its own repo and docs, they could each be registered individually on Context7. That way, developers using AI assistants would get accurate, current docs not just for Flight core but for the entire ecosystem.
Would love to see this happen!
Hey team,
Since Flight explicitly focuses on AI-powered developer experience (skeleton app with AI instruction files, dedicated AI docs page), I think it would make a lot of sense to officially register the Flight documentation on Context7 (https://context7.com).
Context7 feeds current, version-specific docs directly into AI coding assistants (Cursor, Claude Code, Windsurf) via MCP — so developers get accurate Flight API references instead of hallucinated or outdated suggestions.
What's involved:
https://context7.com/flightphp/core/admincontext7.jsonfile to the repo rootTakes about 5 minutes. Full guide: https://context7.com/docs/howto/claiming-libraries
You'd also get access to usage analytics, version management, and the ability to set custom rules for how AI assistants should use Flight.
Bonus idea: It would be awesome if this could also be done for the official plugins — active-record, runway, permissions, container, tracy-extensions, apm, async, etc. Since each plugin has its own repo and docs, they could each be registered individually on Context7. That way, developers using AI assistants would get accurate, current docs not just for Flight core but for the entire ecosystem.
Would love to see this happen!