Summary
Each module section in `llms-full.txt` currently starts with a bare `## path/to/file.py` heading. Adding a structured metadata block would help LLMs index and retrieve module context more reliably.
Proposed format
```markdown
src/api/users.py
```yaml
language: python
exports: [list_users, create_user, UserService]
imports: [fastapi, sqlalchemy, .models]
routes: [GET /users, POST /users]
```
```
Design questions
- YAML vs TOML vs JSON vs HTML comment?
- Which fields are mandatory vs optional?
- Does this break existing llms.txt consumers?
- Should it be opt-in via config (`emit_frontmatter: true`)?
Summary
Each module section in `llms-full.txt` currently starts with a bare `## path/to/file.py` heading. Adding a structured metadata block would help LLMs index and retrieve module context more reliably.
Proposed format
```markdown
src/api/users.py
```yaml
language: python
exports: [list_users, create_user, UserService]
imports: [fastapi, sqlalchemy, .models]
routes: [GET /users, POST /users]
```
```
Design questions