All authors
Claude Skills by mertefesensoy
github.com/mertefesensoy8 skills0 installs15 views
- Build PackageExecute the next Ephesus work package from BUILD-PROMPT.md — resume from docs/PROGRESS.md, run the READ→PLAN→BUILD→TEST→PROVE→COMMIT→REPORT loop, and never proceed on red checks. Use when asked to continue building Ephesus, implement a milestone/package, or "keep going".Votes: 0GitHub stars: 2
- Doc SyncDetect and fix drift between the Ephesus documentation suite and the code — module map vs src/, IPC contract vs handlers, schemas vs validators, invariants vs implementation. Use after landing a milestone, before releases, or when asked whether the docs still tell the truth.Votes: 0GitHub stars: 2
- Ephesus EngineerSenior software engineer operating protocol for the Ephesus project (a multi-agent harness desktop app — Electron + React + TypeScript + Pixi.js + xterm.js + node-pty, governed by a human Architect). Use this skill for ANY work in the Ephesus repository — implementing work packages from BUILD-PROMPT.md, closing findings, running milestone or exit reviews, editing the documentation suite, or when a /goal mentions Ephesus. It defines how to consult the Architect through AskUserQuestion before d...Votes: 0GitHub stars: 2
- GoalDrive the current milestone's goal run end-to-end — resolve the milestone from docs/PROGRESS.md (M3 as of this writing), enforce the Architect's sole git authorship and a properly named feature branch before any commit, then loop the /build-package cycle through the milestone's packages and close with /milestone-review. Use when asked to run the milestone, start "the M<x> run", or invoked as /goal.Votes: 0GitHub stars: 2
- ImproveFile a Gymnasium self-improvement proposal for Ephesus — scan the repo and its records for the highest-leverage improvement, write a structured proposal with measurable success criteria, and queue it for the Architect. Use when asked to find improvements, when a retro/review surfaces recurring friction, or on a scheduled improvement pass.Votes: 0GitHub stars: 2
- Milestone ReviewVerify an Ephesus milestone's exit criteria before declaring it done — run the named scenario suites, check every package's evidence, update PROGRESS.md, and produce an architect-facing review. Use when a milestone looks complete or the user asks "are we done with M<x>?".Votes: 0GitHub stars: 2
- ResearchRun one Stoa research cycle for Ephesus — study ONE Architect-registered repository from docs/stoa/WATCHLIST.md at a pinned commit, scoped by its tags, and file a provenance-cited research brief whose candidates feed /improve. Use when asked to research a watched source, study how another harness solves something, or on a scheduled research pass.Votes: 0GitHub stars: 2
- ImplementationsTwo changes filed together because the second exists to prevent the first: `docs/PROGRESS.md` gains the M8b and M8c milestones it never recorded, and `.claude/skills/ephesus-engineer/SKILL.md` makes the operating protocol — consultation, invariants, evidence tiers, honest reporting — an explicit, loadable standard rather than something each session rediscovers.Votes: 0GitHub stars: 2