Authoritative documentation
docs/system-core.md
Key directories of system-Core
- HTTP:
core/system-Core/http/*.js - Stream:
core/system-Core/stream/*.js(lib/crawl/→web.js/browser.js; see skillxrk-crawl) - Plugin:
core/system-Core/plugin/*.js - Tasker:
core/system-Core/tasker/*.js - CommonConfig (frontend form Schema):
core/system-Core/commonconfig/*.js - Web UI:
core/system-Core/www/xrk/*
Common locations
- v3 Chat Completions:
core/system-Core/http/ai.js - Configuration management API:
core/system-Core/http/config.js - MCP API:
core/system-Core/http/mcp.js - Console entry:
core/system-Core/www/xrk/
Authoritative entry points
- Project overview:
PROJECT_OVERVIEW.md - Code entry points:
src/andcore/correspond to subdirectories - Related documentation:
docs/corresponding topic documents under
Applicable scenarios
- Need to locate the implementation path and configuration entry of this subsystem.
- Need to quickly provide the change locations and compatibility considerations.
Non-applicable scenarios
- Not used to replace the implementation descriptions of other subsystems.
- Do not fabricate paths or fields when evidence is lacking.
Execution steps
- First confirm that the requirement falls within the responsibility boundary of this skill.
- Then provide the code paths, configuration paths, and key fields.
- Finally, supplement the risk points, verification steps, and regression scope.
Common pitfalls
- Only giving concepts without specific file paths.
- Failing to note that code prevails when documentation and code conflict.
- Ignoring the consistency among configuration, Schema, and consuming code.