All authors
Claude Skills by silo-code
github.com/silo-code11 skills0 installs2 views
- Silo Docs SyncUse 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.Votes: 0GitHub stars: 60
- Silo Domain ModelingBuild and sharpen Silo's domain glossary (docs/domain-language.md) as you design — challenge fuzzy terminology, discuss edge-case scenarios, and record decisions the moment they crystallize. Use when pinning down vocabulary, evaluating a naming choice, or when a change touches docs/decisions/ (ADRs) or docs/proposals/ (RFCs).Votes: 0GitHub stars: 60
- Silo Release PublishPublish a drafted Silo app release on GitHub — verify the draft's assets, expand its notes to cover every unpublished version back to the last public one, flip it to public, and confirm the updater picks it up. Use when asked to publish/ship a release, "did we ever publish X", or when a release tweet or announcement needs to match what users can actually install.Votes: 0GitHub stars: 60
- GuideThe `silo-extension-builder` Claude Code skill turns a plain-English description into a working Silo extension — it scaffolds the project, writes the source, compiles it, and installs it into Silo in one session.Votes: 0GitHub stars: 60
- Silo Architecture ReviewReview code for architectural concerns only — boundary violations, wrong-layer logic, undocumented dependencies, and implicit decisions that should become an ADR or RFC. Works on a PR/branch/diff, or on standing code (a package, extension, or subsystem that already exists). Use when asked to "architecture review" something, to check whether code respects Silo's boundaries, before merging something cross-cutting, or when auditing an existing area for drift. Not a code-quality or style review.Votes: 0GitHub stars: 60
- Docs ScreenshotCapture 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/.Votes: 0GitHub stars: 58
- Silo TestingUse 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.Votes: 0GitHub stars: 58
- Verifier GuiLaunch (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.Votes: 0GitHub stars: 58
- Silo Extension BuilderHelp the user design, write, compile, and install a Silo extensionVotes: 0GitHub stars: 58
- Silo Architecture Review OrchestratorDrive an architecture review end to end across multiple fresh sessions — hold the state, hand the user each prompt to paste, verify what comes back, and re-plan when a fixer disagrees. Use when the user wants to run the full review-and-fix loop rather than a single review, says "orchestrate an architecture review", "walk me through the architecture review", or asks what step they're on. Never reviews or fixes anything itself.Votes: 0GitHub stars: 58
- GraftThis repo is indexed by graft/. For ANY task here, whetherVotes: 0GitHub stars: 58