{"owner":"lostisland","repo":"faraday","hasSkills":true,"totalSkillsCount":3,"totalTokensCount":1253,"categories":["claude-rule","cursor-rule","copilot-instructions"],"hasMcp":false,"mcpConfig":null,"found":[".claude/CLAUDE.md",".cursorrules",".github/copilot-instructions.md"],"skills":{".claude/CLAUDE.md":"# Claude AI Agent Instructions for Faraday\n\n## About Faraday\nFaraday is a Ruby HTTP client library with a middleware-based architecture (similar to Rack). It provides a common interface over various HTTP adapters and uses middleware for request/response processing.\n\n## Primary Directive – IMPORTANT: DO NOT SKIP\n**Before making any code changes or suggestions**, you **must** read and follow the comprehensive guidelines in `.ai/guidelines.md`.\nAfter you've done so, provide a confirmation message to the user, then proceed with the task at hand.\n\n## Your Responsibilities\n1. **Read** `.ai/guidelines.md` for all Faraday-specific conventions and patterns\n2. **Follow** the established conventions documented there\n3. **Propose updates** to `.ai/guidelines.md` when you identify:\n   - New code patterns not yet documented\n   - Changes to existing conventions\n   - Inconsistencies between guidelines and actual codebase\n\n## Important Context\n- **New middleware and adapters** should be created as separate gems, NOT added to the base Faraday repository (with rare exceptions for widely-used core middleware)\n- See [faraday-net_http](https://github.com/lostisland/faraday-net_http) as an example adapter in its own repository\n- Focus on Faraday-specific patterns, not generic Ruby/RSpec advice\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete Faraday conventions (PRIMARY REFERENCE)\n- `.github/CONTRIBUTING.md` - Contribution process and policies\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware implementation\n\n---\n\n**Keep `.ai/guidelines.md` current.** Propose updates when you notice any drift between documentation and reality.\n",".cursorrules":"# Cursor AI Rules for Faraday Repository\n\n## Primary Guidelines Reference\n**CRITICAL**: Before making any code changes, read `.ai/guidelines.md` for comprehensive Faraday-specific conventions.\n\n## About Faraday\nFaraday is a Ruby HTTP client library with a middleware-based architecture similar to Rack. It provides a common interface over many HTTP adapters and uses middleware for request/response processing.\n\n## Core Responsibilities\n1. **Read** `.ai/guidelines.md` for all implementation details, patterns, and conventions\n2. **Follow** the Faraday-specific patterns documented in the guidelines\n3. **Propose updates** to `.ai/guidelines.md` when conventions change or new patterns emerge\n\n## Important Context\n- **New middleware and adapters** belong in separate repositories and gems, NOT in the base Faraday repo\n  - Only middleware used by the vast majority of projects can be considered for the base repo\n  - See [faraday-net_http](https://github.com/lostisland/faraday-net_http) for an example adapter in its own repository\n- Focus on Faraday-specific patterns, not generic Ruby/RSpec knowledge\n- Run tests with `bundle exec rspec` and check style with `bundle exec rubocop`\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete conventions and patterns (READ THIS FIRST)\n- `.github/CONTRIBUTING.md` - Contribution process and workflow\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware\n\n---\n\n**Self-Maintaining**: Keep `.ai/guidelines.md` aligned with the actual codebase. Propose updates when you detect any divergence.\n",".github/copilot-instructions.md":"# GitHub Copilot Instructions for Faraday\n\n## Essential Reading\n**Before making any code suggestions**, consult `.ai/guidelines.md` for comprehensive Faraday-specific conventions and patterns.\n\n## About This Repository\nFaraday is a Ruby HTTP client library that provides:\n- A middleware-based architecture (similar to Rack)\n- A common interface over various HTTP adapters (Net::HTTP, HTTPClient, etc.)\n- Extensible request/response processing pipeline\n\n## Your Responsibilities\nAs GitHub Copilot working on Faraday, you must:\n\n1. **Read & Follow**: Always reference `.ai/guidelines.md` for all Faraday conventions and implementation details\n2. **Stay Current**: Suggest updates to `.ai/guidelines.md` when you notice:\n   - New patterns not yet documented\n   - Changes to existing conventions\n   - Discrepancies between guidelines and actual code\n3. **Focus on Faraday**: Provide Faraday-specific guidance, not generic Ruby/RSpec tips\n\n## Critical Context\n\n### Middleware and Adapters\n- **New middleware and adapters should be separate gems**, NOT added to the base Faraday repository\n- Only middleware expected to be used by the vast majority of projects can be considered for the base repo\n- See [faraday-net_http](https://github.com/lostisland/faraday-net_http) as an example of an adapter in its own repository\n- Consult `.ai/guidelines.md` for detailed implementation patterns\n\n### Code Quality\n- Follow RuboCop style guide (`.rubocop.yml`)\n- Run tests: `bundle exec rake` (integration specs in `spec/integration/` run separately with `bin/integration-tests`)\n- Check style: `bundle exec rubocop`\n- Use inclusive language (see `.github/CONTRIBUTING.md`)\n\n## Self-Maintaining Guidelines\nKeep `.ai/guidelines.md` accurate and current. When you identify code patterns not reflected in guidelines, convention changes, or better practices, propose updates to maintain alignment with the actual codebase.\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete conventions and patterns (PRIMARY REFERENCE)\n- `.github/CONTRIBUTING.md` - Contribution process and workflow\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware implementation\n- `.rubocop.yml` - Code style guide\n\n---\n\n**Remember**: The guidelines in `.ai/guidelines.md` are the source of truth for Faraday conventions. Keep them current and refer to them consistently.\n"},"files":{".claude/CLAUDE.md":"# Claude AI Agent Instructions for Faraday\n\n## About Faraday\nFaraday is a Ruby HTTP client library with a middleware-based architecture (similar to Rack). It provides a common interface over various HTTP adapters and uses middleware for request/response processing.\n\n## Primary Directive – IMPORTANT: DO NOT SKIP\n**Before making any code changes or suggestions**, you **must** read and follow the comprehensive guidelines in `.ai/guidelines.md`.\nAfter you've done so, provide a confirmation message to the user, then proceed with the task at hand.\n\n## Your Responsibilities\n1. **Read** `.ai/guidelines.md` for all Faraday-specific conventions and patterns\n2. **Follow** the established conventions documented there\n3. **Propose updates** to `.ai/guidelines.md` when you identify:\n   - New code patterns not yet documented\n   - Changes to existing conventions\n   - Inconsistencies between guidelines and actual codebase\n\n## Important Context\n- **New middleware and adapters** should be created as separate gems, NOT added to the base Faraday repository (with rare exceptions for widely-used core middleware)\n- See [faraday-net_http](https://github.com/lostisland/faraday-net_http) as an example adapter in its own repository\n- Focus on Faraday-specific patterns, not generic Ruby/RSpec advice\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete Faraday conventions (PRIMARY REFERENCE)\n- `.github/CONTRIBUTING.md` - Contribution process and policies\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware implementation\n\n---\n\n**Keep `.ai/guidelines.md` current.** Propose updates when you notice any drift between documentation and reality.\n",".cursorrules":"# Cursor AI Rules for Faraday Repository\n\n## Primary Guidelines Reference\n**CRITICAL**: Before making any code changes, read `.ai/guidelines.md` for comprehensive Faraday-specific conventions.\n\n## About Faraday\nFaraday is a Ruby HTTP client library with a middleware-based architecture similar to Rack. It provides a common interface over many HTTP adapters and uses middleware for request/response processing.\n\n## Core Responsibilities\n1. **Read** `.ai/guidelines.md` for all implementation details, patterns, and conventions\n2. **Follow** the Faraday-specific patterns documented in the guidelines\n3. **Propose updates** to `.ai/guidelines.md` when conventions change or new patterns emerge\n\n## Important Context\n- **New middleware and adapters** belong in separate repositories and gems, NOT in the base Faraday repo\n  - Only middleware used by the vast majority of projects can be considered for the base repo\n  - See [faraday-net_http](https://github.com/lostisland/faraday-net_http) for an example adapter in its own repository\n- Focus on Faraday-specific patterns, not generic Ruby/RSpec knowledge\n- Run tests with `bundle exec rspec` and check style with `bundle exec rubocop`\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete conventions and patterns (READ THIS FIRST)\n- `.github/CONTRIBUTING.md` - Contribution process and workflow\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware\n\n---\n\n**Self-Maintaining**: Keep `.ai/guidelines.md` aligned with the actual codebase. Propose updates when you detect any divergence.\n",".github/copilot-instructions.md":"# GitHub Copilot Instructions for Faraday\n\n## Essential Reading\n**Before making any code suggestions**, consult `.ai/guidelines.md` for comprehensive Faraday-specific conventions and patterns.\n\n## About This Repository\nFaraday is a Ruby HTTP client library that provides:\n- A middleware-based architecture (similar to Rack)\n- A common interface over various HTTP adapters (Net::HTTP, HTTPClient, etc.)\n- Extensible request/response processing pipeline\n\n## Your Responsibilities\nAs GitHub Copilot working on Faraday, you must:\n\n1. **Read & Follow**: Always reference `.ai/guidelines.md` for all Faraday conventions and implementation details\n2. **Stay Current**: Suggest updates to `.ai/guidelines.md` when you notice:\n   - New patterns not yet documented\n   - Changes to existing conventions\n   - Discrepancies between guidelines and actual code\n3. **Focus on Faraday**: Provide Faraday-specific guidance, not generic Ruby/RSpec tips\n\n## Critical Context\n\n### Middleware and Adapters\n- **New middleware and adapters should be separate gems**, NOT added to the base Faraday repository\n- Only middleware expected to be used by the vast majority of projects can be considered for the base repo\n- See [faraday-net_http](https://github.com/lostisland/faraday-net_http) as an example of an adapter in its own repository\n- Consult `.ai/guidelines.md` for detailed implementation patterns\n\n### Code Quality\n- Follow RuboCop style guide (`.rubocop.yml`)\n- Run tests: `bundle exec rake` (integration specs in `spec/integration/` run separately with `bin/integration-tests`)\n- Check style: `bundle exec rubocop`\n- Use inclusive language (see `.github/CONTRIBUTING.md`)\n\n## Self-Maintaining Guidelines\nKeep `.ai/guidelines.md` accurate and current. When you identify code patterns not reflected in guidelines, convention changes, or better practices, propose updates to maintain alignment with the actual codebase.\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete conventions and patterns (PRIMARY REFERENCE)\n- `.github/CONTRIBUTING.md` - Contribution process and workflow\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware implementation\n- `.rubocop.yml` - Code style guide\n\n---\n\n**Remember**: The guidelines in `.ai/guidelines.md` are the source of truth for Faraday conventions. Keep them current and refer to them consistently.\n"},"items":[{"name":".cursorrules","path":".cursorrules","rawUrl":"https://raw.githubusercontent.com/lostisland/faraday/HEAD/.cursorrules","title":"Cursor IDE Native Rules","category":"cursor-rule","format":"markdown","content":"# Cursor AI Rules for Faraday Repository\n\n## Primary Guidelines Reference\n**CRITICAL**: Before making any code changes, read `.ai/guidelines.md` for comprehensive Faraday-specific conventions.\n\n## About Faraday\nFaraday is a Ruby HTTP client library with a middleware-based architecture similar to Rack. It provides a common interface over many HTTP adapters and uses middleware for request/response processing.\n\n## Core Responsibilities\n1. **Read** `.ai/guidelines.md` for all implementation details, patterns, and conventions\n2. **Follow** the Faraday-specific patterns documented in the guidelines\n3. **Propose updates** to `.ai/guidelines.md` when conventions change or new patterns emerge\n\n## Important Context\n- **New middleware and adapters** belong in separate repositories and gems, NOT in the base Faraday repo\n  - Only middleware used by the vast majority of projects can be considered for the base repo\n  - See [faraday-net_http](https://github.com/lostisland/faraday-net_http) for an example adapter in its own repository\n- Focus on Faraday-specific patterns, not generic Ruby/RSpec knowledge\n- Run tests with `bundle exec rspec` and check style with `bundle exec rubocop`\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete conventions and patterns (READ THIS FIRST)\n- `.github/CONTRIBUTING.md` - Contribution process and workflow\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware\n\n---\n\n**Self-Maintaining**: Keep `.ai/guidelines.md` aligned with the actual codebase. Propose updates when you detect any divergence.\n","isInternal":false,"tokens":354,"sizeBytes":1591},{"name":"CLAUDE.md","path":".claude/CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/lostisland/faraday/HEAD/.claude/CLAUDE.md","title":".claude - Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","content":"# Claude AI Agent Instructions for Faraday\n\n## About Faraday\nFaraday is a Ruby HTTP client library with a middleware-based architecture (similar to Rack). It provides a common interface over various HTTP adapters and uses middleware for request/response processing.\n\n## Primary Directive – IMPORTANT: DO NOT SKIP\n**Before making any code changes or suggestions**, you **must** read and follow the comprehensive guidelines in `.ai/guidelines.md`.\nAfter you've done so, provide a confirmation message to the user, then proceed with the task at hand.\n\n## Your Responsibilities\n1. **Read** `.ai/guidelines.md` for all Faraday-specific conventions and patterns\n2. **Follow** the established conventions documented there\n3. **Propose updates** to `.ai/guidelines.md` when you identify:\n   - New code patterns not yet documented\n   - Changes to existing conventions\n   - Inconsistencies between guidelines and actual codebase\n\n## Important Context\n- **New middleware and adapters** should be created as separate gems, NOT added to the base Faraday repository (with rare exceptions for widely-used core middleware)\n- See [faraday-net_http](https://github.com/lostisland/faraday-net_http) as an example adapter in its own repository\n- Focus on Faraday-specific patterns, not generic Ruby/RSpec advice\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete Faraday conventions (PRIMARY REFERENCE)\n- `.github/CONTRIBUTING.md` - Contribution process and policies\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware implementation\n\n---\n\n**Keep `.ai/guidelines.md` current.** Propose updates when you notice any drift between documentation and reality.\n","isInternal":false,"tokens":370,"sizeBytes":1698},{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","rawUrl":"https://raw.githubusercontent.com/lostisland/faraday/HEAD/.github/copilot-instructions.md","title":"GitHub Copilot Instructions","category":"copilot-instructions","format":"markdown","content":"# GitHub Copilot Instructions for Faraday\n\n## Essential Reading\n**Before making any code suggestions**, consult `.ai/guidelines.md` for comprehensive Faraday-specific conventions and patterns.\n\n## About This Repository\nFaraday is a Ruby HTTP client library that provides:\n- A middleware-based architecture (similar to Rack)\n- A common interface over various HTTP adapters (Net::HTTP, HTTPClient, etc.)\n- Extensible request/response processing pipeline\n\n## Your Responsibilities\nAs GitHub Copilot working on Faraday, you must:\n\n1. **Read & Follow**: Always reference `.ai/guidelines.md` for all Faraday conventions and implementation details\n2. **Stay Current**: Suggest updates to `.ai/guidelines.md` when you notice:\n   - New patterns not yet documented\n   - Changes to existing conventions\n   - Discrepancies between guidelines and actual code\n3. **Focus on Faraday**: Provide Faraday-specific guidance, not generic Ruby/RSpec tips\n\n## Critical Context\n\n### Middleware and Adapters\n- **New middleware and adapters should be separate gems**, NOT added to the base Faraday repository\n- Only middleware expected to be used by the vast majority of projects can be considered for the base repo\n- See [faraday-net_http](https://github.com/lostisland/faraday-net_http) as an example of an adapter in its own repository\n- Consult `.ai/guidelines.md` for detailed implementation patterns\n\n### Code Quality\n- Follow RuboCop style guide (`.rubocop.yml`)\n- Run tests: `bundle exec rake` (integration specs in `spec/integration/` run separately with `bin/integration-tests`)\n- Check style: `bundle exec rubocop`\n- Use inclusive language (see `.github/CONTRIBUTING.md`)\n\n## Self-Maintaining Guidelines\nKeep `.ai/guidelines.md` accurate and current. When you identify code patterns not reflected in guidelines, convention changes, or better practices, propose updates to maintain alignment with the actual codebase.\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete conventions and patterns (PRIMARY REFERENCE)\n- `.github/CONTRIBUTING.md` - Contribution process and workflow\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware implementation\n- `.rubocop.yml` - Code style guide\n\n---\n\n**Remember**: The guidelines in `.ai/guidelines.md` are the source of truth for Faraday conventions. Keep them current and refer to them consistently.\n","isInternal":false,"tokens":529,"sizeBytes":2384}],"systemPromptSnippet":"<yakaai_skills repo=\"lostisland/faraday\">\n<!-- File: .cursorrules (Tokens: ~354 | Category: cursor-rule) -->\n# Cursor AI Rules for Faraday Repository\n\n## Primary Guidelines Reference\n**CRITICAL**: Before making any code changes, read `.ai/guidelines.md` for comprehensive Faraday-specific conventions.\n\n## About Faraday\nFaraday is a Ruby HTTP client library with a middleware-based architecture similar to Rack. It provides a common interface over many HTTP adapters and uses middleware for request/response processing.\n\n## Core Responsibilities\n1. **Read** `.ai/guidelines.md` for all implementation details, patterns, and conventions\n2. **Follow** the Faraday-specific patterns documented in the guidelines\n3. **Propose updates** to `.ai/guidelines.md` when conventions change or new patterns emerge\n\n## Important Context\n- **New middleware and adapters** belong in separate repositories and gems, NOT in the base Faraday repo\n  - Only middleware used by the vast majority of projects can be considered for the base repo\n  - See [faraday-net_http](https://github.com/lostisland/faraday-net_http) for an example adapter in its own repository\n- Focus on Faraday-specific patterns, not generic Ruby/RSpec knowledge\n- Run tests with `bundle exec rspec` and check style with `bundle exec rubocop`\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete conventions and patterns (READ THIS FIRST)\n- `.github/CONTRIBUTING.md` - Contribution process and workflow\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware\n\n---\n\n**Self-Maintaining**: Keep `.ai/guidelines.md` aligned with the actual codebase. Propose updates when you detect any divergence.\n\n<!-- File: .claude/CLAUDE.md (Tokens: ~370 | Category: claude-rule) -->\n# Claude AI Agent Instructions for Faraday\n\n## About Faraday\nFaraday is a Ruby HTTP client library with a middleware-based architecture (similar to Rack). It provides a common interface over various HTTP adapters and uses middleware for request/response processing.\n\n## Primary Directive – IMPORTANT: DO NOT SKIP\n**Before making any code changes or suggestions**, you **must** read and follow the comprehensive guidelines in `.ai/guidelines.md`.\nAfter you've done so, provide a confirmation message to the user, then proceed with the task at hand.\n\n## Your Responsibilities\n1. **Read** `.ai/guidelines.md` for all Faraday-specific conventions and patterns\n2. **Follow** the established conventions documented there\n3. **Propose updates** to `.ai/guidelines.md` when you identify:\n   - New code patterns not yet documented\n   - Changes to existing conventions\n   - Inconsistencies between guidelines and actual codebase\n\n## Important Context\n- **New middleware and adapters** should be created as separate gems, NOT added to the base Faraday repository (with rare exceptions for widely-used core middleware)\n- See [faraday-net_http](https://github.com/lostisland/faraday-net_http) as an example adapter in its own repository\n- Focus on Faraday-specific patterns, not generic Ruby/RSpec advice\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete Faraday conventions (PRIMARY REFERENCE)\n- `.github/CONTRIBUTING.md` - Contribution process and policies\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware implementation\n\n---\n\n**Keep `.ai/guidelines.md` current.** Propose updates when you notice any drift between documentation and reality.\n\n<!-- File: .github/copilot-instructions.md (Tokens: ~529 | Category: copilot-instructions) -->\n# GitHub Copilot Instructions for Faraday\n\n## Essential Reading\n**Before making any code suggestions**, consult `.ai/guidelines.md` for comprehensive Faraday-specific conventions and patterns.\n\n## About This Repository\nFaraday is a Ruby HTTP client library that provides:\n- A middleware-based architecture (similar to Rack)\n- A common interface over various HTTP adapters (Net::HTTP, HTTPClient, etc.)\n- Extensible request/response processing pipeline\n\n## Your Responsibilities\nAs GitHub Copilot working on Faraday, you must:\n\n1. **Read & Follow**: Always reference `.ai/guidelines.md` for all Faraday conventions and implementation details\n2. **Stay Current**: Suggest updates to `.ai/guidelines.md` when you notice:\n   - New patterns not yet documented\n   - Changes to existing conventions\n   - Discrepancies between guidelines and actual code\n3. **Focus on Faraday**: Provide Faraday-specific guidance, not generic Ruby/RSpec tips\n\n## Critical Context\n\n### Middleware and Adapters\n- **New middleware and adapters should be separate gems**, NOT added to the base Faraday repository\n- Only middleware expected to be used by the vast majority of projects can be considered for the base repo\n- See [faraday-net_http](https://github.com/lostisland/faraday-net_http) as an example of an adapter in its own repository\n- Consult `.ai/guidelines.md` for detailed implementation patterns\n\n### Code Quality\n- Follow RuboCop style guide (`.rubocop.yml`)\n- Run tests: `bundle exec rake` (integration specs in `spec/integration/` run separately with `bin/integration-tests`)\n- Check style: `bundle exec rubocop`\n- Use inclusive language (see `.github/CONTRIBUTING.md`)\n\n## Self-Maintaining Guidelines\nKeep `.ai/guidelines.md` accurate and current. When you identify code patterns not reflected in guidelines, convention changes, or better practices, propose updates to maintain alignment with the actual codebase.\n\n## Reference Files\n- **`.ai/guidelines.md`** - Complete conventions and patterns (PRIMARY REFERENCE)\n- `.github/CONTRIBUTING.md` - Contribution process and workflow\n- `lib/faraday/middleware.rb` - Middleware base class\n- `lib/faraday/request/json.rb` - Example middleware implementation\n- `.rubocop.yml` - Code style guide\n\n---\n\n**Remember**: The guidelines in `.ai/guidelines.md` are the source of truth for Faraday conventions. Keep them current and refer to them consistently.\n</yakaai_skills>"}