Production architecture decisions your AI coding agent can explain, challenge, and prove.
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying an AI or LLM system: RAG, model routing, memory, tool use, autonomous or multi-agent workflows, safety, evaluation, latency, cost, or rollout. Trigger when model, data, policy, tool, or approval boundaries are central. Use system-architecture-harness for…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying APIs and client contracts: endpoint design, validation, errors, pagination, filtering, bulk behavior, versioning, serialization, webhooks, realtime channels, SDKs, or CLIs. For whole-system architecture use system-architecture-harness; for identity and…
Skill Claude CodeCodex
Use when independently reviewing or verifying an architecture specification, RFC, ADR, diagram, migration plan, AI or agent design, production-readiness proposal, architecture metrics, or post-incident structural causes. May frame review criteria or recommend bounded remediation, but does not own greenfield design or…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying asynchronous work: jobs, workers, schedules, queues, events, outbox or inbox, batch processing, deduplication, email, or notifications. For transaction invariants use transactions-consistency; for retry and overload controls use resilience-flow-control; for…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying identity and access behavior: login, signup, recovery, sessions, tokens, OAuth/OIDC, MFA, passkeys, API keys, service identity, permissions, account lifecycle, tenant isolation, or privileged administration. For whole-system architecture use…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying data models and storage behavior: schemas, identifiers, time, money, constraints, indexes, queries, deletion, lifecycle, files, media, search, provenance, authority, reconciliation, or cleanup. For concurrency use transactions-consistency; for schema…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying Git repositories and version-control workflows: branches, commits, merges, rebases, cherry-picks, conflicts, worktrees, remotes, pull requests, protected refs, force pushes, tags, semantic versions, release branches, history rewrites, secret removal, merge…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying data and contract evolution: schema migrations, expand-and-contract, resumable backfills, API or event compatibility, synchronization, CDC, reindexing, traffic cutover, or legacy integration. For outbox and inbox delivery use async-messaging; for transaction…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying production operations: logs, metrics, tracing, health, audit, async observability, runbooks, incidents, import or export, backup, restore, disaster recovery, high availability, multi-region, or residency. For rollout sequencing use migration-evolution; for…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying quality and release readiness: test strategy, test data, concurrency and failure testing, load and performance evidence, scalability, resource management, compression, release exceptions or waivers, cross-domain completion, and production-ready claims. For…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying resilience and flow controls: caches, invalidation, rate limits, quotas, external integrations, retries, timeouts, circuit breakers, bulkheads, degradation, backpressure, or admission control. For queue delivery use async-messaging; for transactional effects…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying runtime and delivery foundations: project structure, bootstrap, configuration, connection pools, networking, discovery, service communication, graceful startup or shutdown, deployment gates, CI/CD, migration ordering, or infrastructure configuration. For…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying security and privacy controls: secrets, encryption, TLS or PKI, cryptography, hashing, sensitive-data lifecycle, redaction, abuse defense, feature flags, temporary data, or secure randomness. For identity flows use auth-access; for public contract attacks…
Skill Claude CodeCodex
Use when thinking through or changing a production software architecture, or when reviewing or verifying architecture work inside the same design flow: greenfield systems, decomposition, migration, scale, reliability, security, data ownership, distributed workflows, clients, platform governance, or rewrites. Use…
Skill Claude CodeCodex
Use when the question is which ArcForge skill to use and in what order, and nothing should be inspected, changed, or implemented yet: name the owning skill, the mode, the sequence, and the coverage gaps, then stop. Answers where do I start, which skill covers this, which mode should this run in, what order should…
Skill Claude CodeCodex
Use when thinking through, reviewing, changing, or verifying transactional or concurrent behavior: isolation, anomalies, locking, state machines, idempotency, sagas, consistency, replication, sharding, consensus, distributed locks, fencing, or ordering. For jobs, queues, and outbox delivery use async-messaging; for…
Skill Claude CodeCodex
Use when a request needs ArcForge but the owning skill, the mode, or the order is not settled: choose the skill, choose Think, Review, Change, or Verify, resolve required, recommended, handoff, and optional-depth companions, and sequence multi-domain work such as checkout, signup, migration, release, or incident…