Architecture decision record explaining why the collection ships as a Claude Code plugin and why no Codex plugin exists yet. Useful context for anyone packaging their own skills for more than one harness.

Architecture decision record: a skill may point at a setup step only when it is a hard dependency, not as general advice. Documents the reasoning and the consequences for how skills reference each other.

The canonical install instructions, copied verbatim wherever installation is documented so the steps never drift between README and docs. Covers the Claude Code plugin route and the marketplace fallback.

Template and procedure for the human-facing docs page every promoted skill carries. Fixes the four required sections — what it does, when to reach for it, common questions, it's working if — plus section order and where to source the questions.

Defines the two invocation modes every SKILL.md must declare: user-invoked, reachable only by a human via slash command, or model-invoked, which the agent may trigger on its own. Explains the frontmatter and the openai.yaml policy flags that enforce each.

The router skill: maps every user-reachable skill and how they relate, so an agent can pick the right one instead of guessing. Kept in sync whenever a skill is added, renamed or removed, on the principle that a router which lies is worse than none.

Shared domain vocabulary for the repository. Defines Issue tracker, Issue, Decision ticket and Triage role, lists the terms to avoid, maps how the entities relate and records resolved ambiguities, so agent and human use one language instead of drifting synonyms.

The repository contract, auto-loaded by Claude Code and reachable as AGENTS.md through a symlink so Codex-style agents read the same file. Defines the five skill buckets, the promotion rules that keep README, plugin manifest and docs in sync, and the invocation model.

Index of the productivity bucket: seven skills for non-code workflow, each linked to its SKILL.md. Covers grill-me, grilling, handoff, teach, to-questionnaire, wait-what and writing-for-agents.

Index of the engineering bucket: eighteen skills for daily code work, each with a one-line description linked to its SKILL.md. Includes tdd, code-review, diagnosing-bugs, codebase-design, domain-modeling, implement, research, triage and wayfinder.

Full release history of the skills collection, maintained with changesets. Records every skill added, renamed, promoted between buckets or deprecated, which is the fastest way to see how the set has evolved and what is currently moving.

Front door of the pack: what these skills are, how to install them into Claude Code or another harness, and a linked index of all promoted skills split into user-invoked and model-invoked. Start here to see what the collection actually contains.

Bootstrap file for AI agents only; human readers are redirected to README.md. Contains the execute-immediately first instruction, the platform deployment routing table, an example report format, dependency tables, and quick-start paths for wiring any code CLI into the router.

Root-level Kali Linux shortcut entry. Defers to kali/README-kali.md as the source of truth; gives an AI read-then-execute path and a 30-second human quick start, and explains this file's relationship to the main package.

Chinese-language project overview and the most detailed human documentation in the repo. Mirrors README.md (about, quick start, installation, usage, supported scenarios, key files, repository layout) with fuller explanations. Primary reference for Chinese-speaking users.

Human-facing project overview and quick start for reverse-skill, a cybersecurity skills router. Covers About, Built With, Getting Started (prerequisites, installation), Usage with supported scenarios, key files, repository layout and license. The entry point for human contributors.

Chinese edition of the routing matrix (by target type, by user intent, route-not-matched handling, cross-module path crossing). Same enforced protocol: complete routing before acting, output the routing rationale, and pass case-init/scope.md before ACT on a target.

Full task-to-skill routing matrix. Routes by target type, user intent and toolchain; includes CTF wording normalization, ambiguous-intent recovery, route-not-matched handling and cross-module path crossing. Enforced, not advisory: routing must complete before execution.

PRIMARY fast-path routing ladder, kept in sync with scripts/master-route.ps1. Defines the route-before-acting execution contract, the priority order, the scope gate before ACT, evidence append and the reading order. The first file an agent consults.

Master controller and entry point for the skills tree. YAML frontmatter declares the routing scope; the body defines the routing execution contract, RFC-2119 instruction levels, the unified entry, the next-step menu pattern, the precedent library and auto-evolution.

Chinese edition of RULES.md: the same authorization gates and canonical behavior chain (trigger keywords, routing entry, execution principles, security boundaries, completion checklist). The largest file in the navigation set; it drives routing for Chinese-language prompts.

The single source of truth for the behavior chain and authorization gates. Defines the execute-immediately mandate, global config injection on first use, bilingual trigger keywords, the routing entry, execution principles, the canonical behavior chain and a completion checklist.

