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.
Skills IA Documentation
Découvrez les skills Documentation, comparez leurs dépôts et consultez leurs instructions.
Catégories: Documentation
Documentation Effacer les filtres
Explorer
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...
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.
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.
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.
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.
GitHub
i18n
Internationalization and locale management. Use when modifying translation files, adding new translation keys, or working with any locale JSON files (en.json, fr.json, ru.json, cn.json) in public/locales/.
GitHub
hello-world
A simple example skill that demonstrates Claude Code skill structure
GitHub
github-pull-request
Generates GitHub pull request (PR) titles and descriptions from code changes. Use when creating PR, updating PR details, generating PR text for chat output, or when the user mentions pull request, PR, merge req...
GitHub
code-committing
Generate semantic commit messages following conventional commits format. Use when committing code, staging changes, writing commit messages, requesting git commit, or when user mentions commit, commit message,...
GitHub
brand-guidelines
Applies Cinzia's brand colors and typography to any sort of artifact that may benefit from having Cinzia's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design stand...
GitHub
create-skill
Use when creating or modifying skills. Defines skill file structure, naming conventions, and integration patterns.
GitHub
test-driven-development
Use when writing tests or implementing code. Defines RED-GREEN-REFACTOR cycle and test execution workflow.
GitHub
refactor
Use during REFACTOR phase of TDD or when code duplication is suspected. Defines search-first workflow and safe refactoring practices.
GitHub
write-commit-message
Use when creating git commits. Defines conventional commit format and message structure guidelines.
GitHub
install-dependencies
Use when adding project dependencies. Defines dependency management rules and language-specific patterns.
GitHub
specification
Use when writing or updating spec.md files. Defines requirement format, user story structure, and scenario patterns.
GitHub
spec-test-driven-development
Use when user requests new features or functionality. Defines complete workflow from specification through testing to implementation.
GitHub
evaluation
Use when creating or updating agent evaluation suites. Defines eval structure, rubrics, and validation patterns.
GitHub
bdd-feature
Use immediately when user mentions: "テスト", "test", "BDD", "feature", "フィーチャー", "scenario", "シナリオ", "Given", "When", "Then", "カバレッジ", "coverage", "pytest-bdd", "Gherkin". MUST USE this skill f...
GitHub
test-coverage
This skill should be used when the user asks to "テストのドキュメントを作成", "create test document", "テストをレビュー", "review tests", "テスト網羅性を確認", "test coverage", "テストマトリクスを作成", "テスト...
GitHub
dto-design
Use immediately when user mentions: "DTO", "スキーマ", "schema", "データモデル", "data model", "Pydantic", "validation", "バリデーション", "型定義", "type definition", "data structure", "レコード", "record". M...
GitHub
processing-flow-doc
Use immediately when user mentions: "処理フロー", "processing flow", "フロー図", "flow diagram", "Mermaid", "アーキテクチャ", "architecture", "理解負債", "understanding debt", "なぜ", "why", "数式", "理論", "可...
GitHub
data-io-impl
Implement data I/O with immediate DTO conversion using ILoader/ISaver protocols. Use when: building data loaders, result savers, file handlers, model persistence, or any external I/O operations. Triggers: "load...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.