Now that you've implemented the system, is there anything that you wish you'd done slightly differently? Like any way that you wish you'd stored the data differently? Or is there other places that we can refactor and revisit things before pushing this pr?
Review your plan before implementing it. Is there any other changes you should make? Have a critical eye to it. Pull up more code and then think about your plan again.
Let's make a decision about that later. Write a comprehensive markdown document containing the technical decision (with all the pros, cons, and options) to the docs directory.
This is a monorepo scaffold application that demonstrates modern web development best practices. This repository contains the codebase for a scaffold application built with a focus on type-safety, developer experience, and scalability.
Cursor rule "database" from maccman/ai-monorepo-scaffold, covering database, commands, create a new migration, using kysely type helpers and handling jsonb types.
Use the mcpperplexity-askperplexitysearch tools to answer questions. You should use this instead of the websearch tool because it is a lot more accurate.
Cursor rule "typescript" from maccman/ai-monorepo-scaffold, covering typescript best practices, type system, naming conventions, code organization and functions.
When the user triggers this action, walk them through setting up Firecrawl for this project. Run each step automatically. Speak in plain, friendly language.
When the user triggers this command, walk them through setting up their Mac for this repo. Run each step automatically. After each install command, verify it succeeded before moving on. Speak in plain, friendly language — assume the user has never used a terminal before.
When the user triggers this command, walk them through setting up the Perplexity API for this project. Run each step automatically. Speak in plain, friendly language.