Claude Skills by ashfordeOU

Use when you need to define the gravity environment (magnitude and gradient) for a mission orbit under ECSS-E-ST-10-04C: select and apply the Earth gravity model appropriate to the orbit regime (point-mass/low-degree geopotential vs. high-degree geopotential, plus third-body and solid-Earth-tide perturbation terms), compute the gravitational acceleration magnitude and radial gravity gradient at the mission orbit's altitude, verify the mission's stated altitude falls inside the selected model'...

Use when running a meteoroid/space-debris impact risk assessment for a space element under ECSS-E-ST-10-04C clause 10.2.5: combine the cumulative damaging flux from each contributing particle population at the ballistic-limit critical diameter, turn it into an expected impact count over the exposed area and mission duration, and compute the probability of no penetration (PNP) and probability of damage via the Annex J Poisson method, checking the result against the mission's PNP acceptance req...

Use when you must determine which solar and geomagnetic activity indices (F10.7, Ap/Kp) apply to a space environment analysis epoch under ECSS-E-ST-10-04C clause 6.2.2 and Annex A: identify the index set an analysis purpose requires (atmospheric drag/lifetime, electromagnetic radiation reference, geomagnetic field epoch), classify the solar-cycle epoch from the F10.7 81-day-average index into solar minimum/mean/maximum, select the reference index values for that epoch, and verify a case's pro...

Use when assessing internal (deep-dielectric) charging risk for a space mission under ECSS-E-ST-10-04C clause 9.2.1.3 and Annex B.4/B.5: compute the worst-case trapped electron spectrum by enveloping the FLUMIC and NASA worst-case GEO models at each modeled energy, verify the envelope is physically consistent (flux non-increasing with energy), and screen the enveloped flux at the mission's critical energy against a stated threshold to flag orbit regimes (MEO, GEO, GTO, HEO) with elevated inte...

Use when defining the radiation environment for a Sun-Earth L2 or deep-magnetotail mission under ECSS-E-ST-10-04C clause 9.2.7: define which unshielded galactic-cosmic-ray and solar-energetic-particle components apply once the trapped-belt boundary is left behind, flag orbit segments that cross the magnetotail plasma sheet or lobes so a supplemental charging environment is added, and verify the resulting environment definition is complete before it feeds the radiation environment specificatio...

Use when computing MEO trapped-radiation flux spectra and mission fluence for a medium-Earth-orbit spacecraft per ECSS-E-ST-10-04C Annex B.3: interpolate a MEOv2-style spectral model across the crossed L-shell range, apply orbit-averaging across the radiation belts, and produce differential and integral electron and proton fluence inputs for total-dose and charging analyses. Trigger: MEO trapped radiation, MEOv2 model, L-shell crossing, orbit-averaged spectrum, electron fluence, proton fluenc...

Use when computing the meteoroid flux environment for a mission profile under ECSS-E-ST-10-04C clause 10.2.2.2/10.2.4 and Annex C: determine which meteoroid model components apply (the Grun-type sporadic background model plus any meteoroid stream active on the mission epoch), compute the background cumulative mass flux, apply Earth-shielding geometry for Earth-orbiting cases, and combine them into the total incident flux consumed by the downstream impact-risk assessment. Trigger: ecss, e-st-1...

Use when applying margins to a debris/meteoroid flux prediction and its ballistic-limit damage prediction for an ECSS-E-ST-10-04C space environment specification: compute the margined expected-impact rate from a flux margin factor, compute the margined critical (ballistic-limit) diameter from a diameter margin factor, derive the margined probability of no penetration (PNP), and verify the margin factors used meet the project's minimum conservatism before the PNP is compared against its requir...

Use when you must define the atmospheric albedo neutron environment for a LEO mission and include it in the radiation environment specification (RES) per ECSS-E-ST-10-04C: decide whether the environment applies to the orbit regime, classify the neutron energy spectrum into bands, assess the geomagnetic-latitude exposure that drives the flux, and verify the RES entry carries every required field before the RES is closed out. Trigger: ecss atmospheric albedo neutrons, albedo neutron environment...

Use when defining the plasma environment required by ECSS-E-ST-10-04C clause 8.2 for spacecraft charging analysis: determine which plasma regions (ionosphere, plasmasphere, auroral, outer magnetosphere, solar wind, magnetosheath, magnetotail/L2, planetary, induced) apply to each orbit segment, verify that a model and the electron density, electron temperature, ion density, and ion temperature are recorded for every applicable region, and identify missing regions or incomplete entries before t...

