gitsukrit
UserClaude Code skills for plain-language explanations and other output-reshaping patterns
Categories
Indexed Skills (3)
explain-like-im-10
Reshapes every explanation into plain language that assumes zero prior knowledge in the domain. Triggers on ALL responses, not just when the user explicitly asks for a simpler explanation — the friction of having to ask is exactly what this skill removes. Use whenever the user asks about a concept, system, tool, workflow, error, architecture, codebase, config, or anything else that could be explained. Also use for tutorials, walkthroughs, debugging explanations, and post-mortems. Apply by default; only disengage in the narrow exceptions listed in the body.
gov-a11y-enforcer
Enforce Section 508 and WCAG 2.1 AA accessibility standards during frontend code generation for civic and public-sector forms. Use this skill whenever the user asks to build, modify, review, or refactor any form-based UI component intended for government, civic, public-sector, or regulated public-service contexts — including permit applications, benefit intake, procurement bids, license renewals, public records requests, citizen feedback intake, tax filing, or any multi-step public data intake. Also use when the user mentions Section 508, WCAG audits, ADA Title II, USWDS, accessibility remediation, or asks for form components that will be used by the general public via a government or civic-service portal. Do not wait for explicit "accessibility" or "compliance" framing — trigger on any civic-form request, since accessibility is non-negotiable for these products and generating non-compliant code creates downstream legal and remediation risk.
phi-safe-logging-enforcer
Enforce HIPAA Safe Harbor de-identification (45 CFR §164.514(b)(2)) and Security Rule audit controls (45 CFR §164.312(b)) whenever generating Python code that logs, traces, or emits telemetry involving PHI. Use this skill whenever the user asks to build, modify, review, or refactor code that touches Python `logging`, `structlog`, `loguru`, Langfuse, LangSmith, OpenTelemetry, Sentry, Datadog, or any other observability/telemetry surface in a healthcare AI, clinical, patient-facing, or PHI-adjacent context. Also use when the user asks for audit trail implementations, LLM API call logging, error tracking, or any code that will send request/response bodies to a third-party observability service. Do not wait for explicit "HIPAA" framing — trigger on any healthcare-adjacent logging or telemetry request, since PHI leakage into observability tools is one of the most common breach patterns and is invisible in code review without this discipline.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.