Skill Claude CodeCodex
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what…
Skill Claude CodeCodex
Systematic performance optimization for OpenClaw AI agents. Covers session management, context budget optimization, token tracking, and automated maintenance. Use when optimizing OpenClaw agent performance or conducting routine maintenance.
Skill Claude CodeCodex
Interactive architecture design workflow — from requirements gathering to pattern recommendation, tech stack selection, and ADR generation. Use when designing system architecture, choosing between monolith vs microservices, planning scalability, selecting databases or caches, reviewing architecture documents, or…
Skill Claude CodeCodex
A behavior-driven development method that describes expected software behavior in plain language using Given, When, and Then. BDD focuses on whether a feature matches the requirement, while test-driven development, or TDD, focuses on preventing code defects with tests.
Skill Claude CodeCodex
A Chinese-language brainstorming and design-questioning workflow that turns an unclear idea into a detailed plan saved in `.scratch/<feature>/RAD.md`. It first checks whether the project has completed its required setup.
Skill Claude CodeCodex
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Skill Claude CodeCodex
A documentation workflow that creates or updates project reference files from the actual code. It can maintain an architecture overview, API reference, change log, and documentation for larger modules.
Skill Claude CodeCodex
A task-runner skill for projects that track work in Markdown issue files. It finds unfinished issues, follows their dependencies, carries out their acceptance criteria, and records completion.
Skill Claude CodeCodex
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Skill Claude CodeCodex
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Skill Claude Code
A file-based planning method that stores an agent's task plan, findings, progress, and decisions in Markdown files. It treats the conversation as temporary working memory and the files as persistent notes.
Skill Claude CodeCodex
PostgreSQL best practices, query optimization, connection troubleshooting, and performance improvement. Load when working with Postgres databases.
Skill Claude CodeCodex
Build a throwaway prototype to flush out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine…
Skill Claude Code
A mode that changes how an agent responds when the user is frustrated, reports repeated failures, or asks it to try harder. It pushes the agent to examine missing cases, broaden the investigation, and complete the work with verified results.
Skill Claude CodeCodex
A local code-review process for examining Git changes. It checks project rules, likely bugs, code quality, and security risks, then reports only issues judged highly likely to be real.
Skill Claude CodeCodex
A code-quality review guide based on software engineering books and language standards. It checks a project against selected rules and produces a structured report with rule references.
Skill Claude CodeCodex
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
Skill Claude CodeCodex
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
Skill Claude CodeCodex
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.
Skill Claude CodeCodex
Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.
Skill Claude CodeCodex
Sets up an ## Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of pd-to-issues, pd-to-prd, pd-triage, pd-diagnose, pd-tdd…
Skill Claude CodeCodex
Simplifies and refines recently modified code for clarity, consistency, and maintainability while preserving exact functionality. Use when code has just been written or modified, when user asks to clean up, refine, or simplify code, or when reviewing for code quality issues.
Skill Claude CodeCodex
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Skill Claude CodeCodex
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
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: