[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77S9Y696NT8SWR0V1JFCB72":3,"skill-same:01M77S9Y696NT8SWR0V1JFCB72":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M77S9Y696NT8SWR0V1JFCB72","issue-creation",null,"Create Gentle AI issues with issue-first checks. Trigger: creating GitHub issues, bug reports, or feature requests.","janpereira-dev\u002FskillsCurate","janpereira-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6440548?v=4","01M6KKKXBFFK7QF5Y2JFXN35FF","Jan Pereira","01M77ND31QCT5KM25E1SW71M8F",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fissue-creation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: issue-creation\ndescription: \"Create Gentle AI issues with issue-first checks. Trigger: creating GitHub issues, bug reports, or feature requests.\"\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n## When to Use\n\nUse this skill when:\n- Creating a GitHub issue (bug report or feature request)\n- Helping a contributor file an issue\n- Triaging or approving issues as a maintainer\n\n---\n\n## Critical Rules\n\n1. **Blank issues are disabled** — MUST use a template (bug report or feature request)\n2. **Every issue gets `status:needs-review` automatically** on creation\n3. **A maintainer MUST add `status:approved`** before any PR can be opened\n4. **Questions go to [Discussions](https:\u002F\u002Fgithub.com\u002FGentleman-Programming\u002Fagent-teams-lite\u002Fdiscussions)**, not issues\n\n---\n\n## Workflow\n\n```\n1. Search existing issues for duplicates\n2. Choose the correct template (Bug Report or Feature Request)\n3. Fill in ALL required fields\n4. Check pre-flight checkboxes\n5. Submit → issue gets status:needs-review automatically\n6. Wait for maintainer to add status:approved\n7. Only then open a PR linking this issue\n```\n\n---\n\n## Issue Templates\n\n### Bug Report\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Fbug_report.yml`\nAuto-labels: `bug`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Bug Description** | Clear description of the bug |\n| **Steps to Reproduce** | Numbered steps to reproduce |\n| **Expected Behavior** | What should have happened |\n| **Actual Behavior** | What happened instead (include errors\u002Flogs) |\n| **Operating System** | Dropdown: macOS, Linux variants, Windows, WSL |\n| **Agent \u002F Client** | Dropdown: Claude Code, OpenCode, Gemini CLI, Cursor, Windsurf, Codex, Other |\n| **Shell** | Dropdown: bash, zsh, fish, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Relevant Logs** | Log output (auto-formatted as code block) |\n| **Additional Context** | Screenshots, workarounds, extra info |\n\n#### Example — Bug Report via CLI\n\n```bash\ngh issue create --template \"bug_report.yml\" \\\n  --title \"fix(scripts): setup.sh fails on zsh with glob error\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Bug Description\nRunning setup.sh on zsh throws a glob error when no matching files exist.\n\n### Steps to Reproduce\n1. Clone the repo\n2. Run \\`.\u002Fscripts\u002Fsetup.sh\\` in zsh\n3. See error: \\`zsh: no matches found: skills\u002F*\\`\n\n### Expected Behavior\nThe script should handle missing glob matches gracefully.\n\n### Actual Behavior\nScript crashes with glob error.\n\n### Operating System\nmacOS\n\n### Agent \u002F Client\nClaude Code\n\n### Shell\nzsh\n\n### Relevant Logs\n\\`\\`\\`\nzsh: no matches found: skills\u002F*\n\\`\\`\\`\n\"\n```\n\n---\n\n### Feature Request\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Ffeature_request.yml`\nAuto-labels: `enhancement`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Problem Description** | The pain point this feature solves |\n| **Proposed Solution** | How it should work from the user's perspective |\n| **Affected Area** | Dropdown: Scripts, Skills, Examples, Documentation, CI\u002FWorkflows, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Alternatives Considered** | Other approaches or workarounds |\n| **Additional Context** | Mockups, examples, references |\n\n#### Example — Feature Request via CLI\n\n```bash\ngh issue create --template \"feature_request.yml\" \\\n  --title \"feat(scripts): add Codex support to setup.sh\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Problem Description\nThe setup script only configures Claude Code, Gemini CLI, and OpenCode. Codex users have to manually copy skills.\n\n### Proposed Solution\nAdd a Codex option to setup.sh that links skills to the .codex\u002F directory.\n\nExample:\n\\`\\`\\`bash\n.\u002Fscripts\u002Fsetup.sh --agent codex\n\\`\\`\\`\n\n### Affected Area\nScripts (setup, installation)\n\n### Alternatives Considered\nManually symlinking, but that defeats the purpose of the setup script.\n\"\n```\n\n---\n\n## Label System\n\n### Applied Automatically on Issue Creation\n\n| Template | Labels added |\n|----------|-------------|\n| Bug Report | `bug`, `status:needs-review` |\n| Feature Request | `enhancement`, `status:needs-review` |\n\n### Applied by Maintainers\n\n| Label | When to apply |\n|-------|--------------|\n| `status:approved` | Issue accepted for implementation — PRs can now be opened |\n| `priority:high` | Critical bug or urgent feature |\n| `priority:medium` | Important but not blocking |\n| `priority:low` | Nice to have |\n\n---\n\n## Maintainer Approval Workflow\n\n```\n1. New issue arrives with status:needs-review\n2. Review the issue — is it valid, clear, and in scope?\n3. If YES → add status:approved label\n4. If NO → comment with reason, close if needed\n5. Contributor can now open a PR linking this issue\n```\n\n---\n\n## Decision Tree\n\n```\nIs it a bug?                    → Use Bug Report template\nIs it a new feature\u002Fimprovement? → Use Feature Request template\nIs it a question?               → Use Discussions, NOT issues\nIs it a duplicate?              → Link to existing issue, close\n```\n\n---\n\n## Commands\n\n```bash\n# Search existing issues before creating\ngh issue list --search \"keyword\"\n\n# Create bug report\ngh issue create --template \"bug_report.yml\" --title \"fix(scope): description\"\n\n# Create feature request\ngh issue create --template \"feature_request.yml\" --title \"feat(scope): description\"\n\n# Maintainer: approve an issue\ngh issue edit \u003Cnumber> --add-label \"status:approved\"\n\n# Maintainer: add priority\ngh issue edit \u003Cnumber> --add-label \"priority:high\"\n```\n","## When to Use\n\nUse this skill when:\n- Creating a GitHub issue (bug report or feature request)\n- Helping a contributor file an issue\n- Triaging or approving issues as a maintainer\n\n---\n\n## Critical Rules\n\n1. **Blank issues are disabled** — MUST use a template (bug report or feature request)\n2. **Every issue gets `status:needs-review` automatically** on creation\n3. **A maintainer MUST add `status:approved`** before any PR can be opened\n4. **Questions go to [Discussions](https:\u002F\u002Fgithub.com\u002FGentleman-Programming\u002Fagent-teams-lite\u002Fdiscussions)**, not issues\n\n---\n\n## Workflow\n\n```\n1. Search existing issues for duplicates\n2. Choose the correct template (Bug Report or Feature Request)\n3. Fill in ALL required fields\n4. Check pre-flight checkboxes\n5. Submit → issue gets status:needs-review automatically\n6. Wait for maintainer to add status:approved\n7. Only then open a PR linking this issue\n```\n\n---\n\n## Issue Templates\n\n### Bug Report\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Fbug_report.yml`\nAuto-labels: `bug`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Bug Description** | Clear description of the bug |\n| **Steps to Reproduce** | Numbered steps to reproduce |\n| **Expected Behavior** | What should have happened |\n| **Actual Behavior** | What happened instead (include errors\u002Flogs) |\n| **Operating System** | Dropdown: macOS, Linux variants, Windows, WSL |\n| **Agent \u002F Client** | Dropdown: Claude Code, OpenCode, Gemini CLI, Cursor, Windsurf, Codex, Other |\n| **Shell** | Dropdown: bash, zsh, fish, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Relevant Logs** | Log output (auto-formatted as code block) |\n| **Additional Context** | Screenshots, workarounds, extra info |\n\n#### Example — Bug Report via CLI\n\n```bash\ngh issue create --template \"bug_report.yml\" \\\n  --title \"fix(scripts): setup.sh fails on zsh with glob error\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Bug Description\nRunning setup.sh on zsh throws a glob error when no matching files exist.\n\n### Steps to Reproduce\n1. Clone the repo\n2. Run \\`.\u002Fscripts\u002Fsetup.sh\\` in zsh\n3. See error: \\`zsh: no matches found: skills\u002F*\\`\n\n### Expected Behavior\nThe script should handle missing glob matches gracefully.\n\n### Actual Behavior\nScript crashes with glob error.\n\n### Operating System\nmacOS\n\n### Agent \u002F Client\nClaude Code\n\n### Shell\nzsh\n\n### Relevant Logs\n\\`\\`\\`\nzsh: no matches found: skills\u002F*\n\\`\\`\\`\n\"\n```\n\n---\n\n### Feature Request\n\nTemplate: `.github\u002FISSUE_TEMPLATE\u002Ffeature_request.yml`\nAuto-labels: `enhancement`, `status:needs-review`\n\n#### Required Fields\n\n| Field | Description |\n|-------|-------------|\n| **Pre-flight Checks** | Checkboxes: no duplicate + understands approval workflow |\n| **Problem Description** | The pain point this feature solves |\n| **Proposed Solution** | How it should work from the user's perspective |\n| **Affected Area** | Dropdown: Scripts, Skills, Examples, Documentation, CI\u002FWorkflows, Other |\n\n#### Optional Fields\n\n| Field | Description |\n|-------|-------------|\n| **Alternatives Considered** | Other approaches or workarounds |\n| **Additional Context** | Mockups, examples, references |\n\n#### Example — Feature Request via CLI\n\n```bash\ngh issue create --template \"feature_request.yml\" \\\n  --title \"feat(scripts): add Codex support to setup.sh\" \\\n  --body \"\n### Pre-flight Checks\n- [x] I have searched existing issues and this is not a duplicate\n- [x] I understand this issue needs status:approved before a PR can be opened\n\n### Problem Description\nThe setup script only configures Claude Code, Gemini CLI, and OpenCode. Codex users have to manually copy skills.\n\n### Proposed Solution\nAdd a Codex option to setup.sh that links skills to the .codex\u002F directory.\n\nExample:\n\\`\\`\\`bash\n.\u002Fscripts\u002Fsetup.sh --agent codex\n\\`\\`\\`\n\n### Affected Area\nScripts (setup, installation)\n\n### Alternatives Considered\nManually symlinking, but that defeats the purpose of the setup script.\n\"\n```\n\n---\n\n## Label System\n\n### Applied Automatically on Issue Creation\n\n| Template | Labels added |\n|----------|-------------|\n| Bug Report | `bug`, `status:needs-review` |\n| Feature Request | `enhancement`, `status:needs-review` |\n\n### Applied by Maintainers\n\n| Label | When to apply |\n|-------|--------------|\n| `status:approved` | Issue accepted for implementation — PRs can now be opened |\n| `priority:high` | Critical bug or urgent feature |\n| `priority:medium` | Important but not blocking |\n| `priority:low` | Nice to have |\n\n---\n\n## Maintainer Approval Workflow\n\n```\n1. New issue arrives with status:needs-review\n2. Review the issue — is it valid, clear, and in scope?\n3. If YES → add status:approved label\n4. If NO → comment with reason, close if needed\n5. Contributor can now open a PR linking this issue\n```\n\n---\n\n## Decision Tree\n\n```\nIs it a bug?                    → Use Bug Report template\nIs it a new feature\u002Fimprovement? → Use Feature Request template\nIs it a question?               → Use Discussions, NOT issues\nIs it a duplicate?              → Link to existing issue, close\n```\n\n---\n\n## Commands\n\n```bash\n# Search existing issues before creating\ngh issue list --search \"keyword\"\n\n# Create bug report\ngh issue create --template \"bug_report.yml\" --title \"fix(scope): description\"\n\n# Create feature request\ngh issue create --template \"feature_request.yml\" --title \"feat(scope): description\"\n\n# Maintainer: approve an issue\ngh issue edit \u003Cnumber> --add-label \"status:approved\"\n\n# Maintainer: add priority\ngh issue edit \u003Cnumber> --add-label \"priority:high\"\n```\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"gentleman-programming","1.0","main","ba43a4e7e8b0fd6b150b14bcb48978ec40879a28",".agents\u002Fskills\u002Fissue-creation","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev","IT Leader, Scrum Master, FullStack Developer, SEO\u002FSEM Master #Angular #React\r\n","2026-07-13 03:04:32",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add janpereira-dev\u002FskillsCurate --skill issue-creation",{"tool":40,"command":41},"bunx","bunx skills add janpereira-dev\u002FskillsCurate --skill issue-creation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add janpereira-dev\u002FskillsCurate --skill issue-creation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fissue-creation\u002FSKILL.md",true,[],[49,56,63,70,78,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M77T9KN6TEJMPPTQZDEB4K61","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M77T9GN2GABPPWDGDCXJ6QWK","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77T98A9R6PK155P71VX9MND","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77T9505TGQGWHGAYVXGE2KS","web-quality-audit","Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".","MIT","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-quality-audit\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77T8YRVRNK8W4MG63XM80NK","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77T8CEPQFZRRNGBYZX46P4Y","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-react-view-transitions\u002FSKILL.md",[],[]]