#claude-commands
49 resources
Results
- 703-technologies-fuzzing-testing
Design and implement contract-driven fuzz testing for Java APIs using CATS to uncover edge cases and input-validation defects early.
- authentication-patterns
Provides auth patterns for API keys, OAuth, and token management.
- 112-java-maven-plugins
Maven Plugins: pom.xml Configuration Best Practices
- 130-java-testing-strategies
Apply proven testing strategies (RIGHT-BICEP, A-TRIP, CORRECT) to design and verify Java unit tests.
- 131-java-testing-unit-testing
Review and improve Java unit tests using modern JUnit 5, AssertJ, and Mockito best practices.
- 132-java-testing-integration-testing
Set up robust integration-test infrastructure for Java services using WireMock to stub outbound HTTP dependencies.
- 133-java-testing-acceptance-tests
Implement acceptance tests from maintainer-sanitized Gherkin scenario facts.
- 321-frameworks-spring-boot-testing-unit-tests
Apply Spring Boot unit testing guidelines with Mockito.
- 322-frameworks-spring-boot-testing-integration-tests
Apply Spring Boot integration testing guidelines for Spring Boot 4.0.x.
- 323-frameworks-spring-boot-testing-acceptance-tests
Spring Boot acceptance tests from Gherkin
- 421-frameworks-quarkus-testing-unit-tests
Apply fast testing strategies for Quarkus: Mockito-first, QuarkusTest when CDI wiring matters.
- 422-frameworks-quarkus-testing-integration-tests
Apply integration testing patterns for Quarkus with real wiring and reproducible infrastructure.
- 423-frameworks-quarkus-testing-acceptance-tests
Implement happy-path acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus using real HTTP and infrastructure.
- 522-frameworks-micronaut-testing-integration-tests
Prove real wiring in Micronaut with containers and HTTP.
- 523-frameworks-micronaut-testing-acceptance-tests
Implement happy-path acceptance tests from maintainer-sanitized Gherkin scenario facts for Micronaut using real HTTP and infrastructure.
- 151-java-performance-jmeter
Provide a complete JMeter performance testing solution by creating the run-jmeter.sh script from the exact template, making it executable, and configuring the project structure for load testing.
- 161-java-profiling-detect
Java Profiling Workflow / Step 1 / Collect data to measure potential issues
- 521-frameworks-micronaut-testing-unit-tests
Apply fast testing strategies for Micronaut: Mockito-first, narrow @MicronautTest when HTTP or DI replacement is required.
- karpathy-principles
Pre-implementation gate covering think-first, simplicity, surgical edits, and verifiable goals.
- progressive-loading
Implements hub-and-spoke lazy loading to minimize token usage in large skills.
- night-market-diagnostics-toolkit
Run and interpret repo diagnostic scripts (ratchets, validators, token stats).
- pytest-config
Provides standardized pytest config, reusable fixtures, and CI integration patterns.
- skills-eval
Evaluate Claude skill quality through auditing.
- 003-skills-inventory
Create a Checklist with all Java steps to use with system prompts for Java
- 012-agile-epic
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories.
- 013-agile-feature
Guides the creation of detailed agile feature documentation from an existing epic.
- 021-problem-framing
Guide production of a Problem statement, Current state, Desired state, Stakeholders, and Success criteria for a problem or issue under exploration.
- 022-root-cause-analysis
Guide the identification of root causes, not symptoms, for a framed problem, using Five Whys, Fishbone (Ishikawa), Current Reality Tree, and constraint identification.
- 023-assumption-analysis
Guide production of explicit Assumptions, a list of Unknowns, and a Validation plan for a problem under exploration.
- 024-context-mapping
Guide identification of Existing systems, Integrations, Ownership, and External dependencies relevant to a problem under exploration.
- 025-quality-attribute-discovery
Guide identification and prioritization of the quality attributes a future solution must satisfy, before architecture and design decisions begin.
- test-updates
Updates, generates, and validates tests using git-workspace context and TDD/BDD methodology.
- math-review
Verifies math-heavy code for algorithmic correctness and numerical stability.
- rust-review
Audits Rust code for unsafe blocks, ownership issues, and Cargo dependency risks.
- project-execution
After planning phase completes - Ready to implement tasks - Need systematic execution with tracking - Want checkpoint-based validation -…
- skill-library-mission
Build a project skill library in .claude/skills/ via discovery, parallel authoring, and review.
- elegant-code
Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage.
- agent-teams
Coordinates Claude agent teams via filesystem protocol.
- delegation-core
Delegates tasks to Gemini, Qwen, or MiniMax with quota tracking and error handling.
- mission-orchestrator
Orchestrates full project lifecycle by auto-detecting state and routing to the correct phase.
- python-async
Async Python patterns via asyncio and aiohttp for I/O-bound concurrency.
- subagent-testing
Test skills via TDD in fresh subagents.
- architecture-paradigm-functional-core
Applies Functional Core, Imperative Shell to isolate logic from side effects.
- architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling.
- architecture-paradigm-service-based
Applies coarse-grained service architecture for deployment independence.
- night-market-build-and-env
Rebuild the dev environment: uv, Python tiers, pins, traps.
- night-market-completion-integrity-campaign
Bind loop 'done' to unfakeable gates.
- night-market-model-and-harness-updates
Sweep plugins, skills, agents, commands, and hooks after a model release or Claude Code version bump.
- night-market-operations
Run and ship this repo: make targets, artifacts, release runbook.
