Skill Claude CodeCodex
Use when writing code, documentation, or comments - always use accessible and respectful terminology.
Skill Claude CodeCodex
Use when writing code, documentation, or comments - always use accessible and respectful terminology.
Skill Claude CodeCodex
Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones.
Skill Claude CodeCodex
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code.
Skill Claude CodeCodex
IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be added only for legacy support as a second-class citizen.
Skill Claude CodeCodex
Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units.
Skill Claude CodeCodex
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification.
Skill Claude CodeCodex
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end.
Skill Claude CodeCodex
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning.
Skill Claude CodeCodex
Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks.
Skill Claude CodeCodex
Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcpmemory knowledge graph for persistent facts.
Skill Claude CodeCodex
Use for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issues and epics, monitors progress toward milestone completion.
Skill Claude CodeCodex
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission.
Skill Claude CodeCodex
Source royalty-free images and videos from Pexels API for design, placeholders, or content. Supports search, curated/popular content, collections, multiple resolutions, and ALWAYS creates detailed sidecar metadata files.
Skill Claude CodeCodex
MANDATORY when working with geographic data, spatial queries, geometry operations, or location-based features - enforces PostGIS 3.6.1 best practices including STCoverageClean, SFCGAL 3D functions, and bigint topology.
Skill Claude CodeCodex
MANDATORY when touching auth tables, tenant isolation, RLS policies, or multi-tenant database code - enforces Row Level Security best practices and catches common bypass vulnerabilities.
Skill Claude CodeCodex
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary.
Skill Claude CodeCodex
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach.
Skill Claude CodeCodex
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
Instructions file CodexOpenCode
AGENTS.md instructions for troykelly/codex-skills, covering instructions, skills, available skills and how to use skills.
Agent
Use when code changes are complete and a comprehensive review is required; performs the 7-criteria review and posts the mandatory artifact before PR creation.
Agent
Use when reviewing security-sensitive code (auth, input handling, APIs, database queries, credentials); performs a read-only OWASP checklist review.
Agent
Use when designing feature architecture by analyzing codebase patterns and delivering implementation blueprints with concrete files, components, data flows, and build sequences.
Agent
Use when deeply analyzing existing codebase features to trace execution paths, map architecture layers, and document dependencies for new development.
Agent
Use when code has been written or modified and needs simplification for clarity, consistency, and maintainability without changing behavior.