Cratis

You can consult and author architecture decision records, write Diátaxis-structured documentation (tutorials, how-tos, references, explanations), apply Cratis C# house conventions for formatting, nullable handling, and dependency injection, and enforce effect-boundary contracts where partial success is treated as failure.

C# engineers and technical writers working in Cratis repositories. Developers use the conventions and effect-boundary skills when writing or reviewing code, while documentation authors use the Diátaxis writing and docs-authoring skills to produce accurate product and sample documentation.

Use effect-boundaries when code publishes, persists, generates, propagates, or releases and a degraded run could falsely report success. Use the C# conventions skill for style questions like naming, records, primary constructors, XML documentation, structured logging, and service lifetimes.

The skills are free to use. The documentation-writing skill is released under the MIT license; the other four skills reference a repository LICENSE file, so check each skill folder for its exact licensing terms before redistribution.

You need a Cratis-based repository, with a decisions/ folder for decision records. Docs-authoring additionally requires that the owning repository, page placement, document type, and authoritative product sources are already known, since placement and discovery are deferred to companion workflows.