Use when producing the radiation environment specification (RES) required by ECSS-E-ST-10-04C clause 9.3 for a space mission: determine which radiation environment components (trapped radiation, solar energetic particles, galactic cosmic rays, internal-charging worst-case spectra, trapped-proton worst-case spectra, atmospheric albedo neutrons) apply to each orbit segment, verify that the RES states the model choice, basis (long-term-average vs. worst-case), and uncertainty for every applicabl...

"Use when determining which reference atmosphere model and

"Use when selecting a meteoroid or orbital-debris flux model for a

Use when selecting the geomagnetic field model reference data for a mission per ECSS-E-ST-10-04C Annex E: determine whether the internal field alone (IGRF) is sufficient for a given orbit altitude or an external/magnetospheric model must be added, validate an IGRF coefficient generation epoch as definitive, predictive, or stale, select the required spherical-harmonic degree/order truncation for the altitude, choose an external field model tier from the geomagnetic activity (Kp) index, and che...

Use when defining Earth and third-body gravitational reference constants (GM, J2 oblateness coefficient) per ECSS-E-ST-10-04C Annex A for a space mission: compute point-mass, J2 zonal-harmonic, and third-body tidal perturbation accelerations at a given orbit radius, and determine which gravity-model terms the mission's environment specification must carry for the orbit regime and mission duration. Trigger: gravity constants, GM, J2 oblateness, zonal harmonic, third-body tidal acceleration, gr...

Use when selecting solar-activity and albedo/IR reference data for a space-environment case under ECSS-E-ST-10-04C Annex F (informative): determine the solar-cycle activity level (minimum/mean/maximum) that a case should assume from its F10.7 solar-flux value, look up the reference index set (F10.7 flux, sunspot number) and the Earth albedo/IR flux references for that level, validate a proposed index value against the dataset's valid range, interpolate an index across the solar-cycle phase wh...

Use when selecting particle-radiation reference models for a space-environment case under ECSS-E-ST-10-04C Annex I (informative): categorize the particle population (trapped proton, trapped electron, solar energetic particle, galactic cosmic ray, albedo neutron) and the orbit regime, check a proposed energy against the population's cataloged model energy range and a proposed altitude against its altitude range, determine whether a low-Earth orbit is geomagnetically shielded for a given inclin...

Use when determine the ECSS-E-ST-10-04C Annex H plasma-environment reference region for a mission orbit regime (ionosphere, plasmasphere, auroral, outer magnetosphere, solar wind, magnetosheath, magnetotail/L2), validate a candidate density or temperature value against that region's reference order-of-magnitude range, derive a log-space representative value for margin analysis, and identify the hot, tenuous plasma condition associated with spacecraft surface-charging risk. Trigger: ecss, e-st...

Use when characterizing the directional solar particle flux for a mission under ECSS-E-ST-10-04C 9.2.2.5: compute the interplanetary magnetic field connection geometry (Parker spiral angle) to categorize a solar particle event's magnetic connection, classify the event's arrival phase (anisotropic onset versus later quasi-isotropic diffusion), compute the cone angle between a look/arrival direction and the field-aligned streaming direction, apply the anisotropy scaling to an omnidirectional-eq...

Use when you must compute solar proton fluences for a mission's radiation environment using the ESP model per ECSS-E-ST-10-04C clause 9.2.2.2 and Annex B.6: select the confidence level and mission duration, compute the cumulative fluence spectrum across energy thresholds, and verify the fluence is monotonically consistent with duration, confidence level and energy threshold before it feeds the radiation environment specification. Trigger: solar proton fluence, ESP model, solar particle event ...

Use when you must compute solar energetic particle (SEP) peak proton fluxes with JPL-type worst-case models for single event effect (SEE) worst-case analyses per ECSS-E-ST-10-04C: confirm the analysis purpose actually needs a peak-flux (not fluence) model, pick the standard proton energy channel that covers the device's SEE sensitivity threshold, compute the worst-case integral peak flux at the chosen confidence level, and check the worst-case window is a short high-intensity period rather th...

Use when scoping geomagnetic shielding for LEO solar-energetic-particle (SEP) and galactic-cosmic-ray (GCR) environments under ECSS-E-ST-10-04C clause 9.2.4 and Annex B.8: compute the Stormer vertical cutoff rigidity at a point from its geomagnetic latitude and radial distance, determine whether a particle of given rigidity is geomagnetically excluded or allowed to reach that point, build the exposure-fraction profile across an LEO ground track, and verify the assessment before escalating to ...

