By g-cqd
Portable engineering harness: interconnected agents and atomic skills for Swift/Apple-platform development, testing, code review, planning, architecture, security, and Xcode 27 agentic workflows.
Use this agent for all security work on Apple platforms: vulnerability assessment, code review, threat modeling, cryptographic audits, Keychain review, network security, deep link validation, and secure coding guidance for iOS, macOS, watchOS, tvOS, and visionOS. Invoke proactively after writing security-sensitive code (auth flows, data storage, crypto, network handlers, deep links, sensitive user data). Combines attacker-mindset analysis with practical remediation. Examples: <example> Context: User implements Keychain storage. user: "I've written a function to store user passwords in the Keychain" assistant: "I'll use the apple-security-analyst agent to review your Keychain implementation." </example> <example> Context: User implements certificate pinning. user: "Here's my URLSession delegate for handling SSL pinning" assistant: "I'll use the apple-security-analyst agent to analyze for bypass vulnerabilities." </example> <example> Context: User completes a deep link handler. user: "I just finished the URL scheme handler for our app" assistant: "I'll use the apple-security-analyst agent to review for URL scheme hijacking and input validation." </example> <example> Context: User asks about platform security. user: "How does the Secure Enclave protect cryptographic keys?" assistant: "I'll use the apple-security-analyst agent for an in-depth technical explanation." </example>
Plan system architecture and delivery strategy for services, infrastructure, CI/CD, and reliability goals. Use for design decisions, scaling plans, cross-team technical roadmaps, cloud infrastructure, deployment pipelines, and operational strategy. Produces evidence-based plans with explicit tradeoffs and phased rollout.
Use this agent when the user needs expert guidance on brand strategy, visual identity systems, brand architecture, naming conventions, brand voice development, competitive positioning, or brand guidelines documentation. This includes creating brand foundations, conducting brand audits, developing visual identity systems, crafting messaging frameworks, or preparing brand presentations. Examples: <example> Context: User is working on a new startup and needs brand positioning help. user: "I'm launching a fintech app for Gen Z and need help with brand positioning" assistant: "I'll use the brand-strategist agent to help develop your brand positioning strategy." <commentary> Since the user needs strategic brand positioning for a new product targeting a specific audience, use the brand-strategist agent to conduct proper competitive analysis, develop positioning canvas, and create brand foundations. </commentary> </example> <example> Context: User needs to create brand guidelines for an existing company. user: "We need comprehensive brand guidelines for our company" assistant: "Let me launch the brand-strategist agent to architect your brand guidelines documentation." <commentary> Brand guidelines documentation requires systematic thinking about visual identity, typography, color systems, voice, and messaging - all core competencies of the brand-strategist agent. </commentary> </example> <example> Context: User is evaluating their competitive landscape. user: "Can you help me understand how our brand compares to competitors?" assistant: "I'll use the brand-strategist agent to conduct a comprehensive competitive brand audit." <commentary> Competitive analysis and perceptual mapping are strategic brand exercises that require the brand-strategist agent's frameworks and methodologies. </commentary> </example> <example> Context: User needs naming conventions for a product line. user: "We're launching three new products and need a naming system" assistant: "Let me engage the brand-strategist agent to develop your naming architecture." <commentary> Naming architecture requires strategic thinking about scalability, consistency, and brand hierarchy - use the brand-strategist agent for systematic naming frameworks. </commentary> </example>
Collect second-opinion feedback from other installed AI CLIs (Claude, Codex, Gemini) and synthesize consensus, disagreements, and decision-ready recommendations. Use before committing high-impact technical decisions, when architecture tradeoffs are unclear, or when you want external challenge.
Verify framework and API behavior against authoritative documentation and summarize actionable guidance. Use when implementation depends on version-specific API details, policy constraints, platform behavior differences, or when you need to resolve conflicting information about how an API works.
Algorithmic engineering theory, language-agnostic: complexity analysis (time/space, amortized), data-structure selection, algorithm families (divide & conquer, dynamic programming, greedy, graph, string), correctness reasoning with invariants, and space-time/approximation tradeoffs. Use when choosing a data structure, analyzing or reducing complexity, solving an algorithmic problem, reviewing code with non-trivial loops/recursion, or reasoning about scalability limits of an approach.
Local, searchable Apple developer documentation via the apple-docs CLI and MCP server (DocC, Human Interface Guidelines, App Store Review Guidelines, Swift Evolution, Swift Book, WWDC sessions, sample code, SF Symbols). Use whenever an answer depends on exact Apple API behavior, availability, HIG/review-guideline wording, or WWDC content — before trusting training memory. Also use to set up the tooling: detect whether the MCP server or CLI is available and propose installation if not.
Apple platform API adoption for the iOS 26 / macOS 26 SDK generation: Liquid Glass (SwiftUI, UIKit, AppKit, WidgetKit), Swift 6.2 features (InlineArray, Span, concurrency updates), Foundation Models (on-device LLM), Visual Intelligence, AppIntents, StoreKit, SwiftData inheritance, AlarmKit, 3D Charts, MapKit GeoToolbox, AttributedString, visionOS widgets. Use when adopting, migrating to, or asking about these platform APIs. For SDK 27 SwiftUI changes use swiftui-whats-new-27; for general SwiftUI use swiftui.
Secure coding and security review for Apple platforms: threat modeling (STRIDE, attacker profiles), Keychain and Secure Enclave storage, CryptoKit cryptography, network security (ATS, certificate pinning, TLS), input validation (deep links, URL schemes, WebView hardening), jailbreak/integrity checks, and security code-review methodology. Use when writing or reviewing security-sensitive code (auth, storage, crypto, network handlers, deep links). For Xcode build-setting hardening (Enhanced Security, bounds safety) use audit-xcode-security-settings.
Audit and enable security-oriented Xcode build settings. Progressively enables compiler warnings, static analyzer checkers, and Enhanced Security features. Use when: user wants to secure their Xcode project, audit security settings, enable hardening, review security posture of build configuration, set up security-focused static analysis, enable static analysis, improve warning coverage, harden diagnostics, or catch more bugs at compile time in C/C++/Objective-C/Swift. SKIP: network security (TLS/ATS), code signing, privacy APIs.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A portable, self-contained set of 10 agents and 30 atomic skills for agentic software engineering — Swift/Apple-platform deep, with language-agnostic engineering theory (security, performance, algorithms, debugging, practices) and general-purpose planning, review, testing, architecture, and documentation capabilities.
Everything here is project- and company-agnostic. Drop it on any machine.
cp -R skills/* ~/.claude/skills/
cp -R agents/* ~/.claude/agents/
Project-level alternative: copy into <repo>/.claude/skills and
<repo>/.claude/agents to scope to one repository.
This directory is a valid plugin (.claude-plugin/plugin.json):
claude --plugin-dir /path/to/this/directory
or publish it to a git repo and install via a plugin marketplace. Plugin
skills are namespaced (/skills:planner).
Xcode reads the same Agent Skills format. Copy skills into
~/Library/Developer/Xcode/CodingAssistant/<agent-config>/skills/ and keep a
root AGENTS.md in your project (Claude Code reads CLAUDE.md; have one
import the other).
Skills are drop-in. Copilot auto-discovers Agent Skills from
~/.claude/skills/ (personal) and .claude/skills/ / .github/skills/
(project) — so Option A above already covers Copilot. allowed-tools is
honored by the Copilot CLI and ignored elsewhere (harmless).
Agents need conversion for the Copilot CLI and coding agent (VS Code
reads .claude/agents/ natively):
python3 copilot/convert-agents.py --src agents --out <repo>/.github/agents
This translates tool names (Read→read, Grep/Glob→search, Bash→execute, …),
strips Claude-only model aliases, and emits *.agent.md files.
Instructions: use copilot/templates/ — a shared AGENTS.md (the
cross-tool standard, also read by Xcode and the Copilot coding agent), a thin
.github/copilot-instructions.md, a CLAUDE.md import shim, and path-scoped
.github/instructions/*.instructions.md examples (Swift, Kotlin, tests).
| Artifact | Claude Code | Copilot (VS Code/CLI/cloud) | OpenAI Codex | Gemini CLI | Xcode 27 |
|---|---|---|---|---|---|
skills/*/SKILL.md | native | native (.claude/skills, .github/skills) | native (~/.codex/skills, .agents/skills) | native (~/.gemini/skills, .agents/skills alias) | native (CodingAssistant dirs) |
agents/*.md | native | VS Code native; CLI/cloud: convert → .agent.md | convert → TOML (explicit delegation only) | near-compatible Markdown+YAML (.gemini/agents/) | n/a |
AGENTS.md | via CLAUDE.md import | native | native (+ AGENTS.override.md) | via contextFileName setting (default GEMINI.md) | native |
.agents/skills/ is the cross-vendor convergence path — Codex scans it
natively and Gemini treats it as a preferred alias:
cp -R skills/* ~/.agents/skills/ # Codex + Gemini (user-level)
ln -s ../../.agents/skills .claude/skills # optional: one project dir for all
Caveats: Codex shortens skill descriptions when total metadata exceeds
~8,000 chars (this set totals ~18k — first sentences are written to survive
truncation); Gemini gates workspace skills behind folder /trust and
per-activation confirmation; Codex subagents need TOML conversion and never
auto-delegate (not provided here — use the skills, which port cleanly).
agents/ ← subagent definitions (delegated specialists)
skills/ ← atomic knowledge/procedure units (lazy-loaded)
copilot/ ← GitHub Copilot compatibility: agent converter + instruction templates
| Agent | Role |
|---|---|
swift-engineer | Build/design/profile/review Swift & SwiftUI |
apple-security-analyst | Threat modeling, security review, secure coding |
brand-strategist | Brand strategy, identity systems, naming |
quality-reviewer | iOS/Android code review, simplification-first |
tdd-engineer | Strict Red-Green-Refactor implementation |
migration-executor | Phased API/platform/dependency migrations |
architecture-planner | System architecture, CI/CD, delivery strategy |
request-executor | Executes typed XML execution contracts |
docs-researcher | Primary-source API/behavior verification |
cross-cli-opinion-broker | Second opinions from peer AI CLIs |
Agents declare no model — the host's scheduler/default decides, and any
machine can pin one by adding a model: line locally. This keeps the set
portable across vendors and future model generations.
npx claudepluginhub g-cqd/skillsInter-Claude messaging over MCP — also exposes the claude/channel capability so peer messages push into your session in real time (no hook polling).
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer