[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DFQ4H6J28ZXJ4GP7DN5DM":3,"skill-same:01M75DFQ4H6J28ZXJ4GP7DN5DM":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75DFQ4H6J28ZXJ4GP7DN5DM","everything-claude-code-conventions",null,"Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Feverything-claude-code-conventions\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: everything-claude-code-conventions\ndescription: Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.\n---\n\n# Everything Claude Code Conventions\n\n> Generated from [affaan-m\u002Feverything-claude-code](https:\u002F\u002Fgithub.com\u002Faffaan-m\u002Feverything-claude-code) on 2026-03-20\n\n## Overview\n\nThis skill teaches Claude the development patterns and conventions used in everything-claude-code.\n\n## Tech Stack\n\n- **Primary Language**: JavaScript\n- **Architecture**: hybrid module organization\n- **Test Location**: separate\n\n## When to Use This Skill\n\nActivate this skill when:\n- Making changes to this repository\n- Adding new features following established patterns\n- Writing tests that match project conventions\n- Creating commits with proper message format\n\n## Commit Conventions\n\nFollow these commit message conventions based on 500 analyzed commits.\n\n### Commit Style: Conventional Commits\n\n### Prefixes Used\n\n- `fix`\n- `test`\n- `feat`\n- `docs`\n\n### Message Guidelines\n\n- Average message length: ~65 characters\n- Keep first line concise and descriptive\n- Use imperative mood (\"Add feature\" not \"Added feature\")\n\n\n*Commit message example*\n\n```text\nfeat(rules): add C# language support\n```\n\n*Commit message example*\n\n```text\nchore(deps-dev): bump flatted (#675)\n```\n\n*Commit message example*\n\n```text\nfix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691)\n```\n\n*Commit message example*\n\n```text\ndocs: add Antigravity setup and usage guide (#552)\n```\n\n*Commit message example*\n\n```text\nmerge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer\n```\n\n*Commit message example*\n\n```text\nRevert \"Add Kiro IDE support (.kiro\u002F) (#548)\"\n```\n\n*Commit message example*\n\n```text\nAdd Kiro IDE support (.kiro\u002F) (#548)\n```\n\n*Commit message example*\n\n```text\nfeat: add block-no-verify hook for Claude Code and Cursor (#649)\n```\n\n## Architecture\n\n### Project Structure: Single Package\n\nThis project uses **hybrid** module organization.\n\n### Configuration Files\n\n- `.github\u002Fworkflows\u002Fci.yml`\n- `.github\u002Fworkflows\u002Fmaintenance.yml`\n- `.github\u002Fworkflows\u002Fmonthly-metrics.yml`\n- `.github\u002Fworkflows\u002Frelease.yml`\n- `.github\u002Fworkflows\u002Freusable-release.yml`\n- `.github\u002Fworkflows\u002Freusable-test.yml`\n- `.github\u002Fworkflows\u002Freusable-validate.yml`\n- `.opencode\u002Fpackage.json`\n- `.opencode\u002Ftsconfig.json`\n- `.prettierrc`\n- `eslint.config.js`\n- `package.json`\n\n### Guidelines\n\n- This project uses a hybrid organization\n- Follow existing patterns when adding new code\n\n## Code Style\n\n### Language: JavaScript\n\n### Naming Conventions\n\n| Element | Convention |\n|---------|------------|\n| Files | camelCase |\n| Functions | camelCase |\n| Classes | PascalCase |\n| Constants | SCREAMING_SNAKE_CASE |\n\n### Import Style: Relative Imports\n\n### Export Style: Mixed Style\n\n\n*Preferred import style*\n\n```typescript\n\u002F\u002F Use relative imports\nimport { Button } from '..\u002Fcomponents\u002FButton'\nimport { useAuth } from '.\u002Fhooks\u002FuseAuth'\n```\n\n## Testing\n\n### Test Framework\n\nNo specific test framework detected — use the repository's existing test patterns.\n\n### File Pattern: `*.test.js`\n\n### Test Types\n\n- **Unit tests**: Test individual functions and components in isolation\n- **Integration tests**: Test interactions between multiple components\u002Fservices\n\n### Coverage\n\nThis project has coverage reporting configured. Aim for 80%+ coverage.\n\n\n## Error Handling\n\n### Error Handling Style: Try-Catch Blocks\n\n\n*Standard error handling pattern*\n\n```typescript\ntry {\n  const result = await riskyOperation()\n  return result\n} catch (error) {\n  console.error('Operation failed:', error)\n  throw new Error('User-friendly message')\n}\n```\n\n## Common Workflows\n\nThese workflows were detected from analyzing commit patterns.\n\n### Database Migration\n\nDatabase schema changes with migration files\n\n**Frequency**: ~2 times per month\n\n**Steps**:\n1. Create migration file\n2. Update schema definitions\n3. Generate\u002Fupdate types\n\n**Files typically involved**:\n- `**\u002Fschema.*`\n- `migrations\u002F*`\n\n**Example commit sequence**:\n```\nfeat: implement --with\u002F--without selective install flags (#679)\nfix: sync catalog counts with filesystem (27 agents, 113 skills, 58 commands) (#693)\nfeat(rules): add Rust language rules (rebased #660) (#686)\n```\n\n### Feature Development\n\nStandard feature implementation workflow\n\n**Frequency**: ~22 times per month\n\n**Steps**:\n1. Add feature implementation\n2. Add tests for feature\n3. Update documentation\n\n**Files typically involved**:\n- `manifests\u002F*`\n- `schemas\u002F*`\n- `**\u002F*.test.*`\n- `**\u002Fapi\u002F**`\n\n**Example commit sequence**:\n```\nfeat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer\ndocs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex\u002FCursor) skill copies\nfix: address PR review — skill template (When to use, How it works, Examples), bun.lock, next build note, rust-reviewer CI note, doc-lookup privacy\u002Funcertainty\n```\n\n### Add Language Rules\n\nAdds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines.\n\n**Frequency**: ~2 times per month\n\n**Steps**:\n1. Create a new directory under rules\u002F{language}\u002F\n2. Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content\n3. Optionally reference or link to related skills\n\n**Files typically involved**:\n- `rules\u002F*\u002Fcoding-style.md`\n- `rules\u002F*\u002Fhooks.md`\n- `rules\u002F*\u002Fpatterns.md`\n- `rules\u002F*\u002Fsecurity.md`\n- `rules\u002F*\u002Ftesting.md`\n\n**Example commit sequence**:\n```\nCreate a new directory under rules\u002F{language}\u002F\nAdd coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content\nOptionally reference or link to related skills\n```\n\n### Add New Skill\n\nAdds a new skill to the system, documenting its workflow, triggers, and usage, often with supporting scripts.\n\n**Frequency**: ~4 times per month\n\n**Steps**:\n1. Create a new directory under skills\u002F{skill-name}\u002F\n2. Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.)\n3. Optionally add scripts or supporting files under skills\u002F{skill-name}\u002Fscripts\u002F\n4. Address review feedback and iterate on documentation\n\n**Files typically involved**:\n- `skills\u002F*\u002FSKILL.md`\n- `skills\u002F*\u002Fscripts\u002F*.sh`\n- `skills\u002F*\u002Fscripts\u002F*.js`\n\n**Example commit sequence**:\n```\nCreate a new directory under skills\u002F{skill-name}\u002F\nAdd SKILL.md with documentation (When to Use, How It Works, Examples, etc.)\nOptionally add scripts or supporting files under skills\u002F{skill-name}\u002Fscripts\u002F\nAddress review feedback and iterate on documentation\n```\n\n### Add New Agent\n\nAdds a new agent to the system for code review, build resolution, or other automated tasks.\n\n**Frequency**: ~2 times per month\n\n**Steps**:\n1. Create a new agent markdown file under agents\u002F{agent-name}.md\n2. Register the agent in AGENTS.md\n3. Optionally update README.md and docs\u002FCOMMAND-AGENT-MAP.md\n\n**Files typically involved**:\n- `agents\u002F*.md`\n- `AGENTS.md`\n- `README.md`\n- `docs\u002FCOMMAND-AGENT-MAP.md`\n\n**Example commit sequence**:\n```\nCreate a new agent markdown file under agents\u002F{agent-name}.md\nRegister the agent in AGENTS.md\nOptionally update README.md and docs\u002FCOMMAND-AGENT-MAP.md\n```\n\n### Add New Command\n\nAdds a new command to the system, often paired with a backing skill.\n\n**Frequency**: ~1 times per month\n\n**Steps**:\n1. Create a new markdown file under commands\u002F{command-name}.md\n2. Optionally add or update a backing skill under skills\u002F{skill-name}\u002FSKILL.md\n\n**Files typically involved**:\n- `commands\u002F*.md`\n- `skills\u002F*\u002FSKILL.md`\n\n**Example commit sequence**:\n```\nCreate a new markdown file under commands\u002F{command-name}.md\nOptionally add or update a backing skill under skills\u002F{skill-name}\u002FSKILL.md\n```\n\n### Sync Catalog Counts\n\nSynchronizes the documented counts of agents, skills, and commands in AGENTS.md and README.md with the actual repository state.\n\n**Frequency**: ~3 times per month\n\n**Steps**:\n1. Update agent, skill, and command counts in AGENTS.md\n2. Update the same counts in README.md (quick-start, comparison table, etc.)\n3. Optionally update other documentation files\n\n**Files typically involved**:\n- `AGENTS.md`\n- `README.md`\n\n**Example commit sequence**:\n```\nUpdate agent, skill, and command counts in AGENTS.md\nUpdate the same counts in README.md (quick-start, comparison table, etc.)\nOptionally update other documentation files\n```\n\n### Add Cross Harness Skill Copies\n\nAdds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms.\n\n**Frequency**: ~2 times per month\n\n**Steps**:\n1. Copy or adapt SKILL.md to .agents\u002Fskills\u002F{skill}\u002FSKILL.md and\u002For .cursor\u002Fskills\u002F{skill}\u002FSKILL.md\n2. Optionally add harness-specific openai.yaml or config files\n3. Address review feedback to align with CONTRIBUTING template\n\n**Files typically involved**:\n- `.agents\u002Fskills\u002F*\u002FSKILL.md`\n- `.cursor\u002Fskills\u002F*\u002FSKILL.md`\n- `.agents\u002Fskills\u002F*\u002Fagents\u002Fopenai.yaml`\n\n**Example commit sequence**:\n```\nCopy or adapt SKILL.md to .agents\u002Fskills\u002F{skill}\u002FSKILL.md and\u002For .cursor\u002Fskills\u002F{skill}\u002FSKILL.md\nOptionally add harness-specific openai.yaml or config files\nAddress review feedback to align with CONTRIBUTING template\n```\n\n### Add Or Update Hook\n\nAdds or updates git or bash hooks to enforce workflow, quality, or security policies.\n\n**Frequency**: ~1 times per month\n\n**Steps**:\n1. Add or update hook scripts in hooks\u002F or scripts\u002Fhooks\u002F\n2. Register the hook in hooks\u002Fhooks.json or similar config\n3. Optionally add or update tests in tests\u002Fhooks\u002F\n\n**Files typically involved**:\n- `hooks\u002F*.hook`\n- `hooks\u002Fhooks.json`\n- `scripts\u002Fhooks\u002F*.js`\n- `tests\u002Fhooks\u002F*.test.js`\n- `.cursor\u002Fhooks.json`\n\n**Example commit sequence**:\n```\nAdd or update hook scripts in hooks\u002F or scripts\u002Fhooks\u002F\nRegister the hook in hooks\u002Fhooks.json or similar config\nOptionally add or update tests in tests\u002Fhooks\u002F\n```\n\n### Address Review Feedback\n\nAddresses code review feedback by updating documentation, scripts, or configuration for clarity, correctness, or convention alignment.\n\n**Frequency**: ~4 times per month\n\n**Steps**:\n1. Edit SKILL.md, agent, or command files to address reviewer comments\n2. Update examples, headings, or configuration as requested\n3. Iterate until all review feedback is resolved\n\n**Files typically involved**:\n- `skills\u002F*\u002FSKILL.md`\n- `agents\u002F*.md`\n- `commands\u002F*.md`\n- `.agents\u002Fskills\u002F*\u002FSKILL.md`\n- `.cursor\u002Fskills\u002F*\u002FSKILL.md`\n\n**Example commit sequence**:\n```\nEdit SKILL.md, agent, or command files to address reviewer comments\nUpdate examples, headings, or configuration as requested\nIterate until all review feedback is resolved\n```\n\n\n## Best Practices\n\nBased on analysis of the codebase, follow these practices:\n\n### Do\n\n- Use conventional commit format (feat:, fix:, etc.)\n- Follow *.test.js naming pattern\n- Use camelCase for file names\n- Prefer mixed exports\n\n### Don't\n\n- Don't write vague commit messages\n- Don't skip tests for new features\n- Don't deviate from established patterns without discussion\n\n---\n\n*This skill was auto-generated by [ECC Tools](https:\u002F\u002Fecc.tools). Review and customize as needed for your team.*\n","# Everything Claude Code Conventions\n\n> Generated from [affaan-m\u002Feverything-claude-code](https:\u002F\u002Fgithub.com\u002Faffaan-m\u002Feverything-claude-code) on 2026-03-20\n\n## Overview\n\nThis skill teaches Claude the development patterns and conventions used in everything-claude-code.\n\n## Tech Stack\n\n- **Primary Language**: JavaScript\n- **Architecture**: hybrid module organization\n- **Test Location**: separate\n\n## When to Use This Skill\n\nActivate this skill when:\n- Making changes to this repository\n- Adding new features following established patterns\n- Writing tests that match project conventions\n- Creating commits with proper message format\n\n## Commit Conventions\n\nFollow these commit message conventions based on 500 analyzed commits.\n\n### Commit Style: Conventional Commits\n\n### Prefixes Used\n\n- `fix`\n- `test`\n- `feat`\n- `docs`\n\n### Message Guidelines\n\n- Average message length: ~65 characters\n- Keep first line concise and descriptive\n- Use imperative mood (\"Add feature\" not \"Added feature\")\n\n\n*Commit message example*\n\n```text\nfeat(rules): add C# language support\n```\n\n*Commit message example*\n\n```text\nchore(deps-dev): bump flatted (#675)\n```\n\n*Commit message example*\n\n```text\nfix: auto-detect ECC root from plugin cache when CLAUDE_PLUGIN_ROOT is unset (#547) (#691)\n```\n\n*Commit message example*\n\n```text\ndocs: add Antigravity setup and usage guide (#552)\n```\n\n*Commit message example*\n\n```text\nmerge: PR #529 — feat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer\n```\n\n*Commit message example*\n\n```text\nRevert \"Add Kiro IDE support (.kiro\u002F) (#548)\"\n```\n\n*Commit message example*\n\n```text\nAdd Kiro IDE support (.kiro\u002F) (#548)\n```\n\n*Commit message example*\n\n```text\nfeat: add block-no-verify hook for Claude Code and Cursor (#649)\n```\n\n## Architecture\n\n### Project Structure: Single Package\n\nThis project uses **hybrid** module organization.\n\n### Configuration Files\n\n- `.github\u002Fworkflows\u002Fci.yml`\n- `.github\u002Fworkflows\u002Fmaintenance.yml`\n- `.github\u002Fworkflows\u002Fmonthly-metrics.yml`\n- `.github\u002Fworkflows\u002Frelease.yml`\n- `.github\u002Fworkflows\u002Freusable-release.yml`\n- `.github\u002Fworkflows\u002Freusable-test.yml`\n- `.github\u002Fworkflows\u002Freusable-validate.yml`\n- `.opencode\u002Fpackage.json`\n- `.opencode\u002Ftsconfig.json`\n- `.prettierrc`\n- `eslint.config.js`\n- `package.json`\n\n### Guidelines\n\n- This project uses a hybrid organization\n- Follow existing patterns when adding new code\n\n## Code Style\n\n### Language: JavaScript\n\n### Naming Conventions\n\n| Element | Convention |\n|---------|------------|\n| Files | camelCase |\n| Functions | camelCase |\n| Classes | PascalCase |\n| Constants | SCREAMING_SNAKE_CASE |\n\n### Import Style: Relative Imports\n\n### Export Style: Mixed Style\n\n\n*Preferred import style*\n\n```typescript\n\u002F\u002F Use relative imports\nimport { Button } from '..\u002Fcomponents\u002FButton'\nimport { useAuth } from '.\u002Fhooks\u002FuseAuth'\n```\n\n## Testing\n\n### Test Framework\n\nNo specific test framework detected — use the repository's existing test patterns.\n\n### File Pattern: `*.test.js`\n\n### Test Types\n\n- **Unit tests**: Test individual functions and components in isolation\n- **Integration tests**: Test interactions between multiple components\u002Fservices\n\n### Coverage\n\nThis project has coverage reporting configured. Aim for 80%+ coverage.\n\n\n## Error Handling\n\n### Error Handling Style: Try-Catch Blocks\n\n\n*Standard error handling pattern*\n\n```typescript\ntry {\n  const result = await riskyOperation()\n  return result\n} catch (error) {\n  console.error('Operation failed:', error)\n  throw new Error('User-friendly message')\n}\n```\n\n## Common Workflows\n\nThese workflows were detected from analyzing commit patterns.\n\n### Database Migration\n\nDatabase schema changes with migration files\n\n**Frequency**: ~2 times per month\n\n**Steps**:\n1. Create migration file\n2. Update schema definitions\n3. Generate\u002Fupdate types\n\n**Files typically involved**:\n- `**\u002Fschema.*`\n- `migrations\u002F*`\n\n**Example commit sequence**:\n```\nfeat: implement --with\u002F--without selective install flags (#679)\nfix: sync catalog counts with filesystem (27 agents, 113 skills, 58 commands) (#693)\nfeat(rules): add Rust language rules (rebased #660) (#686)\n```\n\n### Feature Development\n\nStandard feature implementation workflow\n\n**Frequency**: ~22 times per month\n\n**Steps**:\n1. Add feature implementation\n2. Add tests for feature\n3. Update documentation\n\n**Files typically involved**:\n- `manifests\u002F*`\n- `schemas\u002F*`\n- `**\u002F*.test.*`\n- `**\u002Fapi\u002F**`\n\n**Example commit sequence**:\n```\nfeat(skills): add documentation-lookup, bun-runtime, nextjs-turbopack; feat(agents): add rust-reviewer\ndocs(skills): align documentation-lookup with CONTRIBUTING template; add cross-harness (Codex\u002FCursor) skill copies\nfix: address PR review — skill template (When to use, How it works, Examples), bun.lock, next build note, rust-reviewer CI note, doc-lookup privacy\u002Funcertainty\n```\n\n### Add Language Rules\n\nAdds a new programming language to the rules system, including coding style, hooks, patterns, security, and testing guidelines.\n\n**Frequency**: ~2 times per month\n\n**Steps**:\n1. Create a new directory under rules\u002F{language}\u002F\n2. Add coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content\n3. Optionally reference or link to related skills\n\n**Files typically involved**:\n- `rules\u002F*\u002Fcoding-style.md`\n- `rules\u002F*\u002Fhooks.md`\n- `rules\u002F*\u002Fpatterns.md`\n- `rules\u002F*\u002Fsecurity.md`\n- `rules\u002F*\u002Ftesting.md`\n\n**Example commit sequence**:\n```\nCreate a new directory under rules\u002F{language}\u002F\nAdd coding-style.md, hooks.md, patterns.md, security.md, and testing.md files with language-specific content\nOptionally reference or link to related skills\n```\n\n### Add New Skill\n\nAdds a new skill to the system, documenting its workflow, triggers, and usage, often with supporting scripts.\n\n**Frequency**: ~4 times per month\n\n**Steps**:\n1. Create a new directory under skills\u002F{skill-name}\u002F\n2. Add SKILL.md with documentation (When to Use, How It Works, Examples, etc.)\n3. Optionally add scripts or supporting files under skills\u002F{skill-name}\u002Fscripts\u002F\n4. Address review feedback and iterate on documentation\n\n**Files typically involved**:\n- `skills\u002F*\u002FSKILL.md`\n- `skills\u002F*\u002Fscripts\u002F*.sh`\n- `skills\u002F*\u002Fscripts\u002F*.js`\n\n**Example commit sequence**:\n```\nCreate a new directory under skills\u002F{skill-name}\u002F\nAdd SKILL.md with documentation (When to Use, How It Works, Examples, etc.)\nOptionally add scripts or supporting files under skills\u002F{skill-name}\u002Fscripts\u002F\nAddress review feedback and iterate on documentation\n```\n\n### Add New Agent\n\nAdds a new agent to the system for code review, build resolution, or other automated tasks.\n\n**Frequency**: ~2 times per month\n\n**Steps**:\n1. Create a new agent markdown file under agents\u002F{agent-name}.md\n2. Register the agent in AGENTS.md\n3. Optionally update README.md and docs\u002FCOMMAND-AGENT-MAP.md\n\n**Files typically involved**:\n- `agents\u002F*.md`\n- `AGENTS.md`\n- `README.md`\n- `docs\u002FCOMMAND-AGENT-MAP.md`\n\n**Example commit sequence**:\n```\nCreate a new agent markdown file under agents\u002F{agent-name}.md\nRegister the agent in AGENTS.md\nOptionally update README.md and docs\u002FCOMMAND-AGENT-MAP.md\n```\n\n### Add New Command\n\nAdds a new command to the system, often paired with a backing skill.\n\n**Frequency**: ~1 times per month\n\n**Steps**:\n1. Create a new markdown file under commands\u002F{command-name}.md\n2. Optionally add or update a backing skill under skills\u002F{skill-name}\u002FSKILL.md\n\n**Files typically involved**:\n- `commands\u002F*.md`\n- `skills\u002F*\u002FSKILL.md`\n\n**Example commit sequence**:\n```\nCreate a new markdown file under commands\u002F{command-name}.md\nOptionally add or update a backing skill under skills\u002F{skill-name}\u002FSKILL.md\n```\n\n### Sync Catalog Counts\n\nSynchronizes the documented counts of agents, skills, and commands in AGENTS.md and README.md with the actual repository state.\n\n**Frequency**: ~3 times per month\n\n**Steps**:\n1. Update agent, skill, and command counts in AGENTS.md\n2. Update the same counts in README.md (quick-start, comparison table, etc.)\n3. Optionally update other documentation files\n\n**Files typically involved**:\n- `AGENTS.md`\n- `README.md`\n\n**Example commit sequence**:\n```\nUpdate agent, skill, and command counts in AGENTS.md\nUpdate the same counts in README.md (quick-start, comparison table, etc.)\nOptionally update other documentation files\n```\n\n### Add Cross Harness Skill Copies\n\nAdds skill copies for different agent harnesses (e.g., Codex, Cursor, Antigravity) to ensure compatibility across platforms.\n\n**Frequency**: ~2 times per month\n\n**Steps**:\n1. Copy or adapt SKILL.md to .agents\u002Fskills\u002F{skill}\u002FSKILL.md and\u002For .cursor\u002Fskills\u002F{skill}\u002FSKILL.md\n2. Optionally add harness-specific openai.yaml or config files\n3. Address review feedback to align with CONTRIBUTING template\n\n**Files typically involved**:\n- `.agents\u002Fskills\u002F*\u002FSKILL.md`\n- `.cursor\u002Fskills\u002F*\u002FSKILL.md`\n- `.agents\u002Fskills\u002F*\u002Fagents\u002Fopenai.yaml`\n\n**Example commit sequence**:\n```\nCopy or adapt SKILL.md to .agents\u002Fskills\u002F{skill}\u002FSKILL.md and\u002For .cursor\u002Fskills\u002F{skill}\u002FSKILL.md\nOptionally add harness-specific openai.yaml or config files\nAddress review feedback to align with CONTRIBUTING template\n```\n\n### Add Or Update Hook\n\nAdds or updates git or bash hooks to enforce workflow, quality, or security policies.\n\n**Frequency**: ~1 times per month\n\n**Steps**:\n1. Add or update hook scripts in hooks\u002F or scripts\u002Fhooks\u002F\n2. Register the hook in hooks\u002Fhooks.json or similar config\n3. Optionally add or update tests in tests\u002Fhooks\u002F\n\n**Files typically involved**:\n- `hooks\u002F*.hook`\n- `hooks\u002Fhooks.json`\n- `scripts\u002Fhooks\u002F*.js`\n- `tests\u002Fhooks\u002F*.test.js`\n- `.cursor\u002Fhooks.json`\n\n**Example commit sequence**:\n```\nAdd or update hook scripts in hooks\u002F or scripts\u002Fhooks\u002F\nRegister the hook in hooks\u002Fhooks.json or similar config\nOptionally add or update tests in tests\u002Fhooks\u002F\n```\n\n### Address Review Feedback\n\nAddresses code review feedback by updating documentation, scripts, or configuration for clarity, correctness, or convention alignment.\n\n**Frequency**: ~4 times per month\n\n**Steps**:\n1. Edit SKILL.md, agent, or command files to address reviewer comments\n2. Update examples, headings, or configuration as requested\n3. Iterate until all review feedback is resolved\n\n**Files typically involved**:\n- `skills\u002F*\u002FSKILL.md`\n- `agents\u002F*.md`\n- `commands\u002F*.md`\n- `.agents\u002Fskills\u002F*\u002FSKILL.md`\n- `.cursor\u002Fskills\u002F*\u002FSKILL.md`\n\n**Example commit sequence**:\n```\nEdit SKILL.md, agent, or command files to address reviewer comments\nUpdate examples, headings, or configuration as requested\nIterate until all review feedback is resolved\n```\n\n\n## Best Practices\n\nBased on analysis of the codebase, follow these practices:\n\n### Do\n\n- Use conventional commit format (feat:, fix:, etc.)\n- Follow *.test.js naming pattern\n- Use camelCase for file names\n- Prefer mixed exports\n\n### Don't\n\n- Don't write vague commit messages\n- Don't skip tests for new features\n- Don't deviate from established patterns without discussion\n\n---\n\n*This skill was auto-generated by [ECC Tools](https:\u002F\u002Fecc.tools). Review and customize as needed for your team.*\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Feverything-claude-code-conventions",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill everything-claude-code-conventions",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill everything-claude-code-conventions",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill everything-claude-code-conventions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Feverything-claude-code-conventions\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]