Njukierick/Riddles-API-Documentation — reverse-engineered prompt

Reverse engineered prompt

Build me a clean documentation site for a Riddles API. I want it to feel like a simple polished docs website where someone can quickly understand what the API does, browse the endpoints, and try interactive docs. The API is for getting all riddles or one by id, filtering by category, getting a random riddle, and creating, updating, or deleting riddles. Make it clear that no authentication is needed.

Please include a main docs section written in readable markdown style with example requests and responses, and also add pages or links for Swagger UI and Stoplight versions of the same API docs. The site should explain the riddle object, show the available categories like easy, hard, kids, math, word, and funny, and make it easy to jump between sections.

Use the existing theme, images, and styling so it looks consistent and pleasant, and keep search and navigation working. If anything is unclear, look up the current docs online and wire everything up so the site is ready to run and deploy.

Want more depth? Deep Reverse