Install the CLI, write a rule, publish it and see strspc reject an edit to it. Commands and output come from a real run.
For: Engineers new to strspc. Evidence: strspc release
Step-by-step guides for engineers, platform teams and compliance leads. New to strspc? Start with SteerSpec 101. The standards guide builds on it, and the drift guide builds on the CLAUDE.md sync guide.
strspc is open source under the Apache-2.0 licence. The 101 and standards guides show output from real runs of strspc. The sync and drift guides are written from the strspc-sync documentation and source, not from a live run, and each guide is pinned to the release linked on its card, so it can lag a newer one.
Install the CLI, write a rule, publish it and see strspc reject an edit to it. Commands and output come from a real run.
For: Engineers new to strspc. Evidence: strspc release
Declare the external standard your rules cite, map a rule to a clause, check the mapping and list it with strspc standards coverage. A mapping is a reference you declare, not an assurance.
For: Engineers and compliance leads who already have a realm. Evidence: strspc release
Write the shared part of CLAUDE.md once in a central repo and have it proposed to every repo as a pull request, with the strspc-sync GitHub Action.
For: Platform and engineering teams. Evidence: strspc-sync release
Find the repos whose copy of CLAUDE.md, agents, skills or settings no longer matches the central standard, on a schedule, with the strspc-sync monitor opening one GitHub issue for each repo and template pair that differs. Written from the strspc-sync documentation and source, not from a live monitor run; in the sources of the linked release, the rule and the quickstart workflow comment disagree on which repository receives the issues.
For: Platform and engineering teams that distribute AI config to many repos. Evidence: strspc-sync release