enhance-theme

Estrelas323

Forks30

Atualizado11 de abril de 2026 às 16:42

Locate, modify, and optionally promote CTk Theme Builder theme JSON files

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

avalon60

avalon60/ctk_theme_builder

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	enhance-theme
description	Locate, modify, and optionally promote CTk Theme Builder theme JSON files

When asked to enhance, tweak, modify, or promote a theme:

Look for the theme JSON file in ~/CTkThemeBuilder/themes/, using <theme_name>.json.
If the file does not exist, report that it was not found and do not continue with edits or promotion.
Treat the file in ~/CTkThemeBuilder/themes/ as the authoritative editable source for this task.
Save all requested theme changes back to ~/CTkThemeBuilder/themes/. Do not write changes to any seed theme location in the repository.
If the user asks to promote the theme, copy the theme JSON file to <repo-root>/user_themes/.
If the user asks to promote the theme to the control panel themes, copy the theme JSON file to <repo-root>/assets/themes/.
Where a <theme_name>.json file exists in the ~/CTkThemeBuilder/palettes directory, and a promotion is requested, then the palette file should be copied to the /assets/palettes directory.
Preserve valid JSON structure and formatting when editing or copying theme files.
If the promotion target already contains a file with the same name, warn before overwriting unless the user has explicitly asked to replace it.
If <repo-root> cannot be determined from the current working context, report that and ask for clarification before attempting promotion.

Mais deste repositório

mesmo repositório

generate-release-notes

avalon60/ctk_theme_builder

Generate release notes for CTk Theme Builder by checking for uncommitted changes, verifying the release version in .bumpversion.cfg, and appending the standard installation and upgrade footer.

2026-04-11323

release-package

avalon60/ctk_theme_builder

Prepare a release artefact for this project by bumping the requested semantic version level and running the packaging script. Use when the user asks to bump a major, minor, or patch release and package or create a release artefact. Do not use for ordinary build or test tasks.

2026-04-11323

ctkfontawesome-usage

avalon60/ctk_theme_builder

Use when implementing Font Awesome icons in a CustomTkinter app with the ctkfontawesome package. Covers how to find icon names, create icon images, keep image references alive, size and recolor icons, and attach them to CTk widgets such as CTkButton and CTkLabel.

2026-04-10323

name	enhance-theme
description	Locate, modify, and optionally promote CTk Theme Builder theme JSON files

When asked to enhance, tweak, modify, or promote a theme:

Look for the theme JSON file in ~/CTkThemeBuilder/themes/, using <theme_name>.json.
If the file does not exist, report that it was not found and do not continue with edits or promotion.
Treat the file in ~/CTkThemeBuilder/themes/ as the authoritative editable source for this task.
Save all requested theme changes back to ~/CTkThemeBuilder/themes/. Do not write changes to any seed theme location in the repository.
If the user asks to promote the theme, copy the theme JSON file to <repo-root>/user_themes/.
If the user asks to promote the theme to the control panel themes, copy the theme JSON file to <repo-root>/assets/themes/.
Where a <theme_name>.json file exists in the ~/CTkThemeBuilder/palettes directory, and a promotion is requested, then the palette file should be copied to the /assets/palettes directory.
Preserve valid JSON structure and formatting when editing or copying theme files.
If the promotion target already contains a file with the same name, warn before overwriting unless the user has explicitly asked to replace it.
If <repo-root> cannot be determined from the current working context, report that and ask for clarification before attempting promotion.