deno
If the project uses deno, use this skill. Use this skill to initialize and work with Deno projects, add/remove dependencies (JSR and npm), run tasks and scripts with appropriate permissions, and use built-in tooling (fmt/lint/test).
What this skill does
# Deno Use Deno as the default runtime/tooling when the repo contains `deno.json`/`deno.jsonc`, uses `deno.lock`, or scripts/documentation reference `deno task`, `deno run`, `deno test`, etc. ## Quick decision rules - Prefer `deno task <name>` if the repo defines tasks. - Use `deno add` / `deno remove` to manage dependencies (writes to config). - Be explicit about permissions for `deno run` / `deno test`. ## Common operations ### Initialize a new project ```bash deno init ``` ### Add dependencies (JSR and npm) ```bash # JSR (recommended for Deno-first packages) deno add jsr:@std/path # npm packages are supported too deno add npm:react # multiple at once deno add jsr:@std/assert npm:chalk ``` ### Remove dependencies ```bash deno remove jsr:@std/path ``` ### Run a script ```bash # Minimal permissions: only what the program needs # Examples: # --allow-net=api.example.com # --allow-read=./data # --allow-env=FOO,BAR deno run --allow-net --allow-read main.ts ``` ### Run tasks ```bash # list tasks deno task # run a task defined in deno.json/deno.jsonc deno task dev ``` ### Formatting, linting, testing ```bash deno fmt deno lint deno test # common permissioned test run deno test --allow-net --allow-read ``` ### Install / run CLIs ```bash # Run a JSR or npm package's CLI without installing globally deno x jsr:@std/http/file-server -p 8080 # Install globally (requires choosing permissions at install time) # Prefer the smallest set of permissions; avoid blanket flags unless necessary. deno install -g -N -R jsr:@std/http/file-server -- -p 8080 ``` ## Notes / pitfalls - Deno is secure-by-default: missing permissions cause runtime errors; add the smallest set of `--allow-*` flags needed. - Dependency specifiers: - `jsr:` for JSR registry packages - `npm:` for npm packages - URL imports are also supported (and cached) - Lockfile: `deno.lock` helps ensure reproducible dependency resolution.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.