メニュー
Finite-state-machine storage abstraction (state plus JSON-marshalled state data) on top of yacache, keyed per-entity. Use for per-user/per-chat conversational or workflow state instead of hand-rolled state tracking.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | goyacodedevutils-yafsm |
| description | Finite-state-machine storage abstraction (state plus JSON-marshalled state data) on top of yacache, keyed per-entity. Use for per-user/per-chat conversational or workflow state instead of hand-rolled state tracking. |
Import path: github.com/YaCodeDev/GoYaCodeDevUtils/yafsm.
Finite-state-machine storage abstraction (state + JSON-marshalled state data) backed by yacache, keyed
per-entity (e.g. per user or chat).
State interface — StateName() string.BaseState[T State] struct — embed it to auto-derive StateName from the concrete type's name via reflection.EmptyState struct — default/no-op state.StateAndData struct — { State, StateData string }.FSM interface — SetState, GetState, GetStateData.DefaultFSMStorage[T yacache.Container] struct + NewDefaultFSMStorage[T](storage yacache.Cache[T], defaultState State) *DefaultFSMStorage[T].EntityFSMStorage struct (per-uid wrapper) + NewUserFSMStorage(storage FSM, uid string) *EntityFSMStorage.SetState marshals the whole state struct to JSON, wraps it as {state, stateData}, and stores it via Cache.Set with no TTL. GetState falls back to defaultState.StateName() (with a nil error) when the key isn't found.yafsm.BaseState[YourStateType] so StateName() reflects the concrete type.yacache + yaerrors; used by yatgbot for per-user conversation state and its StateIs filter.Index of every GoYaCodeDevUtils utility package (config, errors, logging, caching, rate limiting, backoff, hashing, gzip, RSA, feature flags, FSM, thread-safe collections, locales, Telegram bot stack) with a pointer to each package's own skill. Use before hand-rolling infrastructure code GoYaCodeDevUtils may already provide.
High-level Telegram bot framework on top of gotd/td - router/dispatcher with filters and middleware, FSM-aware routing, per-user localization, sequential-update scheduling, and a message-send queue. Use as the starting point for any Telegram bot.
Thin wrapper around gotd/td's telegram.Client adding background-connect-with-retry, bot-token authorization, updates.Manager wiring, and SOCKS5/MTProto proxy helpers. Use for direct low-level Telegram client control instead of raw gotd/td.
Redis-backed persistence for gotd/td's updates.Manager state (pts/qts/seq/date via RedisJSON) plus channel/user access-hash bookkeeping, and a GORM/AES-encrypted session-storage layer. Use for any yatgclient/yatgbot state or session persistence.
Generic pluggable key-value cache abstraction with interchangeable in-memory and Redis backends, hash-oriented API. Use for any caching/session-store need instead of hand-rolling a map or a bare redis.Client call.
Loads JSON locale files into a nested key-tree with lookup, {placeholder} formatting, JSON serving, language-tag normalization, and Go-struct codegen. Use for any i18n/localization instead of hand-rolled JSON locale loading.