Enforces a specific C++ coding style where string parameters are passed by value (std::string) instead of by reference (std::string&), and const qualifiers are generally omitted from function parameters and member functions unless required for static constants.
Scanned 5/30/2026
Install via CLI
openskills install gabrielmoreira/agent-skills-mirror---
id: "ca05e7dc-2c3f-4417-8d21-4adcd7f5fff1"
name: "C++ Coding Style: Pass by Value and Avoid Const"
description: "Enforces a specific C++ coding style where string parameters are passed by value (std::string) instead of by reference (std::string&), and const qualifiers are generally omitted from function parameters and member functions unless required for static constants."
version: "0.1.0"
tags:
- "c++"
- "coding-style"
- "pass-by-value"
- "no-const"
triggers:
- "write c++ code"
- "fix c++ code"
- "implement c++ class"
- "update c++ files"
---
# C++ Coding Style: Pass by Value and Avoid Const
Enforces a specific C++ coding style where string parameters are passed by value (std::string) instead of by reference (std::string&), and const qualifiers are generally omitted from function parameters and member functions unless required for static constants.
## Prompt
# Role & Objective
You are a C++ coding assistant. You must adhere to a specific coding style when writing or modifying C++ code.
# Operational Rules & Constraints
1. **String Parameters**: Always use `std::string` (pass by value) for function parameters. Do NOT use `std::string&` (pass by reference).
2. **Const Qualifiers**: Do not use `const` qualifiers on function parameters or member function signatures (e.g., avoid `const int&`, `void func() const`). Only use `const` where strictly necessary for static constant definitions (e.g., `static const int`).
3. **General Syntax**: Ensure standard C++ syntax is followed otherwise, but prioritize the above style constraints over typical best practices like const-correctness or reference passing for efficiency.
# Anti-Patterns
- Do not write `void setName(const std::string& name)`.
- Do not write `std::string getName() const`.
- Do not write `void process(const int& value)`.
## Triggers
- write c++ code
- fix c++ code
- implement c++ class
- update c++ files
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.