Make install + surface read the registry's derived profileMembership/ capabilityClusters so a capability's tier drives what installs + surfaces. resolveProfile (when given the registry) unions capability skills for the profiles its tier implies before the requires: closure; resolveSurface merges capabilityClusters into the cluster map. bin/install.js, /gsd:surface, and the capability-state resolver all thread the registry. Shipped as a proven no-op: the UI capability is reconciled to tier:full (its skills were full-only in the hand-authored profiles), so it contributes only to the full profile (already the '*' sentinel) and core/standard are unchanged. Equivalence tests prove resolveProfile/resolveSurface/listSurface/staging/ capability-state are identical with vs without the registry; the core-alias staging path is verified equivalent (empty manifest → raw PROFILES.core). Closes #949 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
5.4 KiB
name, description, argument-hint, allowed-tools, requires
| name | description | argument-hint | allowed-tools | requires | |||||
|---|---|---|---|---|---|---|---|---|---|
| gsd:surface | Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall | [list|status|profile <name>|disable <cluster>|enable <cluster>|reset] |
|
|
Sub-commands: list · status · profile · disable · enable · reset
Sub-command routing
Parse the first token of $ARGUMENTS:
| Token | Action |
|---|---|
list |
Show enabled + disabled clusters and skills |
status |
Alias for list plus token cost summary |
profile <name> |
Write baseProfile and re-stage |
profile <n1>,<n2> |
Composed profiles (comma-separated, no spaces) |
disable <cluster> |
Add cluster to disabledClusters, re-stage |
enable <cluster> |
Remove cluster from disabledClusters, re-stage |
reset |
Delete .gsd-surface.json, return to install-time profile |
| (none) | Treat as list |
list / status
Load the capability registry and call listSurface(runtimeConfigDir, manifest, CLUSTERS, registry) from
gsd-core/bin/lib/surface.cjs. The registry is loaded via:
const registry = require('gsd-core/bin/lib/capability-registry.cjs');
Display:
Enabled (N skills, ~T tokens):
core_loop: new-project discuss-phase plan-phase execute-phase help update
audit_review: …
…
Disabled:
utility: health stats settings …
Token cost: ~T (budget cap ~500 tokens for 200k context @ 1%)
For status also append:
Base profile: standard (from .gsd-surface.json)
Install profile: standard (from .gsd-profile)
profile <name>
- Read current surface:
readSurface(runtimeConfigDir)→ if null, seed fromreadActiveProfile(runtimeConfigDir). - Set
surfaceState.baseProfile = name. writeSurface(runtimeConfigDir, surfaceState).- Resolve and re-apply:
const registry = require('gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry); - Confirm: "Surface updated to profile
<name>. N skills enabled."
disable <cluster>
Valid cluster names: core_loop, audit_review, milestone, research_ideate,
workspace_state, docs, ui, ai_eval, ns_meta, utility.
- Validate cluster name against
Object.keys(CLUSTERS). - Read or initialize surface state.
- Add cluster to
surfaceState.disabledClusters(deduplicate). writeSurface→ resolve layout →applySurface:const registry = require('gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry);- Confirm: "Disabled cluster
<cluster>. N skills removed from surface."
enable <cluster>
- Read surface state; if null, nothing to enable — print "No surface delta active."
- Remove cluster from
surfaceState.disabledClusters. writeSurface→ resolve layout →applySurface:const registry = require('gsd-core/bin/lib/capability-registry.cjs'); const layout = resolveRuntimeArtifactLayout(runtime, runtimeConfigDir, scope); applySurface(runtimeConfigDir, layout, manifest, CLUSTERS, registry);- Confirm: "Enabled cluster
<cluster>. N skills added back to surface."
reset
- Check if
.gsd-surface.jsonexists. - Delete it.
- Re-apply using only
readActiveProfile(runtimeConfigDir)(install-time profile). - Confirm: "Surface reset to install-time profile
<name>."
runtimeConfigDir resolution
The runtimeConfigDir for applySurface is the base Claude config directory
(~/.claude), NOT the skills sub-directory (~/.claude/skills).
This matches installRuntimeArtifacts and uninstallRuntimeArtifacts, which also
receive ~/.claude as configDir. The skill dirs themselves live at
~/.claude/skills/gsd-*/ because the claude global layout has destSubpath = 'skills' — they are derived from configDir, not the root for it.
# Claude Code — global install
RUNTIME_CONFIG_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
SCOPE="global"
# Artifact destinations are derived from runtime layout
# via resolveRuntimeArtifactLayout(runtime, RUNTIME_CONFIG_DIR, SCOPE)
# then applySurface(RUNTIME_CONFIG_DIR, layout, manifest, CLUSTERS)
Surface state is stored at ${RUNTIME_CONFIG_DIR}/.gsd-surface.json
(i.e. ~/.claude/.gsd-surface.json).
All paths can be overridden by reading the CLAUDE_CONFIG_DIR env var if set.
Error handling
- Unknown cluster name → list valid cluster names, exit without writing.
- Unknown profile name → list known profiles (
core,standard,full), exit. - Missing
surface.cjs→ prompt: "Runnpm i -g gsd-coreto reinstall GSD."
<execution_context>
Surface state file: ~/.claude/.gsd-surface.json
Install profile marker: ~/.claude/.gsd-profile
Skill dirs: ~/.claude/skills/gsd-*/
Engine module: ~/.claude/gsd-core/bin/lib/surface.cjs
Cluster definitions: ~/.claude/gsd-core/bin/lib/clusters.cjs
</execution_context>