菜单
Guidelines for web development projects using JavaScript/TypeScript frameworks. Activate when working with web projects, package.json, npm/yarn/pnpm, React, Next.js, Vue, Angular, Svelte, or other web frameworks, frontend components, or Node.js applications.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Language-agnostic API design patterns covering REST and GraphQL, including resource naming, HTTP methods, status codes, versioning, pagination, filtering, authentication, error handling, and schema design. Activate when working with APIs, REST endpoints, GraphQL schemas, API documentation, OpenAPI/Swagger, JWT, OAuth2, endpoint design, API versioning, rate limiting, or GraphQL resolvers.
Git workflow and commit guidelines. Trigger keywords: git, commit, push, .git, version control. MUST be activated before ANY git commit, push, or version control operation. Includes security scanning for secrets (API keys, tokens, .env files), commit message formatting with HEREDOC, logical commit grouping (docs, test, feat, fix, refactor, chore, build, deps), push behavior rules, safety rules for hooks and force pushes, and CRITICAL safeguards for destructive operations (filter-branch, gc --prune, reset --hard). Activate when user requests committing changes, pushing code, creating commits, rewriting history, or performing any git operations including analyzing uncommitted changes.
Testing workflow patterns and quality standards. Activate when working with tests, test files, test directories, code quality tools, coverage reports, or testing tasks. Includes zero-warnings policy, targeted testing during development, mocking patterns, and best practices across languages.
Ansible automation workflow guidelines. Activate when working with Ansible playbooks, ansible-playbook, inventory files (.yml, .ini), or Ansible-specific patterns.
Claude Code AI-assisted development workflow. Activate when discussing Claude Code usage, AI-assisted coding, prompting strategies, or Claude Code-specific patterns.
Guidelines for containerized projects using Docker, Dockerfile, docker-compose, container, and containerization. Covers multi-stage builds, security, signal handling, entrypoint scripts, and deployment workflows.
| name | web-projects |
| description | Guidelines for web development projects using JavaScript/TypeScript frameworks. Activate when working with web projects, package.json, npm/yarn/pnpm, React, Next.js, Vue, Angular, Svelte, or other web frameworks, frontend components, or Node.js applications. |
Auto-activate when: Working with package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, tsconfig.json, .eslintrc*, vite.config.*, next.config.*, *.jsx, *.tsx, *.vue, *.svelte, or when user mentions React, Next.js, Vue, Angular, Svelte, npm, yarn, pnpm, or frontend development.
Guidelines for modern JavaScript/TypeScript web projects.
package.json for dependencies and scriptspackage-lock.json, yarn.lock, pnpm-lock.yamlLook for framework-specific configuration files:
next.config.js, next.config.tsvite.config.js, vite.config.tspackage.json dependenciesvue.config.js, vite.config.ts with Vue pluginangular.jsonsvelte.config.jsRespect the project's package manager:
npm install, npm run, npm testyarn install, yarn, yarn testpnpm install, pnpm run, pnpm testDetection: Lock file or config (.npmrc, .yarnrc, pnpm-workspace.yaml)
Check package.json "scripts" section for:
dev or start - Development serverbuild - Production buildtest - Run testslint - Lintingformat - Code formattingpackage.json or dedicated files.test.js, .spec.ts, etc.)Identify and follow the project's styling method:
.module.css)tailwind.config.js).scss files)tsconfig.json - TypeScript configuration.eslintrc - Linting rules.prettierrc - Code formattingjest.config.js or vitest.config.ts - Test configuration.env.local, .env.development - Environment variablesCommon mistakes to avoid:
Note: Web projects vary greatly - always check the project's specific configuration and patterns before making assumptions.