Load Test Generator (Grade A)为 Claude AI 提供安全经过测试的开发技能, 级别 A。 使用 k6、Artillery 或 Locust 从 API endpoints 或 OpenAPI specs 生成负载测试脚本。

Why You Should Use This?

| Audience | Key Benefits | | -------------------- | ------------------------------------------------------------------------------------------------- | | Individual | 30%+ token savings, stop repeating standards, security guardrails, instant scaffolding | | Teams | Consistent AI behavior, day‑one onboarding, codified patterns, compounding cost savings | | Organizations | Always‑on compliance, same standards across 1,000 projects, central governance, measurable ROI |

Asked by Olga Ivanova · Jun 14, 2026

What You Can Customize?

| Section | What It Controls | Example | | ------------- | -------------------------- | ---------------------------------------------- | | project | Project identity | Name, description, repo URL | | techStack | Language, framework, tools | TypeScript + Express or Python + FastAPI | | paths | Directory structure | Where handlers, services, and common code live | | domain | Business entities | Order, Product, Customer + lifecycle states | | patterns | Code patterns | 7‑step handler flow, error handling strategy | | testing | Quality gates | 90% coverage, test/lint/type‑check commands | | database | DB conventions | Soft delete field, timestamp columns, naming | | packages | Internal packages | @your‑org scope, registry URL | | conventions | Git and workflow | Branch prefixes, commit format, PR templates |

Asked by Marisol Pena · Jun 9, 2026

What it detects?

| Category | Signals | | ------------------ | ------------------------------------------------------------------------------------------ | | Language | tsconfig.json, go.mod, Cargo.toml, requirements.txt, pom.xml, file extensions | | Framework | Dependencies in package.json / requirements.txt (React, Express, Django, Spring, etc.) | | Database | ORM configs (prisma/, sequelize, typeorm), .sql files, migration folders | | Testing | jest.config., vitest, pytest, cypress/, playwright.config. | | Infrastructure | Dockerfile, terraform/, cdk.json, serverless.yml, cloud SDK deps | | CI/CD | .github/workflows/, .gitlab-ci.yml, Jenkinsfile |

Asked by Nadia Petrova · Jun 3, 2026

What's Inside?

| 层级 | 数量 | 它做什么 | 触发方式 | | ------------- | ----- | ------------------------------------------------- | ----------------------------------- | | 规则 | 47 | 对每个AI交互都执行代码规范 | 一直开启 — 自动 | | 代理 | 62 | 为复杂任务提供专业助手 | 即时调取 — /代理名 | | 技能 | 50 | 配置有步骤的工作流程及清单 | 上下文环境 — 匹配模式时 | | 命令 | 37 | 轻量快速动作，token效率提升 | 即时调取 — /命令 | | Hooks | 12 | AI循环中的自动化脚本 | 依事件触发 — 前后操作 | | 模板 | 9 | 配置处理器、组件、测试等 | 由技能和代理引用 |

Asked by Wei Chen · May 12, 2026

How It Works?

Layer 1 — Pre-Processing: Hooks inject project context and block dangerous commands before your prompt reaches the AI. Layer 2 — Rules Engine: 47 always‑on rules enforce token efficiency, security, architecture, code standards, database conventions, and testing thresholds. Layer 3 — Specialized Processing: The right component activates — an agent, skill, or command — based on your prompt. Layer 4 — Post-Processing: Hooks validate output, auto‑format, scan for secrets, and verify coverage.

Asked by Jamal Carter · May 4, 2026