Emerge
Official@Harbour-Emerge
Emerge provides operational knowledge skills for the Emerge, Exam Studio, and CleverClass estate, covering repo conventions, deployment, and production host operations.
Agent Skills by Emerge
Showing 6 vetted skills indexed across 1 GitHub repositories.
emerge-context
Maps repositories, deployments, and stale documentation across the Emerge, Exam Studio, and CleverClass estate.
repo-audit
Audits repositories with parallel read-only agents and writes verified CLAUDE.md documentation files.
frontend
Guides client-side development across Next.js 16, React 19, Tailwind 4, CRA, and MUI codebases.
emerge-deploy
Guides building, migrating, rolling, smoke-testing, and rolling back Docker deployments across the Emerge estate.
backend
Guides server-side development across Go, Django, FastAPI, and Laravel codebases with estate-specific conventions.
box-ops
Governs safe SSH operations, container management, and port allocation across shared production hosts.
Frequently Asked Questions About Emerge
FAQPage SchemaWhat tasks can I accomplish using Emerge's skills?▼
You can orient yourself across the Emerge, Exam Studio, and CleverClass repos, audit unfamiliar codebases and refresh CLAUDE.md docs, apply verified frontend and backend conventions, deploy with build-migrate-smoke-test-rollback patterns, and safely operate shared production VMs.
Who are Emerge's skills designed for?▼
Engineers working on the Emerge estate: developers touching Next.js/React/Tailwind or CRA+MUI frontends, backend engineers in Go, Django/DRF, FastAPI, or Laravel services, and operators deploying to or administering the mentis-demo VM and other production hosts.
Which technology stacks do these skills cover?▼
Frontend: Next.js 16, React 19, Tailwind 4, CRA with MUI, and the Emerge-Design generator. Backend: a Go modular monolith (Survey-Forms), Django/DRF and FastAPI (Exam Studio), FastAPI with SQLite (CleverClass), and Laravel (phd-monitoring).
How do the deployment skills work in practice?▼
The emerge-deploy skill encodes the estate's real deploy patterns: SHA-tagged container images, on-box .env files, TLS-ALPN on a host where port 80 is occupied, and preflight checks for silent failures. Load it before writing Dockerfiles, compose files, or debugging failed deploys.
What should I check before running commands on production hosts?▼
Load the box-ops skill first. It documents SSH access, the four-tenant container map, port allocation, disk and resource facts, and explicit rules about what must never be touched on the shared mentis-demo VM and other production hosts.