SebastienDegodez
- 21 skills
- 0 followers
- 3 hours ago last updated
- ▌ Skill Creator · sebastiendegodez bundleGuide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
- ▌ Setup Husky Dotnet · sebastiendegodez bundleUse when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically
- ▌ Creating Dotnet MCP Servers · sebastiendegodez bundleUse when building Model Context Protocol (MCP) servers in .NET, configuring tools, transports (SSE/stdio), JSON serialization for AOT, or testing MCP endpoints
- ▌ Migrating Prompts To Skills · sebastiendegodezUse when converting existing .prompt.md or .instructions.md files to reusable SKILL.md format, before guessing structure or deciding what to keep/remove
- ▌ Generate Microcks Openapi Samples · sebastiendegodez bundleUse when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses
- ▌
- ▌ Gherkin Gate · sebastiendegodezUse before writing any test or implementation task, when observable behavior needs to be captured in business language scenarios and approved by the user before code begins
- ▌ Finding Files · sebastiendegodez bundleUse when searching for files by name, pattern, or type in large directories, or building file lists for pipelines with other tools
- ▌ Querying JSON · sebastiendegodez bundleUse when querying JSON files, filtering or transforming JSON data, or extracting specific fields from large JSON files without loading entire file contents (saves 80-95% context)
- ▌ Querying YAML · sebastiendegodez bundleUse when querying YAML files, filtering or transforming configuration data, or extracting specific fields from large YAML files like docker-compose.yml or GitHub Actions workflows without loading entire files (saves 80-95% context)
- ▌ Viewing Files · sebastiendegodez bundleUse when viewing source files or documentation with syntax highlighting, previewing files with Git integration, or when enhanced readability would improve code review
- ▌ Analyzing Code · sebastiendegodez bundleUse when understanding project composition by language, measuring code change impact, or generating code statistics for CI/CD metrics
- ▌ Replacing Text · sebastiendegodez bundleUse when performing text find & replace, batch transformations across files, or when JavaScript-style regex syntax is preferred over sed
- ▌ Searching Text · sebastiendegodez bundleUse when searching for text patterns across files, finding specific code locations, or getting lines with surrounding context in a single call
- ▌ Outside In Tdd · sebastiendegodez bundleUse when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge
- ▌ Fuzzy Selecting · sebastiendegodez bundleUse when choosing interactively from search results, files, processes, or any command output with preview capabilities
- ▌ Mutation Testing · sebastiendegodezUse when running mutation testing, killing mutants, verifying test quality, checking mutation score, or analyzing survivors after the test baseline is green
- ▌ Red Synthesize Green · sebastiendegodezUse when implementing any feature or fix using TDD, before writing any implementation code
- ▌ Analyzing Code Structure · sebastiendegodez bundleUse when editing code structure with text matching ambiguity, handling "old_string not unique" problems, or performing formatting-independent pattern matching across function signatures, method calls, and class structures
- ▌ Extracting Code Structure · sebastiendegodez bundleUse when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files
- ▌ Clean Architecture Dotnet · sebastiendegodez bundleUse when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).