context-os
Configure and debug ContextOS manifests, resolver selection, profiles, budgets, and adapter exports.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-11
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- context-os
- description
- Configure and debug ContextOS manifests, resolver selection, profiles, budgets, and adapter exports.
02 资源文件 8
- 参考文档EXAMPLES.md1.2 KB
- 参考文档packs.yaml409 B
- 参考文档references/context-rules.md1.7 KB
- 参考文档references/pipeline.md885 B
- 参考文档references/project-graph.md794 B
- 参考文档rules.yaml373 B
- 参考文档TROUBLESHOOTING.md733 B
- 参考文档VALIDATION.json2.3 KB
03 SKILL.md 正文
context-os
Overview
Guide configuration of the ContextOS compiler, resolver, profiles, and agent exports. Executable behavior lives in the CLI and modules; this Markdown entrypoint is guidance.
When to Use
ContextOS skill selection, context budgets, manifests, project overrides, profiles, exports, and configuration drift. Skip for ordinary application changes that do not affect these contracts.
Rules & Patterns
Inspect the active project and installed skills. Canonical sources live in .agents/core/skills; project overrides in .agents/project/skills; plugins provide additional sources. Native .agents/skills contains generated projections. Manifest precedence is skill.v2.yaml, skill.yaml, then manifestless SKILL.md. Respect the declared entrypoint and resolve contained resource paths relative to its skill directory.
Use the resolver with the task and affected files; inspect reasons, risk, warnings, missing skills, and soft-budget overflow. Load references only when needed. Existing authorization and proportional engineering-workflow apply.
Compile validates sources and builds the registry. Resolve recommends skills for a task; export renders all installed skills allowed by the profile. Export and export --check use the same sources. Adapter activation/globs control client delivery; resolver signals.fileGlobs control recommendations. Neither mechanism establishes that a client loads the instructions.
Read references/context-rules.md for budgeting and references/project-graph.md for graph limits.
Code Examples
In this source checkout: node .agents/ctx.js resolve "Fix IDOR" --files src/auth.ts --json. See EXAMPLES.md for source and consumer command boundaries.
Validation Checklist
- [ ] Project root, winning manifest, declared entrypoint, resources, and overrides match the intended sources.
- [ ] Profile, alias, dependency, and budget diagnostics explain the selection.
- [ ] After source changes, compile/export/check agree; local contracts and live client evidence are reported separately.
Common Mistakes
Editing generated projections; assuming catalog skills are installed; treating an estimated budget as total prompt size; expecting AST or document selection from the package graph; claiming schema validation proves agent behavior.
Integration Notes
context-manager is a deprecated compatibility alias. engineering-workflow owns the lifecycle; security owns protected boundaries. packs.yaml and rules.yaml are reference data, not executable policy.
04 同仓库更多 Skills
scoped-frontend
Frontend component design and React guidelines
scoped-backend
Backend service architecture and API endpoints
engineering-workflow
Core software engineering lifecycle workflow
team-auth
ContextOS skill for team-auth
claude
暂无简介
team-order
Team conventions for createOrder and item name normalization in src/order.ts.