发现 编程开发 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
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...
Use when creating or modifying skills. Defines skill file structure, naming conventions, and integration patterns.
Use when writing tests or implementing code. Defines RED-GREEN-REFACTOR cycle and test execution workflow.
Use during REFACTOR phase of TDD or when code duplication is suspected. Defines search-first workflow and safe refactoring practices.
Use when creating git commits. Defines conventional commit format and message structure guidelines.
Use when adding project dependencies. Defines dependency management rules and language-specific patterns.
Use when writing or updating spec.md files. Defines requirement format, user story structure, and scenario patterns.
Use when user requests new features or functionality. Defines complete workflow from specification through testing to implementation.
Use when creating or updating agent evaluation suites. Defines eval structure, rubrics, and validation patterns.
Use immediately when user mentions: "テスト", "test", "BDD", "feature", "フィーチャー", "scenario", "シナリオ", "Given", "When", "Then", "カバレッジ", "coverage", "pytest-bdd", "Gherkin". MUST USE this skill f...
This skill should be used when the user asks to "テストのドキュメントを作成", "create test document", "テストをレビュー", "review tests", "テスト網羅性を確認", "test coverage", "テストマトリクスを作成", "テスト...
Use immediately when user mentions: "DTO", "スキーマ", "schema", "データモデル", "data model", "Pydantic", "validation", "バリデーション", "型定義", "type definition", "data structure", "レコード", "record". M...
Use immediately when user mentions: "処理フロー", "processing flow", "フロー図", "flow diagram", "Mermaid", "アーキテクチャ", "architecture", "理解負債", "understanding debt", "なぜ", "why", "数式", "理論", "可...
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...
This skill should be used when the user asks to "週報", "weekly report", "作業レポート", "進捗報告", "週次報告", "レポート作成", "発信用レポート", "全体発信". MUST USE this skill for: - Creating weekly work re...
Use immediately when user mentions: "Interface", "Protocol", "インターフェース", "プロトコル", "contract", "契約", "abstraction", "抽象化", "DI", "dependency injection", "Generic", "TypeVar". MUST USE this ski...
This skill should be used when the user asks to "プロジェクト憲章", "charter", "プロジェクト定義", "プロジェクト開始", "project kickoff", "Why/What/How", "目的を整理", "スコープ定義", "ゴール設定". MUST USE th...
Create CLI entrypoints for pipeline execution with local/SageMaker environment support and parallel processing. Use when user requests "CLI作成", "エントリーポイント", "entrypoint", "scripts/entrypoint.py", "コ...
Implement pipeline orchestration with step-based structure. Use when: building training/prediction pipelines, orchestrating multiple components. Triggers: "pipeline", "trainer", "predictor", "パイプライン", "ワ...
This skill should be used when the user wants to "create a skill", "スキルを作成して", "add a skill to plugin", "スキルをプラグインに追加して", "write a new skill", "新しいスキルを作成して", "improve skill desc...
Use immediately when user mentions: "実装して", "implement", "機能追加", "feature", "作って", "create", "バグ修正", "fix", "実験", "experiment", "統合", "integrate", "ワークフロー", "workflow", "パイプライン",...
Use immediately when user mentions: "code review", "コードレビュー", "レビュー", "review", "品質", "quality", "チェック", "check", "lint", "format", "test", "type check", "pyright", "ruff", "pytest", "テスト",...
This skill should be used when implementing new features, understanding existing patterns, or when the user asks about "project-specific knowledge", "domain knowledge", "business logic", "data schema", "pipelin...
Use immediately when user mentions: "実験", "experiment", "EDA", "探索的分析", "exploratory", "仮説", "hypothesis", "検証", "verify", "論文形式", "IMRaD", "レポート", "report", "分析結果", "analysis result". M...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。