20 lines
1.4 KiB
Markdown
20 lines
1.4 KiB
Markdown
# 03: Existing frontend: report, then keep or restyle
|
|
|
|
Part of: ../spec.md
|
|
|
|
**What to build:** A developer runs the no-AI skill in a web project that already has a frontend with its own colours. Before changing anything, the skill reports where the frontend is, what stack it uses and what colours it uses, then asks: keep the existing look or restyle. "Keep" adds the dashboard page in the existing tokens, fonts and components. "Restyle" asks for a preset or custom colour and swaps only the theme tokens; layout and logic stay untouched.
|
|
|
|
**Blocked by:** 01
|
|
|
|
**Status:** resolved
|
|
|
|
- [ ] Detection covers plain HTML, React/Vue projects and an embedded PyQt web view, and reports location, stack and the main colour tokens.
|
|
- [ ] "Keep": the new dashboard page uses the project's existing tokens and fonts. No existing styles are changed.
|
|
- [ ] "Restyle": only token blocks change. A diff shows no layout or logic edits.
|
|
- [ ] The colour question is skipped when the user keeps the existing look. The stack question is skipped whenever a frontend exists.
|
|
- [ ] Skill eval on test project (c), a web project with an existing frontend and its own colours: the skill reports the frontend correctly. Both branches produce a page that passes the page check.
|
|
|
|
## Comments
|
|
|
|
Resolved on branch `integration/rpa-dashboard-skills` (Oct 16, 2026). Tests: `uv run --with pytest --with playwright pytest tests` all green; skill eval results in `tests/evals/results/`.
|