How do I install the Ast Template Engineer skill?

Run npx skillmds@latest add ivanestar/ast-template-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ast Template Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ast Template Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ast Template Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ast Template Engineer?

ivanestar (@ivanestar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ast Template Engineer by ivanestar — Agent Skill

Name: Ast Template Engineer
Author: ivanestar

Ast Template Engineer

Protocol for safely modifying TypeScript AST templates, enforcing compilation checks and a strict two-strike fallback rule. Trigger on requests like "edit the template", "modify packages/engine/src/plan/templates", "update the AST generator".

ivanestar 552ca4f 2.2 KB Updated Sep 17, 2026

File contents

AST Template Engineer Skill

Purpose

This skill dictates how AI agents must modify TypeScript template literals (AST generators) inside the EITR engine. It guarantees that generated code templates remain syntactically valid TypeScript and prevents broken string interpolations.

Trigger this skill automatically whenever you modify > 0 files matching the path packages/engine/src/**/templates/*.ts.

Rules & Constraints

1. Mandatory Compilation Check

After modifying > 0 lines in an AST template file, you MUST verify its syntax before proposing the change to the user or making a commit.

Execute exactly: npm run typecheck (or npx tsc --noEmit <path-to-file>).
If the exit code is > 0, you MUST NOT proceed. You must read the error output and attempt a fix.

2. The Fallback Rule (Two-Strike Limit)

If your compilation check fails >= 2 times consecutively on the same file, you MUST abort the modification.
Execute exactly: git checkout -- <file> to revert the file to its last committed state.
Output exactly: "ABORT: Reverting due to unresolvable AST compilation error."

3. Boundary Constraints & Safety

DO NOT use the multi_replace_file_content tool for template refactors if the string spans > 50 lines. If modifying >50 lines, rewrite the specific AST node entirely.
DO NOT remove existing ${} interpolation variables unless explicitly requested by the user.

Examples

Good Example

1. Modified `packages/engine/src/plan/templates/playwright.ts`.
2. Executed `npm run typecheck`.
3. Received exit code 1 (Missing backtick on line 45).
4. Fixed the missing backtick.
5. Re-ran `npm run typecheck`. Received exit code 0.

Bad Example

1. I updated the template string for the Java generator.
2. The code looks correct to me, so I will commit it now.
   _(Violation: Did not run `npm run typecheck`. Relied on visual inspection instead of a deterministic compiler check.)_

---name: ast-template-engineerdescription: Protocol for safely modifying TypeScript AST templates, enforcing compilation checks and a strict two-strike fallback rule. Trigger on requests like "edit the template", "modify packages/engine/src/plan/templates", "update the AST generator".---# AST Template Engineer Skill## PurposeThis skill dictates how AI agents must modify TypeScript template literals (AST generators) inside the EITR engine. It guarantees that generated code templates remain syntactically valid TypeScript and prevents broken string interpolations.Trigger this skill automatically whenever you modify > 0 files matching the path `packages/engine/src/**/templates/*.ts`.## Rules & Constraints### 1. Mandatory Compilation CheckAfter modifying > 0 lines in an AST template file, you MUST verify its syntax before proposing the change to the user or making a commit.- Execute exactly: `npm run typecheck` (or `npx tsc --noEmit <path-to-file>`).- If the exit code is > 0, you MUST NOT proceed. You must read the error output and attempt a fix.### 2. The Fallback Rule (Two-Strike Limit)- If your compilation check fails >= 2 times consecutively on the same file, you MUST abort the modification.- Execute exactly: `git checkout -- <file>` to revert the file to its last committed state.- Output exactly: "ABORT: Reverting due to unresolvable AST compilation error."### 3. Boundary Constraints & Safety- **DO NOT** use the `multi_replace_file_content` tool for template refactors if the string spans > 50 lines. If modifying >50 lines, rewrite the specific AST node entirely.- **DO NOT** remove existing `${}` interpolation variables unless explicitly requested by the user.## Examples### Good Example```markdown1. Modified `packages/engine/src/plan/templates/playwright.ts`.2. Executed `npm run typecheck`.3. Received exit code 1 (Missing backtick on line 45).4. Fixed the missing backtick.5. Re-ran `npm run typecheck`. Received exit code 0.```### Bad Example```markdown1. I updated the template string for the Java generator.2. The code looks correct to me, so I will commit it now. _(Violation: Did not run `npm run typecheck`. Relied on visual inspection instead of a deterministic compiler check.)_```

Frequently asked questions