question is "is this schema good" rather than "is this change safe". |
| `senior-frontend-engineering` | Design | Review or ship a React/component/SPA/Vite frontend change — state ownership, React rendering correctness, loading/empty/error states
prompt files in ignored local locations such as `tools/local/`
- prefer direct local runtime for frontend and dev-server projects unless a repo manifest says otherwise
- treat WordPress repos already managed
Vite + Tailwind (dark), Zustand stores in `src/store/`,
API client in `src/lib/api.ts`
- Ports: backend 11159, frontend 11160
- Tests: `uv run pytest` (light, no torch); webapp: `bun run check`
- ASCII only
mandatory; other fields are optional metadata
// Category naming convention: lowercase, single word (ai, backend, frontend, etc.)
// Skill naming convention: lowercase, hyphen-separated (my-skill-name)
// All skills go under .claude/skills
with llama.cpp for answering questions about uploaded documents.
## Architecture & Service Boundaries
### Core Components
- **Frontend**: React 18 + Vite at `frontend/src/` - UI for search, upload, and results display
- **Backend**: FastAPI at `backend/app/main.py
214mo agoReviewMountCreate a free account to mount
bundled skill categories:
- `core`
- `tools`
- `reasoning`
- `thinking`
- `testing`
- `debugging`
- `methodology`
- `completion`
- `code-style`
- `domains`
- `frontend-design`
- `game-dev`
How skills work in this repo:
- Only the skill index is preloaded
live incident | `dt-obs-problems`, `dt-obs-logs`, `dt-obs-tracing`, `dt-obs-frontends`, `dt-dql-essentials` | Derive entity IDs and time windows from each selected problem; add only
suites of anything that consumes the changed behavior, so an API change pulls the frontend end-to-end that exercises it — and leaves the full suite to CI on push
suites of anything that consumes the changed behavior, so an API change pulls the frontend end-to-end that exercises it — and leaves the full suite to CI on push
github/copilot-instructions.md`. GitHub Copilot reads it automatically and applies these principles when you work on frontend files.
For the full reference set (component patterns, motion, accessibility, etc.), copy the entire `skills/design-taste/references
cargo tauri`.
npm run tauri dev
# Frontend only
npm run dev # Vite dev server (no Tauri shell)
npm run lint # Biome check
npm run format # Biome format --write
# Rust (from
Server restart needed for backend changes (uvicorn, port 8600);
browsers need Ctrl+F5 for frontend changes.
## Engineering standard — enterprise / data-center grade (MANDATORY)
All code must be production-quality. Never
zero-install property. Do not import external packages into `cli/` or `web/`.
- All web frontend code must be compatible with vanilla JavaScript (ES6+), HTML5, and CSS3 without bundling steps (`webpack
name in commit messages.
- **Contract-first**: Read `docs/contracts/{module}.contract.ts` before implementing any endpoint.
## Frontend Rules (Non-Negotiable)
- **Zero raw HTML in pages**: Never write raw ` `, ` `, ` ` directly in page files