context-engineering

Curates rules files, specs, and source context for AI coding agents.

5|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/PHenrique07/Sementis-IFSP-Pirituba --skill context-engineering-phenrique07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/PHenrique07/Sementis-IFSP-Pirituba/tree/main/.github/skills/context-engineering
Command: npx skills add https://github.com/PHenrique07/Sementis-IFSP-Pirituba --skill context-engineering-phenrique07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents produce poor output when given too little context (hallucinated APIs, ignored conventions) or too much context (lost focus, degraded attention). This Skill provides a structured methodology for deliberately managing what an agent sees, when it sees it, and how it is structured across a session. ## Core Features & Use Cases - Five-Level Context Hierarchy: Organizes context from persistent rules files (CLAUDE.md, .cursorrules, AGENTS.md) down to transient conversation history, with templates for each level. - Context Budget Management: Defines a 75% capacity trimming threshold, prioritization tables for what to cut versus protect, and compression strategies to prevent abrupt quality drops in long sessions. - Confusion Management Patterns: Provides explicit formats for surfacing spec conflicts, missing requirements, and inline plans instead of silently guessing. - Use Case: When starting a new project for AI-assisted development, use this Skill to write a rules file covering tech stack, commands, conventions, and boundaries so every subsequent agent session follows project patterns instead of inventing them. ## Quick Start Ask the agent to set up a context rules file and context loading strategy for your project using the context-engineering skill.

Frequently Asked Questions about context-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a CLAUDE.md rules file for my project?▼

A CLAUDE.md file should cover tech stack, build and test commands, code conventions, boundaries like never committing secrets, and one short example of a well-written component in your style. Equivalent files exist for Cursor, Windsurf, Copilot, and Codex.

How much context should I give an AI coding agent?▼

Include only what is relevant to the current task, aiming for under 2,000 lines of focused context. Loading more than 5,000 lines of non-task-specific content causes the agent to lose focus, so more files does not mean better output.

Why does AI agent output quality degrade during long sessions?▼

Long sessions accumulate stale context like failed attempts, replaced drafts, and verbose tool output that fragments the model's attention. Start trimming at 75% capacity, compress old exploration into one-sentence conclusions, and protect the active task and current error.

What should I do when a spec conflicts with existing code?▼

Do not silently pick one interpretation. Surface the conflict explicitly with the spec statement, the existing code evidence, and labeled options, then ask which approach to take before building on a guess.

When should I start a fresh AI coding session?▼

Start fresh at a completed task boundary, not an arbitrary token count. First persist the accepted decisions, current task status, changed files, verification outcomes, and unresolved questions so the new session can resume from durable artifacts.