db-design-interview
Skill3 starsChanged 8 months agoNo licenceView on GitHub
An interactive database design interviewer for relational databases (PostgreSQL, MySQL, SQL Server). Conducts a thorough, multi-phase interview to discover entities, user flows, access patterns, edge cases, and scale considerations — then produces ERD diagrams (Mermaid), access pattern analysis, and pros/cons of design tradeoffs. Use this skill whenever someone says "design a database", "help me think through a schema", "I need to model data for...", "database for a new feature", "walk me through database design", "interview me on my schema", or any variation where they want a guided, conversational approach to relational database design rather than just a schema dump. Also trigger when someone mentions "new database", "data model", "schema design", "ERD", "entity relationship", or "access patterns" in the context of building something new.
In this repository54 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-skillSkill
- agent-flowSkill
- brainstormSkill
- calendar-syncSkill
- capacitySkill
- claude-apiSkill
- confluence-reviewSkill
- cut-releaseSkill
- daily-checkinSkill
- delegate-or-ownSkill
- doctorSkill
- draft-replySkill
- end-of-daySkill
- estimateSkill
- forgeSkill
- hotfixSkill
- implementSkill
- interruptSkill
- jira-reviewSkill
- log-interruptSkill
- mcp-builderSkill
- meeting-prepSkill
- morning-triageSkill
- plan-createSkill
- pr-contextSkill
- prd-createSkill
- qa-checkSkill
- quarterly-goalsSkill
- researchSkill
- review-codeSkill
- security-scanSkill
- setupSkill
- shipSkill
- skill-creatorSkill
- slack-catch-upSkill
- sounding-boardSkill
- standupSkill
- status-reportSkill
- structural-reviewSkill
- sync-permissionsSkill
- template-syncSkill
- test-suggestSkill
- ticket-breakdownSkill
- weekly-planSkill
- weekly-retroSkill
- what-nextSkill
- worktree-feature-createSkill
- worktree-migrateSkill
- worktree-removeSkill
- worktree-review-createSkill
- worktreesSkill
- worktree-syncSkill
- wrap-upSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 19 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.