en un clic
simulacrum
simulacrum contient 12 skills collectées depuis equaltoai, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Use when building or maintaining sim surfaces framework awkwardness — a FaceTheory SSR / routing / hydration pattern gap, a Svelte 5 rune limitation, an Apollo Client / graphql-ws edge case, a Playwright specifics gap. Produces a cleanly-shaped upstream signal rather than a local patch. sim's distinctive context — agent-first UX + strict CSP + vendored-Greater integration + async public routes + research-sandbox — makes its framework-consumption feedback high-signal.
Use after plan-roadmap is approved, if the roadmap warrants a tracked GitHub Project at the equaltoai org level. Translates a roadmap document into a Projects v2 kanban board with issues across affected repos. Follows equaltoai's established project pattern, often with upstream-coordination issues in sibling repos.
Use when a change touches CSP compliance (inline scripts / styles / event handlers / third-party origins / unsafe-eval) or GraphQL-first discipline (new REST paths, REST leaking into data operations). Walks the dual constraint strict CSP on built bundle + GraphQL-first with REST only for auth. Loosening either is refused without explicit governance authorization.
Use after scope-need and relevant specialist skills approve work. Takes the scoped-need document and produces a flat, ordered list of discrete changes required. Each change is scoped to be a single commit aligned with sim's milestone-driven rhythm.
Use to execute a single milestone (Mx.y) or GitHub Project phase — feature branch off main, commits per enumerated task, PR with CI gates + required review, merge to main. Runs one milestone at a time. Install to the two dev-stage instances is handled by install-sim-instance.
Use to walk a merged change through `pnpm build` → `lesser client install` against the two dev-stage target instances (`dev.simulacrum.greater.website`, `dev.theory.greater.website`), followed by Browser Live Smoke workflow validation. Respects the FaceTheory manifest (`facetheory.lesser.json`) + runbook discipline + never-timeout on CI.
Use when a user reports a bug, regression, or unexpected behavior — a public route rendering wrong, a workflow panel failing, a vendored Greater component misbehaving, a GraphQL query returning unexpected shape, a Playwright test flaking, a CSP violation, a deploy / install anomaly, or an LLM-bot-account / research-sandbox issue. Runs before any fix is proposed. The first structural question is always "is this upstream?"
Use after enumerate-changes. Takes a flat enumerated change list and sequences it with dependencies, risks, and an install-rollout plan across the two dev-stage target instances (simulacrum + theory). Produces a roadmap document, not code or project state.
Use when the user pastes or describes an inbound advisor-agent email dispatched to this steward. Advisor emails end with `@lessersoul.ai` and carry a provenance signature. This skill verifies the brief's origin, extracts the request cleanly, and surfaces it to the principal for explicit review before any action. Advisor-dispatched work never executes autonomously.
Use when a bug or gap surfaces in sim that traces to vendored Greater code, pinned Lesser contract, host registry API, body MCP shape, FaceTheory behavior, or upstream open-source framework. Walks "is this upstream?" reasoning, classifies the upstream home, and produces a clean upstream report (GitHub issue draft) rather than a sim-local patch. sim's distinctive discipline.
Use when a user brings a new capability, feature request, or enhancement need for sim in vague terms. Interviews conversationally and produces a scoped-need document. Applies Gate 1 (sim-mission alignment with upstream-first bias), Gate 2 (narrowest scope), Gate 3 (specialist routing). Most scopings that feel like "add a feature" resolve to either upstream routing or explicit milestone framing.
Use when a change touches public-route shape, readiness semantics, terminal states, or testid vocabulary. `docs/browser-validation-contract.md` is the frozen public-routes spec; changes conform to the contract or explicitly evolve it (with doc update). Silent drift is refused.