pracht skill
A set of 33 Claude Code skills for apps built on the Preact framework pracht: scaffolding, audits, tests and deployment.
- 109 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Some skills run dependency audits, tests and build commands in the project.
Install
- Works in
Manual install
npm create pracht@latest my-appThe first README command creates the app and seeds four core skills into `.claude/skills/`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Some skills run dependency audits, tests and build commands in the project.
This is third-party code. Review the repository files before installing.
What it does
pracht is a Preact framework that describes an app's routes and operations as one graph and projects it to browsers and agents. The repository's `skills/` folder holds 33 Claude Code skills: generating routes, shells and APIs, debugging, deployment, migration from Next.js and package upgrades. A separate group audits the app: loaders, security headers, CSRF, secrets in the client bundle, accessibility and bundle size. The same skills are published at `/.well-known/agent-skills/index.json` with SHA-256 digests, and `pracht dev-mcp` starts a stdio MCP server for working with the app graph.
Who it is for. Preact frontend developers building on pracht who want an agent to handle scaffolding, audits and pre-deploy checks.
Good fit when
- A new app is created with `npm create pracht@latest` and the agent needs the project skills.
- A Next.js app is being migrated to pracht.
- Loaders, headers and secrets leaking to the client are checked before release.
- You need to choose SSG, ISG, SSR or SPA per route.
Not a fit when
- The app uses another framework and no migration is planned.
- You want general-purpose skills not tied to pracht.
- The project depends on a stable API; the framework is young.
Example request
Check the app's routes for auth protection and say which render mode suits each.Limitations
The skills only help inside pracht projects. By default `create-pracht` seeds four core skills; the rest are added one at a time with `pracht skills add`, and the full catalog needs `--agent-tools=full`. Some skills run dependency audits and tests, so review what the agent executes. The framework is young and its API still changes; migration and upgrade skills track such changes only within published versions.
How to disable. Delete the `.claude/skills/pracht-*` folders and the `pracht dev-mcp` entry from `.mcp.json`. The skills do not alter code on their own, but generated files stay in the project.
FAQ
How many skills and where do they come from?
`skills/` holds 33. `create-pracht` installs them, or `pracht skills add` reads the published index and verifies SHA-256.
What is in the core set?
Four skills: `pracht-scaffold`, `pracht-debug`, `pracht-deploy` and `upgrade-pracht`.
Is there an MCP server?
Yes, `pracht dev-mcp` starts a stdio server: app graph, diagnostics, change plans and route scaffolding. `create-pracht` writes the `.mcp.json` for it.
Can a Next.js project be migrated?
The `/migrate-nextjs` skill covers both App Router and Pages Router.
How do I enable the whole catalog?
Pass `--agent-tools=full` when creating the app; `--no-agent-tools` skips installation.
Discussion
No questions or reviews yet.
Related
Skillsjulianromli/ai-skills
ai-skills
A collection of 31 skills for Claude Code and other agents: interfaces, React, Postgres, code review, SEO and browser automation
145 skill plugins for Claude Code and Codex: Cloudflare, React, Tailwind, Nuxt, APIs, security, testing, installed one by one
14 skills for Claude Code on Makepad 2.0: DSL, layout, widgets, events, animation, shaders, themes and migration from 1.x
A library of 80 skills for Codex covering design direction, frontend, motion, accessibility, QA and site handoff
Skill and MCP server for Shaders: the agent builds backgrounds, glass, gradients and cursor effects on WebGPU for React, Vue, Svelte, Solid and JS
58 narrow skills on JavaScript, React and Vue patterns from patterns.dev, installed by stack or one at a time
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| pracht (this card) | no | 109 | |
| React Doctor | no | 15,126 | scans React projects; pracht skills are tied to one framework and include scaffolding, migration and deployment |
| Nuxt MCP Toolkit | no | 182 | tooling for Nuxt; this is a Preact framework with skills and MCP included |
README in short
The README sets out the single app graph idea, the `pracht dev`, `build`, `verify`, `plan` and `doctor` commands, three ways of distributing skills and a trust layer with call audit for agents.