Columbia-Cloudworks-LLC
19 verified skills19 total stars
gauge
Use when auditing an application for latency, inefficient loops, heavy assets, unoptimized queries, excessive rendering, or poor resource allocation.
testing1
compasses
Use when reviewing authorization boundaries, rate limiting, tenant isolation, IAM scope, or runtime guardrails that keep the application within its intended bounds.
data-ai1
chisel
Use when polishing existing code for readability, type safety, naming clarity, simpler control flow, or clean-code refinement without deleting behavior or pruning documentation.
development1
common-gavel
Use when auditing a repository or scoped directory for dead code, abandoned work, stale TODOs, unused imports, or documentation drift that may require confirmation before cleanup and refinement.
development1
level
Use when auditing accessibility, keyboard support, contrast, responsive behavior, or experience parity across mobile, tablet, and desktop views.
testing1
reflect
Reflect
tools1
square
Use when checking scoped code against established architectural patterns, folder structure, naming conventions, dependency direction, or repository design rules.
development1
plumb
Use when auditing security posture, secrets handling, input validation, privacy obligations, or compliance readiness against standards such as OWASP, GDPR, CCPA, or SOC 2.
testing1
trowel
Use when auditing dependency health, API contract consistency, shared data shapes, or brittle integration seams between modules, services, and packages.
development1
brand-guidelines
Applies EquipQR's brand colors and design-system tokens to any artifact that should match EquipQR's look-and-feel. Use it when brand colors, style guidelines, visual formatting, or EquipQR design standards apply.
development1
toolbelt
Canonical reference for all MCP servers, CLI tools, and platform integrations available in this workspace. Use when any skill or workflow needs to call Datadog, Supabase, Vercel, Figma, GitHub, Context7, or the browser MCP, or when starting a local dev server. Read this before using any integration tool.
tools1
react-best-practices
React performance optimization guidelines from Vercel Engineering, with EquipQR-specific mappings (Vite + React Router + TanStack Query). Use when writing, reviewing, or refactoring React code in this repo, especially around waterfalls, bundle size, and re-renders.
development1
raise
Run pull request pre-flight checks and prepare a release PR from the current branch to main. Use when the user asks to raise a branch, run CI/CD gates, audit release readiness, or generate a PR description and open-PR commands.
testing1
postgres-best-practices
Postgres performance optimization and best practices from Supabase, adapted to EquipQR's Supabase (Postgres + RLS) workflow. Use when editing SQL, migrations, indexes, or RLS policies.
testing1
pencil
Use when the user has a high-level feature idea and needs a technical specification, API contracts, data models, or file scaffolding before implementation begins.
development1
evidence-producer
Use when producing production-backed audit evidence, screenshots, executive compliance reports, and entity-mapping visuals from equipqr.app, production Supabase, and production Vercel.
testing1
trestle
Use when aligning current repository state with roadmap priorities, reconciling GitHub issues or organization project items with what exists in the codebase, or deriving next steps across code, docs, and EquipQR work tracking.
development1
google-cloud-debug
Retrieve and validate Google Cloud project configuration for debugging using gcloud with evidence-first outputs. Use when the user mentions Google Cloud, GCP projects, API keys, enabled APIs, IAM, billing, quotas, or asks to debug cloud configuration.
development1
auditor
Use when generating a jurisdiction-specific audit questionnaire and pass-fail compliance matrix from a regulatory rule pack, such as Texas audit readiness requests.
testing1