remove-demo-code
Skill0 starsChanged 6 months agoMITView on GitHub
Use when starting a real project from this template. Removes the CRM demo (Contact/Task/Project) cleanly so the repo is a blank slate without breaking guardrails.
- Deletes or force-pushes
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-resourceSkill
- deploy-checklistSkill
- onboard-an-agentSkill
- self-correcting-loopSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
When you start a real project, strip the CRM demo (Contact, Task, Project) but keep all the guardrails, agent files, and skills.
- Very specific: line 64
All four must pass. If any fail, you missed an import — search for Contact, Task, Project.
- Very specific: line 68
If you used degit you don't need this.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Remove the demo code
When you start a real project, strip the CRM demo (Contact, Task, Project) but keep all the guardrails, agent files, and skills. Total time: ~5 minutes.
Steps
1. Reset the database
npm run db:resetWipes the dev DB. Confirm when prompted.
2. Replace the schema
Open prisma/schema.prisma and delete the three demo models (Contact, Task, Project, ProjectMember) and the two enums (TaskStatus, Priority). Keep the datasource and generator blocks. Add your own models.
npm run db:migrate3. Delete demo backend files
rm src/shared/schemas/{contact,task,project}.ts
rm src/server/routers/{contact,task,project}.ts
rm src/server/__tests__/contact.router.test.tsEdit src/shared/schemas/index.ts and src/server/routers/index.ts to remove the deleted exports.
4. Delete demo frontend files
rm src/client/components/{ContactForm,TaskForm,ProjectForm}.tsx
rm src/client/pages/{ContactsPage,TasksPage,ProjectsPage}.tsx
rm src/client/__tests__/ContactForm.test.tsxOpen src/client/App.tsx — remove the demo routes and nav buttons. Open src/client/pages/HomePage.tsx — replace with whatever your app needs (or keep the layout, swap the data).
5. Replace demo seed data
Edit prisma/seed.ts — delete the contacts/projects/tasks and add your own.
6. Update docs
README.md— replace the project description and screenshots with yours.AGENTS.md— update the "Adding a feature" section if your domain is different from CRUD-on-Postgres.package.json— changenameanddescription.
7. Verify
npm run typecheck && npm run lint && npm run test:run && npm run buildAll four must pass. If any fail, you missed an import — search for Contact, Task, Project.
8. Reset git history (optional)
If you used degit you don't need this. If you cloned, reset:
rm -rf .git
git init
git add .
git commit -m "feat: initial commit"Checklist
- Database reset
prisma/schema.prismareplaced- Demo shared schemas removed
- Demo tRPC routers removed +
appRouterupdated - Demo pages/components removed + routes/nav updated
- Seed file replaced
- README, AGENTS, package.json updated
typecheck,lint,test,buildall pass
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

