Loading...
Loading...
Found 7 Skills
Refresh an existing artifact into the current best v0. Use when the user asks to clean up, sync up, dedupe, de-noise, smooth, rewrite, or update an artifact after iteration; when nearby artifacts may have drifted; or when changes in one place should be reflected across related artifacts while keeping the result minimal.
Updates the HWPX-Markdown differences documentation when a new conversion issue is found or a new handling method is implemented. Use this skill when fixing HWPX parsing issues, adding new format handling, or discovering incompatibilities between HWPX and Markdown.
After implementation is complete and tests pass, sync confirmed details back to Intent. Captures finalized interfaces, data structures, naming conventions, and architecture decisions. Use after development is done and user confirms the implementation.
Correct, create, or remove written material so a later reader can rely on it: documentation that no longer matches the system, a fact about to be written down a second time, prose restating what a config file or command already prints, a records folder that has drifted, or a decision worth recording so it stops being re-argued. Prose no human has read counts as a hypothesis, not a source. Use when the user says "the docs are out of date", "readme still says the old flow", "where does this go", "write this down", or "should this be an ADR". Not for judging docs inside a change under review, explaining an existing document, or looking up a third party documentation.
Audit one current-guidance instruction file for worth, placement, and clarity. TRIGGER when: user says 'refine/audit this file', 'prune and tighten this doc', or 'what here is worth keeping'; a skill, agent prompt, AGENTS.md, Claude path rule, maintained current document, or workflow needs one pass. SKIP when: shape-only tightening with no worth/place question (tighten-file).
Refresh stale learning docs and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, replacing, or deleting the drifted ones. Trigger this skill when the user asks to refresh, audit, sweep, clean up, or consolidate stale docs in docs/solutions/ (phrases like "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", "consolidate overlapping docs", "compound refresh", "/ce-compound-refresh"), or when ce-compound has just captured a new learning and flagged a specific older doc in docs/solutions/ as now inaccurate or superseded — invoke with the narrow scope hint ce-compound provides. Also trigger when the user points at a specific learning or pattern doc under docs/solutions/ and calls it stale, outdated, overlapping, or drifted. Do not trigger for general refactor, migration, debugging, or code-review work unless the user has explicitly directed attention to docs/solutions/ itself.
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, replacing, or archiving them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/ for accuracy, when a recently solved problem contradicts an existing learning, or when pattern docs no longer reflect current code.