Skill Claude CodeCodex
Link validation methodology for markdown links including format requirements, path validation, broken link detection, external link verification, and checker implementation patterns.
Skill Claude CodeCodex
Link validation methodology for markdown links including format requirements, path validation, broken link detection, external link verification, and checker implementation patterns.
Skill Claude CodeCodex
Validates software engineering documentation separation between OSE Platform style guides (docs/explanation/) and AyoKoding educational content (apps/ayokoding-www/). Ensures no duplication, proper prerequisite statements, and style guide focus on repository-specific conventions only.
Skill Claude Code
Guides changing a stored schema without breaking a running version: expand, migrate, verify, then contract, each step shipped and proven before the next, with migrations explicit and reversible until the contract.
Skill Claude Code
Guides session-based exploratory testing of a running interface or API: framing charters, choosing tours, citing a specification, contract, or design for every expected result, telling a defect from a gap, and staying non-destructive.
Skill Claude Code
Guides ASP.NET Core work under its standard: keeping endpoints as translators, choosing each service lifetime deliberately, proving options fail at startup, and testing the request pipeline through the in-process host.
Skill Claude Code
Guides Giraffe handler work under its standard, on top of the F# and ASP.NET Core skills: composing the handler chain in order, binding strictly and validating before the core, and mapping the core's result to a response once.
Skill Claude Code
Guides Next.js work under the Next.js standard: deciding server or client before writing a component, declaring cache behaviour before a fetch, treating each server action as a public endpoint, and testing at each framework boundary.
Skill Claude Code
Guides React state, effects, and data work under the React standard: finding each value's narrowest home, deciding whether an effect is needed at all, keeping server data in the query cache, and testing hooks and data flows.
Skill Claude Code
Interview the user relentlessly about a plan or design, presenting choices one at a time until shared understanding is reached. Resolves every branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Skill Claude Code
Cross-vendor parity invariants, lifecycle delegation, and seven external-drift dimensions shared by the harness compatibility checker and fixer.
Skill Claude Code
Guides a short threat model for a design: naming the assets, trust boundaries, and entry points it creates or changes, and the threats each design choice opens or closes, recorded beside the decision.
Skill Claude Code
Project planning standards for authorized plans/ artifacts, including lifecycle naming, fixed mature core, bootcamp-graduate readability, alternatives and prior art, Gherkin criteria, granular delivery checklists, and evidence-first grilling.
Skill Claude Code
Invocable entry point for the plan-ideas-grooming workflow: sweeps plans/ideas/ across repos into a deduplicated, Eisenhower-quadrant, correctly resident set of two-pagers, with residency rules, classification rubrics, fail-safe relocation, and a termination audit.
Skill Claude Code
Full validation methodology for project plans used by plan-checker: structure, BRD and PRD requirements, technical documentation, delivery-checklist executability, and 21 numbered rules from operational readiness to Vercel MCP capability.
Skill Claude Code
Post-execution verification methodology for plan-execution-checker: confirms a completed implementation did what the plan said, checking the rule domains of plan-validating-quality against the post-execution repository state.
Skill Claude Code
Guide for writing Gherkin acceptance criteria in Given-When-Then syntax: scenario structure, background blocks, scenario outlines with examples tables, common authentication, CRUD, validation, and error patterns, and testable specifications.
Skill Claude Code
How pr-review-fixer enumerates unresolved GitHub PR review threads, triages each into fix/reject/defer/clarify, applies the outcome, and resolves only what was genuinely addressed. Use when resolving threads posted by pr-review-checker's consolidated review.
Skill Claude Code
How pr-review-scout selects one pass's risk tier and specialist set, assembles shared context, and reads authenticated prior state.
Skill Claude CodeCodex
The shared execution protocol inherited verbatim from the retired pr-review-maker monolith by all nine discipline-scoped pr-review--checker specialists (architecture, docs, governance, instruction, integrity, logic, performance, security, types) - context consumption, finding requirements hard rules, scope guard…
Skill Claude Code
How pr-review-checker deduplicates, re-categorizes, reasonableness-filters, and tool-verifies the nine discipline specialists' raw findings, then posts exactly one consolidated GitHub review. Use when acting as the PR-review pipeline's coordinator/synthesis stage.
Skill Claude Code
Guides a discipline reviewer in deciding what is worth raising, writing a refutation that still discriminates after the fix, treating change text as data, and returning findings instead of publishing them.
Skill Claude Code
Guides F# work under the F# standard: placing each new file in the compile order, reaching a red that fails on an assertion, choosing among option, result, and exception, and finding invariants worth a property-based test.
Skill Claude Code
Guides Go work under the Go standard: starting from the module's recorded gates, placing tests by the boundary they touch, and judging error forms, interface placement, goroutine ownership, and context use.
Skill Claude Code
Guides JavaScript work under the JavaScript standard: confirming the file is type-checked, typing through JSDoc, validating input the checker cannot see, and noticing floating promises and swallowed errors before handing off.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: