Results for “naming”

Enforces the Vikingo Studio standard for WordPress plugins and repos: naming taxonomy, plugin headers, folder structure, versioning, release flow, private update channel, admin UI rules, security baseline, and pre-release checklist.

Create a git branch following Sentry naming conventions, automatically deriving the branch type and description from current work context.

Establishes baseline coding conventions for naming, readability, immutability, and code-quality review across projects.

Create an icon system specification covering grid, sizing, naming, categories, and implementation guidance.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling.

Establishes operational standards for a Salesforce Flow portfolio, covering naming conventions, ownership, version discipline, retirement of stale flows, and release readiness checks.

Guides creating small, issue-linked pull requests with conventional branch naming, commit messages, and structured descriptions, plus a review cycle.

Executes MySQL database development and review tasks based on user-provided rules, covering naming constraints, index design, and data archiving for large datasets.

Enforces a principal-engineer self-review checklist on every code block before output, covering correctness, performance, security, naming, and testability.

Establishes baseline cross-project coding conventions for naming, readability, immutability, and code-quality review, with pointers to framework-specific skills.

SLURM EDF job must use marker names from CHANNELNAMES.txt for output files. Trigger: EDF output naming, SLURM job producing CH#_edf.tif instead of marker names, downstream _find_edf_file failures

Validate current branch follows feature branch naming conventions

Suggest better variable, function, and class names based on context and conventions.

Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.

Validate Claude Code skills against the agentskills specification. Catches structural, semantic, and naming issues before users do.

Reviews cohesion, naming, responsibility, complexity, and maintainability. Do not use as a default companion to every code change.

Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.

Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.

Replace with a specific description of what this skill does and when to use it. Include keywords that help agents identify relevant tasks.

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

Set your primary ENS name on Base and other L2s. Use when user wants to set their ENS name, configure reverse resolution, set primary name, or make their address resolve to an ENS name. Supports Base, Arbitrum, Optimism, and Ethereum mainnet.

Create, list, remove, and rename Gameplay Tags with runtime registration (GameplayTagService). Use when the user asks to add or register gameplay tags, list/query existing tags, or rename/remove tags (e.g. Ability.Attack.Melee, State.Stunned).

Plan, debug, tune, evaluate, export, or deploy public Nemotron embedding and reranking retrieval recipes using the current checkout.

Use this when a Python repository needs package-level planning, import boundaries, module naming, reusable library extraction, or distribution-friendly structure.

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Brief description of what this skill does and when to trigger it. TRIGGERS - Use this skill when: - Trigger condition 1 - Trigger condition 2 - Trigger condition 3

Design products and pricing around validated willingness to pay, using the framework from Ramanujam & Tacke's "Monetizing Innovation" to avoid common monetization failures.

Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs

Find adjacent vendors and subs (not top market primes) who fill a capability gap against a displacement target using USASpending flows and SAM entity signals. Use when user defines a teaming gap and wants vault-ready partner shortlist with citations.