Skip to content

juspay/vira / .agents/skills/haskell

haskell

Verified

Use this when writing or reviewing Haskell code. Covers error handling, type safety, idiomatic patterns, HLint compliance, Aeson usage, and testing.

FileKindSize
RELUDE.mdmarkdown2.6 KB
SKILL.mdskill md2.0 KB
---
name: haskell
description: Use this when writing or reviewing Haskell code. Covers error handling, type safety, idiomatic patterns, HLint compliance, Aeson usage, and testing.
---

# Haskell Development

## Error Handling

- NEVER use `undefined` or `error` as placeholders
- Handle ALL `Maybe`/`Either` cases explicitly — no silent ignoring
- Handle all pattern match cases — no partial matches
- Use types to make impossible states unrepresentable

## Type Safety & Idioms

- Write type signatures for all top-level definitions
- Prefer `Text` over `String`
- Use `newtype` wrappers for domain types
- Apply smart constructors for validation
- Write total functions — avoid `head`, `tail`, and other partial functions
- Prefer pure functions over IO
- Use explicit module exports
- Favor composition over complex functions
- Write Haddock documentation for public APIs

## Records

- Use `OverloadedRecordDot` (add pragma to modules that use the syntax)
- Use `DisambiguateRecordFields` and `DuplicateRecordFields` for simple field names
- Use lenses for record manipulation when appropriate

## Aeson

- NEVER construct aeson objects by hand
- Create a type and use `encode`/`decode` on it
- Prefer generic deriving; hand-write instances only when the wire format requires it

## HLint

If `.hlint.yaml` exists in the project root, run `hlint` on every modified file. Fix ALL warnings before considering the task complete.

## Build Workflow

If `ghcid.txt` exists in the project, check it after every code change for compile errors. Do not proceed until it is clean. If this file does not exist, use whatever build workflow the project documents.

When adding or deleting `.hs` modules: update the `.cabal` file, or run `hpack` if `package.yaml` exists.

## Relude

If the project uses [relude](https://github.com/kowainik/relude) (check `.cabal` or `package.yaml` dependencies), also follow [RELUDE.md](RELUDE.md) for idiomatic substitutions.

## Testing

- QuickCheck for property-based testing
- HUnit or Hspec for unit tests
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall