adversarial-review
lsh1215/peak-booking-system
Adversarial critic workflow for the limited-stock booking system. Use when the user asks AI to attack a design or implementation for Redis outage, oversell, undersell, duplicate booking/payment, retry storm, fallback collapse, correctness gaps, or operational blind spots.
first-principles-design-review
lsh1215/peak-booking-system
Skeptical first-principles design review skill. Use when the user asks whether a design, architecture, product plan, API, data model, workflow, or system design truly satisfies the real requirements. Reviews from fundamentals: decompose claims into requirements, assumptions, constraints, evidence, invariants, trade-offs, failure modes, and simpler alternatives. Inspired by first-principles reasoning and Cartesian doubt, but does not impersonate any real person.
sysdesign-design
lsh1215/peak-booking-system
Design partner mode for system design practice. Activated when the user wants to design a new system (chat, notification, news feed, URL shortener, etc.). Sets up topic directory, uses the project mock-interview document, loads the matching problem from sysdesign-question-bank, marks the topic as active in .omx/state/, and conducts a back-and-forth Clarifying โ High Level โ Drill Down conversation, updating <topic>/System-Design-Document/mock-interview.md immediately as each decision lands. Uses Alex Xu Vol.1's canned numbers as the starting point (book-first), user adjusts. NOT an interview โ the user drives, this skill is a design collaborator with a calculator (back-of- envelope, latency estimation via auto-injected sysdesign-frameworks) and a reference book (sysdesign-question-bank).
sysdesign-sdd
lsh1215/peak-booking-system
Promote a filled mock-interview.md into a formal Software Design Document (sdd.md) following the IEEE 1016 / Atlassian / Google design-doc style. Activated when the user says they are ready to write the SDD. Reads the topic's mock-interview.md AND the topic's conversation log files (which capture the back-and-forth detail not preserved in the structured mock-interview), then asks the user the SDD-specific questions that mock-interview doesn't cover (Constraints, ADRs, Risk Register, Rollout, Testing strategy). Writes sdd.md incrementally as decisions land.