agentsclimarketplace

Debug & triage

5,150 rows, by stacks then stars

1,113 of these skill files have been read, by 1,020 distinct authors, and what they tell an agent counted. What Debug & triage authors agree on, and what they forbid

  • Launchd exit78 exconfig debug

    bokuwalily/claude-code-skills/skills/launchd-exit78-exconfig-debug Skill

    0★ repo

    launchd ジョブが「last exit code = 78 (EX_CONFIG)」で KeepAlive クラッシュループする時の診断と修復。プロセスが一切起動せずログも残らない spawn 段階失敗が対象。agentmemory が6日間で15,000回ループした実例(2026-06-11)から抽出。

  • Phaser3 scene debug console

    bokuwalily/claude-code-skills/skills/phaser3-scene-debug-console Skill

    0★ repo

    Phaser3ゲームのシーンをwindowに公開し、ブラウザコンソールから決定論的にゲームロジックをテストしたいとき

  • Apex investigate

    zeybek/apex/plugins/apex/skills/apex-investigate Skill

    0★ repo

    Use this skill when investigating a failure whose cause is not yet known — a production incident or outage, a regression, an intermittent or flaky failure, a performance degradation, corrupted or surprising data, or a bug report you must diagnose before fixing. Apply it to triage severity and mitigation, gather and preserve evidence, form and test hypotheses, bisect and localize the cause across components and time, read logs, metrics, and traces, confirm a root cause by mechanism, and record findings in a blameless writeup. Do not use it when the change is already understood and only needs implementation (use apex-implement) or when reviewing a proposed change (use apex-review).

  • Specdd debug

    specdd/plugin-claude/skills/specdd-debug Skill

    0★ repo

    Use when Claude Code needs to diagnose or fix a bug against active SpecDD specs.

  • Triage

    opendatadiscovery/odd-team/.claude/skills/triage Skill

    0★ repo

    Convert raw scanner findings into atomic work items in the backlog. Assigns priority, category, effort, and identifies file conflicts.

  • Node package management

    Saturate/skills/node-package-management Skill

    no license0★ repo

    Reference guide for npm, pnpm, yarn, and bun package managers. Covers workspace configuration, security audits, troubleshooting, and migration between package managers. Use for complex monorepo setup, debugging package issues, or deep package manager reference.

  • Debugging wizard

    simplevaad-debug/superskills/skills/debugging-wizard Skill

    no license0★ repo

    Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.

    The same file is in 2 other repositories

  • Root cause tracing

    kennyolofsson23-netizen/claude-code-config/skills/kaizen/root-cause-tracing Skill

    no license0★ repo

    Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

  • Why

    kennyolofsson23-netizen/claude-code-config/skills/kaizen/why Skill

    no license0★ repo

    Iterative Five Whys root cause analysis drilling from symptoms to fundamentals

  • Triage bug

    Proportione/proportione-plugins/plugins/triage-bug/skills/triage-bug Skill

    0★ repo

    Claude Code plugin marketplace + playbook. 9 QA skills (review, security, architecture, performance, WordPress, Terraform) and 8 production guides from an AI-first consultancy.

  • Triage

    Studio-Moser/skills-n-stuff/plugins/pm/skills/triage Skill

    0★ repo

    Product research, market intelligence, and content tools for AI-native teams

  • Agents debug

    dkmqflx/claude-tools/.claude/skills/agents-debug Skill

    no license0★ repo

    Use when your agent or environment is broken — wrong answers, errors, timeouts, tool failures, or CLI issues. Reads traces and logs to diagnose root causes. Also checks prerequisites when the CLI itself isn't working. Triggers on: "agent not working", "wrong answer", "agent error", "tool call failing", "debug agent", "check logs", "read traces", "broken", "500 error", "424 error", "model access denied", "command not found", "stuck in DELETING", "maxVms exceeded", "cold start diagnosis", "cold start slow", "agentcore create error", "create failed", "exit code 7", "connection refused local dev". Not for deploy failures — use agents-deploy. Not for performance tuning without errors — use agents-optimize. Not for VPC configuration — use agents-build. Not for observability setup or missing logs — use agents-optimize.

  • Agents optimize

    dkmqflx/claude-tools/.claude/skills/agents-optimize Skill

    no license0★ repo

    Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization. Triggers on: "evaluate my agent", "add evaluator", "measure quality", "quality gate", "run evals", "agent too slow", "why is it slow", "reduce latency", "set up observability", "CloudWatch dashboard", "how much does my agent cost", "cost optimization", "logs not showing up", "logs missing", "spans not found", "eval failing", "eval error", "dev traces", "local traces", "agentcore dev traces", "traces to CloudWatch". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.

  • Amazon bedrock

    dkmqflx/claude-tools/.claude/skills/amazon-bedrock Skill

    no license0★ repo

    Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore. Use when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, troubleshooting Bedrock errors (ThrottlingException, AccessDeniedException), or choosing models (Claude, Llama, Nova, Titan). ALSO USE for prompt caching setup and debugging, quota health checks and throttling diagnosis, cost attribution and tracking, migrating between Claude model generations (4.5 to 4.6 to 4.7), chunking strategies, API selection (Converse vs InvokeModel), guardrail capabilities, and model selection. NOT for custom model training, Rekognition, or Comprehend.

  • Aws containers

    dkmqflx/claude-tools/.claude/skills/aws-containers Skill

    no license0★ repo

    Deploys and operates containerized workloads on ECS, Fargate, and ECR. Covers task definitions, Fargate services, ECR repository setup and lifecycle policies, ECS Exec debugging, service scaling, deployment strategies, load balancer integration, and logging configuration. Use when deploying, debugging, or optimizing containers on AWS. ALSO USE for container deployment options (ECS vs ECS Express Mode), networking modes, health check troubleshooting, OOM errors, secrets injection, blue/green deployments, ECR image management, and App Runner sunset guidance and migration. NOT for Kubernetes, EKS, or CI/CD pipelines.

  • Aws serverless

    dkmqflx/claude-tools/.claude/skills/aws-serverless Skill

    no license0★ repo

    Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK. Covers cold starts, CORS debugging, event source mappings, troubleshooting, concurrency, SnapStart, Powertools, function URLs, EventBridge Scheduler, Lambda layers, Durable Functions, durable execution, checkpoint-and-replay, and production readiness. Use when the user mentions Lambda, API Gateway, Step Functions, SAM templates, CDK serverless stacks, DynamoDB stream triggers, SQS event sources, cold starts, timeouts, 502/504 errors, throttling, concurrency, CORS, Powertools, Durable Functions, durable execution, checkpoint-and-replay, or any event-driven architecture on AWS, even if they don't say "serverless." Do NOT use for EC2, ECS/Fargate containers, or Amplify hosting.

  • Nestjs performance logging

    dkmqflx/claude-tools/.claude/skills/nestjs-performance-logging Skill

    no license0★ repo

    NestJS performance and logging/observability best practices. Use when optimizing a NestJS app's throughput or adding structured logging, health checks, or graceful shutdown. Triggers on FastifyAdapter, compression, pino logger, health checks, Terminus, or graceful shutdown.

    The same file is in 1 other repository

  • Systematic debugging

    Topurrra/claude-plugins/plugins/foundational-skills/skills/systematic-debugging Skill

    no license0★ repo

    Use when something does not work as expected such as a crash, wrong output, or flaky behavior, and you need the real root cause instead of a guess.

  • Debug

    latuconsinafr/claude-code-config/skills/debug Skill

    no license0★ repo

    Use when you encounter a bug, error, or unexpected behavior during a task — follows a reproduce → isolate → fix → verify cycle. Invoke this instead of guessing at a fix.

  • Issue triage

    thinkyou0714/github-flow-kit/issue-triage Skill

    0★ repo

    Score and prioritize all open GitHub Issues by Impact x Effort x Urgency. Outputs a triage matrix (TRIAGE.md), applies priority labels, and suggests a sprint plan. Use when your issue backlog is overwhelming, you don't know what to work on next, or you want a structured sprint plan. Triggers on: "issue 整理", "バックログ整理", "何から手をつける", "issue優先度", "sprint plan", "issue-triage", "issue triage". DO NOT USE FOR: closing issues, writing code, or creating new issues.

  • Db telemetry primary docker logs secondary

    Ed3Design/ed3design-skill-bundles/async-forensik/skills/db-telemetry-primary-docker-logs-secondary Skill

    0★ repo

    Use when investigating missing or unexplained behavior in a containerized stack where a high-volume job (MQTT ingester, 5m-fetcher, scraper) runs in the same container as diagnostic jobs, and Docker logs show nothing for the time period in question. Symptom: `docker logs --since 72h` returns only recent lines; older diagnostic entries are gone despite the container running continuously. Root cause: Docker's default JSON log driver rotates files at ~10MB — high-volume sibling output pushes out older diagnostic lines within hours. Fix: query DB-side telemetry (tick_log, job_log, metrics tables) as primary source; Docker logs are only reliable for the last 30–60 minutes. Trigger on phrases like "docker logs shows nothing", "no logs from yesterday", "log rotation", "scheduler history gone", "where are Friday's logs". Do NOT load for fresh containers without DB telemetry infrastructure, single-process containers where log rotation isn't an issue, or log-streaming setups (Loki, CloudWatch, Datadog).

  • Forensic trail for fire and forget sends

    Ed3Design/ed3design-skill-bundles/async-forensik/skills/forensic-trail-for-fire-and-forget-sends Skill

    0★ repo

    Use when designing or hardening any "send + log + swallow" pattern (Telegram bot sends, email notifications, webhook dispatches, Slack pings, push notifications, SMS sends) where DB-state persistence is separated from external API send, send-errors fail-open via log-only, and future forensics may need to distinguish "send happened, user missed" from "send never happened" without relying on log-aggregator availability. Trigger on phrases like "log.warning on send-fail", "fire-and-forget Telegram", "why didn't the notification arrive", "DB save ran but Telegram didn't", "container logs are gone", "*_sent_at column". Produces (1) DB migration for `*_sent_at TIMESTAMPTZ`, (2) update-after-send-OK persistence, (3) forensic query template. Do NOT load for synchronous send-and-wait patterns, sends with guaranteed-persistent external log aggregation, or one-off ad-hoc scripts.

  • Reporting artefact detection before claiming anomaly

    Ed3Design/ed3design-skill-bundles/async-forensik/skills/reporting-artefact-detection-before-claiming-anomaly Skill

    0★ repo

    Use when observing a "surprising anomaly" in backtest output, SQL query result, multi-run-eval-report, ML-model-performance-table, or any reporting-layer artefact suggesting a system bug, market outlier, methodological problem, or drift. Before treating the anomaly as real and dispatching forensic resources, run a 3-step triage: (1) NULL-handling check — are NULLs in numerator/denominator mishandled, was IS NOT NULL omitted? (2) Cross-window / unique-ID check — do overlapping sub-windows / joins count rows multiple times? (3) Methodology-consistency check vs previous report — was the same SQL replicated exactly? Trigger phrases like "why is WR suddenly so low", "I don't understand this anomaly", "24h drift", "baseline has changed", "backtest gives different numbers today than yesterday". Do NOT load for confirmed-real anomalies, first-time-setup-debugging without baseline, code-bugs in the algorithm itself, or UI rendering bugs.

  • Pytest venv first triage

    Ed3Design/ed3design-skill-bundles/code-quality/skills/pytest-venv-first-triage Skill

    0★ repo

    Use when pytest shows multiple failures or errors (especially ModuleNotFoundError clusters) and you're about to dig into individual test fixes. ALWAYS check the Python environment FIRST — `which python3` vs `venv/bin/python3` — before debugging individual tests. System-Python frequently lacks project deps (cachetools, asyncpg, etc.) while project venv has them. Trigger on phrases like "pytest shows many failures", "test errors after pull", "these tests were green yesterday", "ModuleNotFoundError multiple files", "pre-existing failures", "tests broken without code change", "ImportError test sweep". Do NOT load for single-test-fail debugging (use systematic-debugging directly), for Python projects without venv (no env mismatch possible), or for failures with clear test-logic bugs (e. g. assertion errors with concrete values).

  • Harness triage

    ClydeShen/harness-skill/skills/engineering/harness-triage Skill

    0★ repo

    Harness-aware issue triage with effort calibration and agent brief generation. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

  • Task triage

    tarangdeep-goel-by/claude-harness/claude/skills/task-triage Skill

    0★ repo

    Use when starting any new task, feature request, bugfix, enhancement, or refactoring to determine the appropriate level of process before doing any work.

  • Systematic debugging

    chenwei791129/agent-skills/hermes-skills/superpowers/systematic-debugging Skill

    0★ repo

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

  • Ml debug

    nishide-dev/claude-code-ml-research/skills/ml-debug Skill

    0★ repo

    Debug common ML training issues (NaN loss, OOM, slow training, convergence problems) and provide solutions. Use when training fails, metrics don't improve, or encountering errors like NaN loss, CUDA OOM, or slow convergence.

  • Retro debugging

    kaixin1seu/retrospective-system/.claude/skills/retro-debugging Skill

    no license0★ repo

    调试/排错复盘——从根因分析路径、排查效率、信息利用、预防措施等维度深度挖掘

  • Systematic debug fix

    quanpersie2001/pulse/skills/systematic-debug-fix Skill

    no license0★ repo

    Use when the user asks for root-cause-first debugging of bugs, test failures, flaky behavior, build issues, or integration defects with tracked verification and regression lock-down.

  • Agent introspection debugging

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/agent-introspection-debugging Skill

    no license0★ repo

    Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.

    The same file is in 5 other repositories

  • Langsmith fetch

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/awesome-claude-skills/langsmith-fetch Skill

    no license0★ repo

    Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

    The same file is in 10 other repositories

  • Error handling

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/error-handling Skill

    no license0★ repo

    Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

    The same file is in 2 other repositories

  • Langsmith fetch

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/langsmith-fetch Skill

    no license0★ repo

    Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

    The same file is in 10 other repositories

  • Systematic debugging

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/superpowers/skills/systematic-debugging Skill

    no license0★ repo

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    The same file is in 30 other repositories

  • Systematic debugging

    goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/systematic-debugging Skill

    no license0★ repo

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    The same file is in 30 other repositories

  • Agent introspection debugging

    goharabbas321/zeoel-framework/all-skills/agent-introspection-debugging Skill

    no license0★ repo

    Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.

    The same file is in 5 other repositories

  • Langsmith fetch

    goharabbas321/zeoel-framework/all-skills/awesome-claude-skills/langsmith-fetch Skill

    no license0★ repo

    Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

    The same file is in 10 other repositories

  • Error handling

    goharabbas321/zeoel-framework/all-skills/error-handling Skill

    no license0★ repo

    Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages.

    The same file is in 2 other repositories

  • Langsmith fetch

    goharabbas321/zeoel-framework/all-skills/langsmith-fetch Skill

    no license0★ repo

    Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

    The same file is in 10 other repositories

  • Systematic debugging

    goharabbas321/zeoel-framework/all-skills/superpowers/skills/systematic-debugging Skill

    no license0★ repo

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    The same file is in 30 other repositories

  • Debug

    YoniChechik/claude-code-config/skills/debug Skill

    no license0★ repo

    When you get a failed result/error/user says its wrong/its a bug, use this skill to systematically debug and fix the problem.

  • Logging observability

    andresnator/agents-orchestrator/skills/logging-observability Skill

    0★ repo

    Trigger: logging, observability, metrics, traces. Evaluate operationally useful logging for safe refactors.

  • Systematic debugging

    andresnator/agents-orchestrator/skills/systematic-debugging Skill

    0★ repo

    Trigger: debug, debugging, root cause, root-cause analysis, why does this fail, intermittent failure, shotgun fixes. Root-cause debugging loop: reproduce, gather evidence, one falsifiable hypothesis, minimal verified fix.

  • Skill debug

    Moliboy5000/.claude/plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-debug Skill

    no license0★ repo

    Debug issues methodically — use when stuck on errors, test failures, or unexpected behavior. Use when: AUTOMATICALLY ACTIVATE when encountering bugs or failures:. "fix this bug" or "debug Y" or "troubleshoot X". "why is X failing" or "why isn't X working" or "why doesn't X work"

  • Fact check

    Stoica-Mihai/claude-skills/plugins/engineering-principles/skills/fact-check Skill

    0★ repo

    Enforces evidence-based reasoning for any task that involves making factual claims about a codebase — debugging, bug fixing, code investigation, code modification, AND explaining what code does, answering "where is X" / "what does Y do" / "is this safe", or summarizing behavior. Use this skill whenever the user asks to fix a bug, investigate an issue, modify existing code, trace a problem, debug behavior, refactor, change, update code, or explain/locate/audit any part of the codebase. This skill ensures Claude gathers real evidence from source code, docs, git history, and runtime behavior before making any claim — never guessing, never paraphrasing comments as fact, never relying on training memory. Even if the task seems straightforward, use this skill to guarantee that every claim and recommendation is grounded in verified facts.

  • Investigate

    sujeet-pro/agents-devkit/plugins/adk/skills/investigate Skill

    0★ repo

    Investigate, diagnose, RCA, "why is X slow/broken/down", "what changed" for any production symptom. Triggers on a free-text symptom + service, a Datadog incident/monitor/dashboard/log URL, a Slack alert permalink, a Statsig gate/experiment URL, or a Mixpanel/Snowflake/Looker question. Read-only — never modifies a monitor, dashboard, flag, or experiment, and never triggers a rollback or restart (recommends; the human executes). Pins an explicit time window on every query, correlates >=2 independent signals before naming a root cause, and states confidence (low/med/high) with anchored evidence and <=15-word verbatim quotes. Produces a timeline + hypothesis + a lowest-blast-radius next action.

  • Error handling

    thetruong1099/android-mvi-base-code/.claude/skills/error-handling Skill

    no license0★ repo

    Error handling flow from data layer to UI. Use when implementing AppError handling in ViewModels with showErrorToast, adding new error types to AppError sealed class, extending ExceptionMapper for new infrastructure exceptions, extending ErrorHandler for new UI messages, or understanding the complete Exception to AppError to Toast flow.

  • Triage

    bright-room/br-claude-plugins/plugins/dev-workflow/skills/triage Skill

    no license0★ repo

    Issue の棚卸を一括実行する。対応済み Issue のクローズ、ラベル付与、実装プランからの Issue 作成、マイルストーン平準化をすべて行い、棚卸レポートを出力する。

  • K8s debug

    agenticdevops/devops-execution-engine/skills/k8s-debug Skill

    no license0★ repo

    Kubernetes debugging and troubleshooting workflows

  • Log analysis

    agenticdevops/devops-execution-engine/skills/log-analysis Skill

    no license0★ repo

    Cross-platform log analysis patterns and techniques

  • Txt fallback triggers

    sitapix/apple-text/skills/txt-fallback-triggers Skill

    0★ repo

    Catalog every API access and content shape that flips a UITextView or NSTextView from TextKit 2 (NSTextLayoutManager) to TextKit 1 (NSLayoutManager) compatibility mode. Covers explicit layoutManager access, glyph APIs, multi-container layout, NSTextTable / NSTextTableBlock content, the macOS field-editor cascade, framework-internal fallbacks, detection notifications, and recovery. Use when textView.textLayoutManager unexpectedly returns nil, when Writing Tools degrades to panel-only, when scrolling collapses on large documents after a build, or when auditing third-party code or your own extensions for fallback risk before shipping. Trigger on 'why did Writing Tools go panel-only', 'TextKit 2 stopped working', 'scrolling collapses', or any unexplained `textLayoutManager == nil`, even when 'fallback' isn't named. Do NOT use for symptom-driven debugging — see txt-textkit-debug. Do NOT use for the TK1 vs TK2 picker decision — see txt-textkit-choice.

  • Txt layout invalidation

    sitapix/apple-text/skills/txt-layout-invalidation Skill

    0★ repo

    Configure and reason about text layout invalidation across TextKit 1 (NSLayoutManager) and TextKit 2 (NSTextLayoutManager). Covers what triggers invalidation, the lazy-recompute model, ensureLayout / invalidateLayout / invalidateGlyphs / invalidateDisplay scoping, the editing transaction in TextKit 2, NSTextContentStorage element regeneration, viewport-driven layout updates, and why rendering attributes do not invalidate layout. Use when reasoning about how layout gets recomputed after a text edit, after a container size change, or after exclusion-path mutation. Do NOT use for symptom-driven debugging — see txt-textkit-debug. Do NOT use for fallback issues — see txt-fallback-triggers.

  • Txt nstextstorage

    sitapix/apple-text/skills/txt-nstextstorage Skill

    0★ repo

    Subclass and reason about NSTextStorage, NSTextContentStorage, and NSTextContentManager. Covers the editing lifecycle (beginEditing / edited / processEditing / fixAttributes), the four required primitives for an NSTextStorage subclass, NSTextStorageDelegate hooks (willProcessEditing vs didProcessEditing), edit batching, the TextKit 2 performEditingTransaction wrapper, NSTextContentStorageDelegate for display-only paragraph rewriting, and when to subclass NSTextContentManager directly for non-attributed-string backing stores. Use when implementing a custom backing store (rope, piece table, gap buffer), wiring syntax highlighting through delegate callbacks, debugging missing edited() calls, or routing edits through the TextKit 2 transaction model. Do NOT use for symptom-driven debugging — see txt-textkit-debug.

  • Txt textkit debug

    sitapix/apple-text/skills/txt-textkit-debug Skill

    0★ repo

    Diagnose broken behavior in TextKit text editors — stale layout, crashes during editing, TextKit 1 fallback, Writing Tools failures, rendering artifacts, content loss. Use when the question starts with a symptom rather than an API name. Read the actual code before reciting causes from this skill — the patterns here are clues, not answers. Trigger on 'text disappeared', 'layout is wrong', 'editor crashed', 'fonts look weird', 'characters are clipped' even without TextKit named. Do NOT use for the complete TK1-fallback trigger catalog (txt-fallback-triggers), the invalidation model itself (txt-layout-invalidation), or severity-ranked code review findings (txt-audit).

  • Txt textkit1

    sitapix/apple-text/skills/txt-textkit1 Skill

    0★ repo

    Reference for TextKit 1 — NSTextStorage, NSLayoutManager, NSTextContainer. Covers the storage / layout manager / container triad, glyph generation and queries, line-fragment geometry, multi-container layout, exclusion paths, temporary attributes, non-contiguous layout, and NSLayoutManager / NSTextStorage delegate hooks. Use when working with code that already uses NSLayoutManager, when an editor was created with UITextView(usingTextLayoutManager: false), when maintaining legacy TextKit 1 code, or when Apple's apps (Pages, Xcode, Notes) and other TextKit 1 codebases need glyph-level access. Do NOT use for the picker decision between TK1 and TK2 — see txt-textkit-choice. Do NOT use for symptom-driven debugging — see txt-textkit-debug.

  • Txt textkit2

    sitapix/apple-text/skills/txt-textkit2 Skill

    0★ repo

    Reference for TextKit 2 — NSTextLayoutManager, NSTextContentManager, NSTextContentStorage, NSTextLayoutFragment, NSTextLineFragment. Covers the element-based content model, the editing transaction, viewport-driven layout via NSTextViewportLayoutController, rendering attributes vs storage attributes, fragment enumeration options, range types (NSTextRange / NSTextLocation), and delegate hooks for custom paragraphs and custom layout fragments. Use when the editor uses NSTextLayoutManager, when working on TextKit 2 features (Writing Tools inline, viewport layout, custom fragment rendering), or when bridging an attributed-string backing store into the modern stack. Do NOT use for the picker decision between TK1 and TK2 — see txt-textkit-choice. Do NOT use for symptom-driven debugging — see txt-textkit-debug.

  • Txt viewport rendering

    sitapix/apple-text/skills/txt-viewport-rendering Skill

    0★ repo

    Configure TextKit 2 viewport-driven layout, NSTextLayoutFragment / NSTextLineFragment geometry, and rendering attributes vs storage attributes. Covers NSTextViewportLayoutController callbacks, layoutFragmentFrame vs renderingSurfaceBounds, line-fragment local coordinates, the extra trailing line fragment, exclusion paths that split a visual line, lineFragmentPadding vs container insets, font substitution via fixAttributes, and visible/overscroll/estimated regions. Use when working with custom layout fragments, debugging clipped diacritics or descenders, computing document coordinates from a line fragment, integrating with a custom scroll view, or when scroll-bar behavior under estimated heights is the visible problem. Do NOT use for symptom-driven debugging (txt-textkit-debug), the invalidation model (txt-layout-invalidation), or the TextKit 2 API surface in general (txt-textkit2).

  • Go debugger

    JLugagne/claude-skills/dev/go-hexagonal/skills/go-debugger Skill

    0★ repo

    Use when encountering any bug, test failure, or unexpected behavior in Go code — before proposing fixes. Enforces root cause investigation through the hexagonal layers. Also use when go-fixer circuit breaker has fired and the root cause is still unclear.

  • Plex diagnostic expert

    Lunatic16/LLM-Skills-Collection/plex-diagnostic-expert Skill

    no license0★ repo

    Troubleshooting Plex Media Server playback, instability, and library issues by analyzing server logs and environment metadata.