Individual skill
pracht-debug
Debug a pracht app root cause first: route matching, loader and API errors, rendering and hydration, middleware, HMR, and build failures. Use for "debug this", "why is this broken", "blank page", "hydration mismatch", "404 on my route", or any unexpected pracht behavior.
skills/pracht-debug/SKILL.md
Source commit e7c088a615e0bc16659d7a307fe92910ae6bd546
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 106
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- cloudflare-workers Repository topic
- framework Repository topic
- full-stack Repository topic
- llms-txt Repository topic
- mcp Repository topic
- preact Repository topic
- ssg Repository topic
- ssr Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Pracht Debug
**Iron law: no fixes without root-cause investigation first.** Read the
relevant source before diagnosing, start from the most likely cause for the
symptom rather than a full audit, and when you find the root cause explain
*why* it breaks. After fixing, prove the fix — run the test, check the dev
server. Never say "this should fix it."
## Instruments
Reach for these before deep manual inspection:
| Tool | Use |
| ---- | --- |