graphrefly
Official@graphrefly
Offers specialized verification, behavioral tracing, and porting services for TypeScript and Rust implementations against canonical specification invariants.
Agent Skills by graphrefly
Showing 9 vetted skills indexed across 1 GitHub repositories.
parity
Compare graphrefly-ts and graphrefly-py API surfaces, behavior, and test conformance.
dev-dispatch
Implement GraphReFly TypeScript or Python features with spec-aligned plans and approval gates.
research
Conducts multi-source web research and maps findings to a project's implementation plan.
qa
Validate GraphReFly changes via adversarial review and final verification gates.
graph-animation
Create animated GraphReFly concept videos with HyperFrames and GSAP timelines.
rust-review
Generate structured behavioral traces and audit findings for Rust port slices.
design-review
Validate GraphReFly public API designs against Q5–Q9 invariants.
decision-guard
Anchor decision questions to the canonical GraphReFly Rust-port decision log.
porting-to-rs
Convert GraphReFly TypeScript slices into Rust implementations per the canonical spec.
Frequently Asked Questions About graphrefly
FAQPage SchemaWhat specific tasks does GraphReFly enable for developers?▼
GraphReFly enables developers to perform rigorous parity checks between TypeScript and Rust implementations, validate API designs against Q5–Q9 invariants, and generate structured behavioral traces. It also facilitates the conversion of existing logic into Rust while ensuring compliance with canonical project specifications.
Which engineering personas benefit from these capabilities?▼
These capabilities are designed for systems engineers, language migration specialists, and technical architects focused on cross-language parity. It is particularly useful for teams managing complex codebases that require strict behavioral alignment between TypeScript and Rust components during migration or multi-language maintenance phases.
What are the prerequisites for implementing GraphReFly porting?▼
Implementation requires an existing TypeScript codebase and access to the canonical GraphReFly decision log. Users must align their development environment with the project's spec-based approval gates and ensure that all design changes are mapped against the established Q5–Q9 architectural invariants before initiating porting.