Skip to content

Huruikagi/pc-build-planner / .claude/skills/sb-configure

sb-configure

Verified

Configure or explicitly update SpecBind for a project and complete the resulting aftercare. Use for an explicit SpecBind binary or project-asset update request, initial post-install review, or later changes to Agents, role models, artifact language, project instructions, templates, shared Rules, operational adapters, Steering, or existing artifacts affected by configuration changes.

references/rules.md

View on GitHub
# Shared Rules

Use Rules for project-owned authoring or judgment policy shared across several
artifacts, Agents, phases, or reviews. Keep one-artifact creation, maintenance,
or consumption guidance in that template's scoped instructions instead.

## Inspect and edit

```sh
specbind rule list
specbind rule read <selector> --for maintain
specbind rule read <selector> --for consume
```

The accepted selector set is closed. Do not add meaning by dropping an unknown
file below `settings/rules/`. An absent ordinary preference Rule means no
project customization; product protocols and Skill obligations still apply.

`language-style` is the cross-artifact prose preference consumed by every
product Skill. Installation offers its Japanese default only when the
configured language is `ja`; absence in any language is valid. Keep exact
commands, paths, fields, states, diagnostics, structured output, and quoted
output outside this prose policy.

Rules may contain `maintain` and `consume` instructions, never `create`.
Preserve non-waivable CLI structure, lifecycle, protocol, and Skill contracts.

`design-template-selection` is different from optional preference Rules: it is
required routing input and must classify the complete current Design candidate
set exactly once. Coordinate its change with the template procedure.

## Aftercare and verification

Read both projections again. Explain which future authoring, validation, or
review workflows will consume the new policy. Offer review of affected existing
artifacts, but do not rewrite them merely because a Rule changed. Semantic
revision belongs to each artifact's owning workflow.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall