AnswerDotAI / AnswerDotAI/llms-txt

Failed Validation

Open
#84 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
2.6k
Forks
163
Avg merge
1m
Merged PRs (30d)
1

Description

No matter what, my llms.txt file is triggering errors. Here is an example from my llms.txt file:

```
# Jono Young: Product, UX & Design Strategy Leader

> Jono Young is a product and UX design executive with 26+ years of experience helping startups, SaaS companies, and enterprise platforms grow through systems thinking, design leadership, and clarity of purpose. Available for full-time leadership roles or contract and fractional engagements via his consultancy, WePiphany.

## Who I Help
- Brands hiring a Director, VP, or Head of Product Design
- Founders seeking a fractional product and UX strategy partner
- Product teams ready to align vision, systems, and outcomes
- Recruiters vetting design leaders with startup and enterprise experience

## Skills & Specialties
- Product Design Leadership
- UX Strategy and Design Systems
- Product-Led Growth & Activation
- Growth & Retention Strategy
- Circle Community Builds (0 to 1)
- WordPress + Custom Platform Design
- Mixpanel, GA4, and Product Analytics
- Figma Libraries and DesignOps
- Team Mentorship and Career Development
- Accessibility, Responsive UI, and Web Standards
```

**I see these errors and warnings:**
Plain text content is not allowed directly within H2 sections. Only list items are permitted. (Line approx: 6)

H2 Section "Who I Help" has no list items. Consider adding items or removing the section if it's not purely a placeholder.

Everything looks correct. I am editing in VS Code, and directly in Siteground > FileManager > llms.txt and the errors keep appearing.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported validation messages against the example llms.txt content, especially the H2 sections and list-item rules. Trace the validator entry point used for llms.txt files; done means the sample receives a clear, consistent result that matches the documented format rules.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.