Skip to main content
Manus에서 모든 스킬 실행
원클릭으로
neohaskell
GitHub 제작자 프로필

neohaskell

2개 GitHub 저장소에서 수집된 10개 skills를 저장소 단위로 보여줍니다.

수집된 skills
10
저장소
2
업데이트
2026-07-09
저장소 탐색

저장소와 대표 skills

neohaskell-pipeline
소프트웨어 개발자

Orchestrate a NeoHaskell change end-to-end through the spec-gated pipeline - intake to merged PR with exactly two human gates. Use when implementing a feature, fixing a bug, or running any request that should produce a PR.

2026-07-09
neohaskell-security-design-review
정보 보안 분석가

Design-time security review of an approved contract-delta spec, before implementation. Runs when the spec's touches list intersects security-sensitive capabilities. Produces a LOCAL-only review record (gitignored, never pushed — a security review maps attack surface); enforced on the dev machine, not in CI.

2026-07-09
neohaskell-retrospective-miner
기타 컴퓨터 관련 직업

Weekly retrospective mining of pipeline telemetry into ≤5 validated asset-delta recommendations. Use at the weekly telemetry review, once real runs have accumulated in telemetry/runs.jsonl. Reads the deterministic digest, proposes recommendations under a closed contract, and records the ones that pass.

2026-07-08
neohaskell-performance-design-review
소프트웨어 개발자

Design-time performance review of an approved contract-delta spec, before implementation. Runs when the spec's touches list intersects perf-sensitive capabilities. Produces the committed review record; measurement lives in the nightly bench harness, not here.

2026-07-08
neohaskell-implementer
소프트웨어 개발자

Write NeoHaskell (not vanilla Haskell) code in this repo — copy-adapt discipline, the fast repair loop, and the dialect escape hatch. Use when implementing or modifying any .hs file.

2026-07-08
neohaskell-localizer
소프트웨어 개발자

Route a request to exact code locations using the codemap — capability lookup, extension points for new code, signature grep, edit-set expansion. Use at PLAN time, before any implementation; execution must never search.

2026-07-08
neohaskell-dialect-rules
소프트웨어 개발자

Add, modify, or debug NeoHaskell dialect enforcement rules (hlint law + edit-hook teacher). Use when a new dialect rule is needed, a rule misfires, or an exception should be registered or promoted.

2026-07-07
critique-ide-screen
웹·디지털 인터페이스 디자이너

Use when asked to visually critique, screenshot, or review the UX/look of the neo IDE (the Vite/React event-modeling frontend at `assets/ide/`) in the NeoCLI repo at `/Users/nick/repos/neo` — phrases like "critique the IDE screen", "screenshot the IDE", "how does the main canvas look", "review the IDE UX", "/critique-ux on the neo ide". Captures the REAL rendered app (a seeded, populated event model — never an empty canvas) via the Playwright+Brave harness, then judges it. A visual critique without a fresh screenshot is invalid — reasoning from source code alone misses collisions, framing, contrast, and density problems that only appear on screen. Skips when the change is purely backend/Rust with no frontend surface, or when the user supplies their own screenshot to critique.

2026-06-26
error-messages-instruct-llms
소프트웨어 개발자

Use when about to write or modify any user-facing error in the NeoCLI repo at `/Users/nick/repos/neo` — a `NeoError` variant, a `miette::miette!`/`bail!` call, a subprocess-wrap result, a `format!` into stderr, a `panic!` reachable from user input, an `expect(...)` on a `Result` returned to the user, or wrapping an error with `?`. Also use when reviewing an existing error path that surfaced as opaque (e.g. `Subprocess execution failed: cabal build all` with no actionable detail). Enforces the hard invariant that every user-facing error must be parsable by the dumbest small LLM (gemini-flash-2.5, haiku, gpt-3.5-nano level) and tell it exactly how to fix the underlying issue without re-reading any documentation. Skips when the error is purely internal/debug — `tracing::debug!`, `#[derive(Debug)]` on private types — that an end user will never see.

2026-06-11
running-neo-tests
소프트웨어 품질 보증 분석가·테스터

Use when about to run any test layer for the NeoCLI repo at `/Users/nick/repos/neo` — phrases like "run the tests", "cargo test", "run integration tests", "run e2e", "verify cargo test passes", or before declaring a code change done. Wraps the right command for the layer being targeted (unit, integration, e2e, smoke), always inside `nix develop --command` because the toolchain is flake-pinned, and respects the strict-assertion contract (integration assertions assume `nix`+`git`+network are present — fix the env, never weaken the assertion). Skips when the user has explicitly entered `nix develop` already or when the target is the published binary in `result/bin/neo`.

2026-06-10
저장소 2개 중 2개 표시
모든 저장소를 표시했습니다