Skill Codex
Use when designing, refactoring, or adding features of ANY language. This guide is to analyze, design, write, refactor the codebase adhering strictly to established clean code principles.
Skill Codex
Use when refactoring oversized, duplicated, tightly coupled, or poorly organized production code. Split code into cohesive, feature-oriented components while preserving behavior. Do not use for test-only restructuring; use de-slop-tests instead.
Skill Codex
Use when reorganizing or splitting oversized test suites. Refactor tests into cohesive, feature-focused files, preserve all behavioral coverage and assertions, and never modify production code.
Skill Codex
Use EVERY TIME you need to modify or delete an existing file, ensuring changes remain strictly limited to the user’s explicit scope.
Skill Codex
Use EVERY TIME you need to make code changes—such as adding, removing, or updating features—to ensure all modifications remain strictly limited to the user’s explicitly requested scope.
Skill Codex
Use when designing, implementing, reviewing, refactoring, or maintaining software in any programming language where security is a requirement. Apply secure-by-design principles, identify vulnerabilities, and recommend industry best practices throughout the software development lifecycle.
Skill Codex
Use when designing, coding, refactoring, or, updating UI code of ANY language. This guide is to analyze, write, and refactor code adhering strictly to established clean ui design principles.
Skill Codex
Use when committing code with Git.
Skill Codex
Use only when I explicitly ask you to use it. Never activate it implicitly.
Skill Codex
Create or update PDF proposals, reports, and companion static web dashboards for any client using LaTeX/Jinja2 templates, branding, and structured data provided by the user. Use when the deliverable requires reproducible TeX/PDF generation or a dashboard package. Before generating, ask for the branding and template…
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: