{
  "name": "jorgecostamacia-agent-skills",
  "owner": {
    "name": "Jorge Costa Maciá"
  },
  "description": "Agent skills for software engineering: stack-agnostic principles (SOLID, clean architecture, DDD, testing, logging, messaging, GitFlow, changelog, pnpm) and their .NET realizations.",
  "plugins": [
    {
      "name": "gitflow",
      "source": "./plugins/gitflow",
      "description": "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."
    },
    {
      "name": "changelog",
      "source": "./plugins/changelog",
      "description": "How a repository keeps its changelog: one CHANGELOG.md listing, newest first, only what a consumer has to act on (majors, behavior changes, new requirements), written on the release branch with the version bump, while README and AGENTS describe the present and carry no history."
    },
    {
      "name": "code-style-md",
      "source": "./plugins/code-style-md",
      "description": "How Markdown is written in every repository: one paragraph per line, never wrapped by hand and with no forced breaks, kept by Prettier with proseWrap never; code spans for everything literal and bold kept rare; fenced code blocks with their language and commands without a prompt; relative links inside the repo; small tables for comparisons only; sentence-case headings, alerts, Mermaid diagrams, and HTML only where Markdown cannot; and the one-off sweep that brings an existing repo in line."
    },
    {
      "name": "solid",
      "source": "./plugins/solid",
      "description": "Transversal software-engineering principles: SOLID, simple design, clean code, code smells and complexity management — applied with judgment, not dogma."
    },
    {
      "name": "pnpm",
      "source": "./plugins/pnpm",
      "description": "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."
    },
    {
      "name": "clean-architecture",
      "source": "./plugins/clean-architecture",
      "description": "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."
    },
    {
      "name": "clean-architecture-dotnet",
      "source": "./plugins/clean-architecture-dotnet",
      "description": "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<Module>Context / Map<Module>…Context composition, the host as composition only (ProgramBuilder / ProgramApplication), the published Contracts and Query and the internal Shared kernels, and the composition test."
    },
    {
      "name": "ddd",
      "source": "./plugins/ddd",
      "description": "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."
    },
    {
      "name": "ddd-dotnet",
      "source": "./plugins/ddd-dotnet",
      "description": "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."
    },
    {
      "name": "validation-dotnet",
      "source": "./plugins/validation-dotnet",
      "description": "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."
    },
    {
      "name": "testing",
      "source": "./plugins/testing",
      "description": "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."
    },
    {
      "name": "testing-dotnet",
      "source": "./plugins/testing-dotnet",
      "description": "The .NET realization of the testing principles: xUnit v3 on Microsoft.Testing.Platform, test project layout and shared props, InternalsVisibleTo, naming, TestContext cancellation (xUnit1051), Testcontainers fixtures built from the repo's own scripts, test-data helpers, the clock, the host composition test, WebApplicationFactory host tests with hand-written fakes, and running the suites."
    },
    {
      "name": "logging",
      "source": "./plugins/logging",
      "description": "Application logging principles for any stack: the message as a fixed grouping key, all variable data as structured properties, the level as the outcome, correlation in every scope, a failure logged once where it is handled, and observability over log volume."
    },
    {
      "name": "logging-dotnet",
      "source": "./plugins/logging-dotnet",
      "description": "The .NET realization of the logging principles with Serilog: GetType().Name as the message, LogContext properties (a using per property for one statement, a PushProperties helper per class for a reused set), destructured payloads, the exception first in LogError, correlation properties in every scope, the pipeline packages, and minimum levels in configuration."
    },
    {
      "name": "messaging",
      "source": "./plugins/messaging",
      "description": "Asynchronous messaging principles for any stack and broker: commands vs events, contracts with the major in the topic, every message assumed duplicated and out of order, the version in the data with a strict newer-wins guard, optimistic concurrency on the write, retries owned by the broker, and malformed messages parked, not retried."
    },
    {
      "name": "bus-dotnet",
      "source": "./plugins/bus-dotnet",
      "description": "The .NET realization of the messaging principles with the JorgeCostaMacia.Bus family, for every transport: Command/Event records with their two constructors, thin CommandHandler/EventSubscriber adapters, Send/Publish with the incoming transport, the standard retry ladder with ValidationException excluded, retries parked in Quartz and run by a separate jobs worker, routes and the producer/admin/consumer maps."
    },
    {
      "name": "bus-kafka-dotnet",
      "source": "./plugins/bus-kafka-dotnet",
      "description": "How the services use the Kafka transport of the JorgeCostaMacia.Bus family: the topic as the route with the contracts major, partitions declared per service in the admin map, no message key on purpose, the consumer group as a stable contract named after the handler, parked messages in .error, and one broker user per service."
    },
    {
      "name": "efcore-dotnet",
      "source": "./plugins/efcore-dotnet",
      "description": "EF Core conventions for any provider: value objects as ComplexProperty over .Value, keys, explicit column names, a column date kind stated in the mapping, != null in expression trees, sargable half-open date ranges, the token on every call and the FindAsync trap, scoped contexts, and the schema built from the real scripts."
    },
    {
      "name": "efcore-postgres-dotnet",
      "source": "./plugins/efcore-postgres-dotnet",
      "description": "EF Core on PostgreSQL with Npgsql: xmin as a shadow row version for optimistic concurrency, the legacy timestamp switch with timestamp without time zone kept on purpose, microsecond precision, the database collation, one schema per layer, and indexes only on foreign keys."
    },
    {
      "name": "code-style-dotnet",
      "source": "./plugins/code-style-dotnet",
      "description": "How C# is written, enforced as build errors: explicit types (no var, no target-typed new(), no collection expressions) as a stated departure from Microsoft's defaults, braces always, a 120-column width with all-or-nothing wrapping and growing lists kept vertical, naming and modifier conventions, is null outside expression trees, comments only where the code cannot speak, CRLF, dotnet format before committing, and no NoWarn or pragma."
    },
    {
      "name": "build-dotnet",
      "source": "./plugins/build-dotnet",
      "description": "How a .NET repository is built, versioned and restored: the three-tier Directory.Build.props, one VersionPrefix per repo and the separately released piece that keeps its own, Central Package Management, a three-day minimum age for third-party versions, the NuGet vulnerability audit as a build gate, global.json, packing metadata for libraries, and a NuGet configuration without credentials."
    }
  ]
}
