julianromli/faiz-skills · Archived
Use when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics.
npx skills add julianromli/faiz-skills --skill react-doctor
This repository is archived — consider an actively maintained alternative.
Apple's approach to interface design and fluid, physical motion, translated for the web.
3 installsSurvey a codebase's animation and motion code as a senior motion advisor, then produce a priori…
2 installsUse when you need to resolve an in-progress git merge/rebase conflict.
2 installsUI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography,…
2 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…
263K installsUse when finishing a feature, fixing a bug, before committing React code, or when the user type…
14.2K installsOther skills from julianromli/faiz-skills · top by installs.
npx skills add julianromli/faiz-skills
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Parsed from SKILL.md frontmatter.
Files included with this skill beyond the listing page.
SKILL.md
3,275 B
SUMMARY.md
333 B
Scans React codebases for security, performance, correctness, and architecture issues. Outputs a 0–100 health score.
Run npx react-doctor@latest --verbose --scope changed and check the score did not regress.
If the score dropped, fix the regressions before committing.
Run npx react-doctor@latest --verbose (the default --scope full) to scan the full codebase. Fix issues by severity — errors first, then warnings.
Run npx react-doctor@latest design --verbose. This selects only design-tagged UI composition, typography, interaction, accessibility, and motion rules, including focused rules that remain opt-in during a general health scan.
When the user types /doctor, says "run react doctor", or asks for a full triage / cleanup pass (not just a regression check), fetch the canonical local-triage playbook and follow every step in it:
curl --fail --silent --show-error \
--header 'Cache-Control: no-cache' \
https://www.react.doctor/prompts/react-doctor-agent.mdThe playbook is the single source of truth — a scan → filter → triage → fix → validate loop that edits the working tree directly (never commits, never opens PRs). Updating the prompt at its source updates every agent on its next fetch — no skill reinstall needed.
Pair it with the matching per-rule prompts at https://www.react.doctor/prompts/rules/<plugin>/<rule>.md (fetched on demand inside the playbook) so each fix uses the canonical, reviewer-tested recipe.
When the user wants to understand a rule, disagrees with one, or wants to disable / tune which rules run (not fix code), read [references/explain.md](references/explain.md) and follow it. Start with npx react-doctor@latest rules explain <rule>, then apply the narrowest control via npx react-doctor@latest rules disable|set|category|ignore-tag …, which edits your doctor.config.* (or package.json#reactDoctor).
npx react-doctor@latest --verbose --scope changed| Flag | Purpose |
|---|---|
. |
Scan current directory |
--verbose |
Show affected files and line numbers per rule |
--scope changed |
Only report issues introduced vs the base branch (default: full) |
--scope lines |
Only report issues on the changed lines |
--score |
Output only the numeric score |
design |
Run only the focused UI design diagnostics |