Initial commit: plan, spec, tickets and dashboard skill templates

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.scratch/rpa-dashboard-skills/issues/03-existing-frontend-keep-or-restyle.md

@@ -0,0 +1,15 @@
+# 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:** ready-for-agent
+
+- [ ] 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.