一键在 Manus 中运行任何 Skill

sql-lesson

星标0

分支0

更新时间2026年6月11日 16:20

Produce or continue a SQL bootcamp lesson for dinotable, or review Zoha's submitted SQL/ERD work. Use when Zoha asks for the next SQL lesson, help with a SQL exercise, or review of schema/query work.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

ahamedzoha

ahamedzoha/dinotable

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

dinotable SQL bootcamp

Curriculum: the 8-lesson outline in docs/design/system-design.md §16 (tables/constraints → joins → normalization → indexes/EXPLAIN → transactions → locking → window functions/CTEs → migrations discipline). Lessons live in docs/sql-bootcamp/lesson-N-<slug>.md.

Two modes

Lesson mode (default when asked for "the next lesson"):

Check docs/sql-bootcamp/ for existing lessons; continue the sequence.
Every exercise uses the dinotable domain — Users, Restaurants, Branches, Tables, ServicePeriods, Slots, Reservations. Never use generic employees/departments examples.
Lesson structure:
- Concept — the idea and the real problem it solves in this project
- Setup — exact commands; a throwaway dockerized Postgres 16 (docker run --rm -e POSTGRES_PASSWORD=dev -p 5432:5432 postgres:16 plus psql via docker exec) so lessons work before the repo has any code. No installs on the host.
- Guided exploration — queries to type and observe, with expected output
- Exercises — 3–6, escalating difficulty, each framed as a real dinotable need ("the host needs tonight's reservations ordered by slot…")
- Solutions — in a separate lesson-N-solutions.md, not inline. The lesson ends with: attempt everything before opening solutions.
Lessons 5 and 6 (transactions, locking) must include "break it on purpose": two concurrent psql sessions racing for the same slot, observing the anomaly, then fixing it.

Review mode (when Zoha shares SQL, a schema, or an ERD):

Review like a senior reviewing a promising junior: ask questions before giving answers ("what happens if two rows have the same phone?" rather than "add a unique constraint").
Point out what's right explicitly — calibration is part of teaching.
Escalate: question → hint → concrete fix. Full corrected SQL only after Zoha has had a real attempt.
Check the things juniors miss: constraint coverage, NULL semantics, index vs. query-shape mismatch, implicit assumptions about time zones.

Never write schema/migration files into the workspace (apps/, libs/) — all SQL lives in lesson docs until Zoha carries it into the project during a milestone.

同仓库更多 Skills

同仓库

milestone

ahamedzoha/dinotable

Produce the next guided milestone build doc for dinotable (six-part format - Concept, ADR, Guided build, Challenges, Verify, Stretch). Use when Zoha asks to start a phase, begin a milestone, or requests the next build doc.

2026-06-210

mode

ahamedzoha/dinotable

Switch how much application code the AI writes for dinotable — between guided (Zoha writes all code), collab (split), and autopilot (AI writes the frontend, Zoha drives the guided core). Use when Zoha says "set mode to X", "switch to autopilot", "let me write it myself", "just build the web app for me", or asks what the modes are.

2026-06-210

postman

ahamedzoha/dinotable

Generate, extend, or fix the local Postman collection + environment for hitting the dinotable API. Use when Zoha wants to import the API into Postman, add a request for an endpoint, regenerate the collection after routes change, or debug token/OTP/id-chaining in the saved requests. The collection is GENERATED — edit the SPEC in gen-postman.sh, never hand-edit the JSON.

2026-06-210

progress

ahamedzoha/dinotable

Compare the dinotable repo's actual state against the roadmap, log progress, and plan the next session. Use when Zoha asks where things stand, what to do next, starts a session after a break, or seems stuck or demotivated.

2026-06-180

adr-review

ahamedzoha/dinotable

Review an ADR that Zoha has written in docs/adr/. Use when Zoha says an ADR is ready for review, or asks for feedback on a decision record. Never use this to write or rewrite an ADR.

2026-06-110

name	sql-lesson
description	Produce or continue a SQL bootcamp lesson for dinotable, or review Zoha's submitted SQL/ERD work. Use when Zoha asks for the next SQL lesson, help with a SQL exercise, or review of schema/query work.

dinotable SQL bootcamp

Two modes

Lesson mode (default when asked for "the next lesson"):

Check docs/sql-bootcamp/ for existing lessons; continue the sequence.
Every exercise uses the dinotable domain — Users, Restaurants, Branches, Tables, ServicePeriods, Slots, Reservations. Never use generic employees/departments examples.
Lesson structure:
- Concept — the idea and the real problem it solves in this project
- Setup — exact commands; a throwaway dockerized Postgres 16 (docker run --rm -e POSTGRES_PASSWORD=dev -p 5432:5432 postgres:16 plus psql via docker exec) so lessons work before the repo has any code. No installs on the host.
- Guided exploration — queries to type and observe, with expected output
- Exercises — 3–6, escalating difficulty, each framed as a real dinotable need ("the host needs tonight's reservations ordered by slot…")
- Solutions — in a separate lesson-N-solutions.md, not inline. The lesson ends with: attempt everything before opening solutions.
Lessons 5 and 6 (transactions, locking) must include "break it on purpose": two concurrent psql sessions racing for the same slot, observing the anomaly, then fixing it.

Review mode (when Zoha shares SQL, a schema, or an ERD):

Review like a senior reviewing a promising junior: ask questions before giving answers ("what happens if two rows have the same phone?" rather than "add a unique constraint").
Point out what's right explicitly — calibration is part of teaching.
Escalate: question → hint → concrete fix. Full corrected SQL only after Zoha has had a real attempt.
Check the things juniors miss: constraint coverage, NULL semantics, index vs. query-shape mismatch, implicit assumptions about time zones.

Never write schema/migration files into the workspace (apps/, libs/) — all SQL lives in lesson docs until Zoha carries it into the project during a milestone.