[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C3CMZESWCT04P55FY7GK1P":3,"skill-same:01M6C3CMZESWCT04P55FY7GK1P":52},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M6C3CMZESWCT04P55FY7GK1P","documentation-and-adrs",null,"Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.","thegiantbeast\u002Fdotfiles","thegiantbeast","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31733?v=4","01M6C3CJSWCN22VMJ7DZ7KJX02","Ricardo Ferreira","01M6C3CJY6G03VP48FRFK8HEGE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fosmani-picks\u002Fskills\u002Fdocumentation-and-adrs\u002FSKILL.md",[],[19,20,21,22,23,24,25],"documentation","documentation and adrs","shipping","public","decisions","context","use","2026-11-10 10:12:30",false,"---\nname: documentation-and-adrs\ndescription: Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.\n---\n\n# Documentation and ADRs\n\n## Overview\n\nDocument decisions, not just code. The most valuable documentation captures the *why* — the context, constraints, and trade-offs that led to a decision. Code shows *what* was built; documentation explains *why it was built this way* and *what alternatives were considered*. This context is essential for future humans and agents working in the codebase.\n\n## When to Use\n\n- Making a significant architectural decision\n- Choosing between competing approaches\n- Adding or changing a public API\n- Shipping a feature that changes user-facing behavior\n- Onboarding new team members (or agents) to the project\n- When you find yourself explaining the same thing repeatedly\n\n**When NOT to use:** Don't document obvious code. Don't add comments that restate what the code already says. Don't write docs for throwaway prototypes.\n\n## Architecture Decision Records (ADRs)\n\nADRs capture the reasoning behind significant technical decisions. They're the highest-value documentation you can write.\n\n### When to Write an ADR\n\n- Choosing a framework, library, or major dependency\n- Designing a data model or database schema\n- Selecting an authentication strategy\n- Deciding on an API architecture (REST vs. GraphQL vs. tRPC)\n- Choosing between build tools, hosting platforms, or infrastructure\n- Any decision that would be expensive to reverse\n\n### ADR Template\n\nStore ADRs in `docs\u002Fdecisions\u002F` with sequential numbering:\n\n```markdown\n# ADR-001: Use PostgreSQL for primary database\n\n## Status\nAccepted | Superseded by ADR-XXX | Deprecated\n\n## Date\n2025-01-15\n\n## Context\nWe need a primary database for the task management application. Key requirements:\n- Relational data model (users, tasks, teams with relationships)\n- ACID transactions for task state changes\n- Support for full-text search on task content\n- Managed hosting available (for small team, limited ops capacity)\n\n## Decision\nUse PostgreSQL with Prisma ORM.\n\n## Alternatives Considered\n\n### MongoDB\n- Pros: Flexible schema, easy to start with\n- Cons: Our data is inherently relational; would need to manage relationships manually\n- Rejected: Relational data in a document store leads to complex joins or data duplication\n\n### SQLite\n- Pros: Zero configuration, embedded, fast for reads\n- Cons: Limited concurrent write support, no managed hosting for production\n- Rejected: Not suitable for multi-user web application in production\n\n### MySQL\n- Pros: Mature, widely supported\n- Cons: PostgreSQL has better JSON support, full-text search, and ecosystem tooling\n- Rejected: PostgreSQL is the better fit for our feature requirements\n\n## Consequences\n- Prisma provides type-safe database access and migration management\n- We can use PostgreSQL's full-text search instead of adding Elasticsearch\n- Team needs PostgreSQL knowledge (standard skill, low risk)\n- Hosting on managed service (Supabase, Neon, or RDS)\n```\n\n### ADR Lifecycle\n\n```\nPROPOSED → ACCEPTED → (SUPERSEDED or DEPRECATED)\n```\n\n- **Don't delete old ADRs.** They capture historical context.\n- When a decision changes, write a new ADR that references and supersedes the old one.\n\n## Inline Documentation\n\n### When to Comment\n\nComment the *why*, not the *what*:\n\n```typescript\n\u002F\u002F BAD: Restates the code\n\u002F\u002F Increment counter by 1\ncounter += 1;\n\n\u002F\u002F GOOD: Explains non-obvious intent\n\u002F\u002F Rate limit uses a sliding window — reset counter at window boundary,\n\u002F\u002F not on a fixed schedule, to prevent burst attacks at window edges\nif (now - windowStart > WINDOW_SIZE_MS) {\n  counter = 0;\n  windowStart = now;\n}\n```\n\n### When NOT to Comment\n\n```typescript\n\u002F\u002F Don't comment self-explanatory code\nfunction calculateTotal(items: CartItem[]): number {\n  return items.reduce((sum, item) => sum + item.price * item.quantity, 0);\n}\n\n\u002F\u002F Don't leave TODO comments for things you should just do now\n\u002F\u002F TODO: add error handling  ← Just add it\n\n\u002F\u002F Don't leave commented-out code\n\u002F\u002F const oldImplementation = () => { ... }  ← Delete it, git has history\n```\n\n### Document Known Gotchas\n\n```typescript\n\u002F**\n * IMPORTANT: This function must be called before the first render.\n * If called after hydration, it causes a flash of unstyled content\n * because the theme context isn't available during SSR.\n *\n * See ADR-003 for the full design rationale.\n *\u002F\nexport function initializeTheme(theme: Theme): void {\n  \u002F\u002F ...\n}\n```\n\n## API Documentation\n\nFor public APIs (REST, GraphQL, library interfaces):\n\n### Inline with Types (Preferred for TypeScript)\n\n```typescript\n\u002F**\n * Creates a new task.\n *\n * @param input - Task creation data (title required, description optional)\n * @returns The created task with server-generated ID and timestamps\n * @throws {ValidationError} If title is empty or exceeds 200 characters\n * @throws {AuthenticationError} If the user is not authenticated\n *\n * @example\n * const task = await createTask({ title: 'Buy groceries' });\n * console.log(task.id); \u002F\u002F \"task_abc123\"\n *\u002F\nexport async function createTask(input: CreateTaskInput): Promise\u003CTask> {\n  \u002F\u002F ...\n}\n```\n\n### OpenAPI \u002F Swagger for REST APIs\n\n```yaml\npaths:\n  \u002Fapi\u002Ftasks:\n    post:\n      summary: Create a task\n      requestBody:\n        required: true\n        content:\n          application\u002Fjson:\n            schema:\n              $ref: '#\u002Fcomponents\u002Fschemas\u002FCreateTaskInput'\n      responses:\n        '201':\n          description: Task created\n          content:\n            application\u002Fjson:\n              schema:\n                $ref: '#\u002Fcomponents\u002Fschemas\u002FTask'\n        '422':\n          description: Validation error\n```\n\n## README Structure\n\nEvery project should have a README that covers:\n\n```markdown\n# Project Name\n\nOne-paragraph description of what this project does.\n\n## Quick Start\n1. Clone the repo\n2. Install dependencies: `npm install`\n3. Set up environment: `cp .env.example .env`\n4. Run the dev server: `npm run dev`\n\n## Commands\n| Command | Description |\n|---------|-------------|\n| `npm run dev` | Start development server |\n| `npm test` | Run tests |\n| `npm run build` | Production build |\n| `npm run lint` | Run linter |\n\n## Architecture\nBrief overview of the project structure and key design decisions.\nLink to ADRs for details.\n\n## Contributing\nHow to contribute, coding standards, PR process.\n```\n\n## Changelog Maintenance\n\nFor shipped features:\n\n```markdown\n# Changelog\n\n## [1.2.0] - 2025-01-20\n### Added\n- Task sharing: users can share tasks with team members (#123)\n- Email notifications for task assignments (#124)\n\n### Fixed\n- Duplicate tasks appearing when rapidly clicking create button (#125)\n\n### Changed\n- Task list now loads 50 items per page (was 20) for better UX (#126)\n```\n\n## Documentation for Agents\n\nSpecial consideration for AI agent context:\n\n- **CLAUDE.md \u002F rules files** — Document project conventions so agents follow them\n- **Spec files** — Keep specs updated so agents build the right thing\n- **ADRs** — Help agents understand why past decisions were made (prevents re-deciding)\n- **Inline gotchas** — Prevent agents from falling into known traps\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"The code is self-documenting\" | Code shows what. It doesn't show why, what alternatives were rejected, or what constraints apply. |\n| \"We'll write docs when the API stabilizes\" | APIs stabilize faster when you document them. The doc is the first test of the design. |\n| \"Nobody reads docs\" | Agents do. Future engineers do. Your 3-months-later self does. |\n| \"ADRs are overhead\" | A 10-minute ADR prevents a 2-hour debate about the same decision six months later. |\n| \"Comments get outdated\" | Comments on *why* are stable. Comments on *what* get outdated — that's why you only write the former. |\n\n## Red Flags\n\n- Architectural decisions with no written rationale\n- Public APIs with no documentation or types\n- README that doesn't explain how to run the project\n- Commented-out code instead of deletion\n- TODO comments that have been there for weeks\n- No ADRs in a project with significant architectural choices\n- Documentation that restates the code instead of explaining intent\n\n## Verification\n\nAfter documenting:\n\n- [ ] ADRs exist for all significant architectural decisions\n- [ ] README covers quick start, commands, and architecture overview\n- [ ] API functions have parameter and return type documentation\n- [ ] Known gotchas are documented inline where they matter\n- [ ] No commented-out code remains\n- [ ] Rules files (CLAUDE.md etc.) are current and accurate\n","# Documentation and ADRs\n\n## Overview\n\nDocument decisions, not just code. The most valuable documentation captures the *why* — the context, constraints, and trade-offs that led to a decision. Code shows *what* was built; documentation explains *why it was built this way* and *what alternatives were considered*. This context is essential for future humans and agents working in the codebase.\n\n## When to Use\n\n- Making a significant architectural decision\n- Choosing between competing approaches\n- Adding or changing a public API\n- Shipping a feature that changes user-facing behavior\n- Onboarding new team members (or agents) to the project\n- When you find yourself explaining the same thing repeatedly\n\n**When NOT to use:** Don't document obvious code. Don't add comments that restate what the code already says. Don't write docs for throwaway prototypes.\n\n## Architecture Decision Records (ADRs)\n\nADRs capture the reasoning behind significant technical decisions. They're the highest-value documentation you can write.\n\n### When to Write an ADR\n\n- Choosing a framework, library, or major dependency\n- Designing a data model or database schema\n- Selecting an authentication strategy\n- Deciding on an API architecture (REST vs. GraphQL vs. tRPC)\n- Choosing between build tools, hosting platforms, or infrastructure\n- Any decision that would be expensive to reverse\n\n### ADR Template\n\nStore ADRs in `docs\u002Fdecisions\u002F` with sequential numbering:\n\n```markdown\n# ADR-001: Use PostgreSQL for primary database\n\n## Status\nAccepted | Superseded by ADR-XXX | Deprecated\n\n## Date\n2025-01-15\n\n## Context\nWe need a primary database for the task management application. Key requirements:\n- Relational data model (users, tasks, teams with relationships)\n- ACID transactions for task state changes\n- Support for full-text search on task content\n- Managed hosting available (for small team, limited ops capacity)\n\n## Decision\nUse PostgreSQL with Prisma ORM.\n\n## Alternatives Considered\n\n### MongoDB\n- Pros: Flexible schema, easy to start with\n- Cons: Our data is inherently relational; would need to manage relationships manually\n- Rejected: Relational data in a document store leads to complex joins or data duplication\n\n### SQLite\n- Pros: Zero configuration, embedded, fast for reads\n- Cons: Limited concurrent write support, no managed hosting for production\n- Rejected: Not suitable for multi-user web application in production\n\n### MySQL\n- Pros: Mature, widely supported\n- Cons: PostgreSQL has better JSON support, full-text search, and ecosystem tooling\n- Rejected: PostgreSQL is the better fit for our feature requirements\n\n## Consequences\n- Prisma provides type-safe database access and migration management\n- We can use PostgreSQL's full-text search instead of adding Elasticsearch\n- Team needs PostgreSQL knowledge (standard skill, low risk)\n- Hosting on managed service (Supabase, Neon, or RDS)\n```\n\n### ADR Lifecycle\n\n```\nPROPOSED → ACCEPTED → (SUPERSEDED or DEPRECATED)\n```\n\n- **Don't delete old ADRs.** They capture historical context.\n- When a decision changes, write a new ADR that references and supersedes the old one.\n\n## Inline Documentation\n\n### When to Comment\n\nComment the *why*, not the *what*:\n\n```typescript\n\u002F\u002F BAD: Restates the code\n\u002F\u002F Increment counter by 1\ncounter += 1;\n\n\u002F\u002F GOOD: Explains non-obvious intent\n\u002F\u002F Rate limit uses a sliding window — reset counter at window boundary,\n\u002F\u002F not on a fixed schedule, to prevent burst attacks at window edges\nif (now - windowStart > WINDOW_SIZE_MS) {\n  counter = 0;\n  windowStart = now;\n}\n```\n\n### When NOT to Comment\n\n```typescript\n\u002F\u002F Don't comment self-explanatory code\nfunction calculateTotal(items: CartItem[]): number {\n  return items.reduce((sum, item) => sum + item.price * item.quantity, 0);\n}\n\n\u002F\u002F Don't leave TODO comments for things you should just do now\n\u002F\u002F TODO: add error handling  ← Just add it\n\n\u002F\u002F Don't leave commented-out code\n\u002F\u002F const oldImplementation = () => { ... }  ← Delete it, git has history\n```\n\n### Document Known Gotchas\n\n```typescript\n\u002F**\n * IMPORTANT: This function must be called before the first render.\n * If called after hydration, it causes a flash of unstyled content\n * because the theme context isn't available during SSR.\n *\n * See ADR-003 for the full design rationale.\n *\u002F\nexport function initializeTheme(theme: Theme): void {\n  \u002F\u002F ...\n}\n```\n\n## API Documentation\n\nFor public APIs (REST, GraphQL, library interfaces):\n\n### Inline with Types (Preferred for TypeScript)\n\n```typescript\n\u002F**\n * Creates a new task.\n *\n * @param input - Task creation data (title required, description optional)\n * @returns The created task with server-generated ID and timestamps\n * @throws {ValidationError} If title is empty or exceeds 200 characters\n * @throws {AuthenticationError} If the user is not authenticated\n *\n * @example\n * const task = await createTask({ title: 'Buy groceries' });\n * console.log(task.id); \u002F\u002F \"task_abc123\"\n *\u002F\nexport async function createTask(input: CreateTaskInput): Promise\u003CTask> {\n  \u002F\u002F ...\n}\n```\n\n### OpenAPI \u002F Swagger for REST APIs\n\n```yaml\npaths:\n  \u002Fapi\u002Ftasks:\n    post:\n      summary: Create a task\n      requestBody:\n        required: true\n        content:\n          application\u002Fjson:\n            schema:\n              $ref: '#\u002Fcomponents\u002Fschemas\u002FCreateTaskInput'\n      responses:\n        '201':\n          description: Task created\n          content:\n            application\u002Fjson:\n              schema:\n                $ref: '#\u002Fcomponents\u002Fschemas\u002FTask'\n        '422':\n          description: Validation error\n```\n\n## README Structure\n\nEvery project should have a README that covers:\n\n```markdown\n# Project Name\n\nOne-paragraph description of what this project does.\n\n## Quick Start\n1. Clone the repo\n2. Install dependencies: `npm install`\n3. Set up environment: `cp .env.example .env`\n4. Run the dev server: `npm run dev`\n\n## Commands\n| Command | Description |\n|---------|-------------|\n| `npm run dev` | Start development server |\n| `npm test` | Run tests |\n| `npm run build` | Production build |\n| `npm run lint` | Run linter |\n\n## Architecture\nBrief overview of the project structure and key design decisions.\nLink to ADRs for details.\n\n## Contributing\nHow to contribute, coding standards, PR process.\n```\n\n## Changelog Maintenance\n\nFor shipped features:\n\n```markdown\n# Changelog\n\n## [1.2.0] - 2025-01-20\n### Added\n- Task sharing: users can share tasks with team members (#123)\n- Email notifications for task assignments (#124)\n\n### Fixed\n- Duplicate tasks appearing when rapidly clicking create button (#125)\n\n### Changed\n- Task list now loads 50 items per page (was 20) for better UX (#126)\n```\n\n## Documentation for Agents\n\nSpecial consideration for AI agent context:\n\n- **CLAUDE.md \u002F rules files** — Document project conventions so agents follow them\n- **Spec files** — Keep specs updated so agents build the right thing\n- **ADRs** — Help agents understand why past decisions were made (prevents re-deciding)\n- **Inline gotchas** — Prevent agents from falling into known traps\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"The code is self-documenting\" | Code shows what. It doesn't show why, what alternatives were rejected, or what constraints apply. |\n| \"We'll write docs when the API stabilizes\" | APIs stabilize faster when you document them. The doc is the first test of the design. |\n| \"Nobody reads docs\" | Agents do. Future engineers do. Your 3-months-later self does. |\n| \"ADRs are overhead\" | A 10-minute ADR prevents a 2-hour debate about the same decision six months later. |\n| \"Comments get outdated\" | Comments on *why* are stable. Comments on *what* get outdated — that's why you only write the former. |\n\n## Red Flags\n\n- Architectural decisions with no written rationale\n- Public APIs with no documentation or types\n- README that doesn't explain how to run the project\n- Commented-out code instead of deletion\n- TODO comments that have been there for weeks\n- No ADRs in a project with significant architectural choices\n- Documentation that restates the code instead of explaining intent\n\n## Verification\n\nAfter documenting:\n\n- [ ] ADRs exist for all significant architectural decisions\n- [ ] README covers quick start, commands, and architecture overview\n- [ ] API functions have parameter and return type documentation\n- [ ] Known gotchas are documented inline where they matter\n- [ ] No commented-out code remains\n- [ ] Rules files (CLAUDE.md etc.) are current and accurate\n",{"name":5,"description":7},"main","215248b05d6d96e163fec33f3c171019a95abd72",".claude\u002Fskills\u002Fosmani-picks\u002Fskills\u002Fdocumentation-and-adrs","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fthegiantbeast","https:\u002F\u002Fthegiantbeast.tech","2026-11-14 22:47:32",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add thegiantbeast\u002Fdotfiles --skill documentation-and-adrs",{"tool":44,"command":45},"bunx","bunx skills add thegiantbeast\u002Fdotfiles --skill documentation-and-adrs",{"tool":47,"command":48},"pnpm","pnpm dlx skills add thegiantbeast\u002Fdotfiles --skill documentation-and-adrs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fosmani-picks\u002Fskills\u002Fdocumentation-and-adrs\u002FSKILL.md",true,[],[53,60,92,109,118,127],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":59},"01M7DRX19Z4CVSNJQTYT6S1Z2A","context7-mcp","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcontext7-mcp\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"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":76,"publishedAt":26},"01M6CA623HKJ9PE7HJC00DXM04","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\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fweb-quality-audit\u002FSKILL.md",[66,71],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[77,78,79,80,81,82,83,84,85,25,86,87,88,89,90,91],"quality","web","audit","web quality audit","check","review","best practices","page","Lighthouse","site","accessibility","performance","run","seo","website",{"skillNo":93,"name":90,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":99,"publishedAt":26},"01M6CA5Z9ZK57YANF0QTVXNNKJ","Optimize for search engine visibility and ranking. Use when asked to \"improve SEO\", \"optimize for search\", \"fix meta tags\", \"add structured data\", \"sitemap optimization\", or \"search engine optimization\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fseo\u002FSKILL.md",[97,98],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[90,78,100,101,102,103,104,105,25,106,107,77,108],"Optimization","search","Meta","fix","structured data","improve","Meta Tags","engine","data",{"skillNo":110,"name":88,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":26},"01M6CA5W80QAXDSZC196SY8DZC","Optimize web performance for faster loading and better user experience. Use when asked to \"speed up my site\", \"optimize performance\", \"reduce load time\", \"fix slow loading\", \"improve page speed\", or \"performance audit\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fperformance\u002FSKILL.md",[],[88,79,115,116,84,117,103,105,25,78,77,86],"user","web performance","up",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":26},"01M6CA5SHNJN3B562C279YE2BV","core-web-vitals","Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to \"improve Core Web Vitals\", \"fix LCP\", \"reduce CLS\", \"optimize INP\", \"page experience optimization\", or \"fix layout shifts\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fcore-web-vitals\u002FSKILL.md",[],[125,126,78,100,84,77,101,103,105,25],"core web vitals","core",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":26},"01M6CA5PSD25C6WSNBEHKHR8QK","best-practices","Apply modern web development best practices for security, compatibility, and code quality. Use when asked to \"apply best practices\", \"security audit\", \"modernize code\", \"code quality review\", or \"check for vulnerabilities\".","https:\u002F\u002Fgithub.com\u002Fthegiantbeast\u002Fdotfiles\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweb-quality-picks\u002Fskills\u002Fbest-practices\u002FSKILL.md",[],[83,134,135,136,25,137,82,81,78,79,77,138,139,140],"code quality","development","security audit","code","vulnerabilities","web development","security"]