create-yss-spec 2.1.8 → 2.1.10

package/template/.codex/skills/web-video-presentation/themes/warm-keynote/tokens.css

@@ -1,66 +0,0 @@
-/* ─────────────────────────────────────────────────────────────────────
- * Theme · warm-keynote
- *   Modern SaaS keynote with editorial warmth: warm cream canvas + sepia
- *   ink + teal accent + huge rounded glass slabs. Inter for everything,
- *   font-black for hero numbers (chunky modernist).
- *
- *   character knobs:
- *     • hero numbers   — chunky black sans (font-weight 900)
- *     • rule           — 1px solid neutral hairline + 4px accent rule
- *     • card           — large radius (24-32px), soft warm shadow
- *     • surface        — warm 40px paper grid
- *     • motion         — springy with slight overshoot
- * ───────────────────────────────────────────────────────────────────── */
-:root {
-  /* ─── palette ─── */
-  --shell:        #f5efe1;
-  --surface:      #fdfbf7;
-  --surface-2:    #ffffff;
-  --surface-3:    #f0e9d8;
-  --text:         #43302b;
-  --text-2:       #5b443d;
-  --text-mute:    #8a7969;
-  --text-faint:   #b8a994;
-  --rule:         #e6dcc4;
-  --accent:       #14b8a6;
-  --accent-soft:  rgba(20, 184, 166, 0.10);
-  --accent-glow:  rgba(20, 184, 166, 0.45);
-
-  /* ─── fonts ─── */
-  --font-display-cn: "Noto Sans SC", "Source Han Sans SC", -apple-system, sans-serif;
-  --font-display-en: "Inter", "SF Pro Display", -apple-system, sans-serif;
-  --font-body:       "Inter", "Noto Sans SC", -apple-system, sans-serif;
-  --font-mono:       "JetBrains Mono", "SF Mono", ui-monospace, monospace;
-  --font-features:   "cv11", "ss01", "tnum";
-
-  /* ─── motion: springy keynote ─── */
-  --dur-base:       500ms;
-  --dur-slow:       800ms;
-  --dur-cinematic:  1200ms;
-
-  /* ─── design identity: glass slabs ─── */
-  --r-card:        var(--r-xl);     /* 32px keynote slabs */
-  --r-stage:       0;
-  --rule-w:        1px;
-  --rule-style:    solid;
-  --hero-num-font:    var(--font-display-en);
-  --hero-num-style:   normal;
-  --hero-num-weight:  900;
-  --hero-num-track:   -0.04em;
-  --stage-pad-x:   100px;
-  --stage-pad-y:   80px;
-  --card-shadow:
-    0 1px 2px rgba(67, 48, 43, 0.04),
-    0 24px 60px rgba(67, 48, 43, 0.10);
-  --card-glass-bg:     rgba(255, 255, 255, 0.85);
-  --card-glass-border: rgba(255, 255, 255, 0.9);
-  --shadow-stage:
-    0 60px 160px rgba(67, 48, 43, 0.18),
-    0 0 0 1px rgba(0, 0, 0, 0.03);
-
-  /* ─── decoration: warm 40px grid ─── */
-  --surface-pattern:
-    linear-gradient(rgba(190, 175, 150, 0.18) 1px, transparent 1px),
-    linear-gradient(90deg, rgba(190, 175, 150, 0.18) 1px, transparent 1px);
-  --surface-pattern-size: 40px 40px;
-}

package/template/.codex/skills/wireframe-prototype/SKILL.md

