skills.rest
l-adic
l-adicOFFICIAL
Explore all skills by this author →
GitHub

project-developer-guide

Define PureScript development conventions, property-based tests, and three-layer FFI patterns.

4|3|Updated Nov 5, 2025
Search Tags:#testing#development#linting#coding-standards#ffi#purescript
One-click install
npx skills add https://github.com/l-adic/snarky --skill project-developer-guide
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-developer-guide
Source: https://github.com/l-adic/snarky/tree/main/.claude/skills/project-developer-guide
Command: npx skills add https://github.com/l-adic/snarky --skill project-developer-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Development conventions and practices for this codebase, guiding how engineers write PureScript code, tests, and FFI to maintain consistency.

Core Features & Use Cases

  • Establish coding standards across the project.
  • Standardize testing approaches (property-based testing with snarky-test-utils).
  • Codify FFI patterns and three-layer Rust/PureScript integration for reliable tooling and safer interfaces.

Quick Start

Follow these guidelines when starting new PureScript work or contributing tests and FFI.

Frequently Asked Questions about project-developer-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Rust and PureScript FFI bindings safely?▼

Structure Rust and PureScript FFI bindings using a three-layer pattern to maintain interface consistency and safety. This approach enforces explicit guidance on lookups and static sizing for reliable integration.

What is the standard approach for property-based testing in PureScript?▼

The standard approach for property-based testing in PureScript is using snarky-test-utils. This codifies testing conventions to standardize test creation and maintain development consistency across the codebase.

How do I establish coding standards for a PureScript project?▼

Establish coding standards for a PureScript project by defining development conventions and practices for new modules, tests, and FFI. This enforces explicit guidance on lookups, static sizing, and integration patterns.

When do I need to use static sizing in PureScript FFI?▼

You need static sizing in PureScript FFI when implementing Rust bindings to maintain consistency and safety. The three-layer FFI pattern enforces explicit guidance on lookups and static sizing for reliable tooling.

Does this PureScript guide cover linting and coding standards?▼

Yes, this PureScript guide covers linting and coding standards by defining development conventions and practices. It standardizes testing approaches and codifies FFI patterns to maintain consistency across the codebase.

Related Skills

Explore More Software Engineering Skills→
l-adicl-adic
4

ocaml-snarky-kimchi-translation

Translate OCaml Snarky/Kimchi circuits from Mina into idiomatic PureScript.

Official
Advanced
kreuzberg-devkreuzberg-dev
836

ruby-bindings-patterns

Define Ruby bindings for Rust cores using Magnus, RBS, Steep, RSpec, and Rubocop.

Official
Intermediate
mwathibenmwathiben

typescript-review

Review TypeScript and JavaScript diffs against Metabase coding standards.

Community
Intermediate
GoldziherGoldziher
115

Binding Crate Architecture Patterns

Document architectural patterns for binding crates exposing Rust libraries to host languages.

Community
Advanced