All authors

Claude Skills by ChulioZ
github.com/ChulioZ15 skills0 installs2 views
- Accessibility AuditAudit 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.Votes: 0GitHub stars: 2
- AuditRun 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 co...Votes: 0GitHub stars: 2
- Claude File AuditAudit 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 capabi...Votes: 0GitHub stars: 2
- Code Maturity AuditAudit 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 r...Votes: 0GitHub stars: 2
- Create IssueInterview 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.Votes: 0GitHub stars: 2
- DependabotCheck 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.Votes: 0GitHub stars: 2
- ImplementEnd-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 Depen...Votes: 0GitHub stars: 2
- Legal AuditAudit 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.Votes: 0GitHub stars: 2
- Pick IssueSurvey 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), `de...Votes: 0GitHub stars: 2
- Review PrReview 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). Not the built-in `/code-review`, which hunts bugs in a diff — this one decides mergeability: CI state, sign-off and the repo's own constraints.Votes: 0GitHub stars: 2
- Screen Deep DiveTake ONE screen of the app apart and rebuild the case for it: measure how it lays out at phone, tablet, laptop and desktop widths over generated data, diagnose where the height and the width actually go, propose tiered improvements (layout only → structure → character) as live, clickable prototypes in a device-frame artifact, get the operator's decision, and file one implementable issue per agreed slice. Use when asked to rethink, redesign, improve or make "first-class" a specific screen or f...Votes: 0GitHub stars: 2
- Security AuditAudit 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 regist...Votes: 0GitHub stars: 2
- Test DataCreate 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.Votes: 0GitHub stars: 2
- Triage Ai ReviewTriage CodeRabbit's review of a PR this session opened: wait for it to land, read only its unresolved inline threads, verify each finding against the code and `.claude/rules/`, fix the valid ones in ONE batched push, draft a short reply per thread for the user to approve, and log every finding for the CodeRabbit trial. Use when `implement` reaches phase 5, or whenever CodeRabbit has reviewed a PR you are about to ask to merge. Not for judging someone else's PR — `review-pr` reads the findings...Votes: 0GitHub stars: 2
- Ui AuditAudit 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-audi...Votes: 0GitHub stars: 2