@@ -1,56 +0,0 @@
----
-name: wireframe-prototype
-description: Use when low-fidelity product screens, user flows, whiteboards, Excalidraw, Figma, Penpot, tldraw, Axure, or prototype links are needed before detailed API or UI implementation work.
----
-
-# Wireframe Prototype
-
-## 兼容入口
-
-本 skill 仅服务旧名称或既有链接；新的低保真产出遵循 `yss-prototype-stage`，在 Codex 由 `product-design:index` 路由。它不批准产品设计门禁。
-
-Use this skill for low-fidelity product decisions. It favors fast, inspectable artifacts over polished visuals.
-
-## Choose The Medium
-
-| Situation | Recommended medium |
-|---|---|
-| Fast async discussion, page flow, rough layout | Excalidraw or Markdown wireframe |
-| Design-system or high-fidelity collaboration | Figma or Penpot |
-| Infinite-canvas workshop or AI-assisted whiteboard | tldraw |
-| Enterprise clickable prototype already standard in team | Axure or equivalent link |
-
-Do not make the tool the deliverable. The deliverable is the page/flow/state decision captured in `docs/.scratch/<feature>/design/`.
-
-## Minimum Artifact
-
-For each page or major interaction, capture:
-
-- Page name and entry route.
-- Key regions: search/filter, table/list, form, drawer/modal, validation panel, footer actions.
-- Primary action and next screen.
-- Empty, error, no-permission, readonly, conflict, and unsaved-change behavior.
-- Prototype link, exported image path, or Markdown wireframe.
-
-## Data Modeling Example
-
-Sketch:
-
-```text
-模型列表
-[筛选: 关键字][状态][负责人]              [新建模型]
---------------------------------------------------
-| 模型编码 | 模型名称 | 状态 | 最近发布 | 操作 |
-| CUSTOMER | 客户模型 | 草稿 | v3       | 编辑/校验/发布 |
---------------------------------------------------
-
-模型详情
-[基础信息] [字段] [版本历史]
-字段表格 + 字段编辑抽屉 + 校验结果侧栏 + 发布确认弹窗
-```
-
-Then link or paste this into `docs/.scratch/<feature>/design/<feature>-interaction-spec.md`.
-
-## Handoff
-
-After the wireframe is captured, return to `yss-prototype-stage` to fill the interaction spec, state matrix, API implications, and then run `prototype-review`.

package/template/.codex/skills/wireframe-prototype/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Wireframe Prototype"
-  short_description: "Low-fidelity wireframes and flow artifacts"
-  default_prompt: "Use $wireframe-prototype to choose and capture low-fidelity prototype artifacts."

package/template/.codex/skills/wizard/SKILL.md

@@ -1,44 +0,0 @@
----
-name: wizard
-description: Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
----
-
-# Wizard
-
-A **wizard** is a bash script that walks a human, step by step, through a manual procedure that's tedious to do by hand and tedious to re-explain to an AI every time. It opens each URL, says exactly what to click and copy, captures the values, writes them where they belong (`.env`, GitHub secrets), confirms at every stage, and shows how many stages are left. It might configure third-party services, run a one-off migration, or move the project from one state to another.
-
-The delightful UX is already solved by [template.sh](template.sh) — stage-by-stage progress, confirmation gates, cross-platform URL opening (including WSL), hidden secret entry, idempotent `.env` upserts, `gh secret`/`gh variable` writes, and a closing summary. **Your job is only to scope the procedure and author its stages.** The library above the `STAGES` marker is identical in every wizard; that consistency is the point — never hand-edit it.
-
-A wizard is ephemeral by default — built for one run, saved to a scratch or `scripts/` path, deleted when the job's done. Commit it only when the user wants a repeatable setup path that should live in the repo.
-
-## Process
-
-### 1. Scope the procedure
-
-Work out every manual step the human must take and every value that gets captured along the way. Read the repo first — don't ask cold:
-
-- For setup: `.env`, `.env.example`, `.env.*`, `README`, `docker-compose*`, framework config, and `.github/workflows/*` (every `secrets.*` / `vars.*` reference is a value the wizard must produce).
-- For a migration or transition: the current state, the target state, and the irreversible actions between them.
-
-Then show the user the ordered list of stages and the values each produces, and confirm — they may add, drop, or reorder.
-
-**Done when:** every stage is named in order, and for each captured value you know (a) where the human gets it, (b) where it's written (`.env`, a GitHub secret, both, or nowhere — some stages are pure actions), and (c) whether it's secret (hidden entry) or public.
-
-### 2. Map each stage's journey
-
-For each stage, write the precise path a human follows: which URL to open, what to do there, where a value is shown, which variable it fills — e.g. "Dashboard → Developers → API keys → Reveal test key → copy". Where you don't actually know the current UI or the exact command, say so and ask the user or check the docs — never invent steps that may not exist.
-
-**Done when:** every stage traces to concrete instructions a stranger could follow.
-
-### 3. Author the wizard
-
-Copy `template.sh` to the target path. Replace the example stage with one `stage` per step, in dependency order. Use the library helpers — `stage`, `say`/`step`, `open_url`, `ask`/`ask_secret`, `write_env`, `set_secret`/`set_var`, `pause`/`confirm` — and set `TOTAL_STAGES` to the number of stages you wrote.
-
-Hold the bar the template sets: open the URL before asking for its value, use `ask_secret` for anything secret, `write_env` every persisted value, `set_secret` only the values CI actually needs, and `confirm` before any irreversible action. Each `stage` clears the screen so only the current step is visible — keep a stage to one focused task so nothing the human needs scrolls away. Don't touch the library above the marker.
-
-### 4. Verify and hand off
-
-- `bash -n <script>`; run `shellcheck` if available.
-- `chmod +x <script>`.
-- Don't run it end-to-end yourself — it opens browsers and blocks on human input. Trace it statically instead: every value from step 1 is captured and lands where step 1 said, and every `set_secret` name exactly matches a `secrets.*` reference in CI.
-- Tell the user how to run it. If it's a repeatable setup path, commit it and link it from the README so the next person runs the script instead of asking an AI.

