remorses/spiceflow
skills/spiceflow/SKILL.md
Spiceflow is a super simple, fast, and type-safe API and React Server Components framework for TypeScript. Works on Node.js, Bun, and Cloudflare Workers. Use this skill whenever working with spiceflow to get the latest docs and API reference.
$ install --global
skillsauthnpx skillsauth add remorses/kimaki spiceflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 8:29 AM145.6s1 file scanned
SKILL.md
- name:
- spiceflow
- description:
- Spiceflow is a super simple, fast, and type-safe API and React Server Components framework for TypeScript. Works on Node.js, Bun, and Cloudflare Workers. Use this skill whenever working with spiceflow to get the latest docs and API reference.
Spiceflow
Every time you work with spiceflow, you MUST fetch the latest README from the main branch. If that README references relevant subdocuments, you MUST fetch those too:
curl -s https://raw.githubusercontent.com/remorses/spiceflow/main/README.md # NEVER pipe to head/tail, read the full output
# Always read the typed fetch client doc when using createSpiceflowFetch
curl -s https://raw.githubusercontent.com/remorses/spiceflow/main/docs/fetch-client.md
NEVER use head, tail, or any other command to truncate the output. Read the full README every time, then read any referenced subdocuments that are relevant to the task. They contain API details, examples, and framework conventions that are easy to miss if you only read the top-level README.
Typed fetch client rules
When using the typed fetch client (createSpiceflowFetch), follow these rules:
- Use
:parampaths with aparamsobject. Never interpolate IDs into the path string.`/users/${id}`is juststringand breaks all type inference. - All packages in a monorepo must use the exact same spiceflow version. Mismatched versions cause
Types have separate declarations of a private propertyerrors. Usepnpm update -r spiceflow(without--latest) to sync. - Route handlers must return plain objects for the response type to be inferred. Returning
res.json()orResponse.json()erases the type toany. - Never
return new Response(...). It erases the body type. Usereturn json(...)(preserves type and status) orthrowanything (throw new Response(...)is fine since throws don't affect return type). bodyis a plain object, notJSON.stringify(). The client serializes it automatically.- Response is
Error | Data. Check withinstanceof Error, then the happy path has the narrowed type.
Related Skills
remorses/npm-package
development
VerifiedTrustedCommunity
Opinionated TypeScript npm package template for ESM packages. Enforces src→dist builds with tsc, strict TypeScript defaults, explicit exports, and publish-safe package metadata. Use this when creating or updating any npm package in this repo.
1,138SKILL.mdUpdated Apr 25, 2026
remorses/new-skill
documentation
VerifiedTrustedCommunity
Best practices for creating a SKILL.md file. Covers file structure, frontmatter, writing style, and where to place skills in a repository. Use when the user wants to create a new skill, update an existing skill, write a SKILL.md, or asks how skills work.
1,130SKILL.mdUpdated Apr 25, 2026
remorses/new-skill
documentation
VerifiedTrustedCommunity
Best practices for creating a SKILL.md file. Covers file structure, frontmatter, writing style, and where to place skills in a repository. Use when the user wants to create a new skill, update an existing skill, write a SKILL.md, or asks how skills work.
1,087SKILL.mdUpdated Apr 19, 2026
remorses/zustand-centralized-state
tools
VerifiedTrustedCommunity
Centralized state management pattern using Zustand vanilla stores. One immutable state atom, functional transitions via setState(), and a single subscribe() for all reactive side effects. Based on Rich Hickey's "Simple Made Easy" principles: prefer values over mutable state, derive instead of cache, centralize transitions, and push side effects to the edges. Resource co-location in the same store is also valid when lifecycle management is safer that way. Also covers state encapsulation: keeping state local to its owner (closures, plugins, factory functions) so it doesn't leak across the app, reducing the blast radius of mutations. Also covers event sourcing: keeping a bounded event buffer and deriving state with pure functions instead of mutable flags, making event handlers easy to test and reason about. Use this skill when building any stateful TypeScript application (servers, extensions, CLIs, relays) to keep state simple, testable, and easy to reason about. ALWAYS read this skill when a project uses zustand/vanilla for state management outside of React.
1,052SKILL.mdUpdated Apr 25, 2026