Echo-aloha/asphalt-codex-skills-5 / skills/pfc5-asphalt-workflow
pfc5-asphalt-workflow
VerifiedOrchestrate PFC2D/PFC3D 5.0 asphalt-mixture case handoff, specimen generation, fistPkg26 integration, Burger calibration, Marshall or rutting tests, validation, and reproducible delivery; use whenever a user mentions PFC5 asphalt, AC mixtures, fistPkg, Marshall, wheel tracking, or rutting.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.6 KB |
| agents/openai.yaml | config | 327 B |
| dependencies.json | config | 1.4 KB |
| references/fistpkg-contract.md | markdown | 2.6 KB |
| references/intersection-rutting-research-evidence.md | markdown | 5.8 KB |
| references/runtime-verification-manifest.json | config | 2.3 KB |
| references/standards-method-map.md | markdown | 5.9 KB |
| references/standards-policy.md | markdown | 3.2 KB |
| references/standards-source-ledger.json | config | 7.9 KB |
| references/version-matrix.md | markdown | 1.0 KB |
| scripts/check_fistpkg.py | script | 685 B |
| scripts/check_runtime_manifest.py | script | 2.3 KB |
| templates/pfc5-asphalt-intake.yaml | config | 3.5 KB |
| tests/test_check_fistpkg.py | script | 2.1 KB |
| tests/test_pfc5_runtime_assets.py | script | 2.4 KB |
references/fistpkg-contract.md
View on GitHub# fistPkg26 external dependency contract
## Provenance
The inspected package identifies itself as PFC 5.0 FISHTank `fistPkg26`, dated
2018-08-24. This skill treats the dependency at the PFC 5.0 family level and does not
require a particular PFC5.0 subversion. Its public README places source under
`ExampleProjects/fistSrc`.
This skill package does not grant redistribution rights for those files. Keep the
licensed package external and record its checksum/location only in the user's private
case manifest.
## Expected layout
```text
<FISTPKG_ROOT>/
├── fistPkg-README.txt
├── fistPkg-publicMods.txt
├── Documentation/
└── ExampleProjects/
├── fistSrc/
│ ├── fistPkg-version.txt
│ ├── ft.fis
│ ├── ck.fis
│ ├── ct.fis
│ ├── dc.fis
│ └── tt.fis
├── MatGen-Linear/
├── MatGen-ContactBonded/
├── MatGen-ParallelBonded/
├── MatGen-FlatJointed/
└── MatGen-Hill/
```
Hill additionally uses `hl.p3fis`, `udm_hl.p3fis` and a platform-specific DLL. It is
not required for the normal PFC5 asphalt route.
## Integration procedure
1. Run the bundled checker against `<FISTPKG_ROOT>`.
2. Copy only the needed `fistSrc` and one selected `MatGen-X` project into a private
case work directory, following the fistPkg README.
3. Preserve upstream files; implement asphalt parameters and overrides in separately
named files when the PFC5 project loader permits it.
4. Record source release, PFC2D/PFC3D 5.0 product, copied files and any changed functions.
5. Run the original baseline project before applying asphalt changes.
6. Run a small adapted pilot before the production specimen/test.
## dc.fis adapter boundary
The inspected `dc.fis`:
- calls `_dcMakeWalls` from `dcSetupPhase`;
- expects walls with IDs 1 and 2 to become `dcWp0` and `dcWp1`;
- measures and drives the second coordinate as the axial direction;
- calls `ft_SmoothGrainWallInterface`, initializes callbacks and uses a post-peak stop
rule.
Replacing `_dcMakeWalls` is therefore the minimum geometry hook, not proof that a
Marshall adaptation is complete. Audit pointer IDs, head placement/rotation, contact
behavior, smoothing, sign, force/displacement calculation, stop rule and flow
post-processing.
## Checker semantics
`check_fistpkg.py` is read-only. Exit code 0 means the expected text/source layout,
release marker and PFC 5.0 family marker were found. It does not:
- validate the PFC license;
- install the Hill DLL;
- execute FISH;
- prove that a modified case is mechanically valid.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |