mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-16 16:36:53 +08:00
fix(skills): move top-level origin frontmatter key under metadata
The official Agent Skills spec (agentskills.io/specification) whitelists exactly 6 top-level frontmatter keys (name/description/license/compatibility/metadata/ allowed-tools). A top-level `origin` key fails the official validator (anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate). This moves `origin: X` -> `metadata.origin: X` across the canonical skills/ tree, preserving each value verbatim. Frontmatter-only, minimal diff. - 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata) - origin values preserved verbatim (verified 251/251) - YAML validated on all changed files - scoped to canonical skills/ only (docs/<lang> translations + tool mirrors .cursor/.kiro/.agents left untouched; presumably regenerated from canonical) Addresses #2233
This commit is contained in:
BERORINPO
parent
fec84fcf19
commit
db7f2a6fd5
@ -2,7 +2,8 @@
|
||||
name: accessibility
|
||||
description: Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA
|
||||
standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Accessibility (WCAG 2.2)
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: agent-architecture-audit
|
||||
description: Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature.
|
||||
origin: oh-my-agent-check
|
||||
metadata:
|
||||
origin: oh-my-agent-check
|
||||
tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: agent-eval
|
||||
description: Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: agent-harness-construction
|
||||
description: Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Agent Harness Construction
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: agent-introspection-debugging
|
||||
description: Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Agent Introspection Debugging
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: agent-payment-x402
|
||||
description: Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Agent Payment Execution (x402)
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: agent-sort
|
||||
description: Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Agent Sort
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: agentic-engineering
|
||||
description: Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Agentic Engineering
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: agentic-os
|
||||
description: Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Agentic OS
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: ai-first-engineering
|
||||
description: Engineering operating model for teams where AI agents generate a large share of implementation output.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# AI-First Engineering
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: ai-regression-testing
|
||||
description: Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# AI Regression Testing
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: android-clean-architecture
|
||||
description: Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Android Clean Architecture
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: angular-developer
|
||||
description: Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Angular Developer Guidelines
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: api-connector-builder
|
||||
description: Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.
|
||||
origin: ECC direct-port adaptation
|
||||
metadata:
|
||||
origin: ECC direct-port adaptation
|
||||
version: "1.0.0"
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: api-design
|
||||
description: REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# API Design Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: architecture-decision-records
|
||||
description: Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments, records context, alternatives considered, and rationale. Maintains an ADR log so future developers understand why the codebase is shaped the way it is.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Architecture Decision Records
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: article-writing
|
||||
description: Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Article Writing
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: automation-audit-ops
|
||||
description: Evidence-first automation inventory and overlap audit workflow for ECC. Use when the user wants to know which jobs, hooks, connectors, MCP servers, or wrappers are live, broken, redundant, or missing before fixing anything.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Automation Audit Ops
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: autonomous-agent-harness
|
||||
description: Transform Claude Code into a fully autonomous agent system with persistent memory, scheduled operations, computer use, and task queuing. Replaces standalone agent frameworks (Hermes, AutoGPT) by leveraging Claude Code's native crons, dispatch, MCP tools, and memory. Use when the user wants continuous autonomous operation, scheduled tasks, or a self-directing agent loop.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Autonomous Agent Harness
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: autonomous-loops
|
||||
description: "Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems."
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Autonomous Loops Skill
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: backend-patterns
|
||||
description: Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Backend Development Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: benchmark-optimization-loop
|
||||
description: Use when the user asks to make something faster, try many variants, run recursive optimization, benchmark latency/throughput/cost, or choose the best implementation by repeated measured tests.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: benchmark
|
||||
description: Use this skill to measure performance baselines, detect regressions before/after PRs, and compare stack alternatives.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Benchmark — Performance Baseline & Regression Detection
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: blender-motion-state-inspection
|
||||
description: Use this skill when inspecting Blender characters, rigs, poses, animation retargeting, ground contact, facing direction, or model-vs-motion alignment where screenshots alone are not enough.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
---
|
||||
|
||||
|
||||
@ -10,7 +10,8 @@ description: >-
|
||||
complex multi-PR task, or describes work that needs multiple sessions.
|
||||
DO NOT TRIGGER when: task is completable in a single PR or fewer
|
||||
than 3 tool calls, or user says "just do it".
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Blueprint — Construction Plan Generator
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: brand-voice
|
||||
description: Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Brand Voice
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: browser-qa
|
||||
description: Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Browser QA — Automated Visual Testing & Interaction
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: bun-runtime
|
||||
description: Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Bun Runtime
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: canary-watch
|
||||
description: Use this skill to monitor and verify a deployed URL after releases — checks HTTP endpoints, SSE streams, static assets, console errors, and performance regressions after deploys, merges, or dependency upgrades. Smoke / canary / post-deploy verification.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Canary Watch — Post-Deploy Monitoring
|
||||
|
||||
@ -10,8 +10,8 @@ description: >
|
||||
license: Apache-2.0
|
||||
version: 1.0.0
|
||||
homepage: https://github.com/affaan-m/everything-claude-code
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
author: evos
|
||||
clawdbot:
|
||||
emoji: ""
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: cisco-ios-patterns
|
||||
description: Cisco IOS and IOS-XE review patterns for show commands, config hierarchy, wildcard masks, ACL placement, interface hygiene, and safe change-window verification.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Cisco IOS Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: ck
|
||||
description: Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
version: 2.0.0
|
||||
author: sreedhargs89
|
||||
repo: https://github.com/sreedhargs89/context-keeper
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: claude-devfleet
|
||||
description: Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Claude DevFleet Multi-Agent Orchestration
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: click-path-audit
|
||||
description: "Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores."
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# /click-path-audit — Behavioural Flow Audit
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: clickhouse-io
|
||||
description: ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# ClickHouse Analytics Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: code-tour
|
||||
description: Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Code Tour
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: codebase-onboarding
|
||||
description: Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Codebase Onboarding
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: codehealth-mcp
|
||||
description: Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit/PR.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Code Health MCP (CodeScene)
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: coding-standards
|
||||
description: Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Coding Standards & Best Practices
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: compose-multiplatform-patterns
|
||||
description: Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Compose Multiplatform Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: config-gc
|
||||
description: Garbage collection for your Claude Code configuration. Periodically scans ~/.claude (skills, memory, hooks, permissions, MCP servers, caches) for redundant, stale, orphaned, or low-value items, then walks the user through a confirm-each-deletion cleanup. Use when the user says "clean up my config", "config GC", "too many skills", "audit my setup", "my .claude is bloated", or asks for a periodic config review.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Config GC — Garbage Collection for Claude Code Setups
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: configure-ecc
|
||||
description: Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Configure Everything Claude Code (ECC)
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: connections-optimizer
|
||||
description: Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice. Use when the user wants to clean up following lists, grow toward current priorities, or rebalance a social graph around higher-signal relationships.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Connections Optimizer
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: content-engine
|
||||
description: Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Content Engine
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: content-hash-cache-pattern
|
||||
description: Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Content-Hash File Cache Pattern
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: context-budget
|
||||
description: Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Context Budget
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: continuous-agent-loop
|
||||
description: Patterns for continuous autonomous agent loops with quality gates, evals, and recovery controls.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Continuous Agent Loop
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: continuous-learning-v2
|
||||
description: Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
version: 2.1.0
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: continuous-learning
|
||||
description: "[DEPRECATED - use continuous-learning-v2] Legacy v1 stop-hook skill extractor. v2 is a strict superset with instinct-based, project-scoped, hook-reliable learning. Do not invoke v1; route continuous learning, session learning, and pattern extraction requests to continuous-learning-v2."
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Continuous Learning Skill - DEPRECATED
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: cost-aware-llm-pipeline
|
||||
description: Cost optimization patterns for LLM API usage — model routing by task complexity, budget tracking, retry logic, and prompt caching.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Cost-Aware LLM Pipeline
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: cost-tracking
|
||||
description: Track and report Claude Code token usage, spending, and budgets from a local cost-tracking database. Use when the user asks about costs, spending, usage, tokens, budgets, or cost breakdowns by project, tool, session, or date.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Cost Tracking
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: council
|
||||
description: Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Council
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: cpp-coding-standards
|
||||
description: C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# C++ Coding Standards (C++ Core Guidelines)
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: cpp-testing
|
||||
description: Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# C++ Testing (Agent Skill)
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: crosspost
|
||||
description: Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Crosspost
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: csharp-testing
|
||||
description: C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# C# Testing Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: customer-billing-ops
|
||||
description: Operate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like Stripe. Use when the user needs to help a customer, inspect subscription state, or manage revenue-impacting billing operations.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Customer Billing Ops
|
||||
|
||||
@ -11,8 +11,8 @@ description: >
|
||||
license: Apache-2.0
|
||||
version: 1.0.0
|
||||
homepage: https://github.com/affaan-m/everything-claude-code
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
author: evos
|
||||
clawdbot:
|
||||
emoji: ""
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: dart-flutter-patterns
|
||||
description: Production-ready Dart and Flutter patterns covering null safety, immutable state, async composition, widget architecture, popular state management frameworks (BLoC, Riverpod, Provider), GoRouter navigation, Dio networking, Freezed code generation, and clean architecture.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Dart/Flutter Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: dashboard-builder
|
||||
description: Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms. Use when turning metrics into a working dashboard instead of a vanity board.
|
||||
origin: ECC direct-port adaptation
|
||||
metadata:
|
||||
origin: ECC direct-port adaptation
|
||||
version: "1.0.0"
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: data-scraper-agent
|
||||
description: Build a fully automated AI-powered data collection agent for any public source — job boards, prices, news, GitHub, sports, anything. Scrapes on a schedule, enriches data with a free LLM (Gemini Flash), stores results in Notion/Sheets/Supabase, and learns from user feedback. Runs 100% free on GitHub Actions. Use when the user wants to monitor, collect, or track any public data automatically.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Data Scraper Agent
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: data-throughput-accelerator
|
||||
description: Use when large data ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, or table synchronization needs to become much faster while preserving data correctness.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: database-migrations
|
||||
description: Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Database Migration Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: deep-research
|
||||
description: Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Deep Research
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: defi-amm-security
|
||||
description: Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, CEI ordering, donation or inflation attacks, oracle manipulation, slippage, admin controls, and integer math.
|
||||
origin: ECC direct-port adaptation
|
||||
metadata:
|
||||
origin: ECC direct-port adaptation
|
||||
version: "1.0.0"
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: deployment-patterns
|
||||
description: Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Deployment Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: design-system
|
||||
description: Use this skill to generate or audit design systems, check visual consistency, and review PRs that touch styling.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Design System — Generate & Audit Visual Systems
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: django-celery
|
||||
description: Django + Celery async task patterns — configuration, task design, beat scheduling, retries, canvas workflows, monitoring, and testing. Use when adding background jobs, scheduled tasks, or async processing to a Django app.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Django + Celery Async Task Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: django-patterns
|
||||
description: Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Django Development Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: django-security
|
||||
description: Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Django Security Best Practices
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: django-tdd
|
||||
description: Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Django Testing with TDD
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: django-verification
|
||||
description: "Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR."
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Django Verification Loop
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: dmux-workflows
|
||||
description: Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# dmux Workflows
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: docker-patterns
|
||||
description: Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Docker Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: documentation-lookup
|
||||
description: Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Documentation Lookup (Context7)
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: dotnet-patterns
|
||||
description: Idiomatic C# and .NET patterns, conventions, dependency injection, async/await, and best practices for building robust, maintainable .NET applications.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# .NET Development Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: dynamic-workflow-mode
|
||||
description: "Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses."
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Dynamic Workflow Mode
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: e2e-testing
|
||||
description: Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# E2E Testing Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: ecc-guide
|
||||
description: Guide users through ECC's current agents, skills, commands, hooks, rules, install profiles, and project onboarding by reading the live repository surface before answering.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# ECC Guide
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: ecc-tools-cost-audit
|
||||
description: Evidence-first ECC Tools burn and billing audit workflow. Use when investigating runaway PR creation, quota bypass, premium-model leakage, duplicate jobs, or GitHub App cost spikes in the ECC Tools repo.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# ECC Tools Cost Audit
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: email-ops
|
||||
description: Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Email Ops
|
||||
|
||||
@ -11,8 +11,8 @@ description: >
|
||||
license: Apache-2.0
|
||||
version: 1.0.0
|
||||
homepage: https://github.com/affaan-m/everything-claude-code
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
author: evos
|
||||
clawdbot:
|
||||
emoji: ""
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: enterprise-agent-ops
|
||||
description: Operate long-lived agent workloads with observability, security boundaries, and lifecycle management.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Enterprise Agent Ops
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: error-handling
|
||||
description: Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Error Handling Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: eval-harness
|
||||
description: Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: evm-token-decimals
|
||||
description: Prevent silent decimal mismatch bugs across EVM chains. Covers runtime decimal lookup, chain-aware caching, bridged-token precision drift, and safe normalization for bots, dashboards, and DeFi tools.
|
||||
origin: ECC direct-port adaptation
|
||||
metadata:
|
||||
origin: ECC direct-port adaptation
|
||||
version: "1.0.0"
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: exa-search
|
||||
description: Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Exa Search
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: fal-ai-media
|
||||
description: Unified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# fal.ai Media Generation
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: fastapi-patterns
|
||||
description: FastAPI best practices covering project structure, Pydantic v2 schemas, dependency injection, async handlers, authentication, authorization, transactional service layers, and testing with httpx and pytest.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# FastAPI Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: finance-billing-ops
|
||||
description: Evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflow for ECC. Use when the user wants a sales snapshot, pricing comparison, duplicate-charge diagnosis, or code-backed billing reality instead of generic payments advice.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Finance Billing Ops
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: flox-environments
|
||||
description: "Create reproducible, cross-platform development environments with Flox — a declarative environment manager built on Nix. ALWAYS use this skill when the user needs to: set up a project with system-level dependencies (compilers, databases, native libraries like openssl, libvips, BLAS, LAPACK); configure reproducible toolchains for Python, Node.js, Rust, Go, C/C++, Java, Ruby, Elixir, PHP, or any language; manage environments that must work identically across macOS and Linux; pin exact package versions for a team; run local services (PostgreSQL, Redis, Kafka) alongside development tools; onboard new developers with a single command; or solve 'works on my machine' problems. Especially valuable for AI-assisted and vibe coding — Flox lets agents install tools into a project-scoped environment without sudo, system pollution, or sandbox restrictions, and the resulting environment is committed to the repo so anyone can reproduce it instantly. Use this skill even if the user doesn't mention Flox — if they describe needing reproducible, declarative, cross-platform dev environments with system packages, this is the right tool. Also use when the user mentions .flox/, manifest.toml, flox activate, or FloxHub."
|
||||
origin: Flox
|
||||
metadata:
|
||||
origin: Flox
|
||||
---
|
||||
|
||||
# Flox Environments
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: flutter-dart-code-review
|
||||
description: Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Flutter/Dart Code Review Best Practices
|
||||
|
||||
@ -4,7 +4,8 @@ description: >
|
||||
Accessibility patterns for React and Next.js — semantic HTML, ARIA attributes,
|
||||
form labeling, keyboard navigation, focus management, and screen reader support.
|
||||
Use when building any interactive UI component or form.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Frontend Accessibility Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: frontend-design-direction
|
||||
description: Set an ECC-specific frontend design direction for production UI work. Use when building or improving websites, dashboards, applications, components, landing pages, visual tools, or any web UI that needs stronger product-specific design judgment.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# Frontend Design Direction
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: frontend-patterns
|
||||
description: Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Frontend Development Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: frontend-slides
|
||||
description: Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Frontend Slides
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: fsharp-testing
|
||||
description: F# testing patterns with xUnit, FsUnit, Unquote, FsCheck property-based testing, integration tests, and test organization best practices.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# F# Testing Patterns
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: gan-style-harness
|
||||
description: "GAN-inspired Generator-Evaluator agent harness for building high-quality applications autonomously. Based on Anthropic's March 2026 harness design paper."
|
||||
origin: ECC-community
|
||||
metadata:
|
||||
origin: ECC-community
|
||||
tools: Read, Write, Edit, Bash, Grep, Glob, Task
|
||||
---
|
||||
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: gateguard
|
||||
description: Fact-forcing gate that blocks Edit/Write/Bash (including MultiEdit) and demands concrete investigation (importers, data schemas, user instruction) before allowing the action. Measurably improves output quality by +2.25 points vs ungated agents.
|
||||
origin: community
|
||||
metadata:
|
||||
origin: community
|
||||
---
|
||||
|
||||
# GateGuard — Fact-Forcing Pre-Action Gate
|
||||
|
||||
@ -1,7 +1,8 @@
|
||||
---
|
||||
name: git-workflow
|
||||
description: Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
|
||||
origin: ECC
|
||||
metadata:
|
||||
origin: ECC
|
||||
---
|
||||
|
||||
# Git Workflow Patterns
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user