The context-monitor hook tracks usage tiers and injects warnings automatically. This skill covers what the hook can't detect — the subtle signs that quality is already degrading.

Early Warning Signs

Watch for these before the hook's warnings fire:

Silent partial completion — claiming "done" but implementation is incomplete. Verify semantics, not just file existence.
Increasing vagueness — "appropriate handling" or "standard patterns" instead of specific code.
Skipped steps — omitting verification or protocol steps you'd normally follow.
Repetition — restating things already established, burning tokens on known context.

If you notice these, treat it as POOR tier regardless of what the monitor says.

Rules

Don't read what you don't need. Frontmatter or summary over full file.
Don't inline large content. Reference paths; let tools read from disk.
Checkpoint before it's too late. Commit and write a continuation note at first sign of pressure.
Say it. Tell the user when context is getting heavy.

Más de este repositorio

mismo repositorio

planning

5uck1ess/pikit

Writing implementation plans — small testable steps, dependency ordering, upfront risk identification.

2026-04-080

verification

5uck1ess/pikit

Evidence before claims, always — run verification commands and confirm output before making any completion or success claims.

2026-04-080

adr

5uck1ess/pikit

Generate Architecture Decision Records — use when asked to document a decision, create an ADR, record why we chose X, or capture architectural rationale.

2026-04-060

changelog

5uck1ess/pikit

Generate a structured changelog from git history — use when asked to create a changelog, release notes, or summarize what changed between versions/tags/branches.

2026-04-060

creating-workflows

5uck1ess/pikit

How to write pikit workflow YAML files — steps, loops, branches, interpolation.

2026-04-060

deep-research

5uck1ess/pikit

Deep research with Analysis of Competing Hypotheses — use when asked to do deep research, deeply investigate, validate claims, or when correctness is critical and the user wants rigorous analysis with disconfirmation testing.

2026-04-060

name	context-budget
description	Recognizing context pressure before it degrades output quality.

Context Budget

The context-monitor hook tracks usage tiers and injects warnings automatically. This skill covers what the hook can't detect — the subtle signs that quality is already degrading.

Early Warning Signs

Watch for these before the hook's warnings fire:

Silent partial completion — claiming "done" but implementation is incomplete. Verify semantics, not just file existence.
Increasing vagueness — "appropriate handling" or "standard patterns" instead of specific code.
Skipped steps — omitting verification or protocol steps you'd normally follow.
Repetition — restating things already established, burning tokens on known context.

If you notice these, treat it as POOR tier regardless of what the monitor says.

Rules

Don't read what you don't need. Frontmatter or summary over full file.
Don't inline large content. Reference paths; let tools read from disk.
Checkpoint before it's too late. Commit and write a continuation note at first sign of pressure.
Say it. Tell the user when context is getting heavy.