Claude Skills by the-vibey-project

Use when working on serviceability, updates, or driver assistance: diagnostics including UDS and DTC handling, flashing and over-the-air update with its safety and rollback constraints, and ADAS and autonomy — the SAE levels stated precisely, the perception-planning-control stack, safety architecture for autonomy, and the validation problem that makes it hard.

Use when dealing with how automotive software actually gets built and shipped: process and toolchain including ASPICE and the V-model, testing from unit through hardware-in-the-loop and vehicle-level validation, the vehicle domains (powertrain, chassis, body, infotainment, ADAS) and their differing constraints, and the supply chain reality of OEMs, tier-one suppliers and who actually writes the code.

Use when safety or security requirements drive the design: real-time scheduling and timing analysis, functional safety under ISO 26262 including how ASIL is determined, ASIL decomposition, the safety lifecycle, the software mechanisms you will actually implement, and SOTIF (ISO 21448); plus cybersecurity under ISO/SAE 21434 and the UN R155 and R156 regulations that gate market access, with the technical measures they imply.

Use when checking an automotive software anti-pattern, looking up a bus rate, timing or standard number, asking what actually moved in regulation and architecture (verified August 2026), finding the books and standards, or needing a picker and a design review checklist. Companion to the other automotive-software skills.

Use when the commercial or operational reality matters more than the feature list: cost mechanics including commitments, egress and the line items that surprise people, reliability, regions and what an SLA actually promises, infrastructure as code across the native and third-party tools, lock-in and multi-cloud assessed honestly rather than ideologically, and migration approaches and their realistic effort.

Use when starting on a provider comparison or designing an account structure: the honest framing of what genuinely differs between AWS, GCP and Azure versus what is naming, the shared responsibility model, identity and access where the three actually diverge — IAM policies and roles, Entra ID and RBAC, and GCP's resource-oriented model — with the comparison that matters, and resource hierarchy and organization design. Includes the router for the whole aws-gcp-azure-deep-dive reference.

Use when placing workloads: networking including VPC models, peering, private connectivity and the egress paths, compute and the instance families and pricing modes, containers and the managed Kubernetes offerings and how much each provider actually manages, and serverless including the function platforms, their cold-start and concurrency behaviour, and where serverless stops being the right answer.

Use when checking a cloud anti-pattern, mapping a service to its equivalent on another provider, checking what moved in egress pricing under the EU Data Act switching regime or in the AI-driven competitive position (verified August 2026), correcting a misconception, looking up a limit or quota, or needing a picker and a new-environment checklist. Companion to the other aws-gcp-azure-deep-dive skills.

Use when choosing a data or platform service: object, block and file storage and the storage classes and retrieval characteristics, the managed database offerings relational and otherwise, the analytics and warehouse stacks, the AI/ML service layers and what is genuinely differentiated, and observability — the native logging, metrics and tracing products and their limits.

Use whenever working with Azure Role-Based Access Control, Azure resource permissions, service principals, managed identities, scope hierarchy, control plane vs data plane authorization, AKS RBAC, or GitHub Actions Azure authentication. Triggers on any question about who can do what on Azure resources.

Azure service selection and production implementation guide covering compute (Container Apps, AKS, Functions, App Service), messaging (Service Bus, Event Hubs, Event Grid), networking (hub-spoke, Virtual WAN, private endpoints), storage, databases (SQL, Cosmos DB, PostgreSQL), AI/Microsoft Foundry, cost optimization, IaC, identity, and 2024–2026 deprecations. Use when advising on Azure architecture decisions, service comparisons, migration planning, or production configuration patterns.

Use whenever working with Kubernetes infrastructure-as-code, AKS provisioning, Helm charts, Kustomize overlays, GitOps with Flux or ArgoCD, Terraform for AKS, Bicep for Azure resources, or AKS security hardening. Triggers on any AKS, Kubernetes IaC, GitOps, or cluster configuration request.

Use for the constraint layer that shapes what payment systems can do: compliance including KYC, AML, sanctions screening and the de-risking that cuts off whole corridors, security covering the SWIFT-related heists, endpoint compromise and the CSP controls that followed, and the real costs and economics of remittances and where the fees actually go.

