swe-guidelines

Plugin swe-guidelines from marketplace swe-guidelines in baristaze/swe_guidelines. Commands read from the repo's manifest — 3 days ago.

Skills (40)

• audit-credential-lifetimes

  Audit how long each credential keeps working after it should stop: one row per credential kind (auth session, API key, operator token, sign-in, socket ticket, and any other the code has) and channel (HTTP request, realtime socket, bus control message, worker), with where it is checked, how often, wh

• audit-database-calls

  Audit how many database calls each endpoint and each worker flow makes, at its least and at its most: round trips, transactions, and roles, counted at the driver while the real API and worker run in one process over a database of their own. Names what grows a flow, every N+1, every read repeated wit

• audit-deploy-time

  Audit where a deploy's minutes go: the pipeline's jobs and steps from the Actions run, the Terraform apply's resources, the migration's one-off task, each service's rollout from its ECS events, its tasks, and their first log lines, and the settings that pace them (health-check grace, container healt

• audit-provider-calls

  Audit every call to an external provider (WorkOS, the AWS services, any HTTP to a third party), per flow: each route, inbound webhook, worker job, and boot. For each flow, the calls in order, whether they repeat or stand apart, whether they sit on the request path, how often the flow runs, whether t

• audit-query-indexes

  Audit whether the indexes fit the queries, and what breaks first under load: every statement the Postgres storage sends, mapped to the index that serves it and measured with EXPLAIN on a database of its own seeded at a stated scale, under the login and the tenant scope the application uses. Reports

• audit-retention

  Audit which stores grow without bound and what trims them: every table of every role, with what writes it, when a row is stale, the purge that deletes it, its retention, and whether that purge is batched and indexed; then the stores outside the database (log groups, buckets, queues, the cache). Meas

• docs-compact

  Compact the tree's documents to what holds at the head of the main branch: rewrite each ADR to its present decision with a status of one date, remove the ADRs that constrain nothing, cut the changelog to the latest release, clean the rows of specs/architecture.md, and rewrite the comments that tell

• ops-cloud-deployment-create

  Create one cloud environment of the system from nothing, in its own AWS account, as that account's administrator: the bootstrap root (state bucket, registry, OIDC trust, the deploy roles, the investigate role, the budget, the zones), the delegation of its public names at Cloudflare, the investigate

• ops-cloud-deployment-nuke

  Destroy one cloud environment of the system as its account's administrator: empty the buckets, destroy the environment root, remove what Terraform does not own (the secrets the application wrote, whose tenants' share follows the database's final snapshot, and the leftovers AWS made), and report what

• ops-infra-as-code

  Write or change the system's Terraform in the shape the guideline prescribes: one module graph shared by every environment, a variable for everything that differs, the autoscaling switch, the destroyable switch, the budget, the alarms, and the tags; then plan it under the read-only investigate profi

• ops-integration-silent

  Say why an integration went silent, in one environment, with a read-only credential: count what its inbound webhook route answered, read what the worker made of each delivery and the lines it logged, and read the webhooks queue and its dead letters, then report where the deliveries stop, why, and wh

• ops-investigate

  Investigate one environment of the system with a read-only credential: the alarms, the error rate, the latency, the outcomes, gauges, queues, and log lines each namespace's signals file names, the pool, the cost against the budget, and the system's size, then report what is wrong and what to do next

• ops-root-cause

  Find the root cause of one tenant's problem in one environment: read that tenant's rows through the operator plane's read routes with a read-only operator token, correlate them with the logs, the trace, and the error event by request id, at most five ids and one pass each, and report the cause and t

• ops-simulate-traffic

  Drive realistic traffic at one environment of the system through its edge with the system's own traffic generator, at one of four profiles (light, regular, heavy, stress) for a duration, and report the table: requests by route and status, p50, p95, p99, and the error ratio. Use to warm an environmen

• ops-watch

  Watch one environment of the system live from a sub-agent: a log tail, the alarms as they fire, and the error and latency signals, batched per interval and capped, with a read-only credential. Run it in a sub-agent the invoking session spawns, because it polls for the whole window, at most 30 batche

• stress-test-create-or-update

  Write or edit one stress test scenario of the system, ops/stress/<name>.yaml: the profile, the duration, the ramp, the soak, the target p95 and error ratio, and the routes it weights. States what a good stress test has and refuses to write one without a target. Writes a file and nothing else; a run

• stress-test-run

  Run one stress test scenario of the system against one environment with the system's own generator, read the signals back through their own APIs, and report pass or fail against a target stated before the run: the scenario's p95 and error ratio, or the one the run states instead. A real run is the s

