NeoHaskell code style guidelines for writing and reviewing .hs code in this repository.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
| Use | Never |
|---|---|
x |> foo |> bar | bar $ foo x, $ |
do let y = expr | let..in, where |
case x of | patterns in function head |
if cond then a else b | case cond of True -> … |
| Named helpers with one abstraction level; orchestration reads top-to-bottom | nested control-flow pyramids, orchestration mixed with branch mechanics |
| Comments that explain constraints or intent | comments narrating what code does; extract a named function instead |
Early-exit sentinel guards in Task validation | nested if/case pyramids |
[fmt|Hello #{name}!|] | <> / ++ for strings |
Result err val | Either |
Task err val | IO |
Task.yield v | pure, return |
forall element result. | single-letter type params |
import Foo (Foo); import Foo qualified | unqualified imports |
nhcore Core modules (Text, Array, Char, File, Path…) | raw Data.* / System.* / Ghc* imports |
Write generated starters, testbed modules, documentation examples and fixtures
that represent user applications in NeoHaskell's application dialect. Use the
framework markers for the instances they generate. Use newtype when it models
the domain. Never use explicit stock or via deriving strategies in these
application examples.
Keep each deriving clause only for a concrete framework constraint or an
operation the example actually performs. Remove unused Eq, Ord and Show
instances. GHC supplies Typeable automatically, so omit explicit Typeable
deriving. Keep Generic and serialization instances when an actual codec needs
them and a framework marker does not supply them. Apply
Minimize Reader Load to declarations,
imports and annotations as well as control flow.
Framework implementation and compiler fixtures that test GHC integration can use the GHC machinery their internal contracts require. Keep that machinery inside the owning framework boundary.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
日本語の概要は準備中です。原文の説明を表示しています。
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect or supervise a PR or stack through review and CI to merge-ready, using current GitHub evidence and the requested mode.
日本語の概要は準備中です。原文の説明を表示しています。
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you benchmark or report a measured speedup or regression, including complete framework flows and compilation of projects that consume the framework.
日本語の概要は準備中です。原文の説明を表示しています。
Restate the last message in plain human language, with no jargon.
日本語の概要は準備中です。原文の説明を表示しています。
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
日本語の概要は準備中です。原文の説明を表示しています。