Results for “naming-convention”

Validate current branch follows feature branch naming conventions

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

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

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.

Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Validates branch names and automates checkout from the correct base branch.

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

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.

Database Naming Standards

File Naming Standards

Merges mature lessons from a domain memory file into its instruction file, preserving knowledge with minimal redundancy.

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.

Naming Strategist

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

Add or update commands in VS Code extensions following naming conventions, visibility rules, and localization best practices.

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.

Detect and prevent public-over-private name resolution in npm, PyPI, and Maven dependency manifests.

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

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".

Harness Compound

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.

Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude/rules/ for permanent enforcement.

Memory (aaaf-memory)

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

Resolves legacy references to the cyber-intel capability by routing to the current runtime agent or skill.

Recursive self-improving holon λ(ο,Κ,Σ).τ' for knowledge compounding and schema evolution. USE WHEN learning, improving, optimizing, assessing, reflecting, debugging, synthesizing, or refining—whether human, AI, or organizational. Triggers on /learn, /compound, /improve, /refine, /optimize, /assess, /reflect, "lessons learned", "best practices", "continuous improvement". Preserves Κ-monotonicity, η≥4, homoiconicity.

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

Domain-Driven Design methodology using bounded contexts, ubiquitous language, and strategic/tactical patterns

Transforms lessons learned into domain-organized memory instructions (global or workspace). Syntax: `/remember [>domain [scope]] lesson clue` where scope is `global` (default), `user`, `workspace`, or `ws`.

Retrieve deterministic search results, metadata, and full-document Markdown from arXiv, PubMed/PMC, and US policy corpora with daily freshness checks.