better-chatbot Conventions — project standards for the better-chatbot AI chat platform
Project-specific conventions for contributing to the better-chatbot open-source AI chat platform: API architecture, three-tier tool system (MCP, Workflow, Default), server action validators, database repository patterns, compound component design, DAG workflow builder internals, and Playwright E2E setup
- What
- Project-specific conventions for contributing to the better-chatbot open-source AI chat platform: API architecture, three-tier tool system (MCP, Workflow, Default), server action validators, database repository patterns, compound component design, DAG workflow builder internals, and Playwright E2E setup
- Cost
- Free
- Needs
- a local clone of the better-chatbot repository (github.com/cgoinglove/better-chatbot) or an intent to contribute to it — Node.js, PostgreSQL, and the stack's dependencies; familiarity with Next.js App Router and the Vercel AI SDK
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @jackspace's better-chatbot skill, listed here with credit to its creator (standards authored by Jeremy Dawes / Jezweb for the open-source better-chatbot platform at github.com/cgoinglove/better-chatbot): the project-specific conventions, architecture, and contribution guidelines for better-chatbot itself. It teaches the agent the codebase's directory structure (Next.js 15 App Router, AI SDK 5, Better Auth, Drizzle ORM, PostgreSQL), API architecture with RESTful route conventions, the three-tier tool system (MCP, Workflow, Default), server action validators with the safe() wrapper, database repository patterns, compound component design, DAG workflow builder internals, Playwright E2E test setup, and principles like progressive enhancement, defensive programming, and streaming-first — plus templates for adding tools, API routes, and repositories. Honest caveats: this skill is PROJECT-SPECIFIC — it is only useful inside the better-chatbot repository (for contributions and fixes); if you want portable chatbot patterns for your own projects, see the sibling better-chatbot-patterns listing; last verified 2025-11-04, so check current library versions before contributing. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a local clone of the better-chatbot repository (github.com/cgoinglove/better-chatbot) or an intent to contribute to it — Node.js, PostgreSQL, and the stack's dependencies; familiarity with Next.js App Router and the Vercel AI SDK Install "better-chatbot Conventions — project standards for the better-chatbot AI chat platform" for me. It gives my agent @jackspace's better-chatbot contribution skill (standards by Jeremy Dawes / Jezweb): the project's architecture and directory conventions, API route structure, the three-tier tool system (MCP, Workflow, Default), server action validators with the safe() wrapper, database repository patterns, compound component design, DAG workflow builder internals, and Playwright E2E setup — with templates for adding tools, API routes, and repositories. IMPORTANT: this skill is project-specific — it only applies inside the better-chatbot repository. MIT licensed. Repository: https://github.com/jackspace/claudeskillz/blob/main/skills/better-chatbot/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "better-chatbot". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. clone the better-chatbot repo and install its dependencies; confirm the current dependency versions match the skill's 2025-11-04 snapshot). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.