ChulioZ
UserYouth-slang skills for Claude Code: rewrite text into teen-speak, decode slang you don't understand, and calibrate exactly how cringe you want to sound. English + Deutsch.
Categories
Indexed Skills (18)
slang-pack
Rebuild or extend the youth-slang vocabulary pack from live sources. Maintainer tool — researches multiple sources, dates every term, and re-bands what has aged. Use when the pack is stale, when adding a batch of terms, or when asked to refresh the slang data.
cringe-check
Score how badly a piece of text will embarrass you in front of someone younger. Flags dead slang used sincerely, adult tells, and slang stacking. Use before posting something that tries to sound young.
explain-this
Explain what a slang term means, where it came from, and whether it is still alive or will make you sound old. Checks the local pack first, then looks it up live. Use when asked what a slang word means or whether a term is still current.
slangify
Rewrite text into youth slang. Not word-for-word substitution — a genuine register transfer that keeps the meaning. Dials for how current the vocabulary is and how deep the rewrite goes. Use when asked to slangify, gen-z-ify, or make text sound younger.
unslangify
Translate youth slang back into plain, boring English. The inverse of slangify, and its test harness — run it on a rewrite to check the meaning survived. Use when asked what a slang-heavy message actually says.
audit
Run the full audit sweep — accessibility, legal, security, UI, Claude-file, and code-maturity — in one pass and merge the results into a single ranked report with one approval step. Use when asked to audit the app/project/repo generally, for a health check or compliance sweep, before a release or before opening public registration, or when more than one of the six domains is wanted. For a single domain, invoke accessibility-audit, legal-audit, security-audit, ui-audit, claude-file-audit or code-maturity-audit directly.
claude-file-audit
Audit the repo's own documentation — CLAUDE.md, README.md, CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md, LICENSE, the community-health files under .github/ (issue forms, PR template, FUNDING.yml), every committed file under .claude/ (rules, skills, launch config) and the end-user product copy (the landing page text, the in-app FAQ, the landing screenshots) — for staleness, contradictions and drift from the code, and periodically refresh the criteria from current Claude Code/harness capabilities. Use when asked to audit or review the Claude files, rules, skills, CLAUDE.md, the root docs, the GitHub issue/PR templates or the landing/FAQ copy, to check whether the repo's own docs and product copy still match reality, or to clean up the agent-facing documentation. Produces a ranked report; files issues only with your approval.
create-issue
Interview the user and open a GitHub issue that is specific enough to be implemented without further questions. Use when asked to create/file/open an issue, turn an idea or bug report into a tracked issue, or "write this up as an issue". Grounds the issue in this repo's architecture and asks the user targeted questions to remove ambiguity before filing. Pairs with the `pick-issue` and `implement` skills.
implement
End-to-end workflow for implementing a change: branch from up-to-date main, write the prod code + tests, review locally, commit/push, open a PR, review it, merge with the user's go-ahead if safe, watch main's CI + the Railway production deploy, and clean up the branch. Use whenever you're told to implement, build, add, fix, or otherwise ship something — a GitHub issue on this repo, a directly requested change, or similar. Not for reviewing someone else's PR (use `review-pr`) or triaging Dependabot (use `dependabot`).
pick-issue
Survey all open GitHub issues, pending Dependabot PRs, and human-authored pull requests, pick the single best next thing to work on, and hand it to the right builder skill. An open non-draft human PR is reviewed first — only a security exposure or broken core functionality outranks it; everything else is ranked by value-for-effort. Use when asked "what should I work on/implement next?", to triage the backlog, or to choose and start the next issue. Hands the winner to `implement` (issues), `dependabot` (dependency PRs), or `review-pr` (human PRs).
review-pr
Review a GitHub pull request end-to-end to decide whether it is safe to merge. Use when asked to review a PR, check if a PR is mergeable/safe, or vet changes before merging. Not tied to any PR author — works for human and bot PRs alike. For Dependabot-specific batch triage, use the `dependabot` skill (it calls this one per PR).
accessibility-audit
Audit the app's UI/UX for accessibility against a maintained criteria list, and periodically refresh that list from current standards. Use when asked for an accessibility or a11y audit/review, to check WCAG conformance, or to find keyboard, screen-reader, contrast, focus or target-size problems in the UI. Drives the real app in a browser against generated data — never production data. Produces a ranked report; files issues only with your approval.
security-audit
Audit the app's security surface — authentication, authorization and tenant isolation, transport/CSRF/cookies, injection and SSRF, uploads and storage, secrets and logging, the CI security tooling, and public-repo disclosure risk (code whose secrecy is load-bearing) — against a maintained criteria list, and periodically refresh that list from current threats. Use when asked for a security audit/review, a pentest-style pass, or to find and close security holes, and before opening public registration. Defensive only: finds weaknesses to fix them, never to weaponize; a confirmed live hole is disclosed privately. Composes with the built-in /security-review and CodeQL rather than duplicating them. Produces a ranked report; files issues only with your approval.
ui-audit
Audit the app's visual design — colour, layout, spacing, typography, depth, iconography, imagery and motion polish — against a maintained criteria list, and drive it toward being genuinely beautiful and characterful while staying within the brand. Use when asked to improve the UI, make the app prettier/fancier/more polished/stunning, review the visual design, or tighten the look and feel. Plain UI only — never UX (no flows, steps, screen order or copy); accessibility is the accessibility-audit skill's job. Drives the real app in a browser over generated data. Produces a ranked report with before/after evidence; files issues only with your approval.
code-maturity-audit
Audit the codebase's production maturity — repo-wide structure/refactoring smells, hand-rolled code that should become a mature dependency, single-process in-memory-state assumptions under a multi-replica deployment, and test-suite maturity (hand-copied constants, vacuous assertions, undated fixtures) — against a maintained criteria list, and periodically re-check the build-vs-buy calculus against the library ecosystem. Use when asked for a code maturity or refactoring audit, a code-quality review, to find hobby-project patterns unfit for a production multi-tenant SaaS, or hand-rolled code worth replacing with a vetted library. Repo-wide and read-only — unlike the diff-scoped /simplify; exploitable weaknesses belong to security-audit. Produces a ranked report; files issues only with your approval.
dependabot
Check for, review, and merge open Dependabot dependency-update PRs. Use when asked to handle/triage/merge Dependabot PRs, clear the dependency-update backlog, or "merge what's safe". Merges every PR that passes review and, for each intentionally held one, leaves a PR comment explaining why and labels it `blocked` so `pick-issue` skips it until re-checked here.
legal-audit
Audit the app's legal surface — privacy policy, Impressum, Nutzungsbedingungen and the internal records in docs/legal/ — against what the code actually does, and surface recent legal developments as a sourced reading list. Use when asked for a legal/privacy/GDPR/DSGVO/compliance audit, to check whether the policy still matches the app, or before opening public registration. Produces a ranked report; files issues only with your approval, and never adopts a legal duty on its own.
test-data
Create isolated, throwaway test data for automated tests (or manual dev runs) and clean it up afterward. Use when a test or a local experiment needs rounds, games, sessions, or votes to run against, and you must NOT touch the real data/ folder. Covers the temp-DATA_DIR pattern, seeding via the API vs. a raw data.json, and teardown.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.