test
73Command
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
Command
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
Command
Enter a product workspace with full Hamzaish context loaded — config, status, decisions, stage playbook, and the product's own CLAUDE.md.
Plugin Claude Code
A reusable, stack-agnostic website launch system: a verification-gated checklist (Done ≠ Verified), a refuse-to-launch sign-off gate, a Day 1/3/7/14/30 monitoring cadence, an anonymized failure-mode library, and programmatic-SEO-at-scale quality gates. Routes to specialist SEO/security plugins for commodity crafts.
Command
Kick off or resume a verification-gated website launch — scope the project, stamp a per-project tracking workbook, walk the phases, and enforce the pre-launch sign-off gate.
Skill Claude CodeCodex
A library of real, hard-won website-launch failure modes — each with what happened, the root cause, and how to prevent it. Use before starting a launch, when debugging a launch-time SEO/analytics/performance problem (indexation not happening, redirect or canonical issues, analytics undercounting, schema validation…
Skill Claude CodeCodex
Quality and indexation discipline for programmatic / templated SEO at scale — sites with hundreds to tens of thousands of generated pages (directories, /tool, /compare, /category, location or entity pages). Use when planning, launching, or auditing a large templated page set: preventing mass thin-content, designing…
Skill Claude CodeCodex
Run a website launch as a verification-gated process, not a to-do list. Use when taking a site (or a major site section) to production — scoping a launch, building or walking a launch checklist, deciding if a site is ready to ship, or setting up post-launch monitoring. Emits a per-project tracking workbook, enforces a…
Skill Claude CodeCodex
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Skill Claude CodeCodex
Intelligent workflow orchestrator that automatically chains the right skills (spec, plan, build, test, review, code-simplify, ship) based on the current state of the work. Use when you want Claude to drive a feature or task end-to-end without manually invoking each skill.
Skill Claude CodeCodex
Generate a product's full brand-asset set at finishing time — two logo concepts to choose from, then the square app icon, favicon set, horizontal lockup, and a separate square auth-provider logo. One SVG source of truth, rendered with rsvg-convert. Every product needs all of these before launch.
Skill Claude CodeCodex
Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.
Skill Claude CodeCodex
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Skill Claude CodeCodex
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Skill Claude CodeCodex
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Skill Claude CodeCodex
Map a product's competitive landscape — direct + adjacent competitors, their positioning, naming conventions, and white-space. Persists findings to a per-product competitors file so it compounds over time. Use before naming, positioning, pricing, or GTM — and as the collision baseline for name-clearance.
Skill Claude CodeCodex
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
Skill Claude CodeCodex
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Skill Claude CodeCodex
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Skill Claude CodeCodex
Compose interfaces that hold together — skeleton before aesthetics, one alignment per row, sizing by declaration. Use when building or reviewing any UI component, fixing "it looks off but I cannot say why", or adding an element to an existing layout.
Skill Claude CodeCodex
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Skill Claude CodeCodex
Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not…
Skill Claude CodeCodex
Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.
Skill Claude CodeCodex
Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
Skill Claude CodeCodex
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
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: