iamakbarsha1

iamakbarsha1/whetstone

Plugin Claude Code

Agent skills honed on real work.

iamakbarsha1/whetstone

Plugin Claude Code

Agent skills honed on real work — short, self-contained rule sets distilled from concrete engineering failures, so an agent (or human) can apply the lesson without the original context.

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when you're relying on a stored memory, a recalled note, an injected session-start banner, or a description-matched skill to make a required action happen every session or run — especially a recurring logging, bookkeeping, or guardrail step. Passive context is advisory: the agent reads it and can still skip the…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use as the FIRST step of any implementation task handed to you from a checklist, ticket, milestone, or spec — the first step is an existence check, not a design. Trackers record conversations, not deliverables, so grep for the item's key nouns and cross-check spec status before writing code, then pivot "build X" to…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use during design or brainstorming when a user's choice depends on a technical property they assert or imply — state the ground truth of that property before asking downstream questions built on it. Triggers on "should we use X or Y", design trade-off discussions, privacy/data-egress decisions, and any choice that…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use before writing new code in an existing module — match the nearest sibling's pattern first; a repo-wide convention is the default only when the local module has no established pattern of its own. A uniform module beats a globally-conformant outlier. Triggers on "follow the conventions", "match the style", "how do…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when resolving a merge or rebase conflict, or reviewing a merge commit — conflict markers show where git gave up, not the full semantic delta, and 3-way auto-merge silently drops fields outside the markers. Compare ours/theirs/base by symbol and field inventory before trusting the result. Triggers on "merge…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when you just hit a real failure worth keeping — a bug, a wrong fix, a wasted hour — and want to turn it into a reusable skill instead of a private lesson. Turns one concrete failure into a Whetstone-shaped SKILL.md: extract the transferable invariant, write it so an agent can apply it without the original…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when re-engaged to "act on" or "fix the rest of" a review, audit, or recommendation list — the list is not a to-do list. Re-read each item's own disposition first and bucket them; some are explicitly marked no-fix, some need a human decision, some are scale-gated. Triggers on "fix the findings", "address the…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when changing a shared contract — a flag, column, enum/union member, shared type, exported symbol, endpoint shape, or config key. The retired name is the cheapest complete index of consumers: grep the whole workspace and run every suite that crosses the boundary, not just the package you edited. Triggers on…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when writing or refactoring logic that reads ambient state — the clock (now/today), randomness, environment variables, a DB/HTTP handle, the filesystem, the current user. Ambient reads are the main reason otherwise pure logic becomes un-unit-testable; pass them in as parameters and split the pure decision from the…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use before trusting a named aggregate command — a test, lint, type-check, or build script that wraps a tool. Open it and confirm what it actually runs, how it forwards args, and whether it caches, because a green only means what the command covered. Triggers on "npm run test", "type-check passes", "lint is clean"…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when reviewing your own work, or when the author-equals-reviewer guard is deliberately overridden — real independence is gone, so manufacture it: parallel independently-scoped sub-reviews plus an adversarial re-read of source for every high-severity claim, and treat cross-reviewer disagreement as a pointer to the…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when judging whether your change is clean against a red or noisy baseline — failing tests you didn't touch, pre-existing lint/typecheck errors, flaky CI. Innocence is a claim about a delta, so prove it by stash-and-compare or head-vs-base under an identical harness, never by reading which files appear in the…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when a system has a load-bearing "never" constraint — never holds funds, never logs secrets, never calls a forbidden API, never writes to a table, never blocks the event loop. Behavioural tests can't observe a capability that isn't exercised yet, so write a STRUCTURAL test that trips on the mere existence of the…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when reviewing an implementation plan, spec, or task breakdown before handing it to an implementer — catches the class of bug where one intent is encoded twice and the two encodings silently disagree. Triggers on "review this plan", "check this spec", "self-review the plan", "before I implement", "fixture values"…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use after writing a test, or before trusting one that passed — a test that has never failed is unverified. Do one sabotage run (break the thing under test, confirm the right assertion fails) and confirm each new branch is actually reachable by the mocks/fixtures. Triggers on "test passes", "added a test", "green on…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when preparing a repository for public release, or auditing one that already has working code but still reads as neglected to a stranger or to GitHub's own UI — "has the files" is not "reads as maintained". Triggers on "publish a repo", "open source this", "release", "make it look maintained", "license shows…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when hardening against a failure mode or fixing an intermittent/partial failure — instrument the real failing invocation before and after, because a plausible hypothesis is not a diagnosis. Triggers on "why is this failing", "flaky", "intermittent failures", "high failure rate", "harden this", "add retries", "it…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use before launching any long-running, backgrounded, detached, or nohup'd process (backfills, batch migrations, bulk data processing, multi-hour scrapes, crawls), and again when verifying it finished correctly. Also use when reconciling a batch job against a corpus (files, DB rows, records) that other processes …

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when a task's output is sensitive or large data and the destination is a path inside a version-controlled tree — writing the data is not the finish line, an unreviewed commit of it is the failure mode. Triggers on "export the data", "dump the DB", "extract observations", "write it to the repo", "save the logs"…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when reviewing or signing off on a file an agent produced with a write tool — a doc, README, config, data file, or any non-code output. Passing tests prove nothing about stray harness framing: a leaked closing tag, an XML/markdown-fence fragment, or content past the intended EOF compiles and tests clean, then…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when writing tests against a shared store or with fabricated fixtures — a test only proves something if its fixtures mirror data reality and its assertions can't pass trivially. Covers asserting on rows you created (not aggregate counts), real referential integrity, seeded randomness and pinned time, fail-closed…

iamakbarsha1/whetstone

Skill Claude CodeCodex

Use when a user specifies a platform, tool, library, or approach as part of a request — their choice is a proposed MECHANISM, not a spec. Grep the built artifact for disqualifying signals before agreeing, separate their intent from the mechanism, and satisfy the intent with a feasible mechanism when the chosen one…