Use for cross-border payments and the messaging layer: correspondent banking and the nostro-vostro structure that makes international payments slow and expensive, what SWIFT actually is — a messaging cooperative, not a payment system — the MT to ISO 20022 migration and what richer data enables, gpi and end-to-end tracking, governance, sanctions and the geopolitics of network access, and the alternative and parallel systems including CIPS and SPFS.

Use for the modern rails and the digital-money debate: instant payment systems including FedNow, UPI, Pix and SEPA Instant and why domestic instant payments spread faster than cross-border ones, stablecoins and their reserve, redemption and run-risk questions, retail and wholesale CBDCs and the actual state of deployment, and tokenized deposits and wholesale settlement experiments.

Use for the foundations that most payment confusion traces back to: what a payment actually is as a transfer of claims, what a bank is and how deposits are created rather than lent out, central banks and reserve accounts as the ultimate settlement layer, the payment system taxonomy of RTGS, deferred net settlement, card and instant rails, and clearing, netting and Herstatt settlement risk. Includes the router for the whole banking and payments reference.

Use when correcting a payments misconception, looking up a settlement time, volume, fee or migration-deadline figure, finding the sources, or needing a quick-reference picker — plus the current state of the ISO 20022 migration and what is actually settling on blockchain rails. Companion to the other banking and payments skills.

Use when the question involves Ripple or XRP, where conflation is the norm: the three distinct things — the company, the asset and the ledger — kept apart, XRP Ledger mechanics including the consensus protocol and the built-in decentralized exchange, Ripple's actual products and how many of them use XRP, the legal status after the SEC litigation, and an honest assessment of what has and has not been adopted.

Use when reasoning about why a substance behaves the way it does at the molecular level: atomic structure and periodic trends and their underlying cause, electronegativity as the master variable, bond types, VSEPR geometry and orbital models, and the intermolecular forces from dispersion through hydrogen bonding that set boiling points, solubility and phase behaviour, plus solutions and colligative properties. Includes the router for the whole biology-chemistry-foundations reference.

Use when working on the biology side: proteins and their folding, nucleic acids, carbohydrates and lipids; enzymes and enzyme kinetics including the Michaelis-Menten treatment and inhibition; bioenergetics and metabolism from ATP coupling through glycolysis, the citric acid cycle and oxidative phosphorylation; membranes and transport; cell architecture and organelles; the cell cycle and signal transduction; and evolution as the organizing principle underneath all of it.

Use when working with organic structures or interpreting an analytical result: structure, functional groups, stereochemistry and isomerism, and reaction mechanism as the reasoning that actually transfers rather than a list of named reactions; plus analytical methods and spectroscopy — chromatography, mass spectrometry, NMR, IR and UV-Vis — and what each one can and cannot tell you.

Use when correcting a common chemistry or biology misconception, checking a constant, magnitude or physiological value, finding the textbook canon, or needing the core equations and a reasoning checklist for approaching an unfamiliar problem. Companion to the other biology-chemistry-foundations skills.

Use when asking whether a reaction goes and how fast: the laws of thermodynamics and the Gibbs free energy relation, enthalpy and entropy, chemical kinetics and rate laws, activation energy and catalysis, equilibrium and Le Chatelier, acid-base chemistry, pH and buffers, and redox and electrochemistry including half-reactions, cell potentials and the Nernst equation.

Use when working on the physical or experimental side: biomechanics of tissue and gait, biomaterials and biocompatibility, tissue engineering and scaffolds, neural interfaces and prosthetics (recording, the signal chain, prosthetic control), lab automation and instrumentation, and the biostatistics that determine whether a result holds up — study design, multiple comparisons, survival analysis and effect sizes.

Use when building models or pipelines on clinical or genomic data: clinical data structures and standards, the technicals of clinical machine learning — the prevalence problem, calibration rather than discrimination alone, where clinical models learn the wrong thing, and the validation ladder — and bioinformatics including sequence alignment, variant calling, and expression and single-cell analysis.

Use when correcting a common biomedical misconception, checking a physiological or instrument value, finding the textbook canon, or needing the core equations, a method picker, and a debugging checklist for a pipeline producing implausible output. Companion to the other biomedical-engineering skills.

