メニュー
Guardrails for edits to core/base-client.js covering auth injection, retries, circuit breaker behavior, and request/response events. Use when modifying the universal API client or its auth/retry/error handling.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/thefixer3x/onasis-gateway --skill base-client-guardianコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use this skill when recording, recalling, or analyzing behavioral workflow patterns via the LanOnasis MaaS API. Trigger when the user or an agent wants to save a successful workflow for future reuse, recall past patterns before starting a task, analyze how Claude has handled similar tasks before, or when working with the `@lanonasis/mem-intel-sdk` behavior features. Also trigger when the user says things like "remember how I did this", "what's my usual pattern for X", "log this workflow", or "use my previous approach."
Use this skill when adding new methods, tools, or schema changes to the `@lanonasis/mem-intel-sdk`. Trigger when the user wants to extend the SDK with new capabilities, add a new MCP tool to mcp-core, add a new intelligence endpoint, or migrate the behavior_patterns schema. Also trigger when the user says things like "add a new tool to the SDK", "extend mem-intel-sdk", "add behavior X to the MCP server", or "update the SDK schema." Do NOT use for general behavior pattern recording/recall — use the behavior-memory skill for that.
Guardrails for edits to core/security/compliance-manager.js that preserve PCI/GDPR/PSD2/SOX/HIPAA controls (masking, encryption, SCA, consent checks, and audit logging). Use when changing compliance validators, security handling, or audit flows.
SKILL.md を表示中
| name | base-client-guardian |
| description | Guardrails for edits to core/base-client.js covering auth injection, retries, circuit breaker behavior, and request/response events. Use when modifying the universal API client or its auth/retry/error handling. |
This skill applies when modifying the Universal API Client (core/base-client.js).
The Base Client provides:
request() - Main entry point for API callsretryRequest() - Handles retry logic with backoffhealthCheck() - Service health verificationgenerateMethods() - Dynamic method generation from endpointsaddAuthentication() - Auth injection into requestsrequest - Emitted before each requestresponse - Emitted on successful responseerror - Emitted on request failurecircuit-breaker-open - Emitted when circuit opensbearer - Bearer token authapikey - API key (header or query)basic - Basic authhmac - HMAC signature authoauth2 - OAuth 2.0 authCLOSED -> OPEN -> HALF_OPEN -> CLOSED// MUST use exponential backoff
const delay = this.config.retryDelay * Math.pow(2, attempt - 1);
// MUST check shouldRetry() before retrying
if (attempt < this.config.retryAttempts && this.shouldRetry(error)) {
await this.sleep(delay);
return this.retryRequest(config, attempt + 1);
}
// MUST emit events after state changes
this.emit('request', { service, method, url, timestamp });
this.emit('response', { service, status, statusText, timestamp });
this.emit('error', { service, type, message, status, timestamp });
// MUST follow state machine
// On success: reset to CLOSED
this.circuitBreaker.failures = 0;
this.circuitBreaker.state = 'CLOSED';
// On failure: increment and potentially open
this.circuitBreaker.failures++;
if (this.circuitBreaker.failures >= 5) {
this.circuitBreaker.state = 'OPEN';
this.emit('circuit-breaker-open', { service, failures });
}
// On timeout: transition to HALF_OPEN
if (timeSinceLastFailure > 60000) {
this.circuitBreaker.state = 'HALF_OPEN';
}
// MUST handle all auth types in switch statement
switch (auth.type) {
case 'bearer':
case 'apikey':
case 'basic':
case 'hmac':
case 'oauth2':
// Implementation here
break;
}
// Add to the switch statement in addAuthentication()
case 'custom_auth_type':
config.headers['X-Custom-Auth'] = auth.config.customValue;
break;
// Extend shouldRetry() - do NOT replace existing conditions
shouldRetry(error) {
return (
error.code === 'ECONNRESET' ||
error.code === 'ETIMEDOUT' ||
error.code === 'ENOTFOUND' ||
error.code === 'YOUR_NEW_CODE' || // ADD here
(error.response && error.response.status >= 500)
);
}
// Add new events - do NOT modify existing event signatures
this.emit('your-new-event', { service, customData, timestamp });
| Component | Integration Method |
|---|---|
| Metrics Collector | Listen to request, response, error events |
| Compliance Manager | Intercept in addAuthentication() |
| Version Manager | Pass version in request options |
| Vendor Abstraction | Uses request() method |
Before any changes to this file:
# 1. Run existing tests
npm test -- --grep "BaseClient"
# 2. Verify authentication works for all types
node -e "const BaseClient = require('./core/base-client'); const client = new BaseClient({ name: 'test', baseUrl: 'https://httpbin.org' }); console.log('Client initialized:', client.config.name);"
# 3. Test circuit breaker states
# Verify: CLOSED -> OPEN (after 5 failures) -> HALF_OPEN (after 60s)
# 4. Test retry logic
# Verify exponential backoff: delay * 2^(attempt-1)
If changes cause issues:
Immediate Rollback
git checkout HEAD~1 -- core/base-client.js
Verify Recovery
# Restart the server
bun run dev
# Check health endpoint
curl http://localhost:3001/health
Event Listener Check
// Verify all components can still receive events
client.on('request', () => console.log('Request event works'));
client.on('response', () => console.log('Response event works'));
client.on('error', () => console.log('Error event works'));
SOC 職業分類に基づく