@gonzih/skills-restaurant 1.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 gonzih
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,44 @@
+# skills-restaurant
+
+Claude Code skill suite for restaurant owners, managers, and chefs. Four skills, one install.
+
+## Install
+
+```bash
+npx @gonzih/skills-restaurant
+```
+
+Or install as a dev dependency and skills are copied automatically on `postinstall`:
+
+```bash
+npm install @gonzih/skills-restaurant
+```
+
+Restart Claude Code after installing.
+
+## Skills
+
+### `/menu-description-writer`
+Write enticing menu descriptions for any dish. Provide the dish name, key ingredients, prep method, and any notes — get back sensory-rich copy ready for your menu.
+
+### `/catering-proposal`
+Generate a full catering proposal: event overview, tiered menu packages, per-head pricing, staffing plan, event-day timeline, and terms. Ready to send to clients.
+
+### `/staff-schedule-email`
+Produce a weekly staff schedule email with shift assignments by day and role, coverage notes, key reminders, and swap instructions.
+
+### `/review-response`
+Respond professionally to online reviews (Google, Yelp, TripAdvisor). Works for both positive and negative reviews — thanks the guest, addresses specifics, and invites them back.
+
+## Usage examples
+
+```
+/menu-description-writer Pan-seared duck breast, cherry gastrique, roasted beets, microgreens
+/catering-proposal Corporate dinner, 80 guests, June 14, rooftop venue, $95/head budget
+/staff-schedule-email Week of June 9, [paste staff list and shifts]
+/review-response [paste review text]
+```
+
+## License
+
+MIT

package/install.js

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { copyFileSync, mkdirSync, existsSync } from 'fs';
+import { join } from 'path';
+import { homedir } from 'os';
+
+const skillsDir = join(homedir(), '.claude', 'skills');
+const skills = ['menu-description-writer', 'catering-proposal', 'staff-schedule-email', 'review-response'];
+
+for (const skill of skills) {
+  const dest = join(skillsDir, skill);
+  if (!existsSync(dest)) mkdirSync(dest, { recursive: true });
+  copyFileSync(new URL(`./skills/${skill}/SKILL.md`, import.meta.url).pathname, join(dest, 'SKILL.md'));
+  console.log(`✓ Installed /${skill}`);
+}
+console.log('\nSkills installed! Restart Claude Code to use them.');

package/package.json

@@ -0,0 +1,28 @@
+{
+  "name": "@gonzih/skills-restaurant",
+  "version": "1.0.0",
+  "type": "module",
+  "description": "Claude Code skill suite for restaurant owners, managers, and chefs",
+  "main": "install.js",
+  "bin": {
+    "skills-restaurant": "install.js"
+  },
+  "scripts": {
+    "postinstall": "node install.js"
+  },
+  "keywords": [
+    "claude",
+    "claude-code",
+    "skills",
+    "restaurant",
+    "menu",
+    "catering",
+    "hospitality"
+  ],
+  "author": "gonzih",
+  "license": "MIT",
+  "files": [
+    "install.js",
+    "skills/"
+  ]
+}

package/skills/catering-proposal/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: catering-proposal
+description: Writes a professional catering proposal including menus, pricing, staffing, and terms.
+triggers: ["catering proposal", "write a catering quote", "catering event proposal"]
+---
+
+# Catering Proposal
+
+## What this skill does
+Produces a polished, client-ready catering proposal covering event overview, curated menu options, per-head pricing, staffing plan, event timeline, and key terms and conditions. Output is ready to send or lightly customize before delivery.
+
+## How to invoke
+/catering-proposal [event type, guest count, date/time, venue, budget range, any dietary notes]
+
+## Workflow steps
+
+### Step 1 — Event overview
+Summarize the event: type (wedding, corporate, birthday, etc.), date, venue, estimated guest count, and any special requirements or theme.
+
+### Step 2 — Menu options
+Present two or three tiered menu packages (e.g., Standard, Premium, Deluxe) with appetizers, mains, sides, and desserts. Call out dietary accommodations (vegan, gluten-free, halal) for each tier.
+
+### Step 3 — Pricing and staffing
+Break down cost per head for each package, including service staff count and hours, rentals (linens, serveware), setup/breakdown, and gratuity policy.
+
+### Step 4 — Timeline and terms
+Outline the event-day timeline (arrival, service start, last call, teardown). Include deposit amount, payment schedule, cancellation policy, and final headcount deadline.
+
+## Example outputs
+A structured proposal document with labeled sections, a pricing table by package tier, and a signature block for client approval.