package/template/.codex/skills/wizard/agents/openai.yaml

@@ -1,3 +0,0 @@
-interface:
-  display_name: "Wizard"
-  short_description: "Generate an interactive setup wizard"

package/template/.codex/skills/wizard/template.sh

@@ -1,204 +0,0 @@
-#!/usr/bin/env bash
-#
-# A wizard — walks a human through a manual procedure step by step.
-# Generated by the /wizard skill.
-#
-# Everything above the "STAGES" marker is the wizard library: do not hand-edit
-# it. Author the per-step stages below the marker.
-
-set -euo pipefail
-
-# ──────────────────────────────────────────────────────────────────────────
-# Wizard library — delightful, consistent UX. Identical across every wizard.
-# ──────────────────────────────────────────────────────────────────────────
-
-if [[ -t 1 ]] && command -v tput >/dev/null 2>&1 && [[ "$(tput colors 2>/dev/null || echo 0)" -ge 8 ]]; then
-  BOLD=$(tput bold); DIM=$(tput dim); RESET=$(tput sgr0)
-  BLUE=$(tput setaf 4); GREEN=$(tput setaf 2); YELLOW=$(tput setaf 3); RED=$(tput setaf 1)
-else
-  BOLD=""; DIM=""; RESET=""; BLUE=""; GREEN=""; YELLOW=""; RED=""
-fi
-
-# Author sets this at the top of the stages section.
-TOTAL_STAGES=0
-
-_STAGE_INDEX=0
-ENV_FILE="${ENV_FILE:-.env}"
-WRITTEN_ENV=()    # KEYs written to ENV_FILE this run
-WRITTEN_SECRET=() # secret NAMEs set this run
-SKIPPED=()        # things we couldn't do (e.g. gh missing)
-
-# _clear — wipe the terminal so only the current step is on screen. No-op when
-# output isn't a terminal, so piped logs stay readable.
-_clear() {
-  [[ -t 1 ]] || return 0
-  if command -v tput >/dev/null 2>&1; then tput clear; else printf '\033[2J\033[3J\033[H'; fi
-}
-
-# banner "Title" — opening frame: what this wizard does.
-banner() {
-  _clear
-  printf '\n%s%s  %s%s\n' "$BOLD" "$BLUE" "$1" "$RESET"
-  printf '%s  %s stages%s\n\n' "$DIM" "$TOTAL_STAGES" "$RESET"
-  printf '%s  You drive the browser; this wizard tells you exactly what to do and\n' "$DIM"
-  printf '  captures the values you copy back. Stop any time with Ctrl-C and re-run\n'
-  printf '  later — it remembers values already saved.%s\n' "$RESET"
-  pause "Ready to start?"
-}
-
-# stage "Name" — clear the screen, then announce a stage and show progress.
-# Clearing keeps only the current step on screen.
-stage() {
-  _clear
-  _STAGE_INDEX=$((_STAGE_INDEX + 1))
-  printf '\n%s%s▸ Stage %s/%s · %s%s\n' \
-    "$BOLD" "$BLUE" "$_STAGE_INDEX" "$TOTAL_STAGES" "$1" "$RESET"
-}
-
-# say "..." — a plain instruction line.
-say()  { printf '  %s\n' "$1"; }
-# step "..." — a numbered-feeling action the human takes in the browser.
-step() { printf '  %s•%s %s\n' "$BLUE" "$RESET" "$1"; }
-note() { printf '  %s%s%s\n' "$DIM" "$1" "$RESET"; }
-warn() { printf '  %s⚠ %s%s\n' "$YELLOW" "$1" "$RESET"; }
-
-# open_url URL — open in the human's browser, cross-platform incl. WSL.
-open_url() {
-  local url="$1"
-  printf '  %s↗ opening%s %s\n' "$GREEN" "$RESET" "$url"
-  { if   command -v wslview     >/dev/null 2>&1; then wslview "$url"
-    elif command -v explorer.exe >/dev/null 2>&1; then explorer.exe "$url"
-    elif command -v xdg-open    >/dev/null 2>&1; then xdg-open "$url"
-    elif command -v open        >/dev/null 2>&1; then open "$url"
-    else warn "couldn't open a browser — visit it manually: $url"; fi
-  } >/dev/null 2>&1 || warn "couldn't open a browser — visit it manually: $url"
-}
-
-# pause "msg" — wait for the human to confirm they've done the manual part.
-pause() {
-  printf '  %s%s%s ' "$DIM" "${1:-Press Enter to continue}" "$RESET"
-  read -r _ || true
-}
-
-# confirm "question" — y/N gate; returns success on yes.
-confirm() {
-  local reply=""
-  printf '  %s? %s [y/N] ' "$YELLOW" "$1"
-  read -r reply || true
-  [[ "$reply" =~ ^[Yy] ]]
-}
-
-# _existing KEY — current value of KEY in ENV_FILE, if any.
-_existing() {
-  [[ -f "$ENV_FILE" ]] || return 1
-  local line; line=$(grep -E "^${1}=" "$ENV_FILE" | tail -n1) || return 1
-  printf '%s' "${line#*=}"
-}
-
-# ask KEY "Prompt" — read a value into $KEY. Offers the existing .env value as
-# a default on re-runs (Enter keeps it). Visible input (non-secret).
-ask() {
-  local key="$1" prompt="$2" current input
-  current=$(_existing "$key" || true)
-  if [[ -n "$current" ]]; then
-    printf '  %s%s%s %s[Enter keeps current]%s ' "$BOLD" "$prompt" "$RESET" "$DIM" "$RESET"
-  else
-    printf '  %s%s%s ' "$BOLD" "$prompt" "$RESET"
-  fi
-  read -r input || true
-  [[ -z "$input" && -n "$current" ]] && input="$current"
-  printf -v "$key" '%s' "$input"
-}
-
-# ask_secret KEY "Prompt" — like ask, but input is hidden.
-ask_secret() {
-  local key="$1" prompt="$2" current input
-  current=$(_existing "$key" || true)
-  if [[ -n "$current" ]]; then
-    printf '  %s%s%s %s[Enter keeps current]%s ' "$BOLD" "$prompt" "$RESET" "$DIM" "$RESET"
-  else
-    printf '  %s%s%s ' "$BOLD" "$prompt" "$RESET"
-  fi
-  read -rs input || true
-  printf '\n'
-  [[ -z "$input" && -n "$current" ]] && input="$current"
-  printf -v "$key" '%s' "$input"
-}
-
-# write_env KEY VALUE — upsert KEY=VALUE into ENV_FILE (creates it; replaces
-# any existing line). Idempotent.
-write_env() {
-  local key="$1" value="$2" tmp
-  touch "$ENV_FILE"
-  tmp=$(mktemp)
-  grep -vE "^${key}=" "$ENV_FILE" > "$tmp" || true
-  printf '%s=%s\n' "$key" "$value" >> "$tmp"
-  mv "$tmp" "$ENV_FILE"
-  WRITTEN_ENV+=("$key")
-  printf '  %s✓ wrote%s %s → %s\n' "$GREEN" "$RESET" "$key" "$ENV_FILE"
-}
-
-# set_secret NAME VALUE — set a GitHub Actions repo secret via gh. Falls back
-# to a warning (and records it) if gh is unavailable or unauthenticated.
-set_secret() {
-  local name="$1" value="$2"
-  if command -v gh >/dev/null 2>&1 && gh auth status >/dev/null 2>&1; then
-    if printf '%s' "$value" | gh secret set "$name" >/dev/null 2>&1; then
-      WRITTEN_SECRET+=("$name")
-      printf '  %s✓ set%s GitHub secret %s\n' "$GREEN" "$RESET" "$name"
-      return
-    fi
-  fi
-  SKIPPED+=("GitHub secret $name (set it manually: gh secret set $name)")
-  warn "skipped GitHub secret $name — gh not ready; set it later"
-}
-
-# set_var NAME VALUE — set a GitHub Actions repo variable (non-secret).
-set_var() {
-  local name="$1" value="$2"
-  if command -v gh >/dev/null 2>&1 && gh auth status >/dev/null 2>&1; then
-    if gh variable set "$name" --body "$value" >/dev/null 2>&1; then
-      printf '  %s✓ set%s GitHub variable %s\n' "$GREEN" "$RESET" "$name"
-      return
-    fi
-  fi
-  SKIPPED+=("GitHub variable $name")
-  warn "skipped GitHub variable $name — gh not ready; set it later"
-}
-
-# finish — clear, then a closing summary of everything configured.
-finish() {
-  _clear
-  printf '\n%s%s  ✓ Setup complete%s\n' "$BOLD" "$GREEN" "$RESET"
-  (( ${#WRITTEN_ENV[@]} ))    && note "wrote ${#WRITTEN_ENV[@]} value(s) to $ENV_FILE: ${WRITTEN_ENV[*]}"
-  (( ${#WRITTEN_SECRET[@]} )) && note "set ${#WRITTEN_SECRET[@]} GitHub secret(s): ${WRITTEN_SECRET[*]}"
-  if (( ${#SKIPPED[@]} )); then
-    printf '\n'; warn "still to do by hand:"
-    for s in "${SKIPPED[@]}"; do note "  - $s"; done
-  fi
-  printf '\n'
-}
-
-# ──────────────────────────────────────────────────────────────────────────
-# STAGES — author this section. One stage() per step the human takes.
-# Replace the example below. Set TOTAL_STAGES to match the stages you write.
-# ──────────────────────────────────────────────────────────────────────────
-
-TOTAL_STAGES=1
-
-banner "Stripe setup"
-
-# ── Example stage: replace with your real steps ───────────────────────────
-stage "Stripe — API keys"
-say "We'll grab your Stripe test keys and store them for local dev + CI."
-open_url "https://dashboard.stripe.com/test/apikeys"
-step "On the API keys page, copy the Publishable key (starts pk_test_)."
-ask STRIPE_PUBLISHABLE_KEY "Paste the publishable key:"
-step "Click 'Reveal test key' on the Secret key row, then copy it."
-ask_secret STRIPE_SECRET_KEY "Paste the secret key:"
-write_env STRIPE_PUBLISHABLE_KEY "$STRIPE_PUBLISHABLE_KEY"
-write_env STRIPE_SECRET_KEY "$STRIPE_SECRET_KEY"
-set_secret STRIPE_SECRET_KEY "$STRIPE_SECRET_KEY"   # CI needs this one
-# ──────────────────────────────────────────────────────────────────────────
-
-finish