bricerising

20 mods across 1 repository, 7 stars between them.

architecture

04

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Design or refactor multi-service system architecture (domain boundaries, service decomposition, event-driven vs request/response, CQRS, sagas, API gateways, data ownership). Use when work spans multiple processes/services, needs eventual consistency, or requires clearer integration seams. NOT for in-process code…

7 1mo ago A 86 tokens original Apache-2.0

archobs

05

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Run architecture observability analysis on a git repository to measure coupling, boundary health, risk hotspots, and temporal drift. Use when you need empirical data about code structure before making architecture or refactoring decisions, or to validate that changes improved boundary discipline. NOT for choosing…

7 1mo ago C 94 tokens original Apache-2.0

debug

06

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Triage and diagnose production or local issues by following logs → traces → metrics (HTTP/gRPC/async). Use when investigating errors, latency spikes, 5xx responses, SLO violations, or regressions in an instrumented app. NOT for adding new instrumentation (use observability); NOT for applying resilience patterns (use…

7 1mo ago A 69 tokens original Apache-2.0

design

07

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Pick the right in-process code pattern for a refactoring or extensibility need (GoF creational/structural/behavioral), and access implementation guides for specific patterns. Use as a decision workflow when unsure which pattern family fits, or go directly to pattern references when you already know. NOT for…

7 1mo ago A 71 tokens original Apache-2.0

finish

08

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Run a final "definition of done" check before shipping: verify correctness, tighten contracts/docs, and produce a change summary. Use at the end of non-trivial work to confirm nothing was missed before merge/release. NOT for writing tests (use testing); NOT for adversarial code review (use review); NOT for initial…

7 1mo ago A 72 tokens original Apache-2.0

forecast

09

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Predict likely next developments from internal development patterns (git history, archobs clusters) and external signals (intel feeds). Use when you need forward-looking intelligence — what's GOING to happen, not what already happened. NOT for gathering raw signals (use intel); NOT for static code-structure analysis…

7 1mo ago A 82 tokens original Apache-2.0

intel

10

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Gather and shape intelligence signals from collected feeds (RSS, HackerNews, EDGAR) into audience-aware output. Use when you need current context on a technology, industry trend, or domain — or when you need to present signals to a specific audience. NOT for forward-looking predictions (use forecast); NOT for…

7 1mo ago A 78 tokens original Apache-2.0

observability

11

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Add or change observability instrumentation (structured logging, OpenTelemetry traces/spans, RED metrics, dashboards, alerts). Use when adding logs/metrics/traces to code, defining telemetry field contracts, or building monitoring runbooks. NOT for diagnosing existing issues with existing telemetry (use debug); NOT…

7 1mo ago A 70 tokens original Apache-2.0

plan

12

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Break a request into a scoped implementation plan with ordered tasks, risk flags, and verification steps. Use before starting non-trivial, cross-cutting, or ambiguous work to align on approach and prevent rework. NOT for writing spec artifacts or contracts (use spec); NOT for auto-routing across multiple skills (use…

7 1mo ago A 66 tokens original Apache-2.0

platform

13

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Design and maintain shared platform libraries (e.g. packages/shared) that standardize cross-cutting concerns (auth wrappers, config, HTTP/gRPC helpers, typed errors, retry policies, lifecycle hooks). Use when multiple services duplicate boundary logic or need a golden-path primitive; prevents "utils junk drawer"…

7 1mo ago A 88 tokens original Apache-2.0

resilience

14

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Apply fault-tolerance patterns to outbound calls and async consumers (timeouts, retries with backoff+jitter, circuit breakers, bulkheads, idempotency keys, graceful degradation). Use when a service calls external dependencies, processes queues/events, or needs hardening against partial failures and flaky upstreams.…

7 1mo ago A 81 tokens original Apache-2.0

review

15

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Run a structured adversarial code review (critique → defense → rebuttal → verdict) with evidence-backed findings and stable IDs. Use when you want a thorough, multi-perspective review of code changes, a PR, or a design — produces actionable findings ranked by severity. NOT for writing or expanding tests (use testing)…

7 1mo ago A 77 tokens original Apache-2.0

security

16

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Apply security guardrails (authentication, authorization, input validation, SQL/XSS/command injection prevention, secrets management, SSRF protection, secure logging, dependency auditing). Use when adding/changing endpoints, auth flows, data access, file/network I/O, or handling user input and sensitive data. NOT for…

7 1mo ago A 83 tokens original Apache-2.0

spec

17

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Write and maintain spec-first artifacts (service specs, API contracts via OpenAPI/protobuf/WebSocket schemas, ADRs, task lists, quickstarts). Use when creating specs/.md, apps//spec/ bundles, or contracts/ docs, especially before major behavior changes or multi-agent collaboration. NOT for implementation task…

7 1mo ago A 86 tokens original Apache-2.0

testing

18

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Create or expand test suites for microservices (unit, integration, consumer-contract tests for HTTP/gRPC handlers, service flows, event consumers, caches, jobs). Use when adding tests, raising coverage, writing regression tests, or validating consumer-facing behavior. NOT for adversarial code review (use review); NOT…

7 1mo ago A 73 tokens original Apache-2.0

typescript

19

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Write, review, and refactor TypeScript for readability, type safety, and runtime correctness (Node.js/React/shared libs). Use when creating TS modules, modeling domain types, handling errors (Result/Either), validating external inputs (Zod/io-ts), organizing imports, or preventing cyclic dependencies. NOT for choosing…

7 1mo ago A 81 tokens original Apache-2.0

workflow

20

bricerising/enterprise-software-playbook

Skill Claude CodeCodex

Auto-select and orchestrate playbook skills end-to-end for feature, bug-fix, or refactor work. Use when the user gives a general request without naming a specific skill — workflow picks the right skills, sequences them, and keeps overhead proportional to the change size. NOT for creating a standalone task breakdown…

7 1mo ago A 76 tokens original Apache-2.0