• tickets-triage

  Triage the open tickets whose subject is this repository: for each, read it and check it against the code on main, the merged and open pull requests, and the history, then give it a verdict (done, moot, partly done, still relevant, in flight, out of scope, unsure) with the evidence. Writes a report;

• arch-benchmark-browser

  Run the benchmark prompt in the chatgpt.com, claude.ai, gemini.google.com, and grok.com products, signed in, and save each answer with its conversation URL as proof; in a checkout of this repository, also check the run in, redacted, with its row.

• arch-benchmark

  Run a benchmark scenario (a skill, a command, or a question) in a declared runtime and have frontier models score it against the rubric. Use to measure a change to a skill or the text.

• arch-deviate

  Record a deliberate deviation from the guideline as an ADR under docs/adr/: the rule quoted, the decision, the consequences. Use when a finding is accepted as intentional.

• arch-explain

  Explain how the guideline applies to a question, a file, or a change, citing the sections and lenses that govern it. Use when onboarding or before a cross-layer change.

• arch-new-aspect

  Incorporate a new aspect into the guideline and cascade it through the lenses, skills, docs, and README, naming the release level. Runs in a checkout of the guideline repository.

• arch-review-async

  Architecture review through the Async lenses: infra, queues, workers, leases, park vs fail. For a change in this area, or as one leg of arch-review-full.

• arch-review-context

  Architecture review through the Context lenses: stages, scopes, OperatorContext, authorization, tenancy, provenance. For a change in this area, or as one leg of arch-review-full.

• arch-review-contracts

  Architecture review through the Contracts lenses: interfaces, injection, wiring. For a change in this area, or as one leg of arch-review-full.

• arch-review-delivery

  Architecture review through the Delivery lenses: apps, deployment, repo layout, client architecture, logs and telemetry, conventions, substitutions. For a change in this area, or as one leg of arch-review-full.

• arch-review-full

  Full architecture review: the eight lens groups of the guideline run in parallel and merge into one report. Use before a pull request, or when a change crosses layers.

• arch-review-network

  Architecture review through the Network lenses: topology, gateway, public types, clients, realtime, push-first. For a change in this area, or as one leg of arch-review-full.

• arch-review-om

  Architecture review through the Object Model lenses: source of truth, mixins, immutability, identifiers, namespaces, pure rules. For a change in this area, or as one leg of arch-review-full.

• arch-review-ops

  Architecture review through the Operations lenses: roles, credentials, ops skills, alarms, scale-out, cost, environments, traffic, READMEs. For a change in this area, or as one leg of arch-review-full.

• arch-review-storage

  Architecture review through the Storage lenses: storage principles, tables, translation, roles, migrations. For a change in this area, or as one leg of arch-review-full.

• arch-scaffold-app

  Create a client app: the operator console, another browser app, or another command line, in the shape of the scaffold's portal and CLI, with its build, deployment, and tests. TypeScript or Python.

• arch-scaffold-entity

  Add one entity to an object-model namespace: the frozen type, the table and its migration with its policy, storage in Postgres and memory, manager operations, wire types, routes, a portal screen, and tests, in the shape of the scaffold's own. Python and TypeScript.

• arch-scaffold-namespace

  Create an object-model namespace (a swimlane) with its first entity: the manager interface and impl, storage in Postgres and memory, its README, and the wiring into both roots, in the shape of the scaffold's own namespaces. Python.

• arch-scaffold-new

  Start a new system in the guideline's shape: pick its name, copy the scaffold's domain-agnostic core under it, run its gates, record the product's first decisions, then add the first namespace.

• arch-scaffold-service

  Create a second web service beside the API: a domain service hosting some namespaces, or an app-specific service for one app, with its container, settings, routers, image, deployment, and tests, in the shape of the scaffold's API. Python (FastAPI).

• arch-scaffold-worker

  Add a kind of background work: the kind, its payload and permission, its handler in the maintenance worker or in a worker of its own, and the tests, in the shape of the scaffold's work queue and worker. Python.

• arch-upgrade-deps

  Upgrade every dependency of the repository to its latest stable or LTS release (runtimes, tools, images, CI, Terraform, libraries), then run the gates and hold back what breaks.

• arch-upgrade-scaffold

  Move a copy of the scaffold, or a layer whose own scaffold builds on it, to a later release by merging it. The scaffold branch holds the scaffold as the repository took it, and a three-way merge brings in what changed since. The first run grafts a base at the release the repository pins, or takes a

Subagents (1)

• arch-reviewer

  Reviews a scope of code through exactly one lens group of the Software Design and Architecture Guidelines and returns the standard review report. Used by arch-review-full to run the eight groups in parallel; can be delegated to directly with a group name, a scope, and the absolute paths of the lens

Similar plugins