GitHub
bdd-test
Phase 5 of feature development - Create BDD tests with Cucumber/Gherkin and unit tests for the Burraco system. Use after kotlin-implement to add comprehensive test coverage.
☆ 0View skill
abaddon AI Skills
GitHub ↗Browse published AI skills maintained by abaddon. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
7Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
domain-modeling
Phase 3 of feature development - Create domain events, external events, value objects, and aggregate changes for the Burraco system. Use after feature-design to implement the domain model.
☆ 0View skill
GitHub
feature-workflow
Main workflow orchestrator for adding new features to the distributed Burraco card game system. Use this when implementing new game features across Game, Player, and Dealer services following CQRS, Event Sourci...
☆ 0View skill
GitHub
feature-discovery
Phase 1 of feature development - Analyze feature requirements and assess impact on the distributed Burraco system. Use this to understand what services are affected and identify risks before designing.
☆ 0View skill
GitHub
integration-docs
Phase 6 of feature development - Update documentation and verify integration for the Burraco system. Use after bdd-test to complete the feature with proper documentation.
☆ 0View skill
GitHub
feature-design
Phase 2 of feature development - Design architecture, events, commands, and service interactions for the Burraco distributed system. Use after running feature-discovery to create the technical design.
☆ 0View skill
GitHub
kotlin-implement
Phase 4 of feature development - Implement commands, REST handlers, Kafka consumers/producers in Kotlin for the Burraco distributed system. Use after domain-modeling to write the implementation code.
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.