Use when working with physiological signals or medical images: the signals and their frequency bands (ECG, EEG, EMG, PPG), the filtering constraints specific to this domain, detection and feature extraction; and medical imaging — modality physics for CT, MRI, ultrasound, PET and X-ray, the DICOM internals that produce silent errors, reconstruction, and registration and segmentation. Includes the router for the whole biomedical-engineering reference.

Use when modelling biological structure or dynamics: structural biology including protein structure determination and prediction, systems biology and network modelling, pharmacokinetics and pharmacodynamics including compartment models, clearance and dose-response, and physiological models of the cardiovascular, respiratory and metabolic systems.

Use when designing or implementing a UTXO-based chain, modelling transaction inputs and outputs, writing or auditing Bitcoin Script locking and unlocking scripts, deciding which address formats a wallet or node must support, or forking Bitcoin. Covers the UTXO ledger model, block structure and chain linkage, the coinbase transaction and its maturity rule, Script validation, and the four Bitcoin address types. Part 4 of 8 of the Building a Cryptocurrency reference.

Use when deciding between shipping an ERC-20 token, a new account-model chain, or an L2 rollup, and when designing or reviewing account state, EVM data locations, gas budgets, call semantics, or a fungible token contract. Covers the account world-state model, the EVM stack machine and its storage costs, the EIP-1559 gas system, the ERC-20 interface and its integration hazards. Part 5 of the Building a Cryptocurrency reference.

Use when choosing a consensus mechanism for a new chain, sizing confirmation counts before releasing value, reasoning about 51 percent attacks and chain reorganizations, tuning difficulty retargeting, picking a proof-of-work algorithm, or deciding between probabilistic, explicit and instant finality. Covers proof of work, proof of stake, Gasper, BFT and DAG designs, slashing, nothing-at-stake and validator economics. Part 3 of 8 of the Building a Cryptocurrency reference.

Use when choosing a hash function, signature scheme, address format or key-derivation path for a chain, when building Merkle proofs or SPV inclusion checks, or when reviewing a nonce, seed-phrase or multisig design for hazards. Covers hash properties and current status, ECDSA against Schnorr, EdDSA and ring signatures, Merkle trees and the Merkle-Patricia trie, and BIP-32/39/44/380 key derivation. Part 2 of the Building a Cryptocurrency reference.

Use when designing or debugging the peer-to-peer layer of a chain — DNS seeds, peer exchange, inv and getdata gossip, compact block relay, mempool and relay policy — or when setting issuance, supply caps, tail emission, fee markets, token distribution and the security budget. Covers the policy versus consensus distinction and the trade-offs of each distribution method. Part 7 of 8 of the Building a Cryptocurrency reference.

Use when adding sender, receiver or amount privacy to a chain, choosing among ring signatures, stealth addresses and confidential transactions, sizing an anonymity set, planning a move to full-chain membership proofs, or weighing mandatory privacy against exchange delisting and EU AMLR exposure. Covers the Monero reference design end to end: stealth address derivation and view-key scanning, ring size 16, Pedersen commitments with Bulletproofs+ range proofs, FCMP++, Dandelion++, subaddresses a...

Use when auditing a chain or a contract for the failures that actually drain funds, choosing between an ERC-20 token, an L2 rollup and a new blockchain, picking the language, consensus, signature, wallet and explorer stack for a custom chain, or working a pre-mainnet launch checklist. Covers the 2025-2026 loss data, the design principles and key-management rules that prevent most bugs, and the three build paths with their timelines. Part 8 of 8 of the Building a Cryptocurrency reference.

Use when choosing a ledger model, consensus mechanism, programmability level, privacy model or supply schedule for a new chain, when you need the Bitcoin, Ethereum and Monero reference architectures compared cell by cell, or when you need the precise definition of what a blockchain is before designing one. Covers the replicated-state-machine definition and the five upstream decisions that cascade into every downstream implementation choice. Part 1 of 8 of the Building a Cryptocurrency reference.

Use when setting planting dates and seeding depth, designing a rotation, deciding whether a pest is worth spraying, choosing or scheduling irrigation, or comparing farming systems before committing to one. Covers growing degree days, cover crops, the tillage spectrum, IPM economic thresholds and resistance management, irrigation efficiency and salinity, and an honest read on conventional, organic, no-till, regenerative and agroforestry systems. Part 7 of the Building a Homestead reference.

