菜单
Use this skill for EweserDB runtime orientation before running tests/services. It reduces guesswork for local/prod endpoints, worktree-specific ports, and repeated environment setup checks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill to run a focused browser feedback checkpoint for completed EweserDB UI work. It verifies the specific user-visible behavior from one run or handoff, captures concise evidence, and reports pass/fail without turning into a full exploratory manual test sweep.
Use this skill to implement a feature in the EweserDB monorepo from a plan file. Also use it when the user invokes $eweser-coder, asks Codex to code an approved EweserDB plan, continue a run from docs/ai/plans, fix a bug, or make repo changes while preserving quality gates. Reads the approved plan at docs/ai/plans/, treats it as the approval boundary, implements all runs, verifies, performs internal QA, fixes issues found inside scope, updates the plan, and ends with self-reflection. Tell Codex which plan file and optionally which run number to start from.
Use this skill to create a GitHub pull request for completed EweserDB work. Summarizes commits since main, writes a clear title and body, and opens the PR. Use after QA has passed.
Use this skill for standalone re-QA or audit of completed EweserDB work. Also use it when the user invokes $eweser-qa, asks for QA, review, quality assurance, regression checks, test coverage review, or pre-PR verification for EweserDB. Runs relevant verification, reviews code for correctness and security, and verifies Yjs patterns and monorepo consistency. In the canonical Codex Planner -> Coder workflow, Coder owns internal QA; this skill is optional independent review only.
Use this skill in the EweserDB repo when the user wants to stress-test a feature, plan, product decision, or naming choice against EweserDB domain language before implementation. It uses GLOSSARY-MAP.md, package GLOSSARY.md glossaries, INDEX.md navigation, AGENTS.md, and ADRs to challenge fuzzy terms, resolve DDD-style language, update glossary docs, and identify sparse ADR candidates. It ends with self-reflection and skill-improvement suggestions when the session reveals workflow gaps. Planner-style only: do not edit product code.
Use this skill to create a scoped implementation plan for a feature in the EweserDB monorepo. Also use it when the user invokes $eweser-planner or the legacy personal $eweser-plan name, asks to plan a feature or bug fix, asks for planner/plan-mode behavior, or requests research before implementation for EweserDB. Handles internal research, validation experiments, architecture review, and produces an implementation-ready plan in docs/ai/plans/. Use before starting substantial or ambiguous coding work. Planner stops for user approval and does not implement product code.
| name | eweser-runtime-orientation |
| description | Use this skill for EweserDB runtime orientation before running tests/services. It reduces guesswork for local/prod endpoints, worktree-specific ports, and repeated environment setup checks. |
Use this skill whenever you need to run code, start services, run tests, or inspect local/prod environment status for EweserDB.
Agents should avoid guessing environment state. This skill creates a deterministic, low-latency startup path: identify worktree and branch → read project guidance → load local runtime notes → probe listeners/services → run only the required command.
pwd
git rev-parse --show-toplevel
git branch --show-current
LOCAL_DEVELOPMENT.md and nearest INDEX.md files before running tests.sed -n '1,220p' LOCAL_DEVELOPMENT.md
# plus root package-level INDEX.md files where present
mkdir -p ~/.codex/local/eweser-db
if [ ! -f ~/.codex/local/eweser-db/runtime.md ]; then
cat > ~/.codex/local/eweser-db/runtime.md <<'EOF'
# EweserDB Runtime Notes
Machine: $(hostname)
Updated: $(date -Iseconds)
## Worktree Slots
## Service Endpoints
## Dev Notes
EOF
fi
~/.codex/skills/eweser-runtime-orientation/scripts/eweser-runtime-orientation.sh refresh
~/.codex/local/eweser-db/runtime.md is machine-specific and worktree-aware.
# EweserDB Runtime Notes
Machine: <hostname>
Updated: 2026-05-02T00:00:00Z
## Worktree Slots
- /home/jacob/eweser-db: main
- /home/jacob/eweser-db.worktrees/feature-x: pr-1234
## Service Endpoints
- Auth API: http://localhost:3001
- App UI: http://localhost:5174
- Sync: ws://localhost:38181
## Dev Notes
- docker compose: docker compose -f docker-compose.dev.yml up
- caddy: running
- last_cypress_target: auth-api@3001 + app@5174
If live discovery differs from notes, prefer live discovery and refresh notes.
This skill relies on:
~/.codex/skills/eweser-runtime-orientation/scripts/eweser-runtime-orientation.sh status — outputs worktree, branch, and
current listening ports for common Eweser services.~/.codex/skills/eweser-runtime-orientation/scripts/eweser-runtime-orientation.sh refresh — probes ports and writes the
latest observed endpoints into ~/.codex/local/eweser-db/runtime.md.refresh and continue with the refreshed values.