メニュー
Inspect, edit, and switch fstack archetypes. Archetypes are behavior-derived (production, sprint, exploration, etc.) and reference repo/branch combinations via context_distribution.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | fstack-profile |
| version | 0.7.0 |
| description | Inspect, edit, and switch fstack archetypes. Archetypes are behavior-derived (production, sprint, exploration, etc.) and reference repo/branch combinations via context_distribution. |
| allowed-tools | ["Bash","Read","Edit","AskUserQuestion"] |
| triggers | ["show my profile","edit my profile","update my profile","which archetype am I in","profile gap","switch archetype","new manual subprofile","create profile","list profiles"] |
Writes target the active subprofile. To affect a different one, switch first.
Seven dimensions at developer.*. Both ends of each spectrum are legitimate working styles; pick where the user actually lives, not where you think is "best."
| Key | Low end | High end |
|---|---|---|
risk_tolerance | stability | speed |
bias_for_action | deliberate | action |
scope_appetite | focused | ambitious |
test_rigor | lean | rigorous |
architecture_care | pragmatic | principled |
detail_preference | detail-oriented | big-picture |
autonomy | seek-permission | ask-forgiveness |
Five preferences at preferences.*:
code_style (functional, oop, mixed)comment_level (none, minimal, verbose)abstraction (low, medium, high)error_handling (try-catch, result-types, propagate)type_safety (strict, balanced, loose)_FSTACK_BIN=""
_skill_md="$HOME/.claude/skills/fstack-profile/SKILL.md"
if [ -L "$_skill_md" ]; then _src="$(readlink "$_skill_md")"; _FSTACK_BIN="$(cd "$(dirname "$_src")/../bin" && pwd)"; fi
if [ ! -x "$_FSTACK_BIN/fstack-config" ]; then
for cand in "$HOME/Workspaces/fstack/bin" "$HOME/fstack/bin"; do [ -x "$cand/fstack-config" ] && _FSTACK_BIN="$cand" && break; done
fi
"$_FSTACK_BIN/fstack-config" exists || { echo "uninitialized. run /fstack"; exit 0; }
echo "ACTIVE: $("$_FSTACK_BIN/fstack-config" active)"
"$_FSTACK_BIN/fstack-profile" list
Ambiguous? Ask which.
"$_FSTACK_BIN/fstack-profile" show # active
"$_FSTACK_BIN/fstack-profile" show <key> # specific
If active has sample_count >= 5:
"$_FSTACK_BIN/fstack-observe" rollup >/dev/null
"$_FSTACK_BIN/fstack-observe" gap
Surface any |gap| ≥ 0.2.
"$_FSTACK_BIN/fstack-profile" list
Active marked with *.
"$_FSTACK_BIN/fstack-profile" use <key>
Confirm in one line: "active: ." Show the vibe afterward.
If the user said "switch to " but no subprofile by that name exists, offer to create.
Ask:
"$_FSTACK_BIN/fstack-profile" create <key> --label "<label>" --description "<desc>"
If "walk setup now": switch to the new key, then run /fstack's setup flow.
Use when the new profile is mostly the same as an existing one with tweaks.
"$_FSTACK_BIN/fstack-profile" create <new-key> --label "<label>" --clone-from <existing-key>
Clone copies developer + preferences + stack. Resets inferred + declared_at so the new profile records its own observations.
After clone, ask: "Tweak any dimensions now?" Branch into 8 if yes.
"$_FSTACK_BIN/fstack-profile" rename <old> <new>
Confirm via AskUserQuestion before mutating.
"$_FSTACK_BIN/fstack-profile" remove <key>
Cannot remove the last subprofile (binary enforces). Confirm via AskUserQuestion. If removed and was active, active falls back to the first remaining key.
Map phrasing. Both directions are normal working styles; don't assume one end is improvement.
risk_tolerance downrisk_tolerance upbias_for_action downbias_for_action upscope_appetite downscope_appetite uptest_rigor uptest_rigor downarchitecture_care uparchitecture_care downdetail_preference downdetail_preference upautonomy downautonomy upRead current. Compute new (delta ±0.2, clamp 0..1, or use explicit number).
Confirm via AskUserQuestion. Then:
"$_FSTACK_BIN/fstack-config" set-active developer.<dim> <new>
"$_FSTACK_BIN/fstack-config" set-active declared_at "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
If the user phrasing implies the change is mode-specific ("for prod I'm careful"), ask whether to apply to active or create a new subprofile.
"$_FSTACK_BIN/fstack-config" set-active preferences.<key> <value>
Reject values outside the enum.
"$_FSTACK_BIN/fstack-observe" rollup >/dev/null
"$_FSTACK_BIN/fstack-observe" gap
Translate per line:
0.3: "mismatch. Either declared is stale or behavior isn't what you'd say."
Ask: update declared to observed? keep declared? leave as-is? Apply only what the user agrees to:
"$_FSTACK_BIN/fstack-config" set-active developer.<dim> <observed>
"$_FSTACK_BIN/fstack-config" set-active declared_at "$(date -u +%Y-%m-%dT%H:%M:%SZ)"
Confirm. If yes:
"$_FSTACK_BIN/fstack-config" set-active-json developer '{"risk_tolerance":null,"bias_for_action":null,"scope_appetite":null,"test_rigor":null,"architecture_care":null,"detail_preference":null,"autonomy":null}'
"$_FSTACK_BIN/fstack-config" set-active declared_at null
Invoke /fstack to re-declare.
Confirm before mutating declared values. Writes default to active. The user has to switch first to edit a different subprofile.
Design and stub a new API endpoint. Detects style (REST, tRPC, GraphQL, Hono, FastAPI). Calibrates validation to the active subprofile.
Create, inspect, switch, and bootstrap product profiles. A product profile is the per-product binding (verify, delivery, gates, owner-gated, board, done, stack, knowledge) that lets the invariant way of working run on a specific product.
Scaffold a new feature, route, page, or component in line with stack and profile. Logs observations.
Design a data model and migration honoring chosen ORM and DB. Tunes normalization, indexes, constraints to the active subprofile.
Full-stack engineer's companion. Router and setup entrypoint. Detects which archetype you're working in (production, sprint, exploration, etc.) from observed behavior and suggests a switch when context changes.
Create, list, edit, and remove the user's own custom fstack skills. Codify personal patterns into slash commands.