.cursor/skills/chisel/SKILL.md
Use when polishing existing code for readability, type safety, naming clarity, simpler control flow, or clean-code refinement without deleting behavior or pruning documentation.
npx skillsauth add Columbia-Cloudworks-LLC/EquipQR chiselInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The chisel gives shape, precision, and finish to work that already exists.
Perform a standalone craftsmanship pass on selected code to improve clarity, correctness margins, and maintainability.
Unlike common-gavel, this skill does not remove confirmed dead code as its main job and does not act as a doc-pruning workflow. It refines what remains.
/chisel/chisel <optional-scope-path>Copy this checklist and track it while running:
Chisel Progress
- [ ] 1) Confirm scope and non-goals
- [ ] 2) Inspect types, naming, and logic complexity
- [ ] 3) Identify low-risk craftsmanship improvements
- [ ] 4) Apply focused polish
- [ ] 5) Verify behavior remains intact
Define what files or symbols are in scope and whether the pass is limited to readability, type tightening, or structural cleanup.
Look for:
Choose the refinements that improve the code most without turning the task into an architectural rewrite.
Common polish targets:
Run focused checks appropriate to the scope so the polish pass stays trustworthy.
common-gavel for confirmed cleanup.development
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.
testing
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.
development
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.
development
Use when auditing dependency health, API contract consistency, shared data shapes, or brittle integration seams between modules, services, and packages.