个人作者

nes

更新于 2026-09-28

Skills
52
仓库
1
职业覆盖
0
场景覆盖
0
Stars
★ 1

nes 的 Skills 52

nahuelb
nahuelb/pstack-codex

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 1
nahuelb
nahuelb/pstack-codex

unslop

Cut AI tells from any writing. Must always apply.

★ 1
nahuelb
nahuelb/pstack-codex

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 1
nahuelb
nahuelb/pstack-codex

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 1
nahuelb
nahuelb/pstack-codex

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 1
nahuelb
nahuelb/pstack-codex

tdd

Use 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. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

★ 1
nahuelb
nahuelb/pstack-codex

swarm

Fan out N parallel workers, drain them, and return one report. Use for $swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.

★ 1
nahuelb
nahuelb/pstack-codex

show-me-your-work

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for $show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.

★ 1
nahuelb
nahuelb/pstack-codex

setup-pstack

Install, update, remove, or inspect pstack's Codex agent profiles and per-role model registry. Use for setup-pstack or requests to configure pstack agents and models.

★ 1
nahuelb
nahuelb/pstack-codex

setup-benny

Install, inspect, upgrade, or remove the dormant Benny polling pack for Codex. Use when configuring Benny's Slack, tracker, repository, control adapter, canonical state, canaries, or two paused automations.

★ 1
nahuelb
nahuelb/pstack-codex

reflect

Spawn three parallel review subagents over supported active-task history or a digest, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.

★ 1
nahuelb
nahuelb/pstack-codex

recall

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.

★ 1
nahuelb
nahuelb/pstack-codex

principle-type-system-discipline

Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.

★ 1
nahuelb
nahuelb/pstack-codex

principle-test-behavior-not-implementation

Apply when writing or reviewing tests. Verify observable outcomes and identify assertions that cannot detect a relevant defect.

★ 1
nahuelb
nahuelb/pstack-codex

principle-subtract-before-you-add

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

★ 1
nahuelb
nahuelb/pstack-codex

principle-sequence-verifiable-units

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.

★ 1
nahuelb
nahuelb/pstack-codex

principle-separate-shared-state

Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.

★ 1
nahuelb
nahuelb/pstack-codex

principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.

★ 1