sza

Plugin sza from marketplace sza-unified-rules in SerZhyAle/sza-unified-rules. Commands read from the repo's manifest — today.

Skills (20)

• adopt-canon

  Adopt the SZA Unified Rules canon in this repository - write the .sza-canon.json stamp, point the repo's agent-rules file at the canon instead of restating it, reconcile every divergence found, and record the result in the repo's contrib file. Also the re-sync path when the canon has changed since a

• agent-cost

  Measure what an agent session actually costs in this repo and act on the result - mine the Claude Code transcripts for token spend, context growth, tool-failure rates and compaction points, then decide what to gate. Use when asked to measure or reduce agent cost, to find where the tokens go, why a s

• caveman

  Switch this session into terse caveman mode - findings and facts only, no filler, no cheerleading, no preamble - and keep it there until told to stop. Covers the two places brevity is asked for most: a commit message and a code review. Use on "/caveman", "caveman mode", "be brief", "caveman commit",

• contract-sync

  Align this repository with the shared contracts catalog at P:\Contracts - inventory what the repo holds, move the real contracts into the catalog under the function they belong to, replace every local copy with a pointer, fill the registry rows, audit the consumer code against the compatibility law,

• feature-to-site

  Propagate a finished feature to every user-facing surface - in-app strings, the ledger, README and its translations, the product site, support pages, listing sources, and the sza.od.ua hub - each locale in one edit, so nothing goes stale. This is the canon's ship-together surfaces manifest, the /doc

• portfolio-queue

  Work with the portfolio queue runner (pq) - the robots that take tickets from every registered project in the owner's order - see what they are doing, why one is idle, stop, pause or steer them, and read what they did. Use on "pq", "portfolio queue", "start the robots over all projects", "what are t

• promote

  Plan and run free promotion for an SZA product - write or correct its promotion ticket, the positioning worksheet, correct search-engine indexing (host-root robots.txt, sitemap, Search Console, Bing, IndexNow), repository metadata and social card, free package channels and directories, launch moment

• release

  Run a public RELEASE of an SZA product - the one-way, billable operation that stamps a version and publishes it to GitHub, winget, the Microsoft Store, Play, or a marketplace. Detects the repo's shape, channels and frozen anchors, writes "What's new" into every listing surface before tagging, then e

• sa

  Short form of /spec-all - take one named ticket (or an idea text) of any SZA project from its current status to the audit; the ticket can be named across projects as <key>:<id> (/sa fms-web:S0123), and a bare project key (/sa fms-web) takes that project's next eligible ticket. Use on /sa, "sa S0123"

• sd

  Short form of /spec-draft - capture a task or a problem as a Draft ticket in any SZA project, the owner's words kept verbatim. Use on /sd, "sd fix the crash on rotate", or on the Russian phrasings - "создай спеку", "закинь задачу в очередь", "добавь баг в pq", "зафиксируй проблему в проекте".

• site-audit

  Audit a published product site, or every site of the portfolio, the way a crawler without JavaScript and a first-time visitor meet it - read-only lenses for indexing (robots, sitemap, canonical, hreflang), the visitor's path on a laptop and a phone, release facts on the page, structured data and soc

• sn

  Short form of /spec-next - work the next ticket of the project's queue without naming it; takes no argument, or a registered project key (/sn fms-web) to work that project's next ticket from any folder. Use on /sn, "sn fms-web", or on the Russian phrasings - "возьми следующий тикет", "что дальше по

• spec-all

  Take one ticket of any SZA project from where it stands to its audit - claim the ticket's lease, check drift, then run the spec-to-audit lifecycle for it (spec, plan, implement, evidence, self-audit) and release the lease. A new idea text is captured as a Draft first. The ticket may be named across

• spec-draft

  Capture a task description or a problem as a Draft ticket in any SZA project - the owner's words kept verbatim in the spec, the row added to the project's own ticket queue (PLAN/RELEASE_QUEUE.md), and a plain report of whether the portfolio queue (pq) will pick it up and when. Use on /spec-draft, "d

• spec-next

  Work the next ticket of the project's queue without naming it - the harness picks the first eligible ticket in the queue order and claims its lease, then /spec-all takes it from there. Takes no argument, or a registered project key (/spec-next fms-web) to work that project's next ticket from any fol

• spec-quiz

  Clear the tickets that wait for the owner's answers (status BlockQuestions) in any SZA project - find them, research what the code and the records already settle, ask the owner only the real decisions as multiple choice, write the answers into each ticket, and restore each ticket one level so the qu

• spec-to-audit

  Run a task through the full SZA lifecycle - triage, spec, plan, implement, evidence, self-audit, documentation, commit - with a named gate at every boundary that refuses to advance when its preconditions are missing. Use when asked to implement a specification, "do this properly", "сделай по специфи

• sq

  Short form of /spec-quiz - clear the tickets that wait for the owner's answers (BlockQuestions) in any SZA project, as multiple-choice questions with the answers written into each ticket. Use on /sq, "sq S0021", "sq --all", or on the Russian phrasings - "разблокируй тикеты", "что ждёт моих ответов",

• store-publish

  Publish an SZA product to its distribution channels - GitHub Release, winget (microsoft/winget-pkgs), and the Microsoft Store via MSIX and Partner Center. Resolves the repo's manifest paths, reserved identity and frozen anchors at run time, then runs each channel as its own one-way operation with it

• task-flow-init

  Set up how a project works its tasks - the numbered ticket ledger, the queue and ready/done plan files, a ticket template, and an R0 runner that works the backlog one ticket per fresh agent process - from nothing, in one pass, and rehearse it before trusting it. Use when asked to start a new project

Hooks (5)

• SessionStart

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.ps1"

• UserPromptSubmit

  pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/on-user-prompt.ps1"

• PreToolUse

  input=$(cat); case "$input" in *find*|*.ps1*|*[a-z]-[A-Z]*|*'& {'*|*'&{'*|*python*|*node*|*'"/'*|*"'/"*) printf "%s" "$input" | pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/guard-bash.ps1" ;; es

• PreToolUse

  input=$(cat); case "$input" in *'"run_in_background":true'*|*'"run_in_background": true'*) printf "%s" "$input" | pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/guard-fire-and-forget.ps1" ;; esac

• PreToolUse

  input=$(cat); case "$input" in *'"limit"'*|*'"offset"'*) exit 0 ;; esac; printf "%s" "$input" | pwsh -NoProfile -File "${CLAUDE_PLUGIN_ROOT}/hooks/guard-uncapped-read.ps1"

Similar plugins