This very app was built with CI Wiz + Cursor — what does that workflow actually look like?

This app is a direct demonstration of the CI Wiz + Cursor workflow, and the footer attribution is honest about how each tool contributed. **What CI Wiz did:** The database schema for this Q&A app (qa_questions, qa_answers, qa_categories, qa_comments, qa_votes) was designed first. CI Wiz was then used to generate the complete CI4 backend: entity classes, models with validation rules, CRUD controllers with Shield authentication wired in, DataTables list views, form views, route groups, the base layout templates, the sidebar, and the go_common_helper. The DOC.md context document was also produced at this stage. **What Cursor did:** The generated app has a functional but generic Bootstrap 5 admin UI. Cursor was given the DOC.md, told about the existing MVC structure and view template conventions, and asked to build a public-facing frontend using Tailwind CSS on top of the CI4 backend that CI Wiz had already produced. Cursor built the question listing page, question detail view, category navigation, voting UI, and the responsive layout — without touching the controller or model layer that CI Wiz generated. **Why this matters:** Neither tool alone would have been as fast or as clean. CI Wiz generating the frontend would have given you Bootstrap admin views, not a polished Tailwind Q&A interface. Cursor generating the backend from scratch would have taken significantly longer, cost more in API tokens, and produced inconsistent patterns across models and controllers. Together they cover complementary ground — CI Wiz for the schema-driven backend scaffold, AI for the custom frontend on top. The footnote in the footer is accurate attribution and, frankly, a proof of concept for how these tools can be combined.