メニュー
How to use @t4h.framework/fs FileSystemClaim read/write and Binary. Use when handling filesystem claims or imports from @t4h.framework/fs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Documents @t4h.framework/amber (Amber client, Ticket operations, HTTP activities, Basic auth, runtime-claims peers). Use when implementing ticket or protocol flows—integration, creation, updates, transfers, tabulation, comments, locks—or when the user asks about ticket/protocol integration, creating tickets or protocols, or similar; also when they mention @t4h.framework/amber or Amber channel APIs.
Guides assembling T4H apps with Workflow definitions, default-export App wiring, and routing to the correct framework-* skill per @t4h.framework package. Use when scaffolding workflows, structuring main plus src/workflows, nesting startWorkflow, or choosing which package skill to read for HTTP, auth, ORM, Amber, cache, FS, SFTP, or SMTP.
How to use @t4h.framework/cache CacheClaim get/set, TTL, and Serializable values; pairing with @t4h.framework/http OAuth2. Use when implementing caches or imports from @t4h.framework/cache.
How to use @t4h.framework/core App, Workflow, Authorization, Env, Claim, History, Binary, Serializable, startWorkflow, StartWorkflowActivity, WorkflowClaim, and WorkflowRef. Use when building T4H apps, workflows, nested workflow starts, or importing from @t4h.framework/core.
How to use @t4h.framework/http HttpClient, http singleton, HttpRequestActivityInput, HttpAuth, OAuth2, HttpClientRequestClaim. Use when calling HTTP from workflows or extending OAuth2.
How to use @t4h.framework/jwks JWKSAuthorization, context fields, and the authorize module JWT vs raw signature paths. Use when configuring JWKS app authorization or imports from @t4h.framework/jwks.
| name | t4h-framework-fs |
| description | How to use @t4h.framework/fs FileSystemClaim read/write and Binary. Use when handling filesystem claims or imports from @t4h.framework/fs. |
>=22.@t4h.framework/core (workspace:^).import { FileSystemClaim } from '@t4h.framework/fs'
FileSystemClaim| Method | Parameters | Returns |
|---|---|---|
write | path, readable: Readable | Buffer | Binary (sync or async) |
read | path | Binary (sync or async) |
Binary is from @t4h.framework/core.
@t4h.framework/httpAbstractHttpRequestActivity uses http + fs claims: the response stream is written with fs.write to a generated path, then exposed as Body. Projects that use HttpRequestActivity need FileSystemClaim available alongside HttpClientRequestClaim.