context-engineering
Dynamic context injection, mode switching (dev/review/research), selective loading, and strategic compaction for token optimization.
What this skill does
# Context Engineering ## Overview Context management methodology adapted from the Everything Claude Code project. Optimizes context window usage through dynamic injection, mode switching, selective loading, and strategic compaction. ## Context Modes ### Dev Mode - Load: architecture docs, active code files, test files, recent changes - Skip: historical discussions, completed milestones, research notes - Priority: implementation speed ### Review Mode - Load: code diff, coding standards, security rules, test coverage - Skip: architecture docs, planning notes, research - Priority: thoroughness and accuracy ### Research Mode - Load: requirements, existing patterns, external research, alternatives - Skip: implementation details, test files, CI configs - Priority: breadth of information ## Dynamic Injection - Detect project context automatically (language, framework, tools) - Load relevant skills based on detected context - Inject domain-specific patterns and conventions - Adjust tool allowlists per context mode ## Selective Loading - Load only files relevant to the current task - Use glob patterns to scope file reading - Prioritize recently modified files - Skip binary files and generated code ## Strategic Compaction - Monitor context token usage - Suggest compression for resolved/completed items - Archive to memory files (activeContext, patterns, progress) - Pre-compaction state preservation - Automated compaction triggers at token thresholds ## Cross-Platform Detection - Package manager: npm (package-lock.json), pnpm (pnpm-lock.yaml), yarn (yarn.lock), bun (bun.lockb) - Language: TypeScript (tsconfig.json), Go (go.mod), Python (pyproject.toml), Java (pom.xml) - Test runner: vitest, jest, pytest, go test - CI/CD: GitHub Actions, Dockerfile, docker-compose ## When to Use - Session initialization (detect context) - Before each phase (inject relevant context) - Token budget warnings (strategic compaction) - Mode transitions (dev to review to research) ## Agents Used - Used by all agents indirectly through context detection - `context-engineering` agent for explicit compaction analysis
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.