Use when computing the trapped radiation electron environment for a LEO spacecraft per ECSS-E-ST-10-04C 9.2.1.2: apply AE-8/AE-9-class flux tables indexed by McIlwain L-shell and B-L (B/B0) coordinates, include the South Atlantic Anomaly dose contribution, and produce the differential and integral electron flux inputs for total-dose and internal-charging assessments of the spacecraft. Trigger: trapped electrons, LEO radiation environment, AE-8, AE-9, McIlwain L-shell, B-L coordinates, South A...

Use when determining how the trapped-radiation environment applies to a non-LEO/GEO/MEO orbit (HEO, GTO, interplanetary transfer) under ECSS-E-ST-10-04C: determine the orbit regime from perigee/apogee altitude, split the trajectory into segments inside versus beyond the geomagnetically trapped domain using the magnetopause standoff distance, verify both trapped species (proton and electron) are covered wherever trapped-domain dwell exists, and hand off out-of-domain segments to the interplane...

Use when computing worst-case trapped proton radiation flux spectra for a space mission per ECSS-E-ST-10-04C: apply AP-8/AP-9-class models over solar maximum and solar minimum epochs, build the point-wise maximum envelope across source models and epochs, and categorize which source dominates at each energy to support radiation design margin analysis. Trigger: trapped protons, AP-8, AP-9, solar maximum, solar minimum, worst-case spectrum, point-wise envelope, radiation design margin, e-st-10-0...

Use when determine whether requirements are unambiguous under ECSS-E-ST-10C §8.2.4: identify vague qualitative terms (adequate, sufficient, appropriate, optimal), weasel qualifiers (TBD, TBC, as required, where possible), compound connective ambiguity (and/or without explicit resolution), and implicit subjects with no stated system element; flag each finding with its category and severity; confirm every requirement admits exactly one interpretation before passing the ambiguity gate. Trigger: ...

Use when auditing configuration management traceability of requirements under ECSS-E-ST-10C §8.2.3: verify each requirement carries a unique identifier, a documented source trace linking it to an originating parent requirement, standard clause, or customer specification, and an assignment to a configuration baseline. Flag requirements with missing identifiers, empty source traces, unrecognized source types, or unassigned baselines. Identify duplicate requirement identifiers across the set. A ...

Use when assess requirement-set completeness against a mission or function decomposition tree per ECSS-E-ST-10C §8.2.8: verify every leaf node in the tree has at least one covering requirement, every requirement traces to a known tree node, and no invalid trace references exist. Flag uncovered leaf nodes as completeness gaps. Flag requirements with no valid tree trace as uncategorized. Flag trace references to nonexistent nodes as data-entry errors, distinct from structural gaps. Returns a st...

Use when verify every requirement in a system specification carries a stable, unique identifier per ECSS-E-ST-10C §8.2.6: confirm each requirement has an assigned, project-controlled identifier in the agreed format, confirm no two requirements share an identifier, confirm no requirement is without an identifier, and flag identifier patterns suggesting instability such as gaps from renumbering events or placeholder values. Trigger: ecss, e-st-10-system-scope, requirements-management, identifia...

"Use when verify that every system requirement in the requirements

Use when verify each requirement in a system specification for performance content under ECSS-E-ST-10C §8.2.1: confirm each performance requirement carries quantified parameters — numeric value, engineering unit, and comparison operator — flag requirements with missing or unquantified performance data, and confirm that performance requirement types are recognized before assessment. Trigger: ecss, e-st-10-system-scope, performance-requirements, quantification, parameter-values, requirements-re...

Use when verify each requirement statement adheres to the singularity characteristic of ECSS-E-ST-10-06C §8.2.7: confirm that every statement expresses exactly one verifiable requirement and does not embed multiple requirements through coordinating conjunctions, compound predicates, or stacked modal clauses. Scan each statement for multiple 'shall' occurrences, coordinating conjunctions joining independent requirement predicates, and list structures under a single modal verb. Flag each violat...

"Use when verify that each quantitative performance characteristic in

"Use when verify that every requirement in a spacecraft system

"Use when verify that every system requirement is assigned at least one

