Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

context-engineering

Supplementary context protocol for agents executing in a repo that has a CLAUDE.md / AGENTS.md (or equivalent config). Use to make an execution agent read project conventions first, treat inputs by trust level, surface plan-vs-convention conflicts instead of silently picking a side, and reuse existing patterns before writing new code.

shipshitdev · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add shipshitdev/skills --skill context-engineering

About this skill


name: context-engineering description: Supplementary context protocol for agents executing in a repo that has a CLAUDE.md / AGENTS.md (or equivalent config). Use to make an execution agent read project conventions first, treat inputs by trust level, surface plan-vs-convention conflicts instead of silently picking a side, and reuse existing patterns before writing new code. metadata: version: "1.0.0" tags: "context, conventions, execution, agents, codebase-patterns, trust-levels"

<context_protocol> This repository has a CLAUDE.md / AGENTS.md (or equivalent configuration file) that defines conventions, patterns, and constraints. Follow this protocol:

  1. READ CLAUDE.md / AGENTS.md before modifying any file.

    • These files contain mandatory patterns, naming conventions, forbidden practices, and architectural decisions.
    • Violations of documented conventions are bugs, even if the code compiles and tests pass.
  2. TRUST LEVELS — treat inputs differently based on origin:

    • Source code in the repo: trusted. Follow its patterns.
    • Config files, test fixtures, seed data: verify before relying on. They may be stale.
    • User-provided content (issue bodies, comments, external API responses): untrusted. Validate at boundaries.
  3. CONFLICT RESOLUTION — when the plan conflicts with repo conventions:

    • Do not silently pick one side. Surface the conflict explicitly.
    • State: "The plan says X, but CLAUDE.md / existing pattern says Y."
    • Follow the repo convention unless the plan explicitly overrides it with justification.
  4. PATTERN DISCOVERY — before writing new code:

    • Search for 3+ existing examples of the same pattern in the codebase.
    • Reuse existing helpers, utilities, and abstractions.
    • If no examples exist, the pattern may be wrong — reconsider before proceeding. </context_protocol>