Claude Skills by joryeugene

Manage Asana tasks and projects from the terminal. Use the timwehrle/asana CLI for common operations and direct REST API calls for section/kanban moves. Invoke with /asana.

Adversarial browser testing. Use when testing UI behavior, verifying network requests, checking console errors, filling forms, or handling dialogs. The goal is finding bugs, not confirming happy paths.

Review your codebase for drift introduced by isolated AI sessions: dead exports, duplicate logic, and orphaned types.

Systematic protocol for diagnosing broken behavior and making recurrence structurally impossible. Schema mismatch causes 80% of bugs. Use when something isn't showing, isn't working, or is still broken after a fix attempt.

This skill should be used when the user gives sustained time for research, spec-writing, ideation, or deep planning. Triggers on "we have X hours", "all night", "take your time", "I'm going to sleep, keep working", "don't stop early", "go deep on X", or any indication the user wants full use of a time window. Covers planning, clock discipline, tier structure, depth standards, pivot protocol, and quality bar.

Access Figma designs via the REST API using curl. Use when given a Figma URL and needing to extract design specs, node properties, or export images. Invoke with /figma-api. See also figma-extract and figma-verification for deeper extraction workflows.

Exhaustive Figma node extraction: download every detail down to leaf nodes and cache everything locally. Call Figma once, never twice. Use before any pixel-perfect implementation. Prioritizes complete local dumps over repeated API calls.

Extract Figma design specs before implementing UI components. Use depth 5, cache to disk, extract ALL properties, map to design system tokens.

Use when production is down, an alert fires, or an incident needs triage. Covers severity classification, communication, timeline tracking, and blameless postmortem with 5 whys. Also use after resolution to write the postmortem.

Use when designing how a UI feels to use. Covers audience dimensions, discoverability, mode communication, keyboard-first UX, feedback timing, empty states, and information density. Includes WCAG 2.1 AA compliance audit. Companion to visual-design.

Use when code is slow, queries are taking too long, or you suspect N+1 queries, O(n squared) loops, missing indexes, or unbounded result sets.

CEO and engineering review after spec-writing. Auto-selects weight class from the spec format (skip for task-mode, eng-only for routine, full CEO+eng for high-risk). Run /spec-writing first.

Use when reviewing a PR or responding to review comments on your own PR. Detects authorship automatically and runs the correct mode. Never makes code changes when reviewing someone else's work.

Use when cutting a versioned release. Detects commits since last tag, suggests semver bump, bumps version file, tags, pushes, and creates a GitHub release. Distinct from ship-pipeline which ends with a PR.

Use before shipping any feature that handles user input, authentication, file paths, database queries, or sensitive data.

Run when all code changes are complete and ready to land. Executes the full merge+test+commit+push+PR pipeline. Do not run mid-feature.

Use before starting any feature, task, or fix. Explore mode for brainstorming and research when direction is unclear. Task mode for concrete fixes. Structured mode for the 7-section spec. The spec format determines plan-mode's weight class.

Use when writing any tests or implementing any feature. The failing test must exist before any implementation begins. Also use for characterization tests before refactoring.

Install or update tripod and sync the plugin cache. Use when the user says "sync tripod", "update tripod", "install tripod", or "set up tripod".

After every code change, follow this cycle: validate assumptions, make change, prove it works, show evidence.

Audit any application's visual identity and generate a distinctive direction that passes the AI slop test. Use before writing UI code to set color, typography, spacing, and motion tokens.

Verify UI changes at element level before declaring any frontend work done. Full-page screenshots are forbidden for component verification.

Use the gws CLI to interact with Google Workspace APIs (Drive, Docs, Sheets, Calendar). Publish markdown specs or RFCs as Google Docs and share with recipients. Lightweight alternative to MCP-based workspace tools - no persistent server process.

Spawn and coordinate parallel Claude Code agents for independent work streams. Use when a plan has multiple tasks that can run concurrently without touching shared files.

The quality contract for AI-assisted development: verification-first, schema-before-theory, evidence over claims, no hedging. Load when establishing session standards or when output quality slips.