[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77G97W44736V9Q2STP2FK7D":3,"skill-same:01M77G97W44736V9Q2STP2FK7D":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M77G97W44736V9Q2STP2FK7D","ecc-conventions",null,"Development conventions and patterns for ECC. JavaScript project with conventional commits.","viseshrp\u002Fai-skills-archive","viseshrp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11642379?v=4","01M77FS5SES3C3PAVNXVRH1WVJ","Visesh Rajendraprasad","01M77FS5T6KA31CXA6K10TYFDC",0,"MIT","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Faffaan-m__ECC\u002Fsnapshot\u002F.agents\u002Fskills\u002Fecc-conventions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ecc-conventions\ndescription: Development conventions and patterns for ECC. JavaScript project with conventional commits.\nlicense: MIT\n---\n\n# ECC Conventions\n\n> Generated from [affaan-m\u002FECC](https:\u002F\u002Fgithub.com\u002Faffaan-m\u002FECC) on 2026-03-20\n\n## Overview\n\nThis skill teaches Claude the development patterns and conventions used in ECC.\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 Workflow Surface\n\nAdds or updates a workflow entrypoint. Default to skills-first; only add a command shim when legacy slash compatibility is still required.\n\n**Frequency**: ~1 times per month\n\n**Steps**:\n1. Create or update the canonical workflow under skills\u002F{skill-name}\u002FSKILL.md\n2. Only if needed, add or update commands\u002F{command-name}.md as a compatibility shim\n\n**Files typically involved**:\n- `skills\u002F*\u002FSKILL.md`\n- `commands\u002F*.md` (only when a legacy shim is intentionally retained)\n\n**Example commit sequence**:\n```\nCreate or update the canonical skill under skills\u002F{skill-name}\u002FSKILL.md\nOnly if needed, add or update commands\u002F{command-name}.md as a compatibility shim\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","# ECC Conventions\n\n> Generated from [affaan-m\u002FECC](https:\u002F\u002Fgithub.com\u002Faffaan-m\u002FECC) on 2026-03-20\n\n## Overview\n\nThis skill teaches Claude the development patterns and conventions used in ECC.\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 Workflow Surface\n\nAdds or updates a workflow entrypoint. Default to skills-first; only add a command shim when legacy slash compatibility is still required.\n\n**Frequency**: ~1 times per month\n\n**Steps**:\n1. Create or update the canonical workflow under skills\u002F{skill-name}\u002FSKILL.md\n2. Only if needed, add or update commands\u002F{command-name}.md as a compatibility shim\n\n**Files typically involved**:\n- `skills\u002F*\u002FSKILL.md`\n- `commands\u002F*.md` (only when a legacy shim is intentionally retained)\n\n**Example commit sequence**:\n```\nCreate or update the canonical skill under skills\u002F{skill-name}\u002FSKILL.md\nOnly if needed, add or update commands\u002F{command-name}.md as a compatibility shim\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,"license":15,"description":7},"main","2550866e372116f9d9b44ba2cd5c66a6860f3040","archives\u002Faffaan-m__ECC\u002Fsnapshot\u002F.agents\u002Fskills\u002Fecc-conventions","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive","https:\u002F\u002Fgithub.com\u002Fviseshrp","Full-stack engineer by day, building apps and CLI tools.\r\nSelf-hoster by night, running a tiny Raspberry Pi datacenter.","2026-11-10 11:20:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add viseshrp\u002Fai-skills-archive --skill ecc-conventions",{"tool":37,"command":38},"bunx","bunx skills add viseshrp\u002Fai-skills-archive --skill ecc-conventions",{"tool":40,"command":41},"pnpm","pnpm dlx skills add viseshrp\u002Fai-skills-archive --skill ecc-conventions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Faffaan-m__ECC\u002Fsnapshot\u002F.agents\u002Fskills\u002Fecc-conventions\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",258,"https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Faffaan-m__ECC\u002Fsnapshot\u002F.agents\u002Fskills\u002Fecc-conventions\u002Fagents\u002Fopenai.yaml",[52,60,67,74,81,88],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":56,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77MKJBE97JWGCWFH915STTG","test-audit","Audit new or existing tests for behavioral value, duplication, implementation coupling, brittleness, and test-only production seams. Use when writing, changing, reviewing, or pruning tests, including an independent final review of a test diff.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Fskills\u002Ftest-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Fskills\u002Ftest-audit\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77MJ0851ZFCXSBX5YX0CEZ2","last30days","Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fmvanhorn__last30days-skill\u002Fsnapshot\u002Fskills\u002Flast30days\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77MHW9RACV0XNY75ZSJJD56","karpathy-guidelines","Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fmultica-ai__andrej-karpathy-skills\u002Fsnapshot\u002Fskills\u002Fkarpathy-guidelines\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77M349AKHE5GDY8ATT5PP5W","port-github-app-to-origin","Plans the port of an existing GitHub App to a Cursor Origin App. Use when the task is to bring a GitHub App to Origin or compare what it uses against the Origin API. Reads the app's needs out of its code, maps them onto the live Origin spec, and writes a porting brief with feedback for Cursor. Planning only.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fcursor__plugins\u002Fsnapshot\u002Forigin-apps\u002Fskills\u002Fport-github-app-to-origin\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77M30DPGNPY4BDMB1SEHJSK","origin-api","Routes questions about the Cursor Origin API to the right section of the Origin docs and names the few rules to check first. Use when a task mentions Origin, the Origin API, Origin Apps, or Origin webhooks, including creating an Origin App, authenticating as one, calling Origin endpoints, or handling Origin webhook deliveries.","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fcursor__plugins\u002Fsnapshot\u002Forigin-apps\u002Fskills\u002Forigin-api\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77KTXW5T1KVMHX71FMBT7BR","i-have-adhd","Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with \u002Fi-have-adhd; stays on until \"stop adhd mode\".","https:\u002F\u002Fgithub.com\u002Fviseshrp\u002Fai-skills-archive\u002Fblob\u002Fmain\u002Farchives\u002Fayghri__i-have-adhd\u002Fsnapshot\u002Fskills\u002Fi-have-adhd\u002FSKILL.md",[],[]]