Can I vibecode Slab?

Build a deliberately narrow personal substitute for Slab, focusing on a premium, single-user knowledge base experience.
Use exactly this stack: Next.js 15 + TypeScript + Tailwind CSS + SQLite (via Prisma or Drizzle) + TipTap or Novel for rich text editing.

Primary job: Build a fast, beautifully designed local knowledge base for organizing technical and company documentation.

Core Features & Requirements:
1. Hierarchical Organization: Implement a flexible structure using "Topics" (folders) and "Posts" (documents). Topics can contain sub-topics and posts, creating a clear information architecture.
2. Distraction-Free Editor: Integrate a modern WYSIWYG editor that supports Markdown shortcuts, code blocks with syntax highlighting, bold/italic, lists, and blockquotes. The editor should feel seamless and auto-save changes.
3. Verification System: Add a "Verified" status to posts. Users can mark a document as "Up-to-date" with a timestamp, displaying a green badge to indicate trust in the content.
4. Unified Search: Implement a powerful, instant search feature that indexes post titles and contents. Add a Cmd+K / Ctrl+K keyboard shortcut to open a global search modal.
Build a comprehensive personal knowledge base and documentation substitute for Slab, using Next.js 15, TypeScript, Tailwind CSS, and SQLite for local storage.

The primary goal of this application is to serve as a robust, single-user internal wiki or knowledge repository where users can create, organize, and discover documentation effortlessly.

Core Features to Implement:
1. Distraction-Free Editor: Implement a rich-text WYSIWYG editor that supports markdown, code blocks (with syntax highlighting), headers, lists, and basic formatting. The editor should be clean, intuitive, and distraction-free.
2. Hierarchical Organization (Topics): Documents should not just exist in a flat list. Implement a "Topics" system where documents can be organized hierarchically. Users should be able to create nested folders/topics and move documents between them.
3. Powerful Unified Search: Build a fast, client-side search functionality that allows users to instantly search across all document titles and contents.
4. Document History & Versioning: Keep track of document changes. Whenever a document is saved, create a new version so users can view the history of a document and see what changed over time.
5. Interactive UI: The user interface should feel highly responsive, utilizing modern React patterns and Tailwind for a polished, accessible, and fast experience. Include hover states, keyboard navigation, and clear active states for the sidebar navigation.

Technical Requirements:
- Start from an empty directory and scaffold the entire project.
- Use SQLite to persist all data locally (Topics, Documents, Document Versions). Provide an initial schema and seed it with realistic, helpful sample documentation (e.g., "Engineering Onboarding", "Product Specs") to demonstrate the hierarchy.
- The app must be fully functional offline and run locally. No analytics, no telemetry, no required third-party accounts.
- Ensure all forms of input (document titles, rich text content) are validated and sanitized to prevent XSS.
- Implement clear empty states (e.g., when a topic has no documents), loading states, and toast notifications for success/failure actions (like saving a document).
- Add robust import and export capabilities (e.g., export all documents to Markdown files or a single JSON backup) so data isn't locked in.

What to Exclude:
- Do not implement real-time multiplayer editing (operational transformation / CRDTs). This is strictly a single-user system.
- Do not implement external tool integrations (like GitHub, Slack, or Google Drive search). Keep it focused on the internal knowledge base.

Deliverables:
- Complete Next.js source code.
- A `README.md` containing clear setup instructions, architecture overview, and how to run the app.
- Tests covering the core topic creation and document editing flows.
- Add scripts for install, development, test, build, and a production-style local run.
- Run the tests and build before finishing, then fix errors rather than merely describing them.