Use when detailing a wall, roof, window or any penetration and you need the four control layers in the right priority order, when an assembly keeps getting wet or cannot dry, or when specifying concrete, wood, steel or masonry for a house. Covers the rainscreen principle, air leakage as a moisture path, vapor retarder placement by climate, flashing, drying potential, roof falls, and the material properties that actually govern durability. Part 2 of the Building a Homestead reference.

Use when choosing a livestock species for a site, formulating or troubleshooting a ration, preventing acidosis or bloat, or explaining why ruminants live on grass while pigs and poultry cannot. Covers the four stomach compartments and volatile fatty acids, the six nutrient classes and what limits each, body condition scoring, and gestation and estrous cycles for seven species. Part 4 of the Building a Homestead reference.

Use when you are specifying shelter or fencing for cattle, sheep, goats, pigs or poultry, setting quarantine and vaccination practice, planning breeding and calving, or choosing between continuous, rotational and mob grazing. Covers water supply, parasite resistance and FAMACHA, EPDs and dystocia risk, stocking rate versus stocking density, and the Five Freedoms with low-stress handling. Part 5 of the Building a Homestead reference.

Use when you hit an unfamiliar term of art from the homestead reference — Animal Unit, Body Condition Score, CEC, EPD, FAMACHA, GDD, IPM, NDF/ADF, rainscreen, refugia, rumen, shear wall, thermal bridge, volatile fatty acids — and need the definition plus the section that explains it, or when you want the books, codes and free services that actually teach building, livestock and soil. Covers the complete glossary and the complete further-reading list across all three domains. Part 8 of the Bui...

Use when sizing heating, ventilation, electrical or plumbing for a house, allocating ceiling void and services space, setting fire escape and detection provisions, ordering the trades from site preparation to certificate of occupancy, or preparing for plan review and inspections. Covers MEP coordination, structural fire resistance by material, the nine-stage build sequence, temporary works, IRC prescriptive versus engineered design, and the full house build checklist. Part 3 of the Building a...

Use when siting a house, planning ground investigation, choosing a foundation, orienting for solar gain, or selecting a structural system and material. Covers bearing capacity and differential settlement, the gravity load path, shear walls and hold-downs, and a full comparison of timber, masonry, reinforced concrete, mass timber and steel. Part 1 of the Building a Homestead reference.

Use when testing or interpreting soil, setting lime and fertilizer rates, diagnosing compaction or erosion, or planning organic matter and manure applications. Covers soil composition, horizons, cation exchange capacity, soil biology, the 4Rs, nitrogen, phosphorus, potassium and pH management. Part 6 of the Building a Homestead reference.

Use when orienting on a commercial legal question before taking it to counsel: the scope note on what this material is and is not, how legal risk actually materializes, contracts including the clauses that matter and the ones that are negotiated theatre, intellectual property across copyright, trademark, patents and trade secrets, employment and contractor classification, privacy and data obligations, consumer protection and marketing law, and disputes and their realistic costs. Orientation, ...

Use when planning or auditing marketing: the fundamentals, what the advertising evidence actually shows rather than what the folklore claims, brand and advertising and the long-term versus short-term split, measurement and attribution including the limits of last-click and multi-touch models and incrementality testing, and the channels and their differing economics.

Use when reasoning about how a business actually works: business models and unit economics including contribution margin, CAC, LTV and payback and the ways those numbers get misstated, strategy and competitive positioning, operations and organization design, and financing from bootstrapping through venture and debt with the dilution and control consequences. Includes the router for the whole business-marketing-sales-law reference.

Use when checking what moved in marketing measurement after the cookie reversal or in the US state privacy patchwork (verified August 2026), correcting a business, marketing, sales or legal misconception, finding the canon, or needing a picker and the checklist to run before signing anything. Companion to the other business-marketing-sales-law skills.

Use when building or running a sales motion: the sales process and pipeline stages, qualification frameworks and what they are actually for, negotiation including preparation, concession structure and the tactics worth recognizing, and sales management covering forecasting, compensation design and the metrics that drive the wrong behaviour.

Use when designing a part that has to work rather than just print: design for additive manufacturing including overhangs, supports, orientation and anisotropy, tolerances and fits and how to achieve them on a printer that does not hold them natively, and materials and their mechanical, thermal and environmental behaviour.