project-bootstrapper by ersinkoc/project-bootstrap
npx skills add https://github.com/ersinkoc/project-bootstrap --skill project-bootstrapper理念:在编写任何代码之前,定义代码必须如何编写。在设计时预防错误,而非在运行时发现错误。
这是一个元技能——它不编写应用程序代码。它生成规则、模式、护栏和质量标准,这些将在此后由任何开发者或 AI 助手编写的所有代码中强制执行。
[想法] → [访谈] → [技术栈] → [技能图谱] → [生成技能] → [验证] → [代码]
此技能在以下情况下激活:
在生成任何技能之前,您必须按顺序阅读这些参考文件:
references/skill-catalog.md — 包含 40 多个技能领域的完整目录references/skill-template.md — 每个技能必须遵循的通用模板references/generation-guide.md — 包含代码的特定领域生成指南广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
references/quality-standards.mdreferences/cross-cutting-concerns.md — 适用于所有技能的跨领域规则提取或询问以下信息:
是什么(产品):
规模多大(规模):
如何实现(约束条件):
如果用户已经提供了详细信息,请从他们的消息中提取答案,而不是提问。只询问缺失且真正需要用于技术栈决策的信息。
根据答案,推荐一个完整的技术栈。
这是不可协商的。在提出任何技术之前,您必须通过实时查找验证其最新稳定版本。
⚠️ 关键提示:AI 模型的知识存在截止日期。软件包生态系统每天都在发展。使用过时版本生成的技能将产生易受攻击、已弃用的代码。
研究协议(对每项技术执行):
使用可用工具(按优先级顺序):
WebSearch: "{package} latest stable version {current_year}"WebFetch: 官方文档站点(例如 nextjs.org、python.org、go.dev)resolve-library-id → query-docs 获取变更日志提取确切版本:
主版本.次版本.修订版本(例如 Next.js 16.1.0)记录验证信息:
技术:Next.js 版本:16.1.0 验证方式:nextjs.org/blog 验证日期:2026-03-09 发布日期:2026-02-15 Node 要求:>= 22.0.0
硬性规则:
package.json、requirements.txt、Cargo.toml 等)⚠️ 版本未验证——必须确认废弃检测:
示例研究查询:
"next.js latest version" → nextjs.org 或 npm"postgresql latest stable release" → postgresql.org"tailwind css latest version" → tailwindcss.com 或 npm组织成层次化的决策表:
┌──────────────────────────────────────────────────────────────────────┐
│ 技术栈提案(版本已验证:{date}) │
├────────────────┬─────────────────────────────────┬───────────────────┤
│ 类别 │ 选择 │ 理由 │
├────────────────┼─────────────────────────────────┼───────────────────┤
│ 编程语言 │ {名称} {已验证的最新版本} │ │
│ 运行时 │ {名称} {已验证的最新版本} │ │
│ 框架 │ {名称} {已验证的最新版本} │ │
│ 数据库 │ {名称} {已验证的最新版本} │ │
│ ORM/查询 │ {名称} {已验证的最新版本} │ │
│ 缓存 │ {名称} {已验证的最新版本} │ │
│ 认证 │ {名称} {已验证的最新版本} │ │
│ UI 库 │ {名称} {已验证的最新版本} │ │
│ CSS/样式 │ {名称} {已验证的最新版本} │ │
│ 状态管理 │ {名称} {已验证的最新版本} │ │
│ API 风格 │ {名称} {已验证的最新版本} │ │
│ 验证 │ {名称} {已验证的最新版本} │ │
│ 测试 │ {名称} {已验证的最新版本} │ │
│ CI/CD │ {名称} {已验证的最新版本} │ │
│ 托管 │ {名称} │ │
│ 监控 │ {名称} {已验证的最新版本} │ │
│ 邮件 │ {名称} {已验证的最新版本} │ │
│ 文件存储 │ {名称} │ │
│ 搜索 │ {名称} {已验证的最新版本} │ │
│ 队列/作业 │ {名称} {已验证的最新版本} │ │
│ 分析 │ {名称} {已验证的最新版本} │ │
└────────────────┴─────────────────────────────────┴───────────────────┘
仅包含与项目相关的行。每个选择都有一行理由说明。
在继续之前等待用户确认。 技术栈决定了后续的一切。
对于每种语言,验证这些工具的版本:
┌─────────────────────────────────────────────────────────────────────────┐
│ 语言 │ 核心版本 │ 包管理器 │ 代码检查器 │ 测试器 │
├─────────────────────────────────────────────────────────────────────────┤
│ TypeScript │ 最新 Node │ npm/pnpm 10+ │ ESLint 9+ │ Vitest 3+ │
│ Python │ 3.12+ │ pip/uv │ Ruff 0.9+ │ pytest 8+ │
│ Go │ 1.24+ │ go modules │ golangci │ go test │
│ Rust │ 最新 │ cargo │ clippy │ cargo test │
│ Java │ 21 LTS │ Maven/Gradle │ checkstyle │ JUnit 5 │
│ Kotlin │ 2.1+ │ Gradle │ ktlint │ Kotest │
│ C# │ .NET 9+ │ NuGet │ analyzers │ xUnit │
│ Swift │ 6.0+ │ SwiftPM │ swiftlint │ XCTest │
│ PHP │ 8.4+ │ Composer 2+ │ PHPStan 2+ │ PHPUnit 11+ │
│ Ruby │ 3.4+ │ Bundler │ RuboCop │ RSpec │
└─────────────────────────────────────────────────────────────────────────┘
多语言项目:为每种语言生成单独的 {语言}-standards 技能。
基于已确认的技术栈,生成技能图谱——要生成的技能完整列表。阅读 references/skill-catalog.md 获取完整领域目录。
强制技能(为每个项目生成):
project-architecture — 文件夹结构、模块边界、命名{language}-standards — 语言级别的编码规则security-hardening — 深度防御、输入/输出、密钥、依赖项error-handling — 错误层次结构、传播、恢复data-validation — 模式验证、清理、边界testing-strategy — 测试类型、覆盖率、模拟、夹具performance-optimization — 预算、性能分析、缓存、懒加载git-workflow — 分支、提交、PR、发布documentation-standards — 代码文档、API 文档、README、架构决策记录privacy-compliance — 个人身份信息处理、数据生命周期、同意、GDPR/CCPAdependency-management — 版本控制、审计、更新策略、锁定文件条件技能(当项目需要时生成):
{framework}-patterns — 框架特定的约定database-design — 模式、迁移、索引、查询api-design — 端点、版本控制、分页、速率限制ui-engineering — 组件、样式、响应式、无障碍state-management — 客户端/服务器/URL/表单状态模式auth-patterns — 认证、授权、会话、令牌、多因素认证devops-pipeline — CI/CD、环境、部署、回滚observability — 日志记录、指标、追踪、告警accessibility-standards — WCAG 合规性、ARIA、键盘导航internationalization — 国际化、本地化、从右到左、复数形式payment-integration — 计费、订阅、Webhook、PCIfile-handling — 上传、存储、处理、CDNrealtime-system — WebSocket、服务器发送事件、发布/订阅、在线状态email-system — 事务性邮件、模板、队列、合规性search-implementation — 引擎、索引、相关性、自动补全background-jobs — 队列、调度、重试、死信队列mobile-patterns — 导航、离线、推送通知、深度链接desktop-patterns — 窗口管理、托盘、进程间通信、自动更新cli-design — 命令、参数、输出、配置、Shell 补全monorepo-management — 工作区、边界、版本控制ai-integration — 大语言模型调用、提示词、流式传输、成本、安全性caching-strategy — 层级、失效、CDN、陈旧时重新验证rate-limiting — 算法、层级、头部、分布式限制feature-flags — 发布、定向、紧急开关、清理migration-strategy — 零停机时间、数据迁移、向后兼容性container-orchestration — Docker、Kubernetes、健康检查、资源infrastructure-as-code — Terraform/Pulumi、状态、模块event-driven-architecture — 事件溯源、命令查询职责分离、Sagagraphql-patterns — 模式设计、解析器、N+1 问题、批处理websocket-patterns — 连接管理、房间、重新连接microservice-patterns — 服务边界、通信、服务发现按生成层级组织呈现技能图谱。等待用户确认。
按严格的依赖顺序生成技能——后面的技能可以引用前面的技能:
层级 0: project-architecture
(定义文件夹结构、模块边界、命名——其他所有内容都引用此技能)
层级 1: {language}-standards, git-workflow, documentation-standards
(基础的编码和流程标准)
层级 2: security-hardening, error-handling, data-validation, privacy-compliance,
dependency-management
(跨领域的安全和质量关注点)
层级 3: database-design, api-design, auth-patterns, caching-strategy
(数据和通信层)
层级 4: {framework}-patterns, ui-engineering, state-management,
accessibility-standards
(表示和交互层)
层级 5: testing-strategy, performance-optimization
(质量保证——需要所有其他技能先存在)
层级 6: devops-pipeline, observability, container-orchestration,
infrastructure-as-code
(运维层)
层级 7: 领域特定技能(支付、国际化、邮件、搜索、实时系统、
后台作业、功能开关、AI 等)
(仅相关领域)
每个生成的技能必须产生以下文件树:
{技能名称}/
├── SKILL.md # 主要说明(< 500 行)
├── references/
│ ├── patterns.md # 已批准的模式,包含完整代码示例
│ ├── anti-patterns.md # 禁止的模式,包含严重性 + 解释
│ └── checklist.md # 提交前/合并前的验证检查清单
└── templates/ # (可选)代码模板、配置
└── *.template.*
阅读 references/skill-template.md 获取确切的骨架。阅读 references/generation-guide.md 获取特定领域的内容要求。
每个生成的技能必须包含:
生成所有技能后,验证:
{项目根目录}/
├── .claude/
│ └── skills/
│ ├── project-architecture/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── {language}-standards/
│ │ ├── SKILL.md
│ │ ├── references/
│ │ └── templates/
│ ├── security-hardening/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── ... (所有生成的技能)
│ └── _bootstrap-manifest.json
├── .gitignore
└── ... (应用程序代码在引导之后)
生成 _bootstrap-manifest.json:
{
"project": "{名称}",
"bootstrapped_at": "{ISO-8601}",
"tech_stack": {},
"skills_generated": [
{
"name": "{技能名称}",
"path": ".claude/skills/{技能名称}/",
"layer": 0,
"depends_on": [],
"domains_covered": ["architecture", "folder-structure", "naming"]
}
],
"total_skills": 0,
"total_rules": 0,
"total_anti_patterns": 0,
"coverage": {
"security": true,
"performance": true,
"privacy": true,
"testing": true,
"accessibility": true,
"error_handling": true,
"documentation": true,
"observability": true
}
}
在宣布引导完成之前,使用JavaScript 和 Python 验证器运行验证:
depends_on 目标都存在JavaScript/Node.js(默认):
# 验证所有技能
node scripts/validate_bootstrap.js .claude/skills/
# 检查版本一致性
node scripts/version_checker.js .claude/skills/
# 检查合规性(如果有源代码)
node scripts/check_skill_compliance.js src/
Python(替代方案):
# 验证所有技能
python scripts/validate_bootstrap.py .claude/skills/
# 检查版本一致性
python scripts/version_checker.py .claude/skills/
# 检查合规性
python scripts/check_skill_compliance.py src/
呈现一个汇总表:
╔═══════════════════════════════════════════════════╗
║ 引导完成 ║
╠═══════════════════════════════════════════════════╣
║ 项目:{名称} ║
║ 生成的技能:{N} ║
║ 总规则数:{N} ║
║ 总反模式数:{N} ║
║ 安全规则数:{N} ║
║ 性能预算数:{N} ║
║ 隐私控制数:{N} ║
║ 测试要求数:{N} ║
╠═══════════════════════════════════════════════════╣
║ ✅ 未发现矛盾 ║
║ ✅ 所有依赖已解析 ║
║ ✅ 完整覆盖率已验证 ║
║ ✅ 验证器已通过 ║
║ ✅ 准备开始编码 ║
╚═══════════════════════════════════════════════════╝
关键提示: 引导之后,project-manager 技能确保持续的合规性:
JavaScript:
# 检查代码合规性
node scripts/check_skill_compliance.js src/
# 分析技能覆盖率
node scripts/analyze_skill_coverage.js src/
# 生成周报
node scripts/generate_compliance_report.js --week
Python:
# 检查代码合规性
python scripts/check_skill_compliance.py src/
# 分析技能覆盖率
python scripts/analyze_skill_coverage.py src/
# 生成周报
python scripts/generate_compliance_report.py --week
设置自动化的合规性检查:
# 安装提交前钩子
cp scripts/pre-commit.example .git/hooks/pre-commit
chmod +x .git/hooks/pre-commit
结果: 技能成为活跃的护栏,而不仅仅是文档。
引导和验证之后:
.claude/skills/ 中生成project-manager 技能将监控合规性创建或编辑的每个文件都将自动受相关技能管理,并由 project-manager 技能强制执行。
生成后始终运行验证器:
# 选项 1:JavaScript/Node.js(推荐,无需 Python)
node scripts/validate_bootstrap.js .claude/skills/
# 选项 2:Python(如果可用)
python scripts/validate_bootstrap.py .claude/skills/
验证必须通过才能宣布引导完成。
始终生成project-manager 技能 以及其他技能。它:
关键提示: 每项技术的版本必须通过实时查找验证:
WebSearch、WebFetch 或 Context7交接之前:
.claude/skills/ 中生成project-manager 技能_bootstrap-manifest.json 已创建每周安装次数
71
仓库
GitHub 星标数
64
首次出现
2026 年 3 月 9 日
安全审计
安装于
kimi-cli70
gemini-cli70
amp70
cline70
github-copilot70
codex70
Philosophy : Define how code must be written before writing any code. Bugs are prevented at design time, not discovered at runtime.
This is a meta-skill — it does not write application code. It generates the rules, patterns, guardrails, and quality standards that govern all code written afterward, by any developer or AI assistant.
[Idea] → [Interview] → [Tech Stack] → [Skill Map] → [Generate Skills] → [Validate] → [Code]
This skill activates when:
Before generating ANY skills, you MUST read these reference files in order:
references/skill-catalog.md — Full catalog of 40+ skill domainsreferences/skill-template.md — Universal template every skill must followreferences/generation-guide.md — Domain-specific generation instructions with codereferences/quality-standards.md — Quality checklist for generated skillsreferences/cross-cutting-concerns.md — Rules that span all skillsExtract or ask about:
What (Product):
How Big (Scale):
How (Constraints):
If the user already provided details , extract answers from their message instead of asking. Only ask what's missing and genuinely needed to make tech stack decisions.
Based on the answers, recommend a complete tech stack.
This is NON-NEGOTIABLE. Before proposing ANY technology, you MUST verify its latest stable version via real-time lookup.
⚠️ CRITICAL : AI models have knowledge cutoffs. Package ecosystems evolve daily. A skill generated with outdated versions will produce vulnerable, deprecated code.
Research Protocol (execute for EVERY technology):
Use available tools (in priority order):
WebSearch: "{package} latest stable version {current_year}"WebFetch: Official docs site (e.g., nextjs.org, python.org, go.dev)resolve-library-id → query-docs for changelogExtract exact version :
HARDCORE RULES :
package.json, requirements.txt, Cargo.toml, etc.)⚠️ VERSION UNVERIFIED — MUST CONFIRMAbandonment Detection :
Example research queries :
"next.js latest version" → nextjs.org or npm"postgresql latest stable release" → postgresql.org"tailwind css latest version" → tailwindcss.com or npmOrganize as a layered decision table:
┌──────────────────────────────────────────────────────────────────────┐
│ TECH STACK PROPOSAL (versions verified: {date}) │
├────────────────┬─────────────────────────────────┬───────────────────┤
│ Category │ Choice │ Rationale │
├────────────────┼─────────────────────────────────┼───────────────────┤
│ Language │ {name} {verified latest version} │ │
│ Runtime │ {name} {verified latest version} │ │
│ Framework │ {name} {verified latest version} │ │
│ Database │ {name} {verified latest version} │ │
│ ORM/Query │ {name} {verified latest version} │ │
│ Cache │ {name} {verified latest version} │ │
│ Auth │ {name} {verified latest version} │ │
│ UI Library │ {name} {verified latest version} │ │
│ CSS/Styling │ {name} {verified latest version} │ │
│ State Mgmt │ {name} {verified latest version} │ │
│ API Style │ {name} {verified latest version} │ │
│ Validation │ {name} {verified latest version} │ │
│ Testing │ {name} {verified latest version} │ │
│ CI/CD │ {name} {verified latest version} │ │
│ Hosting │ {name} │ │
│ Monitoring │ {name} {verified latest version} │ │
│ Email │ {name} {verified latest version} │ │
│ File Storage │ {name} │ │
│ Search │ {name} {verified latest version} │ │
│ Queue/Jobs │ {name} {verified latest version} │ │
│ Analytics │ {name} {verified latest version} │ │
└────────────────┴─────────────────────────────────┴───────────────────┘
Only include rows relevant to the project. Each choice gets a one-line rationale.
Wait for user confirmation before proceeding. The tech stack determines everything that follows.
For EVERY language, verify these tool versions:
┌─────────────────────────────────────────────────────────────────────────┐
│ LANGUAGE │ CORE VERSION │ PACKAGE MANAGER │ LINTER │ TESTER │
├─────────────────────────────────────────────────────────────────────────┤
│ TypeScript │ Latest Node │ npm/pnpm 10+ │ ESLint 9+ │ Vitest 3+ │
│ Python │ 3.12+ │ pip/uv │ Ruff 0.9+ │ pytest 8+ │
│ Go │ 1.24+ │ go modules │ golangci │ go test │
│ Rust │ Latest │ cargo │ clippy │ cargo test │
│ Java │ 21 LTS │ Maven/Gradle │ checkstyle │ JUnit 5 │
│ Kotlin │ 2.1+ │ Gradle │ ktlint │ Kotest │
│ C# │ .NET 9+ │ NuGet │ analyzers │ xUnit │
│ Swift │ 6.0+ │ SwiftPM │ swiftlint │ XCTest │
│ PHP │ 8.4+ │ Composer 2+ │ PHPStan 2+ │ PHPUnit 11+ │
│ Ruby │ 3.4+ │ Bundler │ RuboCop │ RSpec │
└─────────────────────────────────────────────────────────────────────────┘
Polyglot Projects : Generate separate {language}-standards skills for each language.
Based on confirmed tech stack, produce a skill map — the complete list of skills to generate. Read references/skill-catalog.md for the full domain catalog.
Mandatory skills (generated for every project):
project-architecture — folder structure, module boundaries, naming{language}-standards — language-level coding rulessecurity-hardening — defense in depth, input/output, secrets, depserror-handling — error hierarchy, propagation, recoverydata-validation — schema validation, sanitization, boundariestesting-strategy — test types, coverage, mocking, fixturesperformance-optimization — budgets, profiling, caching, lazy loadinggit-workflow — branches, commits, PRs, releasesdocumentation-standards — code docs, API docs, READMs, ADRsConditional skills (generated when the project needs them):
{framework}-patterns — framework-specific conventionsdatabase-design — schema, migrations, indexing, queriesapi-design — endpoints, versioning, pagination, rate limitingui-engineering — components, styling, responsive, a11ystate-management — client/server/URL/form state patternsauth-patterns — authn, authz, sessions, tokens, MFAdevops-pipeline — CI/CD, environments, deployment, rollbackobservability — logging, metrics, tracing, alertingaccessibility-standards — WCAG compliance, ARIA, keyboard navPresent the skill map organized by generation layer. Wait for user confirmation.
Generate skills in strict dependency order — later skills can reference earlier ones:
Layer 0: project-architecture
(defines folder structure, module boundaries, naming — everything else references this)
Layer 1: {language}-standards, git-workflow, documentation-standards
(foundational coding and process standards)
Layer 2: security-hardening, error-handling, data-validation, privacy-compliance,
dependency-management
(cross-cutting safety and quality concerns)
Layer 3: database-design, api-design, auth-patterns, caching-strategy
(data and communication layer)
Layer 4: {framework}-patterns, ui-engineering, state-management,
accessibility-standards
(presentation and interaction layer)
Layer 5: testing-strategy, performance-optimization
(quality assurance — needs all other skills to exist first)
Layer 6: devops-pipeline, observability, container-orchestration,
infrastructure-as-code
(operations layer)
Layer 7: Domain-specific skills (payments, i18n, email, search, realtime,
background-jobs, feature-flags, AI, etc.)
(only relevant domains)
Every generated skill MUST produce this file tree:
{skill-name}/
├── SKILL.md # Main instructions (< 500 lines)
├── references/
│ ├── patterns.md # Approved patterns with full code examples
│ ├── anti-patterns.md # Forbidden patterns with severity + explanation
│ └── checklist.md # Pre-commit/pre-merge verification checklist
└── templates/ # (optional) Code templates, configs
└── *.template.*
Read references/skill-template.md for the exact skeleton. Read references/generation-guide.md for domain-specific content requirements.
Every generated skill MUST contain:
After generating all skills, verify:
{project-root}/
├── .claude/
│ └── skills/
│ ├── project-architecture/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── {language}-standards/
│ │ ├── SKILL.md
│ │ ├── references/
│ │ └── templates/
│ ├── security-hardening/
│ │ ├── SKILL.md
│ │ └── references/
│ ├── ... (all generated skills)
│ └── _bootstrap-manifest.json
├── .gitignore
└── ... (application code comes AFTER bootstrap)
Generate _bootstrap-manifest.json:
{
"project": "{name}",
"bootstrapped_at": "{ISO-8601}",
"tech_stack": {},
"skills_generated": [
{
"name": "{skill-name}",
"path": ".claude/skills/{skill-name}/",
"layer": 0,
"depends_on": [],
"domains_covered": ["architecture", "folder-structure", "naming"]
}
],
"total_skills": 0,
"total_rules": 0,
"total_anti_patterns": 0,
"coverage": {
"security": true,
"performance": true,
"privacy": true,
"testing": true,
"accessibility": true,
"error_handling": true,
"documentation": true,
"observability": true
}
}
Before declaring bootstrap complete, run validation using both JavaScript and Python validators :
depends_on targets existJavaScript/Node.js (default):
# Validate all skills
node scripts/validate_bootstrap.js .claude/skills/
# Check version consistency
node scripts/version_checker.js .claude/skills/
# Check compliance (if you have source code)
node scripts/check_skill_compliance.js src/
Python (alternative):
# Validate all skills
python scripts/validate_bootstrap.py .claude/skills/
# Check version consistency
python scripts/version_checker.py .claude/skills/
# Check compliance
python scripts/check_skill_compliance.py src/
Present a summary table:
╔═══════════════════════════════════════════════════╗
║ BOOTSTRAP COMPLETE ║
╠═══════════════════════════════════════════════════╣
║ Project: {name} ║
║ Skills Generated: {N} ║
║ Total Rules: {N} ║
║ Total Anti-Patterns: {N} ║
║ Security Rules: {N} ║
║ Performance Budgets: {N} ║
║ Privacy Controls: {N} ║
║ Test Requirements: {N} ║
╠═══════════════════════════════════════════════════╣
║ ✅ No contradictions found ║
║ ✅ All dependencies resolved ║
║ ✅ Full coverage verified ║
║ ✅ Validators passed ║
║ ✅ Ready to code ║
╚═══════════════════════════════════════════════════╝
CRITICAL: After bootstrap, the project-manager skill ensures ongoing compliance:
JavaScript:
# Check code compliance
node scripts/check_skill_compliance.js src/
# Analyze skill coverage
node scripts/analyze_skill_coverage.js src/
# Generate weekly report
node scripts/generate_compliance_report.js --week
Python:
# Check code compliance
python scripts/check_skill_compliance.py src/
# Analyze skill coverage
python scripts/analyze_skill_coverage.py src/
# Generate weekly report
python scripts/generate_compliance_report.py --week
Set up automated compliance checking:
# Install pre-commit hook
cp scripts/pre-commit.example .git/hooks/pre-commit
chmod +x .git/hooks/pre-commit
Result: Skills become active guardrails , not just documentation.
After bootstrap and validation:
.claude/skills/project-manager skill will monitor complianceEvery file created or edited will be governed by the relevant skills automatically, enforced by the project-manager skill.
ALWAYS run validators after generation:
# Option 1: JavaScript/Node.js (recommended, no Python needed)
node scripts/validate_bootstrap.js .claude/skills/
# Option 2: Python (if available)
python scripts/validate_bootstrap.py .claude/skills/
Validation must pass before declaring bootstrap complete.
ALWAYS generate theproject-manager skill alongside other skills. It:
CRITICAL: Every technology version MUST be verified via real-time lookup:
WebSearch, WebFetch, or Context7Before handoff:
.claude/skills/project-manager skill included_bootstrap-manifest.json createdWeekly Installs
71
Repository
GitHub Stars
64
First Seen
Mar 9, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
kimi-cli70
gemini-cli70
amp70
cline70
github-copilot70
codex70
Skills CLI 使用指南:AI Agent 技能包管理器安装与管理教程
46,600 周安装
Major.Minor.PatchNext.js 16.1.0Document verification :
Technology: Next.js Version: 16.1.0 Verified via: nextjs.org/blog Verification date: 2026-03-09 Release date: 2026-02-15 Node requirement: >= 22.0.0
privacy-compliance — PII handling, data lifecycle, consent, GDPR/CCPAdependency-management — versioning, auditing, update policy, lockfilesinternationalization — i18n, l10n, RTL, pluralizationpayment-integration — billing, subscriptions, webhooks, PCIfile-handling — uploads, storage, processing, CDNrealtime-system — WebSocket, SSE, pub/sub, presenceemail-system — transactional, templates, queue, compliancesearch-implementation — engine, indexing, relevance, autocompletebackground-jobs — queues, scheduling, retry, dead lettermobile-patterns — navigation, offline, push, deep linksdesktop-patterns — window mgmt, tray, IPC, auto-updatecli-design — commands, args, output, config, shell completionmonorepo-management — workspaces, boundaries, versioningai-integration — LLM calls, prompts, streaming, cost, safetycaching-strategy — layers, invalidation, CDN, stale-while-revalidaterate-limiting — algorithms, tiers, headers, distributed limitingfeature-flags — rollout, targeting, kill switches, cleanupmigration-strategy — zero-downtime, data migrations, backward compatcontainer-orchestration — Docker, K8s, health checks, resourcesinfrastructure-as-code — Terraform/Pulumi, state, modulesevent-driven-architecture — event sourcing, CQRS, sagasgraphql-patterns — schema design, resolvers, N+1, batchingwebsocket-patterns — connection management, rooms, reconnectionmicroservice-patterns — service boundaries, communication, discovery