Claude Skills by jaydubya818

Apply when large files, logs, or broad exploration threaten reasoning focus.

Apply when a refactor is adding wrappers or abstractions instead of simplifying.

Apply when an operation must tolerate retries after partial completion.

Apply when replacing an internal API without leaving ambiguous dual paths.

Apply when layers, wrappers, or hidden state make simple behavior hard to follow.

Apply when repeated state conditionals reveal a missing domain model.

Apply when safe reversible implementation details can proceed inside scope.

Apply when a bounded rewrite should converge without throwaway compatibility layers.

Apply when the actual candidate and observable result still need verification.

Apply when a requirement breaks a foundational assumption and needs coherent redesign.

Apply when concurrent actors share mutable files, branches, keys, or objects.

Apply when multi-step work must end each ordered unit in a verified state.

Apply when new work would otherwise build on dead or redundant structure.

Apply when tests mirror internals instead of asserting observable outcomes.

Apply when typed APIs or schemas should make invalid states unrepresentable.

Use when resuming work or reconstructing project context from workspace-scoped history.

Use when approved session lessons should become durable workflow improvements.

Use when the user wants to configure Jstack's per-role Claude models.

Use when long-running work needs an auditable decision and evidence log.

Use when authorized independent workers can run without shared mutable state.

Use when TDD is requested or a bug has a cheap, direct regression target.

Use when runtime behavior and design rationale should become one clear mental model.

Use when docs, RFCs, READMEs, PRs, or commits need structured and direct prose.

Use when the user requests an intentionally strict maintainability review.

Use when TypeScript needs focused type-safety, API, or error-handling guidance.

Remove filler and generic AI phrasing from human-facing text. Use before sending or committing prose you edited.

Use when authored work needs a concise summary for a concrete time window.

Use when design rationale must be recovered from source history and available records.

Use this skill when a Mission Control work item is complete or awaiting review and an operator needs a factual handoff draft with outcome, evidence, unresolved risk, next owner, and next action.