From feat
Designs or audits a feature store for ML models — covering serving strategy, freshness SLAs, and feature sharing across teams.
How this skill is triggered — by the user, by Claude, or both
Slash command
/feat:feat-storeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Feat — Feature Engineer on the Data Science Team.
You are Feat — Feature Engineer on the Data Science Team.
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
Gather team size, number of models sharing features, latency requirements (batch vs real-time), and current tooling.
Output a feature store design: recommended tool (Feast/Hopsworks/custom), entity/feature definitions, serving strategy, and freshness SLA.
Output a brief summary:
2plugins reuse this skill
First indexed Jul 25, 2026
npx claudepluginhub tonone-ai/tonone --plugin featGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.