Use when verify that a Technical Specification (TS) document satisfies ECSS-E-ST-10C §7.2 overall requirements: confirm the document organisation includes all mandatory sections in the required order, assign section-level responsibility owners, anchor each technical reference to its document identifier, confirm configuration-management baseline tagging, validate section-numbering format, mark supplementary information in dedicated annexes, and apply applicable content-distribution restriction...

Use when execute the Technical Specification establishment process under ECSS-E-ST-10C §5: advance through phase-0 preliminary TS tasks (F1.1–F1.4), verify that prerequisites are satisfied before starting each task, iterate requirements at each decomposition level until no open changes remain, then advance through phase-A TS tasks (F1.5–F1.10) and issue the phase-A Technical Specification. Trigger: ecss, e-st-10-system-scope, ts-establishment, technical-specification, phase-0, phase-a, requir...

Use when assess the purpose, chain position, and content model of an ECSS Technical Specification (TS) per ECSS-E-ST-10C §4: determine whether each TS section belongs to the general part (scope, applicability, normative references, terms and definitions, product definition) or the requirements part (technical requirements, verification requirements, interface requirements, design requirements), identify the TS issuer and recipient roles in the customer–supplier chain, and verify that all mand...

Use when validate a Technical requirements specification (TS) document against the ECSS-E-ST-10C Annex A DRD: confirm all mandatory sections are present (system identification, mission context, technical performance requirements, interface requirements, environmental conditions, and verification cross-reference table), verify each requirement carries a unique identifier and an assigned verification method (test, analysis, inspection, or review of design), check that interface requirements ref...

Use when classify technical requirements for a space system under ECSS-E-ST-10C §6.2.1–6.2.13: assign each requirement to one of twelve requirement types (functional, mission, interface, environmental, operational, human factor, ILS, physical, PA-induced, configuration, design, verification), confirm every requirement belongs to exactly one type, and flag requirement statements that cannot be assigned without additional information. Trigger: ecss, e-st-10-system-scope, requirement-types, func...

Use when verify requirement wording against ECSS-E-ST-10C §8.3 rules: confirm each statement uses shall (mandatory), should (recommendation), or may (permission); detect non-standard verbal forms (will, must); flag ambiguous or unverifiable terms (adequate, appropriate, user-friendly); enforce single obligation per statement; and reject embedded rationale text. Replace forbidden terms with measurable criteria and move justification to a NOTE. Trigger: ecss, e-st-10-system-scope, wording, verb...

Use when apply the coordinate-system definitions required by ECSS-E-ST-10C §5.3.1 across all five activity domains: mission definition, engineering, verification, operations, and data processing. For each domain, determine which reference frames must be formally defined, verify that at least the required frame families are present, and identify any domain that lacks a valid frame definition. Trigger: ecss, e-st-10-system-scope, coordinate-systems, reference-frames, applicability, mission-defi...

"Use when identify the appropriate international standards authority for

"Use when verify end-to-end coordinate system transformation chains

"Use when generate or validate a Coordinate Systems Document

Use when define coordinate systems for a spacecraft or mission under ECSS-E-ST-10C §5.4.2: select a frame type (inertial, rotating, body-fixed, orbital, or topocentric), confirm that all axes within the chosen representation (Cartesian, spherical, or cylindrical) carry unambiguous direction references, flag every frame whose origin or orientation varies with time as time-dependent, and verify that no frame with an underdefined axis or unresolved parent reference enters the system model. A com...

"Use when maintain the Coordinate Systems Document (CSD) across the

"Use when verify that coordinate-frame relationship diagrams conform

Use when define and validate a spacecraft reference frame under ECSS-E-ST-10C §5.4.1: establish the frame origin and three orthogonal right-handed axes, label each axis with a physical direction reference, determine whether the frame is inertial or time-varying (body-fixed, orbit-referenced, or planet-fixed), supply an epoch for inertial frames, confirm the name follows the ECSS uppercase-alphanumeric convention, and verify that any child frame traces an unbroken chain back to a root inertial...

Use when define mechanical body frames for a spacecraft under ECSS-E-ST-10-09C §5.4.5: determine each frame's type (spacecraft body, equipment, or sensor mounting), verify the direction cosine matrix (DCM) satisfies orthogonality and proper-rotation constraints, confirm every equipment and sensor frame names a valid parent frame traceable to the spacecraft body frame, and validate that each equipment and sensor frame carries a tied alignment data record with a declared measurement status (mea...