[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75139H4FTEX0H3R8RT4J1D7":3,"skill-same:01M75139H4FTEX0H3R8RT4J1D7":44},{"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":6,"updatedAt":29,"install":30,"resources":43},"01M75139H4FTEX0H3R8RT4J1D7","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.","chrisbarrantes\u002Fmandrel","chrisbarrantes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4534419?v=4","01M7511VXT2H7WE09JE4ZMBESG","Chris Barrantes","01M7511VYGPFHQCE9HNVKES0QN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcore\u002Fdocumentation-and-adrs\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: documentation-and-adrs\ndescription:\n  Records decisions and documentation. Use when making architectural decisions,\n  changing public APIs, shipping features, or when you need to record context\n  that future engineers and agents will need to understand the codebase.\n---\n\n# Documentation and ADRs\n\n## Policy Capsule\n\n- Document the **why**, not the what. Capture context, constraints, alternatives considered, and trade-offs — code already shows what was built.\n- Write an ADR for any decision that would be expensive to reverse (framework choice, data model, auth strategy, API architecture, hosting platform).\n- Store ADRs at `docs\u002Fdecisions\u002F` with sequential numbering (`ADR-001`, `ADR-002`, …) and the canonical sections: **Status, Date, Context, Decision, Alternatives Considered, Consequences**.\n- Mark an ADR's status as `Accepted`, `Superseded by ADR-XXX`, or `Deprecated`. Never silently delete an ADR — supersede it.\n- Do **not** document obvious code; do **not** restate what the code already says. Stale or redundant docs are worse than no docs.\n- Comments explain **non-obvious intent** (the why). If a comment describes what the code does, refactor the code instead.\n- Keep user-facing docs (README, API docs, changelog) updated as part of the change — out-of-date docs are bugs.\n- Pair every public API change with a changelog entry that links the relevant Story\u002FEpic and any superseding ADR.\n- When you find yourself explaining the same thing repeatedly in chat, write it down — the explanation belongs in the project docs or an ADR.\n\n## Overview\n\nDocument decisions, not just code. The most valuable documentation captures the\n_why_ — the context, constraints, and trade-offs that led to a decision. Code\nshows _what_ was built; documentation explains _why it was built this way_ and\n_what alternatives were considered_. This context is essential for future humans\nand 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\nrestate 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\nhighest-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\n\nAccepted | Superseded by ADR-XXX | Deprecated\n\n## Date\n\n2025-01-15\n\n## Context\n\nWe need a primary database for the task management application. Key\nrequirements:\n\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\n\nUse PostgreSQL with Prisma ORM.\n\n## Alternatives Considered\n\n### MongoDB\n\n- Pros: Flexible schema, easy to start with\n- Cons: Our data is inherently relational; would need to manage relationships\n  manually\n- Rejected: Relational data in a document store leads to complex joins or data\n  duplication\n\n### SQLite\n\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\n- Pros: Mature, widely supported\n- Cons: PostgreSQL has better JSON support, full-text search, and ecosystem\n  tooling\n- Rejected: PostgreSQL is the better fit for our feature requirements\n\n## Consequences\n\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```text\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\n  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\n\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\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\n\nBrief overview of the project structure and key design decisions. Link to ADRs\nfor details.\n\n## Contributing\n\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\n### Added\n\n- Task sharing: users can share tasks with team members (#123)\n- Email notifications for task assignments (#124)\n\n### Fixed\n\n- Duplicate tasks appearing when rapidly clicking create button (#125)\n\n### Changed\n\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\n  them\n- **Spec files** — Keep specs updated so agents build the right thing\n- **ADRs** — Help agents understand why past decisions were made (prevents\n  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## Policy Capsule\n\n- Document the **why**, not the what. Capture context, constraints, alternatives considered, and trade-offs — code already shows what was built.\n- Write an ADR for any decision that would be expensive to reverse (framework choice, data model, auth strategy, API architecture, hosting platform).\n- Store ADRs at `docs\u002Fdecisions\u002F` with sequential numbering (`ADR-001`, `ADR-002`, …) and the canonical sections: **Status, Date, Context, Decision, Alternatives Considered, Consequences**.\n- Mark an ADR's status as `Accepted`, `Superseded by ADR-XXX`, or `Deprecated`. Never silently delete an ADR — supersede it.\n- Do **not** document obvious code; do **not** restate what the code already says. Stale or redundant docs are worse than no docs.\n- Comments explain **non-obvious intent** (the why). If a comment describes what the code does, refactor the code instead.\n- Keep user-facing docs (README, API docs, changelog) updated as part of the change — out-of-date docs are bugs.\n- Pair every public API change with a changelog entry that links the relevant Story\u002FEpic and any superseding ADR.\n- When you find yourself explaining the same thing repeatedly in chat, write it down — the explanation belongs in the project docs or an ADR.\n\n## Overview\n\nDocument decisions, not just code. The most valuable documentation captures the\n_why_ — the context, constraints, and trade-offs that led to a decision. Code\nshows _what_ was built; documentation explains _why it was built this way_ and\n_what alternatives were considered_. This context is essential for future humans\nand 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\nrestate 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\nhighest-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\n\nAccepted | Superseded by ADR-XXX | Deprecated\n\n## Date\n\n2025-01-15\n\n## Context\n\nWe need a primary database for the task management application. Key\nrequirements:\n\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\n\nUse PostgreSQL with Prisma ORM.\n\n## Alternatives Considered\n\n### MongoDB\n\n- Pros: Flexible schema, easy to start with\n- Cons: Our data is inherently relational; would need to manage relationships\n  manually\n- Rejected: Relational data in a document store leads to complex joins or data\n  duplication\n\n### SQLite\n\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\n- Pros: Mature, widely supported\n- Cons: PostgreSQL has better JSON support, full-text search, and ecosystem\n  tooling\n- Rejected: PostgreSQL is the better fit for our feature requirements\n\n## Consequences\n\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```text\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\n  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\n\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\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\n\nBrief overview of the project structure and key design decisions. Link to ADRs\nfor details.\n\n## Contributing\n\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\n### Added\n\n- Task sharing: users can share tasks with team members (#123)\n- Email notifications for task assignments (#124)\n\n### Fixed\n\n- Duplicate tasks appearing when rapidly clicking create button (#125)\n\n### Changed\n\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\n  them\n- **Spec files** — Keep specs updated so agents build the right thing\n- **ADRs** — Help agents understand why past decisions were made (prevents\n  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","22b1847659cc2a98f4fb8c24858f2199d91fda66",".agents\u002Fskills\u002Fcore\u002Fdocumentation-and-adrs","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes","2026-05-27 08:16:47",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add chrisbarrantes\u002Fmandrel --skill documentation-and-adrs",{"tool":36,"command":37},"bunx","bunx skills add chrisbarrantes\u002Fmandrel --skill documentation-and-adrs",{"tool":39,"command":40},"pnpm","pnpm dlx skills add chrisbarrantes\u002Fmandrel --skill documentation-and-adrs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcore\u002Fdocumentation-and-adrs\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M75171YZD373TXY5ZWJNXGS9","no-capsule-skill","Fixture without a Policy Capsule section.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002Ftests\u002Forchestration\u002Ffixtures\u002Fskill-capsule\u002Fno-capsule-skill\u002FSKILL.md",[],[],{"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":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7516ZA88ESAAY3JWXBNA56K","backend-security-patterns","Combined backend protocols for authentication (Clerk JWT verification) and PII-safe observability. Use when handling auth on the server, verifying Clerk webhooks via `svix`, scoping metadata via `publicMetadata`\u002F `privateMetadata`, or sanitizing logs to keep emails, tokens, and request bodies out of telemetry.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fsecurity\u002Fbackend-security-patterns\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7516WFQMKD2NGFMDNFG6C4A","vitest","Writes fast, isolated unit and integration tests with Vitest. Use when each test must run on file-save without shared state — `vi.mock()` for external deps, `vi.spyOn()` for call monitoring, AAA structure, and edge-case coverage for null\u002Fundefined\u002Fboundary inputs.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fvitest\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7516T8FX7B0B0D510EE2FAP","playwright","Robust E2E browser testing with Playwright. Use when writing browser-driven tests — leverage auto-waiting (no `waitForTimeout`), prefer user-visible locators (`getByRole`, `getByText`, `getByLabel`) over CSS\u002FXPath, reuse `storageState` for auth, and enable trace-on-first-retry for CI debugging.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7516PHY868BJXHHZJ0FRYSX","playwright-bdd","Wires Gherkin `.feature` files to Playwright via the `playwright-bdd` library. Use when running BDD scenarios on a Playwright runtime — pairs with the `gherkin-authoring` skill (scenario prose) and the `playwright` skill (browser conventions). Drives execution by tag expression with trace-first debugging and Playwright-native sharding.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Fplaywright-bdd\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7516KEGSBBFJXRZWYBKYM4P","lighthouse-baseline","Codifies the capture-and-check baseline pattern for long-running quality signals (Lighthouse scores, bundle size, p95 latency, runtime memory). Use when wiring a new metric that needs a baseline file, paired :capture \u002F :check npm scripts, a tolerance-bounded gate, and a weekly refresh cadence — the goal is a hard CI signal that ratchets only with intent.","https:\u002F\u002Fgithub.com\u002Fchrisbarrantes\u002Fmandrel\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstack\u002Fqa\u002Flighthouse-baseline\u002FSKILL.md",[],[]]