Skill Claude CodeCodex
Axum + Askama + HTMX stack for single-binary web apps. Use when: building server-rendered UI, lightweight frontends, single deployable binary. Triggers: "htmx", "askama", "templates", "server-rendered", "single binary frontend".
Skill Claude CodeCodex
Build GraphQL APIs with schema design, resolvers, and subscriptions. Use when: creating GraphQL server, API with complex queries. Triggers: "graphql", "gql", "apollo", "async-graphql", "strawberry".
Skill Claude CodeCodex
An idea-review helper that examines a proposed application and creates a detailed product requirements document. A product requirements document records what the product should do and saves it as docs/PRD.md.
Skill Claude CodeCodex
Project type definitions with type-specific questions, patterns, and stacks. Use when: determining project architecture, asking type-specific questions. Referenced by: idea-validation, brainstorming, /ship command.
Skill Claude CodeCodex
Validates project after initialization. Checks static files, endpoints, CSS, health. Use when: after rust-project-init, before TDD loop. Triggers: "validate project", "check project", "verify init".
Skill Claude CodeCodex
Automatic OWASP security checks on generated code. Use when: any code is generated in the pipeline. Triggers: internal use only.
Skill Claude CodeCodex
Automatically choose the best tech stack based on requirements. User never sees this. Use when: starting a new project after idea validation. Triggers: internal use only, called by build pipeline.
Skill Claude CodeCodex
A guide for building Telegram bots, which are programs that respond to messages and events in Telegram. It uses current bot-development frameworks.
Skill Claude CodeCodex
A skill for generating user-interface components from plain-language descriptions.
Skill Claude CodeCodex
Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion.
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: