review-staged-changes
Lichens-InnovationReviews staged git changes for code quality, maintainability, readability, and potential regressions. Verifies changes make sense in context, improve maintainability, enhance readability, and don't introduce side effects. Use when reviewing staged changes, examining git diffs, or when the user asks to review modifications before committing.
hello-world
Lichens-InnovationSimple skill to welcome user in ASCII Art Format with operating system information
coding-standards
Lichens-InnovationLOAD THIS SKILL when: creating or editing any TypeScript, JavaScript, React, or Node.js file, naming variables/functions/components, designing API endpoints, handling async operations, structuring React components, reviewing code for quality, refactoring existing code, or setting up a new project structure. Also trigger when the user asks "how should I name...", "what's the best way to...", "is this good practice...", or "can you review this code". DO NOT load for: CSS-only changes, documentation writing, JSON config edits, shell scripts.
generate-pr-description
Lichens-InnovationGenerate pull request descriptions by comparing current branch with parent branch. Creates semantic commit-style PR titles and fills PR templates. Use when the user asks to generate PR description, prepare pull request, or create merge request description.
react-ts-guidelines
Lichens-InnovationTypeScript, React, and Node.js coding standards: naming, types, hooks, components, error handling, refactoring, code review. Use when creating/editing TS/JS/React files, naming variables or components, designing API endpoints, handling async, structuring components, or when the user asks "how should I name...", "what's the best way to...", "is this good practice...", "can you review this code". Keywords: TypeScript, React, hooks, React Query, Jest, RTL, naming, immutability. Do not load for: CSS-only changes, documentation writing, JSON config edits, shell scripts.
generate-pr-description
Lichens-InnovationGenerate pull request descriptions by comparing current branch with parent branch. Creates semantic commit-style PR titles and fills PR templates. Use when the user asks to generate PR description, prepare pull request, or create merge request description.
react-files-structure-standards
Lichens-InnovationEnforces file and folder naming and structure standards for React/TypeScript projects. Use when normalizing file/folder names, auditing project structure, renaming files or directories, or when the user asks to align file/folder naming with standards.
React Linter Setup
Lichens-InnovationSet up ESLint for React and TypeScript projects aligned with company standards. Use this when installing or configuring the project linter, adding devDependencies, adding custom ESLint rules or package.json scripts, or when a user requests setup or migration to the company's React/TypeScript ESLint stack.
react-coding-standards
Lichens-InnovationEnforces internal React and TypeScript coding standards using avoid/prefer rules. Use when reviewing or refactoring React/TS code, applying company standards, or when the user asks to align code with coding standards.
react-single-responsibility
Lichens-InnovationStrategies to simplify components, hooks, and methods: decomposition order (utilities, hooks, sub-components), early returns, control flow, parameter design, and code smell fixes. Use when refactoring a large component, hook, or function, reducing complexity, applying single responsibility, or when the user asks how to simplify a component, hook, or method.
coding-standards
Lichens-InnovationLOAD THIS SKILL when: creating or editing any TypeScript, JavaScript, React, or Node.js file, naming variables/functions/components, designing API endpoints, handling async operations, structuring React components, reviewing code for quality, refactoring existing code, or setting up a new project structure. Also trigger when the user asks "how should I name...", "what's the best way to...", "is this good practice...", or "can you review this code". DO NOT load for: CSS-only changes, documentation writing, JSON config edits, shell scripts.
single-responsibility
Lichens-InnovationStrategies to simplify components and methods: decomposition order (utilities, hooks, sub-components), early returns, control flow, parameter design, and code smell fixes. Use when refactoring a large component or function, reducing complexity, applying single responsibility, or when the user asks how to simplify a component or method.
hello-world
Lichens-InnovationSimple skill to welcome user in ASCII Art Format with operating system information
react-single-responsibility
Lichens-InnovationStrategies to simplify components, hooks, and methods: decomposition order (utilities, hooks, sub-components), early returns, control flow, parameter design, and code smell fixes. Use when the user says: ungodify this method/function/component, simplify this method/function/component, make this method/function/component less complex; or when refactoring a large component, hook, or function, reducing complexity, applying single responsibility, or asking how to simplify a component, hook, or method.
review-staged-changes
Lichens-InnovationReviews staged git changes for code quality, maintainability, readability, and potential regressions. Verifies changes make sense in context, improve maintainability, enhance readability, and don't introduce side effects. Use when reviewing staged changes, examining git diffs, or when the user asks to review modifications before committing.
react-coding-standards
Lichens-InnovationEnforces internal React and TypeScript coding standards using avoid/prefer rules. Use when reviewing or refactoring React/TS code, applying company standards, or when the user asks to align code with coding standards.