package/skills/menu-description-writer/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: menu-description-writer
+description: Writes enticing, sensory-rich menu descriptions for restaurant dishes.
+triggers: ["write menu description", "menu copy", "describe this dish"]
+---
+
+# Menu Description Writer
+
+## What this skill does
+Crafts compelling, sensory-rich menu descriptions that make dishes irresistible to guests. It highlights key ingredients, preparation methods, flavor profiles, and portion cues using evocative language that fits your restaurant's voice.
+
+## How to invoke
+/menu-description-writer [dish name, key ingredients, prep method, any notes]
+
+## Workflow steps
+
+### Step 1 — Gather dish details
+Collect the dish name, star ingredients, cooking technique (grilled, braised, house-made, etc.), flavor profile, and any origin story or seasonal angle worth mentioning.
+
+### Step 2 — Draft sensory language
+Write 2–4 sentences leading with the most evocative element (aroma, texture, origin). Use active verbs and concrete nouns. Avoid filler words like "delicious" or "amazing."
+
+### Step 3 — Add portion and pairing cues
+Close with a subtle portion signal ("serves two," "small plate") or pairing suggestion (wine, beer, side) to set guest expectations and upsell naturally.
+
+## Example outputs
+"Slow-braised short rib, fork-tender after eight hours in a red-wine jus, arrives atop truffle-whipped Yukon Golds with a tangle of crispy shallots. Rich, deeply savory, and satisfying — best shared, but rarely is."

package/skills/review-response/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: review-response
+description: Writes professional, on-brand responses to positive and negative online reviews.
+triggers: ["respond to review", "review response", "reply to customer review"]
+---
+
+# Review Response
+
+## What this skill does
+Crafts professional, empathetic responses to online reviews (Google, Yelp, TripAdvisor, etc.) for both positive and negative feedback. Responses thank the guest, acknowledge specific details they mentioned, address any concerns directly, and invite them back — protecting the restaurant's reputation while showing genuine care.
+
+## How to invoke
+/review-response [paste the review text, note sentiment: positive or negative, restaurant name optional]
+
+## Workflow steps
+
+### Step 1 — Identify tone and key points
+Determine whether the review is positive, mixed, or negative. Pull out the specific details the guest mentioned (dish names, staff, wait time, ambiance) to personalize the reply.
+
+### Step 2 — Open with a genuine thank-you
+Start by thanking the reviewer by name (if available) and acknowledging the specific experience they described. Avoid generic openers like "Thank you for your feedback."
+
+### Step 3 — Acknowledge and address
+For positive reviews: reinforce what made the experience great and name the team or dish if called out.
+For negative reviews: acknowledge the concern without being defensive, apologize sincerely for the shortfall, and briefly explain what is being done to prevent recurrence (without over-promising).
+
+### Step 4 — Invite back
+Close every response — positive or negative — with a warm, specific invitation to return. Offer a direct contact (manager's email or phone) for negative reviews so the conversation can move offline.
+
+## Example outputs
+A 3–5 sentence response that reads warm and professional, mirrors the guest's specific experience, and fits within the character limits of major review platforms.

package/skills/staff-schedule-email/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: staff-schedule-email
+description: Writes a clear weekly staff schedule email with shift assignments, reminders, and swap instructions.
+triggers: ["staff schedule email", "weekly schedule", "write schedule for staff"]
+---
+
+# Staff Schedule Email
+
+## What this skill does
+Generates a ready-to-send weekly staff schedule email that clearly lists shift assignments by day, highlights key operational reminders, flags coverage gaps or double-coverage, and tells staff exactly how to request shift swaps.
+
+## How to invoke
+/staff-schedule-email [week dates, staff names and roles, shift times, any reminders or special notes]
+
+## Workflow steps
+
+### Step 1 — Format the schedule grid
+Lay out the week (Monday–Sunday) with each day's shifts: staff name, role (server, host, line cook, etc.), start and end times, and station or section if relevant.
+
+### Step 2 — Add coverage and conflict notes
+Call out any days that are understaffed, any staff member working a double, and any confirmed time-off or call-outs already accounted for.
+
+### Step 3 — Include key reminders
+Add 2–4 brief operational reminders relevant to the week: upcoming reservations, menu changes, side-work assignments, uniform requirements, or mandatory pre-shift meeting times.
+
+### Step 4 — Swap and contact instructions
+Close with clear instructions for requesting shift swaps (deadline, who to contact, approval process) and the manager's name and preferred contact method.
+
+## Example outputs
+A plain-text email with a day-by-day schedule table, a bulleted reminders section, and a short swap-policy paragraph — ready to paste into any email client or messaging app.