Root-level file that Claude Code auto-loads. Declares the repository a task skill router for authorized reverse engineering and security work, names RULES.md as the single source of truth, and fixes the routing order, with per-OS first-run setup and a coherence check.

Guide for adding a new skill module to the pack. Defines the standard flow: compliance-engineering constraints, when to add a skill, the directory-structure template, and the mandatory SKILL.md contents including the strong-execution skeleton that forces agents to act rather than merely acknowledge.

Keep a Changelog / SemVer changelog. Documents the 1.0.0 release (2026-07-18): the ops/combat-contract layer, PRIMARY routing and case tooling, core skills and localization, plus an Unreleased section with Fixed, Security, Added and Removed changes.

Navigation across the markdown files of zhaoxuya520/reverse-skill with measured metrics: 402 .md files, 83 SKILL.md, all in git mode 100644. Documentation is split by audience — 46 KB for humans, 157 KB for agents. Covers the routing chain and three license zones (MIT / GPL-3.0 / third-party MIT).

You are a test automation expert specializing in generating comprehensive, maintainable unit tests across multiple languages and frameworks. Create tests that maximize coverage, catch edge cases, and follow best practices for assertion quality and test organization. Use it to give an agent explicit responsibilities, steps and constraints.

CSS Styling Approaches Reference captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

Compound components share implicit state while allowing flexible composition. Use it to give an agent explicit responsibilities, steps and constraints.

Accessibility Patterns Reference captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

Build reusable, maintainable UI components using modern frameworks with clean composition patterns and styling approaches. Use it to give an agent explicit responsibilities, steps and constraints.

A modular scale creates harmonious relationships between font sizes using a mathematical ratio. Use it to give an agent explicit responsibilities, steps and constraints.

The 8-point grid is the industry standard for consistent spacing. Use it to give an agent explicit responsibilities, steps and constraints.

Color Systems Reference captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

Build cohesive, accessible visual systems using typography, color, spacing, and iconography fundamentals. Use it to give an agent explicit responsibilities, steps and constraints.

Fluid design creates smooth scaling experiences by using relative units and mathematical functions instead of fixed breakpoints. This approach reduces the need for media queries and creates more natural-feeling interfaces. Use it to give an agent explicit responsibilities, steps and constraints.

responsive-design — detailed patterns and worked examples captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

Container queries enable component-based responsive design by allowing elements to respond to their container's size rather than the viewport. This paradigm shift makes truly reusable components possible. Use it to give an agent explicit responsibilities, steps and constraints.

Effective breakpoint strategies focus on content needs rather than device sizes. Modern responsive design uses fewer, content-driven breakpoints combined with fluid techniques. Use it to give an agent explicit responsibilities, steps and constraints.

React Navigation Patterns captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

iOS Navigation Patterns captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

iOS Human Interface Guidelines Patterns captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

Material Design 3 Theming captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

Android Navigation Patterns captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

Microinteraction Patterns Reference captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

Create engaging, intuitive interactions through motion, feedback, and thoughtful state transitions that enhance usability and delight users. Use it to give an agent explicit responsibilities, steps and constraints.

A robust theming system enables applications to support multiple visual appearances (light/dark modes, brand themes) while maintaining consistency and developer experience. Use it to give an agent explicit responsibilities, steps and constraints.

Design tokens are the atomic values of a design system - the smallest pieces that define visual style. They bridge the gap between design and development by providing a single source of truth for colors, typography, spacing, and other design decisions. Use it to give an agent explicit responsibilities, steps and constraints.

Well-architected components are reusable, composable, and maintainable. This guide covers patterns for building flexible component APIs that scale across design systems. Use it to give an agent explicit responsibilities, steps and constraints.

The Web Content Accessibility Guidelines (WCAG) 2.2 provide recommendations for making web content more accessible. They are organized into four principles (POUR): Perceivable, Operable, Understandable, and Robust. Use it to give an agent explicit responsibilities, steps and constraints.

Mobile accessibility ensures apps work for users with disabilities on iOS and Android devices. This includes support for screen readers (VoiceOver, TalkBack), motor impairments, and various visual disabilities. Use it to give an agent explicit responsibilities, steps and constraints.

accessibility-compliance — detailed patterns and worked examples captures reusable agent playbook guidance for accessibility & mobile ux. Use it to give an agent explicit responsibilities, steps and constraints.

ARIA (Accessible Rich Internet Applications) provides attributes to enhance accessibility when native HTML semantics are insufficient. The first rule of ARIA is: don't use ARIA if native HTML can do the job. Use it to give an agent explicit responsibilities, steps and constraints.

