Menu
SkillsMP has collected 18 skills from axross/ptcgp.axross.dev. Open a skill to review its source and details.
Showing 18 of 18 collected skills.
Drive one unit of work — a GitHub issue, a pull request, or a free-form prompt — from intake to a review-ready pull request in one continuing session; plan and pause for human approval, implement and verify, request the independent review, and address its…
The authoring discipline for agent skills under the host project's skill root (e.g., `.claude/skills/`) — agentskills.io format, frontmatter management and invocation-control fields, kebab-case naming, description and when_to_use writing for discovery,…
The security and privacy review lens for code changes. Covers secrets/env vars, the framework's public/client-exposed env-var prefix, input validation, public exposure, output-encoding/injection in rendered content, SSRF/outbound fetching, error-reporting…
The review methodology for every review task, including post-implementation self-review. Covers reviewer-mode reset, diff scoping with `git status`/`git diff`, severity labels, file-line evidence, fix snippets, verification evidence, second-pass re-review…
How to build React components in this project. Covers component anatomy and naming, CSS Modules pairing, Base UI headless primitives, server/client boundary decisions, test-id hooks, accessibility mechanics, and when a repeated pattern earns a shared…
Conventions for MDX content pages on this Pokémon TCG Pocket documentation site. Covers page placement and metadata exports, heading structure, tables and examples, internal/external linking, tone, game terminology, and the unofficial-fan-content boundary.
The project's baseline working rules. Covers the format/lint loop, scoped change management, current-docs lookup triggers, run-script commands, type-safety discipline, source-comment and doc-comment conventions, verification requirements, MDX content-layer…
Conventions for Playwright end-to-end tests in this project. Covers the test directory layout and file naming, structured test/step naming, stable test-id chained/scoped locators with a role-then-copy fallback hierarchy (text matching only when asserting the…
How an agent reads and writes GitHub (issues, pull requests, comments, labels, reviews, branches) through a proxy-mediated single-operator identity, as a Claude Code + GitHub MCP harness does. Covers routing everything through the one sanctioned tool channel,…
Suspend this session's in-progress work into a self-contained, downloadable handoff package — a handoff-<unix epoch>.md document plus an optional same-epoch .zip of patches and artifacts — that a fresh-context agent session takes over with /address continue.
The reviewer's maintainability lens on changed code, on top of the project's development, structure, and any project-defined component/routing rules. Covers naming and file organization, route-local vs shared abstraction boundaries, complexity/readability…
Error-handling and reporting conventions for this project. Covers `try`/`catch` placement, Sentry capture calls, top-level error boundaries, and error-message quality.
The reviewer's lens on runtime cost and failure-mode behavior. Covers server/client boundary cost and async waterfalls, deferred/streamed loading splits, caching correctness (lifetime, scope, invalidation), asset/image optimization, client bundle and…
How to write a product requirement, feature spec, or issue description. Covers framing the problem/outcome before the solution, separating "what" from "how", explicit non-goals and assumptions, right-sizing scope to the change, testable acceptance criteria,…
The repository's structure and conventions. Covers the Next.js App Router layout, the src/ by-purpose organization, MDX content placement, colocation rules for tests and styles, and path aliases.
The reviewer's QA lens on verification evidence, on top of development verification and e2e testing rules. Covers format/lint proof, e2e coverage for new routes/features/surfaces, required test-id hooks, intentional snapshot updates, flaky-test investigation,…
The design vocabulary for how a surface of this site should look — color roles and the CSS-variable palette, light/dark theming, typography and the prose column, control selection, spacing, responsive behavior, copy tone in the chrome, and accessibility…
Conventions for Vitest unit tests in this project. Covers test framework configuration, explicit test-API imports, colocated test files, describe/case naming and grouping conventions, behavior-focused test design, fixture quality, AHA test abstraction, mocks…