원클릭으로
convex-synapse
convex-synapse에는 Iann29에서 수집한 skills 7개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.
이 저장소의 skills
Build and maintain the Synapse auto-installer (v0.6) — pure-bash setup.sh + supporting helpers + bats tests. Use when the user asks to "work on the installer", "improve setup.sh", "add a pre-flight check", "make installation easier", or anything under installer/ / setup.sh in the repo.
Background on Synapse — the self-hosted Convex control plane this project uses instead of (or alongside) Convex Cloud. Loads when the agent needs context on what Synapse is, how it differs from Convex Cloud, or what the project's runtime architecture looks like.
Run Aster's end-to-end docker smoke tests, including the v0.6 module-query smoke that proves a real `npx convex deploy` bundle executes inside a v8cell against real Postgres. Use when the user asks to "smoke aster", "test aster end-to-end", "prove aster works", "run aster docker smoke", or wants to verify the Aster integration after pulling new aster-runner changes.
Add a new feature end-to-end across Synapse — backend handler + integration test + dashboard UI + Playwright spec + API docs + commit. Use when the user asks to "add a new endpoint", "build a new feature", "expose X via the API", or any task that crosses backend + frontend boundaries.
Diagnose common Synapse failures — CORS errors in the browser, deployments stuck "provisioning", containers that can't reach each other inside the synapse-network, postgres connection refused, dashboard 401 loops, Playwright timing issues. Use when the user reports something in Synapse "isn't working", "is broken", "won't start", or shows error symptoms.
Spin up the Synapse local dev stack (postgres + Go backend), reset the database, run smoke tests against the API. Use when the user asks to "run synapse", "start the backend", "reset the db", "rebuild and run", or wants to manually exercise endpoints.
Exercise the Synapse API end-to-end with curl flows that cover the happy path plus the standard 401/403/404/409 negative cases. Use when the user asks to "test the API", "verify the backend", "run smoke tests", or after touching auth/teams/projects/deployments handlers.