Explore skills
Showing 21001–21030 of 77079 skills
Catch the user up on what changed in this chat since their last message, in a few plain sentences and small visuals. Give each action item just enough context to make the call. Use for /ketchup.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexPeriodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexImplement 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexNeoHaskell code style guidelines for writing and reviewing .hs code in this repository.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexKeep established Haskell language-extension defaults consistent across Cabal components and their tools. Use before adding, removing, or reviewing LANGUAGE pragmas, Cabal extensions, or compiler/linter extension mismatches.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexDelegate to a comment reviewer, fix accepted findings, and offer encodings for claimed constraints.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that assumes it.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply when designing, implementing or reviewing NeoHaskell framework data structures, service flows, concurrency, storage, codecs or generated APIs. Design toward a hypothetical 50,000 requests per second with explicit cost and workload assumptions; distinguish design reasoning from measured performance.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexChoose NeoHaskell module, type, and operation names that a junior TypeScript developer can understand without knowing GHC implementation terms.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply 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.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexApply when designing or reviewing Haskell types and signatures in NeoHaskell internals. Use algebraic data types, semantic newtypes, boundary parsing, exhaustive pattern matching, existing derivation, and total functions to express useful guarantees.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexCapture repeatable failing and passing evidence for NeoHaskell runtime regressions or compiler acceptance and expected rejection, with distinct checks for assertion failures and diagnostics.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexAutonomously combine NeoHaskell's ordinary generated release preparations, repair failing CI, merge the verified candidate, and verify one published release when explicitly asked to run a release sweep.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexSelect provider-aware models for workflow roles, or update the repository's central role-to-model-and-effort mapping.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexKeep authored or revised skill guidance durable with self-contained examples, owned operational dependencies, and separate run evidence. Apply to skill packages and their routing instructions.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodexUse only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target.
neohaskell/NeoHaskell
Stars: 348Claude CodeCodex