mir-cloud
SolidMake It Right (cloud pillar). Constraint-first infrastructure selection across AWS, GCP, Azure and Cloudflare - AI names whichever provider its training data mentions most; this ranks them from the workload's own numbers. Characterizes the workload first (egress GB/month, latency target and user geography, execution duration, GPU need, compliance and data residency), then runs a two-stage decision table: HARD CONSTRAINTS that eliminate providers outright (no region in the required country, FedRAMP/IRAP-class authorization, a runtime-duration ceiling the workload exceeds, a GPU family the provider does not sell), then SCORED TRADEOFFS across the survivors keyed on workload class. Costs AI under-models: egress (R2 zero-egress vs. hyperscaler per-GB tiers, NAT Gateway processing, cross-AZ transfer), cold-start behaviour, and managed-service exit cost. TRIGGER only while the provider or compute model is still open - comparing two or more providers, choosing serverless vs. container vs. VM, modelling cloud cost, p
Install
Quality Score: 81/100
Skill Content
Details
- Author
- anantbhandarkar
- Repository
- anantbhandarkar/make-it-right
- Created
- 3 months ago
- Last Updated
- 1 weeks ago
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
mir-devsecops
Make It Right (DevSecOps pillar). Constraint-first protocol for the path from commit to production - AI writes pipelines that go green, not pipelines safe to trust. Covers: supply chain (dependency pinning and lockfile integrity, install-script execution, typosquatting and slopsquatting of AI-hallucinated package names, SBOM, Sigstore/SLSA provenance); CI identity (the pull_request_target class of GitHub Actions bug, actions pinned by commit SHA not tag, secrets in forked-PR runs, OIDC federation, not long-lived cloud keys); secret storage, rotation, and detection; IaC (Terraform state as a credential store, drift, plan-vs-apply review, policy-as-code); containers (base-image provenance, non-root, scanning, registry trust); runtime IAM least privilege and egress restriction. Records per control WHERE it is enforced and whether it BLOCKS or WARNS. TRIGGER for CI/CD workflow files, release pipelines, Dockerfiles, Terraform/OpenTofu/Pulumi/Helm/Kubernetes manifests, dependency and lockfile changes, secret handli
mir-backend
Make It Right (backend pillar). Constraint-first backend planning protocol for AI coding agents — AI makes code that WORKS on the happy path; this makes it RIGHT under concurrency, failure, and load. Forces the model OUT of pattern-completion ('autocomplete from latent space') and INTO explicit constraint discovery before any code is written. Use whenever a task involves backend logic that changes state, touches money/inventory/auth, spans multiple tables or services, runs under concurrency, or persists data beyond a single request. Runs a hard-gated pipeline: Intent → Constraint Interrogation → Assumption Ledger → Invariants & Failure Modes → Risk Register → Design Review → Implementation → Production-Readiness Review. Spawns specialized reviewer sub-agents. Chains into a runtime tier (e.g. mir-backend-python for CPython concerns) and a framework module (e.g. mir-backend-python-fastapi for FastAPI/SQLAlchemy/Alembic). TRIGGER for backend work in ANY language (Python, Node, TypeScript, Go, Rust, Java, Kotlin,
mir-mobile
Make It Right (mobile pillar). Constraint-first NATIVE MOBILE planning protocol — AI writes screens that run in the simulator; this makes them RIGHT under process death, permission denial, flaky cellular, OS background limits, and app-store review. Runs the hard-gated pipeline (Intent → Constraint Interrogation → Assumption Ledger → Invariants & App State Machine → Risk Register → Design Review → Implementation → Production-Readiness + store submission). Carries the release gates AI ignores: Google Play targetSdk and Play Billing deadlines, restricted-permission declarations, Apple's Xcode/SDK minimum, PrivacyInfo.xcprivacy required-reason APIs. TRIGGER for app work that ships to the App Store or Google Play in ANY mobile stack — Swift/SwiftUI, Kotlin/Jetpack Compose, Kotlin Multiplatform, React Native, Flutter — including background work, offline sync, runtime permissions, keychain/keystore, push, deep links, in-app purchase, and store submission; also enterprise/MDM, OEM-preload and sideloaded builds. Chain