Initialize a design system with design tokens, component patterns, and documentation. Creates a foundation for consistent UI development. Use it to give an agent explicit responsibilities, steps and constraints.

Review existing UI code for design issues, usability problems, and improvement opportunities. Provides actionable recommendations. Use it to give an agent explicit responsibilities, steps and constraints.

Guided workflow for creating new UI components following established patterns and best practices. Use it to give an agent explicit responsibilities, steps and constraints.

You are an expert design system architect specializing in building scalable, maintainable design systems that bridge design and development. Use it to give an agent explicit responsibilities, steps and constraints.

You are an expert accessibility specialist dedicated to creating inclusive digital experiences that work for all users regardless of ability. Use it to give an agent explicit responsibilities, steps and constraints.

A curated reference on api, backend & databases centered on GitHub Issue Resolution Expert. Use it to give an agent explicit responsibilities, steps and constraints.

You MUST follow these rules exactly. Violating any of them is a failure. Use it to give an agent explicit responsibilities, steps and constraints.

You are an expert TDD orchestrator specializing in comprehensive test-driven development coordination, modern TDD practices, and multi-agent workflow management. Use it to give an agent explicit responsibilities, steps and constraints.

rust-async-patterns — detailed patterns and worked examples captures reusable agent playbook guidance for linux, networking & embedded. Use it to give an agent explicit responsibilities, steps and constraints.

memory-safety-patterns — detailed patterns and worked examples captures reusable agent playbook guidance for linux, networking & embedded. Use it to give an agent explicit responsibilities, steps and constraints.

go-concurrency-patterns — detailed patterns and worked examples captures reusable agent playbook guidance for linux, networking & embedded. Use it to give an agent explicit responsibilities, steps and constraints.

You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing setup, and configuration following Rust best practices. Use it to give an agent explicit responsibilities, steps and constraints.

Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A. Use it to give an agent explicit responsibilities, steps and constraints.

Comprehensive guide to tracking, calculating, and optimizing key performance metrics for different startup business models from seed through Series A. Use it to give an agent explicit responsibilities, steps and constraints.

Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups. Use it to give an agent explicit responsibilities, steps and constraints.

Start with total market size and narrow to addressable segments. Use it to give an agent explicit responsibilities, steps and constraints.

Curated list of credible sources for market research and sizing analysis. Use it to give an agent explicit responsibilities, steps and constraints.

Complete TAM/SAM/SOM calculation for a B2B SaaS startup using bottom-up and top-down methodologies. Use it to give an agent explicit responsibilities, steps and constraints.

Comprehensive frameworks for analyzing competition, identifying differentiation opportunities, and developing winning market positioning strategies. Use it to give an agent explicit responsibilities, steps and constraints.

Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) calculations using both bottom-up and top-down methodologies. Use it to give an agent explicit responsibilities, steps and constraints.

Create a comprehensive 3-5 year financial model with revenue projections, cost structure, headcount planning, cash flow analysis, and three-scenario modeling (conservative, base, optimistic) for startup financial planning and fundraising. Use it to give an agent explicit responsibilities, steps and constraints.

Generate a comprehensive, investor-ready business case document covering market opportunity, solution, competitive landscape, financial projections, team, risks, and funding ask for startup fundraising and strategic planning. Use it to give an agent explicit responsibilities, steps and constraints.

You are an expert startup business analyst specializing in helping early-stage companies (pre-seed through Series A) with market sizing, financial modeling, competitive strategy, and business planning. Use it to give an agent explicit responsibilities, steps and constraints.

Cookbook-style walkthrough for cryptographically signed receipts on every Claude Code tool call. This is the teaching skill. For the runtime implementation, install the protect-mcp plugin. Use it to give an agent explicit responsibilities, steps and constraints.

You are a technical analyst. Your job is to scan the project codebase and produce accurate, project-specific documentation used by all downstream agents. Use it to give an agent explicit responsibilities, steps and constraints.

You are a Senior Code Reviewer with 30 years of experience in software quality, security analysis, and architectural compliance. You are objective, constructive, and precise. You explain the why behind every finding. Use it to give an agent explicit responsibilities, steps and constraints.

You are a Senior QA Engineer with 15 years of experience in software testing and quality assurance. You are systematic, evidence-driven, and thorough. You test against requirements — you do not modify production code. Use it to give an agent explicit responsibilities, steps and constraints.