Ryu0118

Create or update egg templates. Use when user wants to: (1) create a new template from scratch, (2) add/modify/remove macros, (3) update template files or lifecycle hooks, (4) convert files to Stencil format. For fetching/pinning/syncing existing templates from a repo (egg template install, eggs.yml manifests, egg template sync/update), use egg-cli-guide instead.

CLI usage guide for the egg scaffolding tool. Use when an agent or user wants to hatch a template, needs the preview/apply/rollback/discard/transactions transaction flow, wants to manage templates (create/list/detail/install/validate/duplicate/move/delete/open), or wants to declare/pin/sync template sources reproducibly via an eggs.yml manifest (egg template sync/update).

Create SwiftASTLint lint rules for a user's linter project. Covers Rule (no args) and ParameterizedRule (YAML-configurable args) APIs, RuleSet composition, YAML config for per-rule args/include/exclude/disabled_rules, autofix with SwiftSyntax FixIt, and unit testing with SwiftASTLintTestSupport. Use when: user asks to "add a lint rule", "create a rule", "write a rule", mentions "SwiftASTLint rule", "lint rule", "AST rule", wants to check code patterns via SwiftSyntax, or needs help writing Rule closures. Also trigger when user says "add a check for...", "detect when...", "enforce that...", "ban X in code", or any request about catching code patterns at the AST level — even if they don't mention SwiftASTLint. Also use when user runs /rule-creator.

Use when installing, configuring, running, fixing, or explaining my-swift-linter, swift-ast-lint rules, .swift-ast-lint.yml, Swift lint diagnostics, or the my-swift-linter CLI.

docsync is a CLI tool that keeps documentation in sync with source code via SHA-256 checksums. Use this skill when: (1) setting up docsync.yml for a new project, (2) a docsync check error appears (out of sync / missing checksum / glob no matches), (3) deciding what sources to tie to what docs, (4) adding glob patterns to docsync.yml, (5) integrating docsync into CI or git hooks.

Use the Interaction Swift library to build terminal UIs. Use when a developer wants to: (1) prompt for text input with validation, (2) present single- or multiple-choice menus, (3) render tables or styled/colored text, (4) confirm yes/no, or (5) detect terminal capabilities. Covers the public API of the `Interaction` module.

The single skill for everything Firetrack. Use when (a) installing or adopting the Firetrack CLI in a project — set up a firetrack.yml tracking plan as the source of truth for Firebase Analytics / GA4, install the firetrack binary (install script, mise, or nest), generate type-safe Swift analytics code, or wire validate/generate into CI; (b) designing, validating, syncing, or analyzing a Firebase Analytics / GA4 tracking plan; or (c) editing the Firetrack Swift package itself — its CLI, GA4 sync logic, YAML validation, Swift code generator, tests, or docs. Triggers include "install firetrack", "set up firetrack", "add analytics tracking plan", "adopt firetrack", "design a GA4 tracking plan", "sync GA4 custom dimensions", and "work on the Firetrack package".