silo-testing

Stars12

Forks1

UpdatedJuly 31, 2026 at 21:50

Use when writing or updating unit tests in the Silo repo. Covers the co-located Vitest setup, the pure-logic (no @testing-library/react) style and how to extract testable helpers, driving host state directly via the valtio store, and the contract-and-edges coverage expectations.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

silo-code

silo-code/silo

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	silo-testing
description	Use when writing or updating unit tests in the Silo repo. Covers the co-located Vitest setup, the pure-logic (no @testing-library/react) style and how to extract testable helpers, driving host state directly via the valtio store, and the contract-and-edges coverage expectations.

Testing in Silo

Every change that adds or changes behavior ships with unit tests in the same change. Tests are part of the work, not a follow-up. Don't mark a task done until pnpm test is green with coverage for what you added.

How testing works here:

Vitest, co-located. Put *.test.ts / *.test.tsx next to the source it covers; the package vitest.config.ts picks up src/**/*.{test,spec}.{ts,tsx}. Run everything with pnpm test, or one package with pnpm --filter <pkg> exec vitest run <path>.
Pure-logic style. The suite tests logic, not rendered React (@testing-library/react is intentionally not a dependency). When the logic you're adding lives inside a component, extract it into a pure, exported helper and test that — e.g. view-switcher-model.ts (switcher show/segmented/ dropdown rules), markdown-preview/menu.ts (context-menu enablement), and markdown-preview/match.ts (file matching) were factored out of their components precisely so the rules are unit-testable. Components stay thin glue.
Host state can be driven directly: set up store (the valtio proxy) and the relevant registries in beforeEach, exercise the service, assert on the store — see editor-service.test.ts and editor-registry.test.ts.
Cover the contract and the edges, not just the happy path: fallbacks, no-ops/guards, disabled states, and "hidden/absent" cases (the editor view-switching tests pin the priority tie-break, stale-viewType fallback, read-only Cut/Paste, and the single-view/diff/untitled hidden cases).

More from this repository

same repository

silo-docs-sync

silo-code/silo

Use when adding or changing any public @silo-code/sdk symbol — a new ctx method, exported type, or field — or when editing the project positioning / Context7 index. Covers the docs-in-sync workflow (TSDoc, @public/@internal + @category tags, barrel re-export, hand-authored ctx member page, pnpm docs:api, roadmap flip) and how apps/docs is indexed by Context7.

2026-07-3112

verifier-gui

silo-code/silo

Launch (or attach to) the Silo dev app and drive it for runtime verification through the dev automation RPC bridge — exec commands, eval DOM, capture screenshots, and create/activate/delete workspaces, terminals, editors. This is the repo's GUI evidence-capture handle for the `verify` skill. Use when verifying a change by running the real app and observing it. Always works inside a throwaway sandbox workspace, never the user's real workspaces.

2026-07-3012

docs-screenshot

silo-code/silo

Capture a 600×400 documentation screenshot from the running Silo app and composite it on the standard wallpaper. Use whenever adding or updating screenshots in apps/docs/public/img/guide/.

2026-06-2712

silo-extension-builder

silo-code/silo

Help the user design, write, compile, and install a Silo extension from a natural-language description. The extension follows the same format as any publishable Silo extension and can be shared via npm or a tarball URL when ready.

2026-06-1812

name	silo-testing
description	Use when writing or updating unit tests in the Silo repo. Covers the co-located Vitest setup, the pure-logic (no @testing-library/react) style and how to extract testable helpers, driving host state directly via the valtio store, and the contract-and-edges coverage expectations.

Testing in Silo

How testing works here:

Vitest, co-located. Put *.test.ts / *.test.tsx next to the source it covers; the package vitest.config.ts picks up src/**/*.{test,spec}.{ts,tsx}. Run everything with pnpm test, or one package with pnpm --filter <pkg> exec vitest run <path>.
Pure-logic style. The suite tests logic, not rendered React (@testing-library/react is intentionally not a dependency). When the logic you're adding lives inside a component, extract it into a pure, exported helper and test that — e.g. view-switcher-model.ts (switcher show/segmented/ dropdown rules), markdown-preview/menu.ts (context-menu enablement), and markdown-preview/match.ts (file matching) were factored out of their components precisely so the rules are unit-testable. Components stay thin glue.
Host state can be driven directly: set up store (the valtio proxy) and the relevant registries in beforeEach, exercise the service, assert on the store — see editor-service.test.ts and editor-registry.test.ts.
Cover the contract and the edges, not just the happy path: fallbacks, no-ops/guards, disabled states, and "hidden/absent" cases (the editor view-switching tests pin the priority tie-break, stale-viewType fallback, read-only Cut/Paste, and the single-view/diff/untitled hidden cases).