NeoHaskell

Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Apply when tempted to ask 'should I do X?' on reversible work.

The English summary is being prepared. Showing the original description.

Sweep the current repository's open Dependabot PRs on demand. Assess upgrade value, repair routine incompatibilities, merge verified upgrades, close unsuitable upgrades, and leave useful blocked upgrades open with a comment.

The English summary is being prepared. Showing the original description.

Run matched baseline and treatment measurements for NeoHaskell framework flows, compiled test suites and consumer compilation, retaining workload counts, inputs and raw samples.

The English summary is being prepared. Showing the original description.

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

The English summary is being prepared. Showing the original description.

Implement and review NeoHaskell framework, language, and toolchain internals. Use for Haskell API design, boundary parsing, service records, effects, concurrency, derivation, and their tests in this repository; not as an application-building guide.

The English summary is being prepared. Showing the original description.

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at their owning boundaries, including public framework APIs. Trust established invariants, retain necessary runtime checks, and keep core logic in pure functions.

The English summary is being prepared. Showing the original description.

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

The English summary is being prepared. Showing the original description.

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

The English summary is being prepared. Showing the original description.

Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

The English summary is being prepared. Showing the original description.

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

The English summary is being prepared. Showing the original description.

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy or self-report. Compilation directly checks compilation and type-level claims; it does not prove runtime behavior.

The English summary is being prepared. Showing the original description.

Apply when designing, implementing or reviewing NeoHaskell framework trust boundaries, authorization, secret handling, data isolation or resource access. Put security guarantees in owning APIs and safe defaults, grounded in reachable flows.

The English summary is being prepared. Showing the original description.

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

The English summary is being prepared. Showing the original description.

Apply when integrating a new requirement into an existing design.

The English summary is being prepared. Showing the original description.

Apply when changing shared mutable state, worker coordination, or task lifetimes in NeoHaskell framework internals. Reuse the owning subsystem, separate genuinely independent state, and use existing concurrency primitives where synchronization is required.

The English summary is being prepared. Showing the original description.

Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.

The English summary is being prepared. Showing the original description.

Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.

The English summary is being prepared. Showing the original description.

Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change. Use property-based testing for contracts over many inputs.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Inspect or supervise a PR or stack through review and CI to merge-ready, using current GitHub evidence and the requested mode.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.