J
JorgeCostaMacia/skills
Curated agent skills for AI coding agents — GitFlow, SOLID, clean/hexagonal architecture, DDD, testing/TDD…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 2 ★ · JorgeCostaMacia/skills · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-09 · last seen 2026-11-14 · seen 6× · listed by 1 sources
- Score
- score 103 · 2 ★ · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
JorgeCostaMacia/skills;first catalogued 2026-11-09;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# skills
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Curated agent skills and workflows for AI coding agents — installable as a Claude Code plugin marketplace (agentskills.io standard).
Each skill lives as its own plugin under plugins/, so you can install only what you need. The stack-agnostic skills (ddd, testing, logging, messaging…) hold the principles; each -dotnet skill is their .NET realization and declares a dependencies entry on them, so installing a -dotnet skill enables the principles it builds on.
## Available plugins
| Plugin | Description |
| gitflow | A GitFlow workflow for branches and releases: feature/bugfix/release/hotfix start and finish, SemVer tags, default merge messages, commit identity, and the phased-publish caveat. |
| solid | Transversal software-engineering principles: SOLID, simple design, clean code, code smells and complexity management — applied with judgment, not dogma. |
| pnpm | Package-management baseline for any Node.js work: pnpm 12 with dependency build scripts denied unless reviewed (allowBuilds), a strict 3-day minimum release age, no exotic transitive sources, pinned package manager and Node 26, and frozen lockfile in CI. |
| clean-architecture | Clean architecture layering with hexagonal (ports & adapters) boundaries, stack-agnostic and canon-anchored: the four layers inside each bounded context, the inward dependency rule, ports for external capabilities, and the name mapping to Evans, Uncle Bob, Microsoft and Jason Taylor. |
| clean-architecture-dotnet | The .NET realization of clean architecture: one project per module with its four layer folders, internal by default with one public Context per module, the static Add Context / Map …Context composition, the host as composition only (ProgramBuilder / ProgramApplication), the published Contracts and Query and the internal Shared kernels, and the composition test. (depends on clean-architecture) |
| ddd | Tactical Domain-Driven Design, stack-agnostic and canon-anchored: ubiquitous language, aggregates, factories & hydration, value objects, validation principles, per-aggregate data accessors, domain events and domain errors. |
| ddd-dotnet | The .NET realization of tactical DDD: the JorgeCostaMacia.DDD. base types, value objects with their four factories and Convert, no coercion or defaults, aggregates (From cascades, Create seals), the exception family with fixed codes, events collected on the root, and one DbContext per aggregate as its accessor. (depends on ddd, validation-dotnet) |
| validation-dotnet | The .NET realization of validation with FluentValidation, for anything that gets validated: one validator and one exception per validated thing, per-call validators from DI or static Create() chains, composition with Include/SetValidator, every rule evaluated (no Cascade), rule and message conventions, optional boundary validators, and use-case preconditions in Application. (depends on ddd) |
| testing | Testing principles and the pragmatic TDD loop, stack-agnostic and canon-anchored: done means tested, the test pyramid, one test file per unit, names as specification, AAA and independence, classicist test doubles, behavior over implementation, and rule coverage over line coverage. |
Each skill lives as its own plugin under plugins/, so you can install only what you need. The stack-agnostic skills (ddd, testing, logging, messaging…) hold the principles; each -dotnet skill is their .NET realization and declares a dependencies entry on them, so installing a -dotnet skill enables the principles it builds on.
## Available plugins
| Plugin | Description |
| gitflow | A GitFlow workflow for branches and releases: feature/bugfix/release/hotfix start and finish, SemVer tags, default merge messages, commit identity, and the phased-publish caveat. |
| solid | Transversal software-engineering principles: SOLID, simple design, clean code, code smells and complexity management — applied with judgment, not dogma. |
| pnpm | Package-management baseline for any Node.js work: pnpm 12 with dependency build scripts denied unless reviewed (allowBuilds), a strict 3-day minimum release age, no exotic transitive sources, pinned package manager and Node 26, and frozen lockfile in CI. |
| clean-architecture | Clean architecture layering with hexagonal (ports & adapters) boundaries, stack-agnostic and canon-anchored: the four layers inside each bounded context, the inward dependency rule, ports for external capabilities, and the name mapping to Evans, Uncle Bob, Microsoft and Jason Taylor. |
| clean-architecture-dotnet | The .NET realization of clean architecture: one project per module with its four layer folders, internal by default with one public Context per module, the static Add Context / Map …Context composition, the host as composition only (ProgramBuilder / ProgramApplication), the published Contracts and Query and the internal Shared kernels, and the composition test. (depends on clean-architecture) |
| ddd | Tactical Domain-Driven Design, stack-agnostic and canon-anchored: ubiquitous language, aggregates, factories & hydration, value objects, validation principles, per-aggregate data accessors, domain events and domain errors. |
| ddd-dotnet | The .NET realization of tactical DDD: the JorgeCostaMacia.DDD. base types, value objects with their four factories and Convert, no coercion or defaults, aggregates (From cascades, Create seals), the exception family with fixed codes, events collected on the root, and one DbContext per aggregate as its accessor. (depends on ddd, validation-dotnet) |
| validation-dotnet | The .NET realization of validation with FluentValidation, for anything that gets validated: one validator and one exception per validated thing, per-call validators from DI or static Create() chains, composition with Include/SetValidator, every rule evaluated (no Cascade), rule and message conventions, optional boundary validators, and use-case preconditions in Application. (depends on ddd) |
| testing | Testing principles and the pragmatic TDD loop, stack-agnostic and canon-anchored: done means tested, the test pyramid, one test file per unit, names as specification, AAA and independence, classicist test doubles, behavior over implementation, and rule coverage over line coverage. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/jorgecostamacia-skills/)
- Source
- github · https://github.com/JorgeCostaMacia/skills
- Browse by field
- Agent skills
- Traction
- 2 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.