archetype-schema

Defines the archetype.json structure for Dev CLI code generation archetypes.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/thomasmartinsen/talks --skill archetype-schema-thomasmartinsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archetype-schema
Source: https://github.com/thomasmartinsen/talks/tree/main/20260519%20-%20Agentic%20engineering/primitives/skills/creator/skills/archetype-schema
Command: npx skills add https://github.com/thomasmartinsen/talks --skill archetype-schema-thomasmartinsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating or editing Dev CLI archetype definitions requires knowing the exact archetype.json schema, and mistakes in properties, parameters, or file mappings cause generation failures. ## Core Features & Use Cases - Schema Reference: Documents every top-level property of archetype.json including name, version, extends, triggers, and targetProjects. - Parameter System: Covers parameter types, sources (argument, computed, inferred, environment, prompt), transforms like PascalCase and kebab-case, and built-in parameters such as ProjectName and RepositoryRoot. - Files and Post-Actions: Explains how to map Scriban templates to output files with conditions, and how to configure success messages, warnings, and run-command post-actions. - Use Case: When building a new CQRS query archetype, use this Skill to write a valid archetype.json with required parameters, conditional test file generation, and a success post-action. ## Quick Start Create an archetype.json for a new Dev CLI archetype that generates a handler class and its tests from Scriban templates.

Frequently Asked Questions about archetype-schema

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an archetype.json for a Dev CLI archetype?

Place archetype.json in .dev/archetypes/<archetype-name>/ with required fields name, displayName, description, and version. Add a parameters object and a files array mapping .scriban templates to output paths, then finish with optional postActions.

How do I add parameters to a Dev CLI archetype?

Define each parameter under the parameters object with a type and description. Choose a source such as argument, computed, inferred, environment, or prompt, and optionally apply transforms like PascalCase or kebab-case to the resolved value.

What transforms are available for archetype parameters?

Available transforms are PascalCase, camelCase, kebab-case, snake_case, UPPER_CASE, Pluralize, and Singularize. They are applied to string values after the parameter value is resolved from its source.

Can archetype files be generated conditionally?

Yes, each entry in the files array supports a condition property containing a Scriban expression. The file is only generated when the expression evaluates to true, such as {{ IncludeTests }} for optional test files.

Why is my computed parameter not resolving in archetype.json?

Parameters with source set to computed must include a computed property containing a valid Scriban expression using {{ }} syntax. Check that referenced parameters exist and that the expression syntax matches Scriban rules.