Run any Skill in Manus with one click

web-frontend-dev

Stars0

Forks0

UpdatedJuly 16, 2026 at 08:55

Coordinate Ratatoskr backend web integration with the external React + TypeScript + Vite frontend. Trigger keywords -- web, frontend, React, Vite, TypeScript, ratatoskr-web, app/static/web, Frost, UI change.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

po4yka

po4yka/ratatoskr

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web DevelopersComputer and Mathematical Occupations·SOC 15-1254

SKILL.md

readonly

More from this repository

same repository

langgraph-summarize-loop

po4yka/ratatoskr

Debug the LangGraph summarize graph (the sole summarize path) -- node walk, validate/repair retry loop, and the LLM attempt trail. Trigger keywords -- LangGraph, summarize graph, graph node, retry, repair loop, attempt_trigger, attempt_index, graph_node, validation failure, self-correction, summarization agent.

2026-07-180

pi-deploy

po4yka/ratatoskr

Build, ship, and restart the Ratatoskr container on the Raspberry Pi via cross-platform Docker image streaming. Trigger keywords -- pi deploy, raspi, raspberry pi, pi-deploy, ship to pi, deploy production, build-and-deploy-pi.

2026-07-170

ponytail-help

po4yka/ratatoskr

Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: @ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".

2026-07-150

ponytail

po4yka/ratatoskr

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.

2026-07-150

ponytail-help

po4yka/ratatoskr

Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".

2026-07-150

testing-workflows

po4yka/ratatoskr

Test bot functionality locally using CLI runner, message simulation, and workflow validation. Trigger on "test", "CLI runner", "message simulation", "bot testing", "workflow validation", "pytest".

2026-07-150

name	web-frontend-dev
description	Coordinate Ratatoskr backend web integration with the external React + TypeScript + Vite frontend. Trigger keywords -- web, frontend, React, Vite, TypeScript, ratatoskr-web, app/static/web, Frost, UI change.
version	2.0.0
allowed-tools	Bash, Read, Write, Edit, Grep

Web Frontend Development

Editable frontend source lives in the separate sibling repository ../ratatoskr-web. This repository owns the FastAPI root SPA serving contract, generated OpenAPI artifacts, a pinned frontend revision, and the reviewed release bundle.

Repository boundaries

Concern	Location
React/TypeScript source, npm checks, browser tests	`../ratatoskr-web/`
Backend API and auth	`app/api/`
Local staged SPA output	`app/static/web/` (ignored)
Pinned frontend revision	`ops/docker/ratatoskr-web.commit`
Reviewed release archive	`ops/docker/ratatoskr-web.bundle.tar.gz`
Integration contract	`docs/reference/frontend-web.md`

Do not create or edit a local web/ source tree in this repository.

Frontend checks

Run the client repository's own scripts from its checkout and inspect its package.json before assuming script names:

cd ../ratatoskr-web
npm ci
npm run check:static
npm run test
npm run build

Render and inspect UI changes in that repository. If browser verification cannot run, report the gap explicitly.

Backend integration workflow

Change FastAPI routers/models in this repository.

Regenerate and validate the API contract:

make generate-openapi
make check-openapi-drift
make check-openapi-validate
make check-openapi

Update or regenerate the client in ratatoskr-web.
Run client static checks, tests, build, and browser verification there.
Stage a local build for directly launched FastAPI only when needed:
```
make stage-web WEB_REPO=../ratatoskr-web
```
For a release, update the reviewed revision and rebuild the deterministic archive:
```
make web-bundle WEB_REPO=../ratatoskr-web
```

Docker release images consume the reviewed archive, not whatever happens to be in ignored app/static/web/.

Key files

Integration guide: docs/reference/frontend-web.md
FastAPI app and routers: app/api/main.py, app/api/routers/
Static serving: app/api/main.py (root SPA routes and app/static/web/index.html)
Bundle builder: tools/scripts/build_web_bundle.py
Revision pin: ops/docker/ratatoskr-web.commit
OpenAPI workflow: docs/reference/openapi-contract-workflow.md

Changes to auth, cookies, sync, or streaming contracts must be coordinated with the external client even when no frontend files exist in this repository.