archetype-scriban

What problem does it solve? Writing Scriban templates for Dev CLI archetypes involves subtle syntax rules, truthy evaluation gotchas, and custom casing filters that are easy to get wrong, leading to broken code generation or incorrect conditional output. ## Core Features & Use Cases - Syntax Reference: Covers variables, conditionals, loops, whitespace control, and built-in string/array filters used in .scriban template files. - Custom Filters: Documents pascal_case, camel_case, kebab_case, snake_case, pluralize, singularize, indent, and nullable transforms for naming conventions. - Gotcha Guidance: Explains truthy evaluation rules, JSON computed-expression quoting, and common mistakes like using string parameters as boolean conditions. - Use Case: When authoring an archetype.json with computed parameters like "{{ ProjectName }}.Features.{{ FeatureName }}" or a conditional C# template, consult this Skill to write correct expressions and avoid rendering errors. ## Quick Start Ask the AI to write a Scriban template for a C# handler class with a conditional dependency injection block and kebab-case output file name.