743 skills · sorted by relevance
Naming conventions, file structure, and coding standards for Angular projects. Use for Angular-specific naming and organization; defer language-only TypeScript naming questions.
The English summary is being prepared. Showing the original description.
The craft of creating and maintaining cohesive brand identity systems. Branding translates brand strategy into tangible visual and verbal identity—logos, color systems, typography, imagery, and voice guidelines that work together to make a brand recognizable and memorable. This skill covers logo design, visual identity systems, brand guidelines, naming, verbal identity, and brand application across touchpoints. Great branding is invisible when done right—it feels inevitable, as if the brand couldn't have looked any other way. Use when "logo, branding, brand identity, brand guidelines, visual identity, color palette, typography, brand book, naming, rebrand, brand refresh, brand system, branding, identity, logo, visual-design, guidelines, naming, typography, color" mentioned.
The English summary is being prepared. Showing the original description.
Use when refactoring code with poor names, when asked to improve naming, or when a user struggles to name a class/method/variable. Symptoms include -Manager/-Util suffixes, single-letter variables, process/handle/do verbs, primitive obsession, god methods with multiple responsibilities. Two modes — audit (broad scan, list opportunities) and improve (walk one specific identifier through the process).
The English summary is being prepared. Showing the original description.
アプリ名・サービス名の命名を、5つの専門エージェントチームで多角的に評価・決定するスキル。 ブランディング、商標/法的リスク、デジタルプレゼンス(SEO/ASO/SNS)、国際展開(多言語/発音)の 4観点から候補を提案・調査・議論し、コンテキストファイルと議事録で次回セッションへ引き継ぐ。 Use when: アプリ名を決めたい、サービス名を変更したい、プロダクト名を検討したい、 ネーミングブレスト、名前の商標チェック、アプリ名のリネーム。 Triggers: "アプリ名", "サービス名", "プロダクト名", "ネーミング", "名前を決め", "リネーム", "rename", "app name", "naming", "ブランド名", "商標チェック"
The English summary is being prepared. Showing the original description.
Use this skill to configure and manage NPSP Household Accounts: household naming rules, formal/informal greeting formats, primary contact designation, household merges, and household splits. Trigger keywords: NPSP household naming, household account not updating, merge duplicate households NPSP, household greeting customization, primary affiliation NPSP. NOT for FSC (Financial Services Cloud) households — use admin/household-model-configuration. NOT for bulk-loading constituents and households into NPSP — use data/constituent-data-migration.
The English summary is being prepared. Showing the original description.
Refactor code by renaming variables, methods, classes, and concepts for clearer intent. Use when asked to improve names, clarify naming, perform a naming pass, or run `/refactor:names`.
The English summary is being prepared. Showing the original description.
Use when the user asks to "codify our brand voice", "define naming rules for our products and tiers", or "write the tone-of-voice guide with banned phrases"; produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand's own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms) that seeds the narrative-registry canon and that every channel's voice adaptation points up to. Not for per-platform voice adaptation — use channel-registry's voice-dossier; not for finished copy or blog posts — use content-writer; not for the message hierarchy itself — use message-system-architect; not for claim adjudication — use offer-claims-registry. 品牌语气/词汇表/命名税/禁用词/品牌语言规范
The English summary is being prepared. Showing the original description.
Ensure tests use clear naming and cover edge cases with proper describe/it structure.
The English summary is being prepared. Showing the original description.
有馬記念分析システムの命名ドメイン適合性レビュー。関数名・変数名・型名が競馬ドメインの意図（馬・騎手・調教師・血統・レース・出走・着順・上がり3F・馬場・会場・枠順・ローテ）を表現しているか、汎用名・技術接尾辞・命名規則の逸脱（snake_case 混入・アンダースコア付きメソッド名）・同一概念に別名が混在していないか（venue と course、同名異義の型）を検証。Use when user says '命名レビュー', 'review naming', '名前チェック', or 'ドメイン命名確認'.
The English summary is being prepared. Showing the original description.
Extract unwritten coding conventions from an existing project and turn them into an AI style rules file. Resolve conflicting patterns with the user, identify example files, and update the rules as the codebase changes.
Write and review Java services using conventions for naming, immutable data, exception handling, project structure, and tests. Detects Spring Boot or Quarkus from build files and applies the relevant framework rules.
Review and refine code using shared conventions for clear names, readability, error handling, and updates that preserve original data. Identify duplication, oversized functions, and unnecessary complexity to make code easier to understand and maintain.
Plan the retirement of old APIs, features, and systems, then move their users to replacements in stages. The skill also guides database schema changes through additive steps that keep old and new application code compatible during rollout.
Supports palette creation and contrast checks using color science references. It also covers color naming, pigment mixing, and historical color theory, helping you explore color choices for design and creative work.
Review pending database migration SQL before applying schema changes. Check references between tables, rollback coverage, required defaults, destructive operations, and naming conventions, then report errors, warnings, and suggestions with file paths and line numbers.
Guides code cleanup and restructuring by mapping dependencies, assessing test coverage, and planning small changes. Supports tasks such as extracting functions or renaming symbols, with checks after each step and recovery when verification fails.
Set consistent Python conventions for naming, formatting, type checking, and documentation. Configure ruff and mypy or pyright, write clear function descriptions, and organize README and changelog content so a team can maintain shared standards.
Prepare repository contributions by checking existing guidelines, related issues, branch naming rules, commit formats, and pull request templates. Organize changes into logical commits and assemble submissions that follow the project's documented contribution process.
Create and check Git branch names using Conventional Branch rules. Choose a prefix for the task, normalize the description, detect the repository’s base branch, and create and switch to the new branch.
Keeps customer-facing CopilotKit Intelligence documentation consistent by applying an approved vocabulary to prose, navigation, buttons, and image descriptions. Checks disallowed alternatives and exceptions while preserving code identifiers and the labels users actually see in product controls.
Keeps CopilotKit documentation aligned with released Inspector panels, the views shown in its local web overlay. It updates reader guidance and panel mappings when panels change, and checks quickstart instructions against supported platforms.
Prepare a new month of tracking in Google Sheets by copying a template tab within the same spreadsheet and renaming the copy for the month you want to record.
Build reusable parts for n8n workflows instead of copying shared logic. This skill guides typed inputs, consistent outputs, naming, and execution settings so workflows and AI agents can call the same processing steps.
Guide changes to the published @kortix/sdk package with rules for preserving public APIs, writing failing tests before behavior changes, keeping the core independent of frameworks, and checking package installation. It also covers exports, streaming transport, and release version handling.