All authors
Claude Skills by matthews-wong
github.com/matthews-wong62 skills0 installs14 views
- Spec WritingUse when turning a fuzzy feature request into an implementable spec by interviewing the user first — planning a feature, writing a SPEC.md or design doc, or eliciting requirements before coding. Covers the interview technique (structured questions on implementation, UI/UX, edge cases, tradeoffs) and a self-contained SPEC.md template that ends in a verification step.Votes: 0GitHub stars: 2
- Standards EnforcerCheck a diff against an editable org coding-standards profile — naming, file organization, error handling, no secrets or debug prints, docstrings on public APIs. Use when reviewing a diff or PR for convention compliance, before committing, or when the user asks to enforce coding standards or style rules. Triggers on "enforce standards", "check conventions", "style review", "does this follow our standards", "lint my diff".Votes: 0GitHub stars: 2
- Iac PolicyUse when reviewing Terraform or other IaC for security/compliance, running policy-as-code, or writing OPA/Rego rules. Triggers: "terraform security", "policy as code", "conftest", "opa", "rego", "tfsec", "checkov", "trivy config", "public S3 bucket", "open security group", "0.0.0.0/0", "missing encryption", "required tags", "IaC scan", "CIS benchmark terraform".Votes: 0GitHub stars: 2
- Coverage GatingUse when the user asks to check, enforce, or gate test coverage, set a coverage threshold, find untested code, or wants to know why coverage dropped. Triggers: "coverage", "coverage gate", "coverage threshold", "untested code", "pytest-cov", "nyc", "c8", "go test -cover", "fail build under X% coverage".Votes: 0GitHub stars: 2
- Test Running GuidanceUse when the user wants to run the project''s fast test suite on demand or understand the auto-test-after-edit hook. Points to /test-guardian. Triggers on "run the tests", "run the fast tests", "did my change break anything", "run the suite", "auto-run tests after edits".Votes: 0GitHub stars: 2
- Threat ModelingUse when the user asks to "threat model" a feature or system, wants a "security design review", mentions "STRIDE", "attack surface", "trust boundaries", "data flow diagram", or asks "what could go wrong security-wise" with a design. Produces a structured STRIDE threat model with prioritized, mapped mitigations.Votes: 0GitHub stars: 2
- Token Budget GuidanceUse when a session feels heavy, slow, or near its context limit, or before deciding to /compact or /clear — summarizes what is filling the context window and gives concrete steps to trim it. Points to /token-budget. Triggers on "context is full", "session feels slow", "running out of context", "should I compact or clear", "token budget", "trim context".Votes: 0GitHub stars: 2
- Typescript TypingApply precise TypeScript typing when writing or fixing types in .ts/.tsx files. Triggers on "type error", "any", "unknown", generics, interfaces, discriminated unions, "readonly", "satisfies", type narrowing, type guards, tsconfig strict, or TS compiler complaints. Use whenever modeling data, designing type signatures, or resolving type-checker errors.Votes: 0GitHub stars: 2
- App Verification GuidanceUse when the user wants to confirm a change actually works end to end — run the app or build, exercise the happy path and key flows, and get PASS/FAIL with real captured evidence. Delegates to the verify-app subagent via /verify-app. Triggers on "verify the app", "prove it works", "run the happy path", "did the build pass", "confirm it works before I''m done".Votes: 0GitHub stars: 2
- Pre Review Verification GuidanceUse before committing, opening a PR, or requesting review — runs the project''s tests, lint, and build/typecheck and reports a clear PASS/FAIL on whether the changes are ready. The verify step that comes before code review. Points to /verify. Triggers on "is this ready to review", "run tests lint and build", "verify before PR", "quality gate before review".Votes: 0GitHub stars: 2
- Worktree IsolationUse when running multiple agents or parallel tasks that would otherwise edit the same working tree. Explains how to give each agent its own git worktree (a separate checkout on its own branch backed by one repository) so parallel work stays isolated and merges back cleanly instead of colliding. Triggers on "worktree", "isolate the agents", "run agents in parallel without conflicts", "separate checkouts".Votes: 0GitHub stars: 2
- Writer ReviewerUse when reviewing a just-implemented change with fresh eyes — checking a diff against a plan/spec/requirements before a PR, running an adversarial or second-pass review, or when one session writes code and another reviews it. Emphasizes flagging only correctness/requirement gaps and avoiding over-engineering, since a gap-seeking reviewer always finds something.Votes: 0GitHub stars: 2