Phylaxsystems Skills

Phylax Credible Layer assertions invariant mapping. Use when starting a protocol to map invariants before writing phylax/credible layer assertions or tests.

Phylax Credible Layer assertions testing. Tests assertions with CredibleTest, focused pcl E2E behavior tests, fuzzing, and backtesting.

Phylax Credible Layer assertions design. Designs high-signal invariants, classifies protocol protection surfaces, and maps them to V2 triggers before implementation.

Phylax Credible Layer assertions backtesting. Runs assertion backtests against historical transactions. Use when validating phylax/credible layer assertions on real chain data or known exploits.

Phylax Credible Layer assertions workflow. Guides the end-to-end PCL workflow (project setup, testing, store/submit, and deploy). Use when setting up or deploying phylax/credible layer assertions with the CLI and dApp.

Phylax Credible Layer assertions implementation. Implements V2 Credible Layer assertion contracts using triggers, fork-aware precompiles, call context, and focused helper structure.

Phylax Credible Layer assertions troubleshooting. Diagnoses common assertion failures and non-triggering issues. Use when phylax/credible layer assertions fail unexpectedly or do not execute.

Deploy a Credible Layer assertion project on-chain end-to-end with the pcl CLI, fully agentically. Use when asked to deploy assertions, create or activate an assertion release, set up pcl auth/RPC/wallet for deployment, set or transfer a protocol manager, or deactivate a release. Assumes assertions are already written (see write-protection-assertions for authoring).

Run local agentic triage for Phylax PCL/Credible Layer invalidations, protected-loss events, blocked transactions, failed or pending debug traces, and "we got hacked" requests by using the pcl CLI plus keyless/public or keyed JSON-RPC, cast, Sourcify/4byte/explorer source lookups, and Heimdall-rs local decompiler/disassembler evidence. Use when a user reports a new invalidation, asks what a dropped transaction attempted, why an assertion invalidated it, whether it looks malicious or benign, what value or protocol state was protected, what risk remains, or what action to take next across any EVM protocol, chain, asset type, router, bridge, vault, lending market, token, or custom assertion.

Optimize Credible Layer/PCL Solidity assertion trigger selection for existing or newly edited assertions. Use when an assertion fires too often, relies on broad onFnCall/registerFnCallTrigger usage, needs lower execution overhead, or needs a trigger review that preserves the same security invariant while preferring narrower triggers such as onTxEnd/registerTxEndTrigger, ERC20-change triggers, storage-change triggers, or cumulative flow triggers where appropriate.

Create or update high-quality Credible Layer Solidity example assertions and E2E tests for a protocol repository by classifying the protocol against the existing protection suite, using bundled V2 trigger/precompile digests, organizing examples under the right protection category, and prioritizing a small set of focused external-state invariants that are not already enforced by protocol require statements. Use when the user provides or references a GitHub/protocol repo and asks for example assertions, protection-suite coverage, invariant design, pcl test E2E validation, or assertion workflow guidance.

Use when changing credible-sdk assertion-executor, credible-std, assertion-verification, or sidecar behavior that should be proven with a new assertion-driven test, especially for new precompiles, trigger semantics, assertion specs, or LocalInstance-based integration coverage.